RE: [Nolug] How to get rid of lilo?? -- other option

On Fri, 2004-02-13 at 15:38, Petri Laihonen wrote:
> -----Original Message-----
> From: owner-nolug@joeykelly.net [mailto:owner-nolug@joeykelly.net] On Behalf
> Of Jame Scott
> Sent: Friday, February 13, 2004 2:49 PM
> To: nolug@joeykelly.net
> Subject: RE: [Nolug] How to get rid of lilo?? -- other option
>
>
> On Fri, 2004-02-13 at 10:05, Petri Laihonen wrote:
> > In order to get the installation done today, I've decided to put in IDE
> > drive for the setup.
> >
> > Q: What would be the easiest way of copying the OS from IDE to SCSI drive
> as
> > it's entirety and then boot off of this SCSI drive?
> >
> > Any suggestions?
> >
> > P
> >
> > ___________________
> > Nolug mailing list
> nolug@nolug.org
> Petri,
> The best way is to do as the others have suggested. The solution
> prescribed takes a couple of minutes at best and and always works.
> What you suggest in this scenario will give you less than desirable
> results. There are lots of to copy everything from one drive to another
> however, this does not mean it will actually boot and run as intended
> without a lot of configuration changes.
> You could install to your ide drive and then mount the other drive to a
> directory and copy any data you want off of it but if your interest is
> in a clean install and there is no actual data that needs to be
> recovered off of the SCSI drive whats the point?
> YOu could do the install to the IDE drive then add a line to your boot
> loader to boot the kernel on the other drive but again what is the
> point?
> Any dos based boot disk will have fdisk on it and the cmd fdisk/mbr will
> do away with lilo.
> Further I suggest using grub. There are less mistakes to make in
> configuration.
My apologies. I should have realized this issue was related to the SCSI
subsystem. I think your solution should work. Others could have been
to get to the SCSI card (usually but not always available on boot)
utility and choosing not to boot from the SCSI chain at all or changing
drive ID or changing boot order. You are right sometimes one just must
find a work around.
The essence of this issue is there is no drive in the computers BIOS to
control. In a SCSI system the hard drive specs and there boot order is
not listed here. This is in the SCSI subsystem BIOS. The computer BIOS
is read then later the SCSI BIOS. The later information over rides the
earlier in essence.

-- 
James Scott <jhs_technical@cox.net>
___________________
Nolug mailing list
nolug@nolug.org