Re: Latest kernel/module restructuring
On Tue, Sep 12, 2000 at 06:11:20PM +0200, Niels Chr. Bank-Pedersen wrote: > Hmm, how about those of us doing buildworlds/buildkernels on > one (nfs)server for subsequent installworlds/installkernels > on multiple other machines? Use the `make reinstall' target with KERNEL_KO set to the name of the kernel core filename you want. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
In message <[EMAIL PROTECTED]> Sheldon Hearn writes:
: Folks, I agree that it would be nice to have a reinstallkernel target in
: src/Makefile.inc1. Other than that, it really does sound like
: everyone's just arguing for the sake of being heard.
Let's see if this knocks down the noise level:
Index: if_ep_pccard.c
===
RCS file: /home/imp/FreeBSD/CVS/src/sys/dev/ep/if_ep_pccard.c,v
retrieving revision 1.14
diff -u -r1.14 if_ep_pccard.c
--- if_ep_pccard.c 2000/07/13 22:54:23 1.14
+++ if_ep_pccard.c 2000/09/13 03:51:01
@@ -88,7 +88,7 @@
if ((desc = ep_pccard_identify(epb->prod_id)) == NULL) {
if (bootverbose)
device_printf(dev, "Pass 1 of 2 detection "
- "failed (nonfatal)\n");
+ "failed (nonfatal) id 0x%x\n", epb->prod_id);
epb->cmd_off = 2;
epb->prod_id = get_e(sc, EEPROM_PROD_ID);
if ((desc = ep_pccard_identify(epb->prod_id)) == NULL) {
@@ -127,6 +127,8 @@
return ("3Com Etherlink III 3C589");
case 0x2056: /* 3C562/3C563 */
return ("3Com 3C562D/3C563D");
+ case 0x0010:/* 3C1 */
+ return ("3Com Megahertz C1");
}
return (NULL);
}
@@ -140,6 +142,7 @@
case 0x2b57: /* 3C572BT */
case 0x4057: /* 3C574 */
case 0x4b57: /* 3C574B */
+ case 0x0010: /* 3C1 */
epb->mii_trans = 1;
return (1);
case 0x2056: /* 3C562D/3C563D */
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
On Tue, 12 Sep 2000 18:11:20 +0200, "Niels Chr. Bank-Pedersen" wrote: > Hmm, how about those of us doing buildworlds/buildkernels on > one (nfs)server for subsequent installworlds/installkernels > on multiple other machines? You run buildkernel once, and then installkernel multiple times. That's if all your machines want the same kernel and modules. If they require different kernels and modules, you'll want something like: master> make KERNEL=HOST1 buildkernel master> make KERNEL=HOST2 buildkernel master> make KERNEL=HOST3 buildkernel host1> make installkernel host2> make installkernel host3> make installkernel > With the current targets, you either have to build modules > over and over againg for each `client', or you have to accept > that /boot/kernel/* gets nuked when running installkernel > (or, as you point out, one can use the old manual scheme). Right now, the general feeling seems to be that the options specified in the kernel config might affect the way in which modules for that kernel are built. I don't like this idea, but that's the prevailing wisdom. So yes, you have to build each machine's modules separately. If you agree with me that the prevailing wisdom is stupid, then you can build every kernel after HOST1's with -DNO_MODULES and copy HOST1's modules into the obj dir for the remaining hosts' kernels. You could probably even get away with a symlink. Folks, I agree that it would be nice to have a reinstallkernel target in src/Makefile.inc1. Other than that, it really does sound like everyone's just arguing for the sake of being heard. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
On Tue, Sep 12, 2000 at 04:04:20PM +0200, Sheldon Hearn wrote: > > > On Tue, 12 Sep 2000 10:00:06 -0400, Michael Lucas wrote: > > > Some of us rebuild kernels without supping. I, for one, play with all > > sorts of kernel options to see what they do. > > Then you probably want the kernel reinstall target. I don't think that > this target is available from src/Makefile.inc1, so you'd have to use > the old style of kernel building. > > If you want something like ``make reinstallkernel'' from /usr/src to > work, you should probably ask marcel nicely. > > But the original proposal was ill-conceived and simply won't cut it. Hmm, how about those of us doing buildworlds/buildkernels on one (nfs)server for subsequent installworlds/installkernels on multiple other machines? With the current targets, you either have to build modules over and over againg for each `client', or you have to accept that /boot/kernel/* gets nuked when running installkernel (or, as you point out, one can use the old manual scheme). > Sheldon. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
On Tue, 12 Sep 2000 10:00:06 -0400, Michael Lucas wrote: > Some of us rebuild kernels without supping. I, for one, play with all > sorts of kernel options to see what they do. Then you probably want the kernel reinstall target. I don't think that this target is available from src/Makefile.inc1, so you'd have to use the old style of kernel building. If you want something like ``make reinstallkernel'' from /usr/src to work, you should probably ask marcel nicely. But the original proposal was ill-conceived and simply won't cut it. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
> > To remedy this, I suggest we have an option in /etc/defaults/make.conf > > to _not_ wipe out any modules in /boot/kernel (except kernel.ko of > > course) if modules are not built with kernel. > This sounds like a very bad idea, since it encourages folks to use > modules which are not synchronized with the running kernel. Some of us rebuild kernels without supping. I, for one, play with all sorts of kernel options to see what they do. When 5.0-stable comes out, a lot of people would like this. Having to rebuild the modules when I want to add USER_LDT to my kernel would be bad. ==ml -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest kernel/module restructuring
On Tue, 12 Sep 2000 05:33:10 -0400, Donn Miller wrote: > To remedy this, I suggest we have an option in /etc/defaults/make.conf > to _not_ wipe out any modules in /boot/kernel (except kernel.ko of > course) if modules are not built with kernel. This sounds like a very bad idea, since it encourages folks to use modules which are not synchronized with the running kernel. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
