Hacker News new | past | comments | ask | show | jobs | submit login

I reboot once a month, so that it reboots at all.

Despite using Arch Linux, and weekly "upgrade everything".

I know it isn't everyone's experience, but I was exceedingly choosey about the hardware that went into my machine, so that I could do this.

The only problem I've had in the last two years, was an incompatibility between ocaml and fish shell, which eliminated my PATH. Unfortunate, but an issue on the ocaml side of things. A big problem, for certain, but two years of bleeding edge updates, and that's it.




Mostly the same experience, running Debian Unstable on my X201. Keeping a simple environment (AwesomeWM and urxvt, rather than Gnome or KDE; dhcpcd, rather than NetworkManager) probably helps. I put it to sleep every day, often multiple times, and it never fails to come up, connect to Wifi, etc.


If you upgrade Arch without rebooting, don't you get messed up by losing unloaded kernel modules (because Arch doesn't keep old kernels)?


Hasn't been an issue yet.

But it ever does, I'll probably adopt and adapt one of the solutions from this thread [0].

[0] https://www.reddit.com/r/archlinux/comments/4zrsc3/keep_your...


Oh, excellent; thank you. I mentioned it because this has bitten me, so I'll want to use that fix.

Fun story: for $REASONS, I have an Arch system with root on btrfs and /boot on ext4, and it doesn't usually have the boot partition mounted (it's a poorly done mutiboot issue). I recently discovered that this means if I forget to mount boot before updating I get stuck with no loaded drivers to mount /boot :) Thankfully kexec worked, but I'd like to not need to do that:)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: