Date: Tue, 19 Apr 2005 23:30:57 +0100 From: Mark Dixon <mark@markdnet.demon.co.uk> To: freebsd-stable@freebsd.org Subject: Re: Newbie Question About System Update Message-ID: <200504192331.02772.mark@markdnet.demon.co.uk> In-Reply-To: <20050419162546.A83584@denninger.net> References: <426447F8.5090209@charter.net> <200504191402.04374.kstewart@owt.com> <20050419162546.A83584@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart2264939.3dKb74MXiX Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 19 April 2005 22:25, Karl Denninger wrote: > > > > My attitude is that if you don't boot -s, you are simply playing > > Russian-roulette with your system. Some day, it will bite you. > > > > Kent > > Not if your update procedure saves the old kernel. > > Yes, you will have to get there to recover. You have to get there (either > physically or serial console) anyway if it blows up on you. The only problem I can see with this is if one of the more exotic disk=20 controller drivers or file systems drivers goes homicidal (diskicidal?).=20 Booting multi, you will automount all your big disks and arrays giving the= =20 drivers the chance to wreak havoc before you can do much about it. This see= ms=20 pretty unlikely on -STABLE though. You're still in trouble though because=20 you've probably lost / which probably contains the backup of the old kernel. In conclusion, its probably best if disk controller drivers and filesystem= =20 drivers don't have bugs in them. Mark --nextPart2264939.3dKb74MXiX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCZYamLqgJ90OcaiARAnSiAKD+zHpUvt01FHAFd3NYIWuNpxm2OQCgmFz3 FumKm1iTCcUbHx72cJBDLwA= =FeoG -----END PGP SIGNATURE----- --nextPart2264939.3dKb74MXiX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504192331.02772.mark>