Re: [cobalt-security] Glibc Security Update 2.0.1

[Bruce Timberlake <bruce@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri April 25 2003 08:58, Robbert Hamburg \(HaVa Web- & Procesdesign\) 
wrote:
> > If you install the PKGs from the command line the reboot won't happen.
> > Alternatively, on the RaQ 4 anyway, you can choose to say "No" when it
> > prompts you to reboot after installation.  The 550 forces you to make
> > the choice before installation, and if you choose "no" it doesn't do
> > the install.  The commandline option is the only alternative for that.
>
> Am i correct with my assumption that you mean that installing from the
> prompt doesnt require a reboot at all ???

Correct.  It ignores the "reboot required" specification... (either 
automatically or via command-line switch; depends on the exact server 
model you're doing this on).

> Or do you mean reboot after finishing all the installs ??

Yes, do the command-line installs of all PKGs, then issue a "reboot" 
command.

All this is, of course, subject to the caveats Eddy mentioned about 
dynamically linked dependent programs using glibc, etc.  If you left the 
system up and running for a long period of time, I think you'd be more 
likely to see problems.  But once the major processes are already loaded 
and operating, it is my understanding that they have loaded a "snapshot" 
of the glibc bits they are dependent upon, and won't try to reread things 
from the (now changed) disk version.  Only if you loaded a new program, or 
shut down and restarted an existing daemon, for example, would the version 
conflict come into play.

I have done the multiple PKG install, then a reboot, many many times on 
operating RaQs and have yet to suffer any problems.  Doesn't mean it can't 
happen, but I haven't personally experienced it.

- -- 
Bruce Timberlake

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+qWyCvLA2hUZ9kgwRAohxAJ4oX2Pi/Qk70ipDk/I+3YmWb8PnGACfUFIN
3169X7KyqUixT5ZEG2QGwGQ=
=ZuPb
-----END PGP SIGNATURE-----