On Fri 04 Apr 2003 at 01:15:36, Stuart Jansen said: > Short of upgrading the kernel, it should almost never be necessary to > reboot a linux box, but I did it.
The safest way to upgrade glibc without rebooting the system is to take it down to single-user mode. Every single app loaded into memory is linked to glibc [0], so if there are any hiccups in the upgrade -- and there often are -- you'll start getting major segfaults throughout the system. You wouldn't really think twice about having to re-start a GTK app after upgrading libgtk; the same goes for glibc. Running in single user mode both reduces the number of apps in memory, and when you go back to multiuser it reloads everything but init. I suppose if you needed to reload init, then you'd have to reboot, but this should be necessary only for major revision changes, like glibc 2.X -> 3.X [1]. [0] Is this actually true? Are there any apps *not* linked to glibc? Is it even possible to compile one without linking it to glibc? I guess you could probably write something in assembler that is entirely self-contained. [1] Speaking of which, does anyone remember the a.out -> ELF change? The libc5 -> glibc (aka libc6) change? Ah, those were the days... -- Soren Harward [EMAIL PROTECTED] ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
