Re: Boot order with firewire 4.8-RELEASE

2003-06-24 Thread Bill Campbell
On Tue, Jun 24, 2003 at 10:31:32AM -0700, Bill Campbell wrote: >On Tue, Jun 24, 2003 at 08:15:41AM +0100, Matthew Seaman wrote: ... >>You can get round that by 'wiring down' the SCSI buses and devices in >>your kernel config. Eg. assume that your boot drive is at LUN 0 on an >>Adaptec SCSI interfa

Re: Boot order with firewire 4.8-RELEASE

2003-06-24 Thread Bill Campbell
On Tue, Jun 24, 2003 at 08:15:41AM +0100, Matthew Seaman wrote: >On Mon, Jun 23, 2003 at 04:40:24PM -0700, Bill Campbell wrote: > ... >> My basic question is how does one control the order devices are scanned >> during the boot process? I would like to be sure that the system will come >> up after

Re: Boot order with firewire 4.8-RELEASE

2003-06-24 Thread Matthew Seaman
On Mon, Jun 23, 2003 at 04:40:24PM -0700, Bill Campbell wrote: > Be that as it may, when I booted the new kernel with an external firewire > disk turned on, the new kernel detected the firewire disk before it did the > SCSI on the adaptec controller, and naturally couldn't find a working > system

Boot order with firewire 4.8-RELEASE

2003-06-23 Thread Bill Campbell
I've just installed 4.8-RELEASE on an SMP system, making the newbie mistake of running CVSup, then building a new kernel to enable SMP without doing a ``make world'' first. The kernel make worked, and booted -- with the minor problem that ``ps'' and friends didn't work, and booting kernel.old pani