Re: Removing /boot/modules from BSD.root.dist
On Fri, 15 Nov 2002, Ruslan Ermilov wrote: REHi! RE REAnyone objects to this patch? Yes. Where do a install my modules then, that don't build with the kernel? harti RE RE%%% REIndex: BSD.root.dist RE=== RERCS file: /home/ncvs/src/etc/mtree/BSD.root.dist,v REretrieving revision 1.58 REdiff -u -5 -r1.58 BSD.root.dist RE--- BSD.root.dist10 Jun 2002 04:47:26 - 1.58 RE+++ BSD.root.dist15 Nov 2002 08:38:24 - RE@@ -10,12 +10,10 @@ RE boot RE defaults RE .. RE kernel RE .. RE-modules RE-.. RE .. RE dev RE fd mode=0555 RE .. RE .. RE%%% RE RE RECheers, RE -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing /boot/modules from BSD.root.dist
On Fri, 15 Nov 2002, Ruslan Ermilov wrote: Anyone objects to this patch? Yes - this is the only place to put modules which are not built as part of the kernel, for example /usr/ports/comms/ltmdm. Gavin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing /boot/modules from BSD.root.dist
On Fri, Nov 15, 2002 at 12:47:59PM +, Gavin Atkinson wrote: On Fri, 15 Nov 2002, Ruslan Ermilov wrote: Anyone objects to this patch? Yes - this is the only place to put modules which are not built as part of the kernel, for example /usr/ports/comms/ltmdm. This port puts it under /usr/local/share/ltmdm/ltmdm.ko. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg46720/pgp0.pgp Description: PGP signature
Re: Removing /boot/modules from BSD.root.dist
On Fri, 15 Nov 2002, Ruslan Ermilov wrote: On Fri, Nov 15, 2002 at 12:47:59PM +, Gavin Atkinson wrote: On Fri, 15 Nov 2002, Ruslan Ermilov wrote: Anyone objects to this patch? Yes - this is the only place to put modules which are not built as part of the kernel, for example /usr/ports/comms/ltmdm. This port puts it under /usr/local/share/ltmdm/ltmdm.ko. OK, it may have been a bad example, but I prefer having my kernel modules loaded via the standard loader.conf method rather than using kldload for modules which I always want to exist. /boot/modules has been documented as being in the search path for modules for ages now, it seems unnecessary to change this. I think that we do need somewhere on the root partition where modules can be kept, without them being lost on the next upgrade. Gavin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing /boot/modules from BSD.root.dist
On Fri, Nov 15, 2002 at 01:51:57PM +, Gavin Atkinson wrote: On Fri, 15 Nov 2002, Ruslan Ermilov wrote: On Fri, Nov 15, 2002 at 12:47:59PM +, Gavin Atkinson wrote: On Fri, 15 Nov 2002, Ruslan Ermilov wrote: Anyone objects to this patch? Yes - this is the only place to put modules which are not built as part of the kernel, for example /usr/ports/comms/ltmdm. This port puts it under /usr/local/share/ltmdm/ltmdm.ko. OK, it may have been a bad example, but I prefer having my kernel modules loaded via the standard loader.conf method rather than using kldload for modules which I always want to exist. /boot/modules has been documented as being in the search path for modules for ages now, it seems unnecessary to change this. I think that we do need somewhere on the root partition where modules can be kept, without them being lost on the next upgrade. Yes, the standard search path is /boot/kernel;/boot/modules;/modules. Nevertheless, we don't create /modules, why should we create /boot/modules? When you say ``documented'', what do you mean? ``grep -r /boot/modules doc/en_US.ISO8859-1'' returns nothing. Do you mean kldconfig(8) only? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg46722/pgp0.pgp Description: PGP signature
Re: Removing /boot/modules from BSD.root.dist
On Fri, Nov 15, 2002 at 03:35:18PM +0200, Ruslan Ermilov [EMAIL PROTECTED] wrote: Anyone objects to this patch? Yes - this is the only place to put modules which are not built as part of the kernel, for example /usr/ports/comms/ltmdm. This port puts it under /usr/local/share/ltmdm/ltmdm.ko. This is bad practice. The /boot/modules directory was discussed long time ago and meant to third-party modules as I remember. That's why I haven't discarded it locally. Even if ports have rules to install everything under ports-dir they should install kernel modules into /boot/modules. Otherwise it's a sphagetti to manage. The IMHO thing applies to this message also quite well. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing /boot/modules from BSD.root.dist
On Fri, 15 Nov 2002, Ruslan Ermilov wrote: REOn Fri, Nov 15, 2002 at 01:51:57PM +, Gavin Atkinson wrote: RE On Fri, 15 Nov 2002, Ruslan Ermilov wrote: RE On Fri, Nov 15, 2002 at 12:47:59PM +, Gavin Atkinson wrote: RE On Fri, 15 Nov 2002, Ruslan Ermilov wrote: RE REAnyone objects to this patch? RE RE Yes - this is the only place to put modules which are not built as part RE of the kernel, for example /usr/ports/comms/ltmdm. RE RE This port puts it under /usr/local/share/ltmdm/ltmdm.ko. RE RE OK, it may have been a bad example, but I prefer having my kernel modules RE loaded via the standard loader.conf method rather than using kldload for RE modules which I always want to exist. /boot/modules has been documented as RE being in the search path for modules for ages now, it seems unnecessary to RE change this. I think that we do need somewhere on the root partition where RE modules can be kept, without them being lost on the next upgrade. RE REYes, the standard search path is /boot/kernel;/boot/modules;/modules. RENevertheless, we don't create /modules, why should we create /boot/modules? Because then Makefiles don't have to fiddle with creating directories. I don't have a rule for creating /usr/bin in every Makefile that installs into /usr/bin. Why should I have one for /boot/modules? harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing /boot/modules from BSD.root.dist
In the last episode (Nov 15), Ruslan Ermilov said: Yes, the standard search path is /boot/kernel;/boot/modules;/modules. Nevertheless, we don't create /modules, why should we create /boot/modules? When you say ``documented'', what do you mean? ``grep -r /boot/modules doc/en_US.ISO8859-1'' returns nothing. Do you mean kldconfig(8) only? I think /modules is in the path because that's where 3rd-party modules went in 4.*, and is just there for compatibility. Putting them in /boot/modules lets you (theoretically) have a small /boot partition with just the files required to get the kernel booted and root mounted. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
