Today is a great day to learn about Debian.
It's far from perfect, but by golly once you learn it it's pretty sweet. Highlights:
- Everything is transparent, sometimes painfully so
- Debian isn't a company
- You still have
apt, sodebpackages still probably work - Flatpak makes desktop use easy
- Hate updates? Debian only releases a major new version every two years.
- Nobody is ever, ever, ever going to sell you "Debian Pro"
If Ubuntu's got you down today, I dare you: give Debian a try.
Also, shouting this one with the bold text:
Debian isn't just for servers. Debian rocks on a desktop.
"But Veronica, I need newer packages!"
Do you really? If I'm doing dev work and need something newer, I'm using containers. If I need desktop applications, there's usually Flatpak/AppImage/Nix/source. And backporting and pinning is an option if you want to get super nerdy with it.
I don't like when my desktop updates. It means I have to relearn stuff. If you feel the same way, consider Debian. On your desktop. Seriously.
@veronica so much this, and thank you. as Debian Developer I use unstable as productive system daily, and in 3 years I had only 3 major bugs (2x MESA, 1x kernel). If one can live with that you get get all the newest packages straight from the source. More stable than arch IME.
@Linux
Sudo is enabled if you choose not to set the root password. This requires you to go into expert mode in the installer though, although you don't have to do the full install that way.
What I do:
Run the installer normally
When prompted to enter the root PW, use the 'back' button until you're in the main menu
(1/2)
@veronica
Sudo is enabled if you choose not to set the root password. This requires you to go into expert mode in the installer though, although you don't have to do the full install that way.
What I do:
Run the installer normally
When prompted to enter the root PW, use the 'back' button until you're in the main menu
(1/2)
@veronica
- replies
- 2
- announces
- 0
- likes
- 1
Choose the 'set debconf priority' option
Remember what the priority is set to currently.
Select 'low'. Congratulations, you're now in expert mode
Choose the 'set users and passwords' option.
You will now see a question whether you want to set a root PW. Choose not to.
Finish the 'set users and passwords' menu item
Go back to the 'set debconf priority' option.
Set the priority back to what it was.
You're not in expert mode anymore.
(2/2)
@veronica @Linux
Remember what the priority is set to currently.
Select 'low'. Congratulations, you're now in expert mode
Choose the 'set users and passwords' option.
You will now see a question whether you want to set a root PW. Choose not to.
Finish the 'set users and passwords' menu item
Go back to the 'set debconf priority' option.
Set the priority back to what it was.
You're not in expert mode anymore.
(2/2)
@veronica @Linux
@nazokiyoubinbou
You can run systemd without systemd-resolved. I have done so ~forever.
The idea is that it makes certain things easier (e.g., having different DNS configs for different network interfaces), but the systemd developers know and understand that it isn't a valid thing everywhere.
@waldi @veronica
You can run systemd without systemd-resolved. I have done so ~forever.
The idea is that it makes certain things easier (e.g., having different DNS configs for different network interfaces), but the systemd developers know and understand that it isn't a valid thing everywhere.
@waldi @veronica
@nazokiyoubinbou
No.
I don't subscribe to the idea that there is anything 'in' or 'out' of scope for anyone. You want to write something, and people want to use it? Great. Do that. We already have a scarcity of maintainers, let's not make it worse.
As long as the not-init-system parts can be disabled (and they can be), I see no problem with systemd providing a whole bunch of extra tools that work well with the rest of the system.
@waldi @veronica
No.
I don't subscribe to the idea that there is anything 'in' or 'out' of scope for anyone. You want to write something, and people want to use it? Great. Do that. We already have a scarcity of maintainers, let's not make it worse.
As long as the not-init-system parts can be disabled (and they can be), I see no problem with systemd providing a whole bunch of extra tools that work well with the rest of the system.
@waldi @veronica
@nazokiyoubinbou
I agree there's scope for tools that run on your system. That scope can be achieved if you make things optional.
I don't agree there's scope in what a developer is or isn't allowed to develop. You're not anyone's boss.
As for opt out, you forget that distributions have a faaaar larger influence on what happens to be installed on your system by default then whatever the upstream developers decide to put out there.
@waldi @veronica
I agree there's scope for tools that run on your system. That scope can be achieved if you make things optional.
I don't agree there's scope in what a developer is or isn't allowed to develop. You're not anyone's boss.
As for opt out, you forget that distributions have a faaaar larger influence on what happens to be installed on your system by default then whatever the upstream developers decide to put out there.
@waldi @veronica