![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://linux.community/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2F4271bdc6-5114-4749-a5a9-afbc82a99c78.png)
Considering how much systemd breaks the concept of “everything is a file”, this would not surprise me in the least
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…
And exactly where do you propose they talk about it and actually have people see it?
I’m pretty sure their ad revenue from their own pages is a tiny fraction of their overall advertising revenue… They basically own the advertising market online, almost anywhere you see ads googie is getting a cut
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)
When I rebuilt mine a few months back, I got two drives so I could put windows on one of them, and mounted my old drives for the same reason… I’ve barely touched the old data and the second SSD has not even been formatted yet, and when I do it’ll probably be to give my current system more space
Depending on use case, virtualization can actually be way easier
Give it a go, it was surprisingly not as big an issue as I thought it would be, even for gaming (though not perfect for gaming, I’ve been able to get things working without too much headache at least)
So you want to throw a brick through OneDrive’s Windows?
Oh, that’s okay though, you signed them the rights to do that by having an account with them
… I’m sure is how they’ll spin it
I’m seeing that a hell of a lot this year… Linux might actually finally make some real headwind with the tech crowd
Does that make it better?
Thank you for providing the good reasons for it, it makes much more sense now
The accounts started out optional with benefits to entice
They’re now mandatory for Home and hard to bypass
How long before they extend this to Pro and Enterprise? To Server? To Active Directory itself?
They’re not done yet, not by a long shot.
Tesla isn’t a car… It’s an EXPERIENCE!!!
(/s just in case it isn’t obvious enough)
It’s worse than that: it requires the old school lead acid 12v battery to be charged, so even if the car’s battery is full, it doesn’t matter if that old car battery has failed
That’s not unique to Tesla EVs, but it being required to open the doors may be (the 12v lead acid runs the general vehicle electronics rather than down converting the 400v or 800v main battery… I don’t understand that decision, but I’m no electronics expert so there may be really good reasons for it…)
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