Post A8FsfQimRcmsY2tpMu by mithrandir@pl.wizards.zone
 (DIR) More posts by mithrandir@pl.wizards.zone
 (DIR) Post #A8FsfQF0EKy53gy2xE by nytpu@tilde.zone
       2021-06-13T21:07:24Z
       
       0 likes, 0 repeats
       
       Everyone always says that you don't need to restart after upgrading arch/arch-derivatives except for the implied-rare case of kernel updates, but for me seems like every single time I upgrade the kernel has an upgrade and I have to restart if I don't want issues (particularly loopback issues for tombs I'm using). Maybe if I used linux-lts it'd be different.
       
 (DIR) Post #A8FsfQimRcmsY2tpMu by mithrandir@pl.wizards.zone
       2021-06-13T21:12:48.257458Z
       
       0 likes, 0 repeats
       
       @nytpu I don't usually have problems with upgrading the kernel, or much of anything really.The most typical reason to restart is because a library gets updated but an AUR package is out of date and references an old one
       
 (DIR) Post #A8FwthKvriiFwzntI0 by crlf@raru.re
       2021-06-13T21:58:46Z
       
       1 likes, 0 repeats
       
       @mithrandir @nytpu The biggest thing that happens for me right after a kernel upgrade is I can't mount filesystems until a reboot. Existing mounts continue to work, so it's only an issue if I need to hit a usb drive or the nfs.I always assumed that was typical. Do you just not mount drives often?
       
 (DIR) Post #A8Fwv5bZ7d7LVUFO9g by mithrandir@pl.wizards.zone
       2021-06-13T22:00:27.458557Z
       
       0 likes, 0 repeats
       
       @crlf @nytpu no that happens to me too, I just don't mount drives often