John-Mark Gurney wrote:
>
> I did a couple installs using normal slices and standard MBR, and when
> the machine restarted, I got the "Operating System Missing" error...
> the only way I was able to install on the system was to use dangerous
> dedicated mode... I've seen this happen a couple time
> On Wed, May 12, 1999 at 05:06:03PM -0700, Mike Smith wrote:
> > > well, I wonder if other people have noticed this also, but if you don't
> > > have a previous boot loader installed (like windows/dos) the ONLY way
> > > to install onto a machine is TO use a dangerously dedicated mode...
> >
> >
On Thu, May 13, 1999 at 12:16:17PM +1200, a little birdie told me
that Joerg Micheel remarked
>
> Virgin systems is not virgin disks. If you buy a complete PC, this
> bootloader from Redmonton is already on the disk. I had similiar
> problems a while back and unless someone has explicitely looked
Mike,
On Wed, May 12, 1999 at 05:06:03PM -0700, Mike Smith wrote:
> > well, I wonder if other people have noticed this also, but if you don't
> > have a previous boot loader installed (like windows/dos) the ONLY way
> > to install onto a machine is TO use a dangerously dedicated mode...
>
> This
> Mike Smith scribbled this message on May 12:
> > >
> > > no, it's a "dangerously dedicated" SCSI disk.
> >
> > That's never a good start.
>
> well, I wonder if other people have noticed this also, but if you don't
> have a previous boot loader installed (like windows/dos) the ONLY way
> to ins
Mike Smith scribbled this message on May 12:
> >
> > no, it's a "dangerously dedicated" SCSI disk.
>
> That's never a good start.
well, I wonder if other people have noticed this also, but if you don't
have a previous boot loader installed (like windows/dos) the ONLY way
to install onto a machin
>
> no, it's a "dangerously dedicated" SCSI disk.
That's never a good start.
> the loader shows the floppy as DISK A and the SCSI disk as DISK B.
Are you sure it lists the SCSI disk as B and not C? If it's showing up
as B your BIOS is doing funny stuff.
--
\\ Sometimes you're ahead,
On Tue, 11 May 1999 21:39:42 +0200, Gary Jennejohn wrote:
> I switched to the new config(8) today, where the ``config kernel root on..''
> line is no longer tolerated in the config file.
As a workaround, try the following, taken directly from LINT
options ROOTDEVNAME=\"da0s2e\"
Ciao,
Poul-Henning Kamp writes:
>In message <199905111939.vaa02...@peedub.muc.de>, Gary Jennejohn writes:
>>I switched to the new config(8) today, where the ``config kernel root on..''
>>line is no longer tolerated in the config file.
>>
>>I now have to ``boot -r'' to avoid a `can't mount root' panic. Th
Mike Smith writes:
>> I switched to the new config(8) today, where the ``config kernel root on..''
>> line is no longer tolerated in the config file.
>>
>> I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't
>> necessary before.
>>
>> I know I can probably put something int
> I switched to the new config(8) today, where the ``config kernel root on..''
> line is no longer tolerated in the config file.
>
> I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't
> necessary before.
>
> I know I can probably put something into /boot/ to automate this.
In message <199905111939.vaa02...@peedub.muc.de>, Gary Jennejohn writes:
>I switched to the new config(8) today, where the ``config kernel root on..''
>line is no longer tolerated in the config file.
>
>I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't
>necessary before.
>
I switched to the new config(8) today, where the ``config kernel root on..''
line is no longer tolerated in the config file.
I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't
necessary before.
I know I can probably put something into /boot/ to automate this.
Just thought
13 matches
Mail list logo
