Re: Unable to use network early in boot with recent -current
- From: Skip Ford <skip.ford@xxxxxxxxxxx>
- Date: Wed, 21 Feb 2007 16:10:39 -0500
Kevin Oberman wrote:
Any thought of making module loads default to the directory of the
booted kernel (e.g. /boot/kernel.old) instead of /boot/kernel?
This should already happen if you "set kernel" to kernel.old and
then "boot".
--
Skip
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Unable to use network early in boot with recent -current
- From: Scot Hetzel
- Re: Unable to use network early in boot with recent -current
- References:
- Re: Unable to use network early in boot with recent -current
- From: Scot Hetzel
- Re: Unable to use network early in boot with recent -current
- From: Kevin Oberman
- Re: Unable to use network early in boot with recent -current
- Prev by Date: psm(4) doesn't work with custom kernel config
- Next by Date: Re: linuxolator related LOR
- Previous by thread: Re: Unable to use network early in boot with recent -current
- Next by thread: Re: Unable to use network early in boot with recent -current
- Index(es):