Posts by jimsalter@fosstodon.org
 (DIR) Post #B5iuvEWjoLM7M1r2lk by jimsalter@fosstodon.org
       1 likes, 0 repeats
       
       Installed Ubuntu 26.04 for the first time. Logged into a TTY.me@box:~$ sudo-sPassword: ********************EXCUSE ME--ASTERISKS? WTF?Look, obviously I appreciate that seeing the character count as you type makes it easier. But this is supposed to be suitable for high security environments. And making it easy to see the character count is a significant entropy leak. This should not be the default configuration, particularly in Ubuntu *server* (which is what I installed). DISAPPROVE.
       
 (DIR) Post #B6lnSdQqXo3n9lf1yi by jimsalter@fosstodon.org
       0 likes, 0 repeats
       
       This is what it looks like when Gnome3 (under Ubuntu 26.04) shits the bed and unlocks the secondary display while leaving the primary display locked.Yes, really. No, power cycling the display didn't change anything. And I had to invoke Firefox from the CLI after using ctrl-alt-T to spawn a new terminal, so I could look up the command to log off the desktop from the terminal, BECAUSE THE PRIMARY DISPLAY IS WHERE THE MENUS LIVE.The command is gnome-session-quit, btw.
       
 (DIR) Post #B6lnxvkQUqR6wHk3pw by jimsalter@fosstodon.org
       0 likes, 0 repeats
       
       @astraleureka Wayland.
       
 (DIR) Post #B6nAhHrDX5rWgvuY1g by jimsalter@fosstodon.org
       1 likes, 0 repeats
       
       Fuck systemd. Seriously. FUCK THAT SHIT. I am so goddamn tired of it getting its nasty, poorly-coded, bug-ridden fingers into EVERYTHING like some kind of goddamn Microsoft library would.I can't use the shutdown command anymore, because systemd says "but you have a terminal open! In your own UID! that you're issuing the shutdown command from!" and prevents it from happening.So I have to instead systemctl reboot -f. And the -f is REQUIRED because see above, re my own TTY.IT GETS WORSE.
       
 (DIR) Post #B6nAhI8wTC2ZZuChea by jimsalter@fosstodon.org
       0 likes, 1 repeats
       
       I needed to reboot a client server, which normally I would do with at 1800 shutdown -r now. But I can't do that anymore, and I can never remember the arguments for systemctl, so I look them up.OH HEY, how convenient, there's a "when" option. No need to faff about with at anymore! Just do --when=+220min, as documented at https://linuxcommandlibrary.com/man/systemctl-reboot !
       
 (DIR) Post #B6nAhIN7cTNoHsq1ku by jimsalter@fosstodon.org
       0 likes, 0 repeats
       
       Except like the Windows "settings" app and about a quarter of systemd bullshit, systemctl reboot was clearly designed in the biggest hurry possible by somebody with all the system administration and quality assurance chops of a drunken crocodile.root@[elided]-prod0:/etc/netdata# systemctl reboot -f --when=+220minRead from remote host [elided]-prod0.wg: Connection reset by peerConnection to [elided]-prod0.wg closed.client_loop: send disconnect: Broken pipeI repeat: FUCK systemd.