Message Board -  Archive

[ Login ] [ Create Account ]
[ Board List ] [ View Board ] [ Post Reply ]
  Author  Subject: re: Boot to External 1394 Drive

Posted on 08-19-2003 02:44 p.m. ET  reply

Original Poster: derek

I don't think you can "boot" the 1394 external drive, period. Not sure why
someone did not come right out and say this earlier. Yes, LILO can load a
kernel from another physical disk - but it usually has to be one that is
connected via basic hardware components, typically low-level IDE/SCSI.
Otherwise, LILO would need to have firewire (and maybe USB) drivers built-in -
which it does not as far as I know. Does anyone know if GRUB is any
different? (I don't think it is)

It is my understanding that using LILO to boot a firewire (and maybe USB too)
drive/device will not work. The kernel itself has modules to enable you to
use such devices, and if you are trying to boot off one of those devices, you
are putting the cart before the horse, so to speak.

The "sda1" entry you are referring to is a nomenclature from Linux that is
assigned after/while the kernel is loading and giving you firewire/1394
support. That does not mean it is a native low-level IDE/SCSI device -
despite the "sda" nomenclature.

I don't think you can boot to the external firewire device period. However,
if you can put some basic kernel and associated elements on a more typical
drive, and boot that kernel - you could then reference the external drive for
all your other files and directories as someone already mentioned. But, I see
that this will not help for development purposes where you want to have a
different OS running separately from your working environment. You could also
consider burning a bootable CD-Rom (or more than one) that can hold some of
this booting/kernel data if space is tight on your existing drives.

No one seemed to mention using a virtual OS package for your purposes.
Commercial ones include "VMware" where you can literally load another OS
(even if it is also Linux) in a "virtual" space outside your current running
OS. This is good for development and testing, so you do not crash your
working OS. There are other non-commercial options including maybe "bochs"
and you can look for more along those lines. These products/apps are used for
not only running another Linux/Unix OS, but also for running MS Windows, Mac,
and emulating other OS environments from within Linux. With your idea of
booting another Linux (and thereby closing out the other first) from the
external drive, just to test something, and then having to reboot back into
your other OS - seems like a lot of wasted time and a good example of when to
use virtual OS software. You could have all 3 of your environments up and
running without crashing each other (Windows, Linux, Linux 2).

virtual machine links to get started: (run various OS inside a host OS) (run various OS inside a host OS) or (run MS Win OS inside Linux)

< Previous 1 Next >

Site Contents