The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Today's Linux enjoyment.
Consistent network device naming.
In the beginning there was "eth0" "eth1" and it usually worked but sometimes switched names depending on discovery order.

I'm setting up my file server, array controller not installed yet. All good. Installed array controller. Can't ssh in. Luckily it has IPMI/IP-KVM. Login, see no IP address assigned. Check cable, etc. all good. Finally check the config. I'm glad Debian still allows /etc/network/interfaces if you don't install NetworkManager but this one time it didn't work right(besides all the other times it didn't work right...). On install the eth device was enp9s0. After adding the array controller it's now enp10s0, and /etc/network/interfaces uses actual names and won't follow device changes like NetworkMangler.

Consistent names, my ass.
If I add a non-network-card then the device names shouldn't change. Better yet they should map to the physical slot they're plugged into not whatever this shit is. The funny thing is this is how it should work according to the docs, but doesn't.
 
DavidS877 said:
Today's Linux enjoyment.
Consistent network device naming.
In the beginning there was "eth0" "eth1" and it usually worked but sometimes switched names depending on discovery order.

I'm setting up my file server, array controller not installed yet. All good. Installed array controller. Can't ssh in. Luckily it has IPMI/IP-KVM. Login, see no IP address assigned. Check cable, etc. all good. Finally check the config. I'm glad Debian still allows /etc/network/interfaces if you don't install NetworkManager but this one time it didn't work right(besides all the other times it didn't work right...). On install the eth device was enp9s0. After adding the array controller it's now enp10s0, and /etc/network/interfaces uses actual names and won't follow device changes like NetworkMangler.

Consistent names, my ass.
If I add a non-network-card then the device names shouldn't change. Better yet they should map to the physical slot they're plugged into not whatever this shit is. The funny thing is this is how it should work according to the docs, but doesn't.
Click to expand...
Oh yeah I hate that. When you add another network card it changes the names on next reboot, and they don't go back. I suspect you could temporarily brick any Debian/Ubuntu server by plugging in a usb ethernet nic and rebooting it.
 
Betonhaus said:
Oh yeah I hate that. When you add another network card it changes the names on next reboot, and they don't go back. I suspect you could temporarily brick any Debian/Ubuntu server by plugging in a usb ethernet nic and rebooting it.
Click to expand...
The one good thing is that doesn't work. USB devices get MAC address based names
enx3213f0f900d2 for instance.
You might ask why my file server also thinks it has a USB based network device... I have no fucking idea and haven't looked yet.
 
Legalize Asbestos said:
What the fuck does that even mean?
Click to expand...
Let's assume I'm an Android dev making an app called Shitpostr, it costs $2.99

Let's assume this app is very useful for shitting on the streets. It's so useful that Indians keep googling it. Now they're being led to sites where you can sideload pirated Shitpostr for free. But now, that's not my signed version, and it's been changed, and then Indians are leaving bad reviews after uncle and auntie were led to the train tracks and mowed over.

This is the point of Google Play verification.
 
DavidS877 said:
Today's Linux enjoyment.
Consistent network device naming.
In the beginning there was "eth0" "eth1" and it usually worked but sometimes switched names depending on discovery order.

I'm setting up my file server, array controller not installed yet. All good. Installed array controller. Can't ssh in. Luckily it has IPMI/IP-KVM. Login, see no IP address assigned. Check cable, etc. all good. Finally check the config. I'm glad Debian still allows /etc/network/interfaces if you don't install NetworkManager but this one time it didn't work right(besides all the other times it didn't work right...). On install the eth device was enp9s0. After adding the array controller it's now enp10s0, and /etc/network/interfaces uses actual names and won't follow device changes like NetworkMangler.

Consistent names, my ass.
If I add a non-network-card then the device names shouldn't change. Better yet they should map to the physical slot they're plugged into not whatever this shit is. The funny thing is this is how it should work according to the docs, but doesn't.
Click to expand...
This is not a Linux problem, but a systemd one, after systemd was allowed to maliciously embrace and extend udev.

enp[x]s[y] names are supposed to be named based on x: PCI bus y: slot.

You have a couple different solutions.
1) You should be able to boot the kernel with the parameter:
net.ifnames=0

That will return to standard, human, eth0, wlan0 type names.
2) You can also do some gay shit where you map a interface from a MAC address to an arbitrary name based on UDEV rules, but that is gay and dumb. Just use trad names.

Death to Lennart Poettring.
 
DavidS877 said:
Today's Linux enjoyment.
Consistent network device naming.
In the beginning there was "eth0" "eth1" and it usually worked but sometimes switched names depending on discovery order.

I'm setting up my file server, array controller not installed yet. All good. Installed array controller. Can't ssh in. Luckily it has IPMI/IP-KVM. Login, see no IP address assigned. Check cable, etc. all good. Finally check the config. I'm glad Debian still allows /etc/network/interfaces if you don't install NetworkManager but this one time it didn't work right(besides all the other times it didn't work right...). On install the eth device was enp9s0. After adding the array controller it's now enp10s0, and /etc/network/interfaces uses actual names and won't follow device changes like NetworkMangler.

Consistent names, my ass.
If I add a non-network-card then the device names shouldn't change. Better yet they should map to the physical slot they're plugged into not whatever this shit is. The funny thing is this is how it should work according to the docs, but doesn't.
Click to expand...
I had a similar issue a few weeks back. Added a pcie card with 4 nvme slots to my server. The network enp number would switch around occasionally on a reboot. Was pulling my hair out trying to figure out why a pcie card would kill my network and found a 10 year old forum post mentioning it. Ended up just setting both of the enp numbers that it was grabbing to the same static address since I just have a single NIC.
 
For getting around ethernet name madness, I just setup a udev rule under /etc/udev/rules.d/99-my-ethernet-names.rules:
Code: 
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="50:7c:6f:XX:XX:XX", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="ethagg0"
You can name it whatever you like, you just need to make sure the MAC address match. I don't nearly have enough ethernet cards to have MAC addresses clashing.
 
prollyanotherlurker said:
I for one welcome our systemd overlords. And would like to remind them I as a linux sperg I can be helpful in rounding up the nonbelievers to forcibly wipe their heretical non-systemd distros to install fedora.
Click to expand...
We love the leader!
 
Get Phobo said:
What would you need CUDA for in gaming?
Click to expand...

CUDA is hella overused by NVIDIA for various features going by various different names. NVDEC was originally called CUVID, and it uses CUDA under the hood to offload the decoding of FMVs. Then there's GPU-accelerated PhysX, which was used to make [toilet]paper and other small environmental objects move more realistically in games like Batman: Arkham Asylum. There's also each incarnation of DLSS for upscaling assets in games, as well as other frame generation technologies. When you run games in Proton, fire up a terminal and run nvidia-smi and look for which processes have G, which ones have C and which ones have C+G. Anything with C+G is a graphical process which is also taking advantage of compute (which is diverted through CUDA) somewhere or somehow, even if it isn't being used in that moment.

The Saltening said:
How do you think antifa being a terrorist organization will effect linux? And I guess open source in general considering all the trannies in open source.
Click to expand...

With that, one man's terrorist is another man's freedom fighter takes on a whole other meaning!

In practical terms, nothing will change. Bullshit rhetoric is bullshit rhetoric, no matter where it comes from, and corporations will [ab]use anyone as long as the normies turn a blind eye to it.
 
Okay, but how does it affect performance compared to Windows? I've heard that some games on AMD run better on Linux than Windows, but I haven't heard of any that would do on NVidia, because NVidida on Linux always runs worse.
 
Get Phobo said:
Okay, but how does it affect performance compared to Windows? I've heard that some games on AMD run better on Linux than Windows, but I haven't heard of any that would do on NVidia, because NVidida on Linux always runs worse.
Click to expand...
Gaming on Linux is a mixed bag, some games will run better, some games will run worse. NVIDIA usually has a ~13% drop from windows, AMD is far closer to being equal to running it on windows, with the exception of directx 12, where both NVIDIA and AMD suffer a 10% drop, and raytracing, where AMD suffer a big drop on Linux.
 
Get Phobo said:
Okay, but how does it affect performance compared to Windows? I've heard that some games on AMD run better on Linux than Windows, but I haven't heard of any that would do on NVidia, because NVidida on Linux always runs worse.
Click to expand...
I have all AMD hardware and I have not noticed any differences really. Every game I play seems to just run as good if not slightly better (especially load times). I know some people have real aids performance depending on their distro. I just use mint and everything works out of the box gaming wise.
 
Lonjil said:
I know some people have real aids performance depending on their distro. I just use mint and everything works out of the box gaming wise.
Click to expand...
My Ryzen 5700G just works, and it just works great. Debian, Arch, Gentoo, Artix. All X11, Org and Libre. I have a Intel 6xxx something laptop and the integrated on that works great too, no hassles. My old Skylake's integrated worked for everything I wanted back in the day. The 5700G handled 1080p Death Stranding decently with their downsampling nonsense.
 
teriyakiburns said:
Your link is busted.
Click to expand...
Sorry, edit limit passed. This is a collection proxy/vpn client for china for android/chinese android based OSes. This one's made by an uwu anime troon but my point still stands (the original toolset creator was widely believed to have gotten a free tea party)
glow.webp
 
To be honest I feel like this thread is one of few places where using X11 instead of Wayland isn't a crime and suggesting XLibre as a proper X11 successor doesn't make you literally Hitler.

As for my distro, I use Debian with LXQt Xorg desktop and might either stay there or make my switch to Devuan as systemd is a ticking time bomb of an init.
Which alternate init would you recommend to a relative beginner in serious Linux stuff?
 
You must log in or register to reply here.
Back
Top Bottom