On Sun, Jan 24, 1999 at 09:29:59AM -0800, Mike Smith wrote:
> num_ide_disks is now deprecated, you can throw it
> away. If you resup, you won't need root_disk_unit either - that just
> avoids the code I broke.
Confirmed. My system now boots quite happily without num_ide_disks o
> On Wed, Jan 20, 1999 at 11:00:27PM -0800, Mike Smith wrote:
> > Right now I'm looking at stamping the disklabel which contains the
> > designated root filesystem and passing the stamp into the kernel, which
> > will then go look for it. There are still gremlins with this approach,
> > but I c
On Wed, Jan 20, 1999 at 11:00:27PM -0800, Mike Smith wrote:
> Right now I'm looking at stamping the disklabel which contains the
> designated root filesystem and passing the stamp into the kernel, which
> will then go look for it. There are still gremlins with this approach,
> but I can't think
> > > I'm not sure about anybody else here, but to my mind a "Winblows on C:
> > > drive and let's try out FreeBSD on the second disk" configuration should
> > > really be supported seamlessly.
> >
> > You're more than welcome to propose a technical solution that solves
> > the problem.
>
> OK,
On Wed, 20 Jan 1999, Mike Smith wrote:
> > The option of putting the second drive
> > as slave on the primary interface would work, however anybody that knows
> > anything about IDE (read somebdy interested in trying FreeBSD) would put
> > it on the second interface for speed reasons.
>
> Er, you
> I'm not sure about anybody else here, but to my mind a "Winblows on C:
> drive and let's try out FreeBSD on the second disk" configuration should
> really be supported seamlessly.
You're more than welcome to propose a technical solution that solves
the problem.
> The option of putting the sec
> The next option is configuring my master drive on the secondary interface
> as wd1 instead of wd2.
This works fine. I guess the real solution is to make the IDE disk scan
the same as we do for SCSI, which also happens to be the same as the
BIOS does. We possible need a config syntax like
contro
I wrote:
> I'm off now to play now with rootdev and boot_askname.
Well, if I let the standard boot process occur, then I stop the loader and
set rootdev=disk3s1a: I can get the kernel running in single user mode
but mount refuses to remount / as rw. It's curious that the message about
changing the
On Wed, 20 Jan 1999, Daniel C. Sobral wrote:
> John Saunders wrote:
> > I have had no success in booting -current with the new loader. I can boot
> > the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt.
> > However if I enter either 1:wd(1,a)/boot/loader (the default) or
> > 1:wd(2
unders
> Cc: freebsd-current@FreeBSD.ORG
> Subject: Re: Booting -current with new loader
>
>
> > The only solution I have is bypass the loader all-together, but I really
> > wanted a splash screen :( Or possibly use config to make my second disk
> > appear as wd1 instead of
John Saunders wrote:
>
> I have had no success in booting -current with the new loader. I can boot
> the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt.
> However if I enter either 1:wd(1,a)/boot/loader (the default) or
> 1:wd(2,a)/boot/loader I get the loader started but the kern
> The only solution I have is bypass the loader all-together, but I really
> wanted a splash screen :( Or possibly use config to make my second disk
> appear as wd1 instead of wd2 (not tried yet because I consider it an ugly
> hack).
Try "set num_ide_disks=-1" in the loader.
--
\\ Sometimes yo
Hi,
I have had no success in booting -current with the new loader. I can boot
the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt.
However if I enter either 1:wd(1,a)/boot/loader (the default) or
1:wd(2,a)/boot/loader I get the loader started but the kernel won't boot.
The the se
13 matches
Mail list logo
