The Linux Thread - The Autist's OS of Choice

[俺たちファームズでノッテる]

One way around this used to be to chain from the windows bootloader to grub, so windows wouldn't get snippy at you. I had a machine set up like that for a long time, until I realised I wasn't ever booting into the windows partition and decided to just nuke the whole thing.

Technically speaking windows devs competence is the reason why it doesn't work well with dual booting. However I personally think that it's purposely made bad so that people aren't encouraged to dual boot into Linux.

View attachment 7678515
I don't get people's obsession with keeping their PC's up and running all the time. It's not a router, and even then I reboot mine every 1-2 months whenever a firmware update rolls out. Besides, modern boot times, even on bloated shitheaps like Windows, are nothing when you have NVMe SSD's. My smartphone takes longer to reboot than my PC.

I'm on a Arch based system, So I'm constantly updating my Laptop. However I'm not keeping my system up constantly to prove a point. The longest I've ever left my laptop on with Linux was 14 hours.
Even though nothing happened I was still freaked out a bit. I just don't think personal systems (unless for sever use) shouldn't be on for any longer than you use it.

 

[Slav Power]

I just don't think personal systems (unless for sever use) shouldn't be on for any longer than you use it.

I think that it doesn't matter all that much. If your PC is doing some low priority background work like seeding torrents then it won't hurt for it to be on for a few days straight or off for a few hours. The only real concern with power cycling can be hard drive longevity if you haven't built a NAS yet, but even then consumer drives, and basically all drives for that matter, are designed with power cycling in mind. Even in a NAS or a CCTV system with NAS/CCTV grade HDD's you can have a power outage, and then what?

Besides, there's always one crucial issue with uptime fanatics. Even though Linux's file systems allow you to update your OS while it's running, it doesn't mean you don't have to reboot since you'll still be running outdated code in the memory with all the potential exploits any recent security updates you've installed were meant to patch. So it's a wise idea to not only reboot your servers every so often after doing an update, you should be rebooting your desktop PC as well to give it that refresh. Also to avoid the occasional runtime bugs where TIOAOA solves the issue, and you know damn well these like to happen.

 

[Betonhaus]

Is there a way for Linux to tell RGB devices to go to sleep mode without actually going into sleep mode? My computer often hangs when it goes to sleep mode and I don't realize until I notice the fans still going or try to use it.

 

[prollyanotherlurker]

How often do you people boot?
20:06:18 up 147 days, 12:51, 1 user, load average: 0.14, 0.13, 0.09
And that was just because the UPS died and I had to replace it.

Pretty often. Depends what I'm doing. But I have 2 systems I use. So I reboot from one, and go into the other.

Or on updates, I reboot no matter what. At least if it was anything semi important that was updated. You will get some potential issues if you don't reboot. Or at the very least you are going to need to manually restart things. And it's easier to reboot.

Either way. I generally like to have nice performance where I can get it in my computer. The boot time being lower is just a nice bonus.

 

[Trans Fat 41g]

I reboot after updates, suspend when I'm away for an hour or two, turn off if I'm away all day. The last is precautionary in the event of an outage.