Date: Wed, 5 Mar 2003 00:06:00 +0200 From: Ruslan Ermilov <ru@freebsd.org> To: src-committers@freebsd.org, cvs-src@freebsd.org Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern kern_linker.c src/sys/boot/common help.common loader.8 module.c Message-ID: <20030304220600.GB73366@sunbay.com> In-Reply-To: <20030304174544.GB40822@dragon.nuxi.com> References: <200303032253.h23MrZ4F038178@repoman.freebsd.org> <20030304005242.GA38799@dragon.nuxi.com> <20030304092528.GA76504@sunbay.com> <20030304174544.GB40822@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--/WwmFnJnmDyWGHa4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 04, 2003 at 09:45:44AM -0800, David O'Brien wrote: > On Tue, Mar 04, 2003 at 11:25:28AM +0200, Ruslan Ermilov wrote: > > > Please back this out until the 5-STABLE branch; then reapply for > > > 6-CURRENT. When I did the change to /boot, those of us behind it at = BSDi > > > intended for /modules to remain as a transition aid. > > >=20 > > As I said (and many others have mentioned), having /modules > > by default can only cause a panic -- 4.x modules would kill > > 5.0. Those who want it, can easily edit /boot/loader.conf. >=20 > rm'ing /boot can also cause big problems. Why would a base module in > /modules be used before /boot/modules? If someone only installs a > kernel, then it is expected they know what hey are doing. >=20 >=20 > > Also, when you request a backout, would you please explain > > why it should be done, in more details. What is good for > > having /modules in by default in 5.x? >=20 > What more do you want??? >=20 > 1. It was left by design [by me]. >=20 Huh? RCS file: /home/ncvs/src/etc/mtree/BSD.root.dist,v Working file: BSD.root.dist head: 1.60 branch: locks: strict access list: keyword substitution: kv total revisions: 76; selected revisions: 1 description: ---------------------------- revision 1.46 date: 2000/09/06 10:27:26; author: obrien; state: Exp; lines: +3 -3 The default is for 3rd party kernel modules to live in /boot/modules rather than /modules. > 2. 4.x->5.x transition aid. >=20 Aid? :-) Loading 4.x modules kills 5.x. > > If you so demand on it, we'd better make /modules a symlink > > for /boot/modules, rather than allow for 4.x /modules to > > crash the pristine 5.0. >=20 > The idea was that someone might have a _3rd_party_ module (as I mentioned > in another email) installed in /modules. 3 Years later is it impossible > that any 4.x module can work on 5.0? I don't know. But you didn't > mention that either as a reason to make your change. >=20 The idea is that "someone" can easily add one line in /boot/loader.conf. Seriously, do you have an example of a working 4.x module running under the 5.0-RELEASE or later kernel? Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --/WwmFnJnmDyWGHa4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+ZSNHUkv4P6juNwoRAq5cAJ4yUcWUZ9IJC5QJY28diJgrB5oCQwCfW4Ut 0MyRyOfPsYcTUyv3mbvX1I0= =nepo -----END PGP SIGNATURE----- --/WwmFnJnmDyWGHa4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-src" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030304220600.GB73366>