Date: Wed, 05 Mar 2003 13:40:50 -0600 From: Kirk Strauser <kirk@strauser.com> To: freebsd-questions@freebsd.org Subject: Major upgrades and vinum (was Re: Make installworld problem (4.7)) Message-ID: <87llztppod.fsf_-_@strauser.com> In-Reply-To: <15974.15390.589544.775805@guru.mired.org> (Mike Meyer's message of "Wed, 5 Mar 2003 12:04:14 -0600") References: <5.2.0.9.2.20030305083743.00bcfc80@mail.servplex.com> <3E4A973500003B77@cpfe6.be.tisc.dk> <5.2.0.9.2.20030305114541.00bd5cb8@mail.servplex.com> <15974.15390.589544.775805@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Transfer-Encoding: quoted-printable At 2003-03-05T18:04:14Z, Mike Meyer <mwm-dated-1047319455.6dc16a@mired.org>= writes: > Since kernels have to support old binaries, but not vice versa, you can > usually reboot with the new kernel and old world and have it work. Sometimes, though you can't. I've found myself in the situation where the old version of vinum(8) wouldn't run against the new kernel, further complicated by the fact that the new vinum was in /usr/obj, which is on a vinum volume. This hasn't been a problem in well over a year, but it bit me hard once. Is there an officially-supported guaranteed-to-work method for handling this? I've been doing: make buildworld cp /usr/obj/usr/src/sbin/vinum/vinum /sbin/vinum.new ... just in case. Is this still a necessary step? =2D-=20 Kirk Strauser In Googlis non est, ergo non est. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+ZlLC5sRg+Y0CpvERAmt6AJ9xNOg34xy/wCXzR1xQHVqkErG/tgCdG/Lv zj2wHk4SUZmCLuEX2X60gSk= =FE/V -----END PGP SIGNATURE----- --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87llztppod.fsf_-_>