The question's not stupid or trivial, and there's a number of
solutions (see the thread). I found a direct boot from Jaz wasn't
possible, but have a near hit using floppy and borrowing a fixed
harddrive partition. Here's my 2 cents.
What you can do depends on your hardware, including some issues you
- what's your SCSI adapter? Is it bootable?
- what's your hard drive(s) If non-SCSI (eg: IDE), can boot be
disabled? (hint: probably not)
- what else do you have on your system. How badly do you want to
avoid trashing it?
Most machines will boot from the following, in order
1. Floppy (if present, always)
2. IDE hard drive (if present, always?)
3. SCSI drive(s) (if bootable, as configured in SCSI setup)
My system is NT/Linux, with Linux on Jaz. 2GB Western Digital HD is
IDE, and pretty darn near all NTFS, with one 4MB FAT partition up
high. This partition is labled 'L' under NT (for Linux, naturally),
but is seen as 'C' when booting from a DOS floppy. Because the
partition is not in the first sector of the disk, I cannot boot DOS
directly from HD.
My solution, after mucking around with a number of options (trying to
boot Jaz (impossible, in my case), boot floppies (didn't work)), was
to use a plain 'ole DOS boot floppy with an AUTOEXEC.BAT on it.
AUTOEXEC launches LOADLIN.EXE on the FAT partition, which also has a
linux image and (if needed) an initrd (inital RAM disk, useful for
loading modules, such as SCSI drivers, if needed and not available in
LOADLIN is a DOS executable which launches linux by "pulling the rug
out" from under DOS. It was supplied with my installation (RedHat
4.1), and is available for download (don't ask me where <g>).
This works great, doesn't endanger my NT partitions, and is fast --
faster than a boot floppy, even faster than NT boot. DOS and
AUTOEXEC.BAT are all I read off of floppy. LOADLIN and the linux
image read from harddrive in less than a second, most of the wait is
watching intrd go through runlevels (which could be streamlined...).
Only problem so far is that my original Linux jaz disk crapped out (1
of 6 bought so far) -- bad blocks up about 60% of the way through the
disk. Because I'd created multiple filesystems (11!), I only lost one
filesystem (/data) with hardly anything on it. This is the best
argument I can give for partitioning a single disk, which otherwise
might seem overkill.
I didn't have a good way to back off everything else. Did a pretty
good backup by tarring and compressing config files which I untarred
back after a fresh install of Linux on a new disk. Strongly recommend
a *real* backup device (I'm leaning toward DAT), and/or a dedicated
machine or internal HD after you fall in love with Linux. A larger
FAT partition would also make transfers between the NT and Linux world
a bit easier.
FSs, BTW, for a mostly single-user workstation, PPP dialup, possible
local network server:
Device Mount Size
/dev/sda1 swap 32MB
/dev/sda2 / 20MB
/dev/sda3 /usr 250MB
/dev/sda5 /usr/lib 130MB
/dev/sda6 /usr/local 100MB
/dev/sda7 /usr/src 50MB
/dev/sda8 /home 50MB
/dev/sda9 /var 50MB
/dev/sda10 /tmp 15MB
/dev/sda11 /data 348MB
/dev/hda6 /mnt/hd 4MB (msdos)
I've found I can kludge a data transfer by booting from the install
floppy, and copying data to and from the Linux Jaz disk to a ramdisk
(I've got 96 MB ram, easy to set up a 10 - 40 MB ramdisk), to/from a
transfer Jaz disk. This is how I accomplish sw installs from internet
downloads right now -- kludgy, but it works. Reboots are necessary.
On or about Tue, 16 Sep 1997 12:49:00 -0500, Ivo Penzar
>Wannabe a Linux user. Also, buying an Iomega Jaz Drive Insider...
>Thinking why not - if possible - to use my Jaz Drive as an alternative
>boot device, e.g. for Linux operating system?
>Sorry if the question is technically incorrect, stupid, or
>My computer gives mi the choice to boot either from floppy, CD-ROM,
>hard disk or network. However, SCSI devices are not mentioned in its
>On Iomega Web site I just found the following notice:
>> The Jaz drive can be used as the computer's boot disk if configured
>> properly. Normally the drive must be set to SCSI ID 0 and the SCSI
>> adapter must have a bootable BIOS. For example, the Jaz Jet PCI SCSI
>> adapter is a bootable adapter.
>I do have a Jaz Jet PCI SCSI adapter, and now I'm buying the Jaz
>I would like to try Linux, but for now from Jaz removable disk ONLY.
>I'm not yet willing to reorganize my hard disk partitions and/or to
>add another HDD for the Linux operating system.
>As I understand, System Commander might/should help (?), but may I go
>[Computer: HP Pavilion, OS: Windows 95 (and how if upgraded to NT?).]
>Thank you for your expertise,
...humans, remove the spam guard from the above
...spambots, spam to hell
What part of "gestalt" don't you understand?