Windows is doing stuff behind that splash screen too though
And arch does the exact same thing as Ubuntu :/ not sure what they are trying to say with this one.
Yeah idk, many distros show the classic startup/shutdow process
Mine just kills the power. Faster than manually unplugging the pc
Did you configure it that way? I’m fairly sure the default is to safely shutdown via systemd. How do disk caches get flushed, are you setup to never cache in memory, or do you just lose data?
I don’t know what I did but it does that anyway, and I think it’s cool. I like to use my pc in the very very not recommended way so I’m not 100% sure if it’s normal behavior, but it did that on multiple installs so it probably is
It’s not. A normal Arch install shuts down the exact same way as Ubuntu.
Chaotic mofo 😂
It is. Just never says what’s hung.
Frankly It’s more like
Windows - “shut down please. No it’s fine, I’ll wait. Indefinately is fine”
Linux “ shut down please. You have 30 seconds or I’ll shut you down myself”
If my pc doesn’t shut down when I click on the shutdown button, I just pull it out of the wall or switch off the psu depending on my mood. At this point I think it’s just affraid of me
You’re forgetting the 10 minutes of mandatory Windows updates.
Only ten??
I remember going from MS-DOS to Windows and being really annoyed that I couldn’t see the loading log.
Same with Android phones in the beginning when they were still the scrappy underdog. I wanted to see machinery at work!
I would rather watch console output I don’t understand scrolling by too fast to read than some dumb spinning dots >:[
A stop job is running for Simple Desktop Display ManagerI think you can configure systemd to force shutdown such things in like 2 seconds which is the only way I can shut down my Thinkpad running Debian 12.
Wait you guys don’t
sudo echo o > /proc/sysrq-trigger?I think you’d have to do
echo o | sudo tee /proc/sysrq-trigger, otherwise sudo only works for the echo, not the write.Holy shit the reason for
teenever really clicked until I saw this post. I’d used it in pasted commands, but it had always seemed superfluous.What does
teedo?It writes to a file like
, and echos it back at the same time; in this case the latter isn’t needed (we’re just using it to write with sudo), but it’s good to know.
echo c | sudo tee /proc/sysrq-trigger🫣Ah I guess I just use sudo bash a lot 😅
deleted by creator
button?
I don’t get it, shutting down looks like the Ubuntu one to me.
There’s a kernel option to disable the text and it’s on by default on Arch, but not on Ubuntu.
Edit: It seems that the kernel parameter is not on by default. I’ve always used GRUB and the text hasn’t appeared for me until I’ve removed the quiet option in the GRUB config file so I thought it was on by default. It might be on by default with GRUB or I’m remembering wrong.
I’m not sure that’s right. I just installed arch a few days ago, and I see that text during startup and shutdown. I didn’t change any kernel options. Also, I’ve never seen that stuff with ubuntu, just a big ubuntu logo.
it’s on by default on Arch
I don’t think there is a default in Arch. You have to choose your own bootloader, and the documentation just lays out the options on what kernel parameters to pass. For systemd-boot, the Arch documentation gives example configurations that don’t include the “quiet” parameter.
It’s not on by default.
I get stuck on a black screen about every 10 or so reboots/shutdowns
