And I don’t care, so whatever

I mean, you should be careful with destructive changes and commands whether the interface names can change or not… And since they won’t change outside of a reboot, I’ve yet to run into a scenario where that becomes a problem as I’m looking at and making sure I’m talking to the correct device before starting anyway

You know Linux isn’t just used by enterprise sysadmins, right?

And even speaking as an enterprise sysadmin myself, I’ve not had need or use for deterministic interface naming once in my career. I have no clue how common that is, but most of the servers, both physical and virtual, that I’ve worked on only had one Ethernet port connected.

I see the purpose of this, but don’t see a reason why it should be the default, or why it couldn’t have been implemented like HHD/SSD UUIDs where the old dev names were left intact for easy use outside of fstab and the like where consistency could become a problem

ETA: you also seemed to miss the part of my initial reply to you about it being something that can be enabled by those who need it… And if you’re going to say that the enterprise professionals who need it shouldn’t have to turn it on every time they spin up a system, I’ll remind you that enterprise admins working at that level where they’re setting up enough servers for that to be a hassle are probably using orchestration like Ansible, Chef, or Puppet, and can just add that into their configs once

Considering how much systemd breaks the concept of “everything is a file”, this would not surprise me in the least

But the SSD/HDD solution doesn’t replace /dev/[s|h]da# entirely, just adds a consistent way to set them in configs like fstab. You can still use the old device names so working with them at the command line is still easy for the most part.

Yes, because everyone has need of this solution, and wants to have to copy and paste interface names every time they need to touch them, rather than having deterministic naming be an option to enable for those who actually need it…

Couldn’t they be configured to always set each interface to a particular name? I’d think that would be the better solution anyway…

Microsoft at least isn’t trying to be a walked garden (at least, they didn’t used to)

It’s not much, but the bar to be “better than Apple” from that perspective ain’t exactly high

(Also, since they didn’t mention Microsoft at all or make some statement about how Apple was the worst, I don’t see how it even implies that… If you inferred that, I think that’s on you)

Pretty sure it’s just about the shared name

Since my other systems were unaffected, I’m pretty sure it’s something on my PC, possibly an update for the Wi-Fi drivers introduced a bug that affects the 5.8 channels

It’s been stable since switching so it’s more academic at this point, I have no burning need to be connected to the 5ghz channels

It seems to be an issue with using a 5.8 gigahertz WiFi endpoint, which has worked fine up until a couple days ago when it started dropping packets going outside my local network: I could watch a continuous ping start failing for a couple minutes while using Synergy to control my laptop that was connected to my work VPN without issue, so it only seemed to be an issue routing outside my network, which is really weird. Switching to the 2.4 gigahertz channels seems to have fixed it entirely.

What I need to do is look up the JournalD commands to be able to read the logs correctly and find what I’m after… Might also spin up a VM to see if that goes out at the same time, would be interesting if the VM can still work while the host is dropping packets…

Honestly, the only reason I’m not using a non-SystemD distro is this is my first time actually going all in and having larger communities to help with issues plus just trying to force myself to learn it since it seems like it’s not going away

But yeah, I’m not a fan.

Working through a networking issue right now and the layers of obfuscation SystemD adds, especially with JournalD, leaves me not really sure where to even look

It is tempting to say screw it and load up Gentoo on my desktop though

Because SystemD must do all and will not rest until GNU/Linux becomes SystemD/Linux

Krita is better for some things but I find Gimp’s workflow easier for me in a lot of things

Krita’s Wacom tablet support, though, was way smoother and easier to get working with Krita, which is the main reason I even tried it out

I don’t know much of anything about Anycubic, but isn’t pretty much everything Creality releases open? How are they withholding from the community?

I can screenshot too

Note where you said “only ever tried Gimp”, when they said they have, in fact, used Photoshop. Additionally, nowhere in that did they say they’ve not used anything else since then even, just not Photoshop.

But you think you’ve made some credible point here, and likely won’t back down no matter how wrong you are, so go ahead and respond telling me some twisted logic about why you’re right and I’m wrong and I can ignore it so you can walk away thinking you’ve won some useless internet points.

Same… I think Photoshop would probably feel difficult to me to get my head around at this point since Gimp’s workflow is the one I’ve known and used for over a decade and a half now

I mean, even if that was what they said, that would make it and things that function like it more intuitive to them, wouldn’t it? And someone who’s used to a different workflow would find it unintuitive.

So yeah… Intuitive is relative

The problem with that, though, is if they changed the workflow to be like Photoshop, it would leave those of us who know how to use Gimp but not Photoshop high and dry

Gimp is intuitive to me at this point because I have some idea of how it looks at raster image manipulation from using it off and on for years. I have no clue how to do things in Photoshop that I can do easily in Gimp. It may be the better user experience, I don’t know.

If they ever do that, I really hope they leave the option for it to work like classic Gimp in there, because people like me don’t actually do image editing that much overall and relearning would be painful for much longer than someone who can deep immerse themselves until they get it. I’d hate to do it but I think I’d have to stick with an old version if that happened without any way to keep doing things the same way

I’ve frequently seen Windows ignore that setting and force the restart while the system is actively being used

The mega corp neither needs or deserves your defense. They’ve fucked up the update system with Windows 10 and it’s not gotten any better since then.