-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 02 December 2002 12:55, Richi Plana wrote:
> Mark Lane wrote:
> > There's an easier way than using up2date. We have a script that will
> > list which updates apply for your architecture. That list can be used
> > as an argument to rpm -Fvh and all updates will be installed. To
> > automatic this you could just use a cronjob.
>
> Unassisted updates certainly are cool and thorough, but I should caution
> you as some users might leave their workstations in a state where an
> update could result in loss of data.
such as? no update should result in a reboot, no update should over-write
user-modifi[ed | able] files, no update should kill running processes, and
any services that get restarted should do so gracefully (e.g. continue
handling current connections) ... any violations of those principles should
be considered bugs... have you run across any such situations??
> There is a point to the
> Microsoft-world advice to "close all applications" before performing an
> upgrade.
yes, the point is that their OS sucks.
did you know you STILL can't just move files around at will even on XP? "This
file is in use" ... stupid stupid stupid. someone should tell MS engineers
about file handles and the beauty of keeping apps the fuck out of the file
system. i had a very frustrating episode on the west coast because of this
particular stupidity. BLARG!
- --
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
"Everything should be made as simple as possible, but not simpler"
- Albert Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE968l41rcusafx20MRAufiAKCq47Tqk1j4CvtpcKrNljotbj1jkgCgi4u4
h9gL794J644zNbjXJBvwRE8=
=s38G
-----END PGP SIGNATURE-----
