Date: Sat, 22 Nov 2003 21:36:35 -0200 From: "Daniel C. Sobral" <dcs@newsguy.com> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/boot/i386/loader loader.rc Message-ID: <3FBFF303.3090001@newsguy.com> In-Reply-To: <xzp4qwxtkre.fsf@dwp.des.no> References: <200311211901.hALJ12uN003276@repoman.freebsd.org> <xzp4qwxtkre.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Sm=F8rgrav wrote: > "Daniel C. Sobral" <dcs@FreeBSD.org> writes: >=20 >> Log: >> With the beastie menu a problem was introduced in which selecting a >> different kernel to boot with kernel=3D"NAME" would load the kernel a= nd >> loader.conf-selected modules from /boot/NAME, but it would not change= >> module_path. So, for instance, the automatically loaded acpi.ko would= come >> from /boot/kernel/acpi.ko, *always*. >=20 > Thanks for fixing this. Unfortunately, loader.rc is only installed if > it doesn't already exist, and mergemaster doesn't handle it, so > installed systems need to be fixed manually. Is there something we > can do to the Makefile and / or mergemaster to address this? There have been many discussions around this subject before. The problem = is that /boot/loader.rc is deemed to be untouchable, so the solutions I=20 support won't handle this particular problem. I'd like to have=20 /boot/defaults/loader.rc to be loaded _if_ a /boot/loader.rc can't be=20 found, and only install that file. That would solve this kind of=20 situation in the future, but not now. I suggest a note in UPDATING. I can't see what more we could do. --=20 Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@banana.bsdconspiracy.net I'd like to work for something named "Alcohol, Tobacco and Firearms".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FBFF303.3090001>