Boot Loaders

A general purpose floppy disk boot loader

Newsgroups: comp.os.linux.misc
Date: 2002-09-11 14:51:10 PST

> Don't know much about what you really want, but there is the program
> "Loadlin.exe" that will load the kernel to any Linux OS you want.

Basically yes. Thanks.

> You only need to know where the partition is /dev/hd?? and a small DOS
> "FAT" to boot into in order for it to work. Then use DOS config.sys with
> the MENU commands Autoexec.bat to load the needed batch file to load
> "loadlin ---parameters to load version of kernel to load".  so then you
> will have a menu of each kernel to load crated with a file you can name as
> Debian for Debian, Redhat for Redhat, etc.

Hmm… what I meant "general purpose" is that I can boot to any system without pre-configuration. Ok, if this is the *only* choice I can have, I'll buy it anyway.

A general purpose floppy disk boot loader

> > a LILO created boot loader on a floppy disk which can boot /vmlinuz
> > found on any hard disk partition which can be found on a system (
> > /dev/hdXY and /dev/sdXY, where X=a,b,c,d and Y=1,2,3,4,5,6,7,8 ).  It
> > was rather trivial, once you know a little about boot loaders and
> > installing them on a floppy disk.
>
> Could you tell us how you did it please?

I modified a (generic) root/boot floppy disk (which includes LILO) to automatically run a short script after the system has started. The script appends a bunch of image sections (declared as optional) to a generic lilo configuration file, and then executes lilo to put a new boot loader on the same floppy disk, with entries for all the /vmlinuz images available on _that_ system. Upon successful map file installation the script reboots the machine. Think of it as a disposable boot diskette, as you have to make a new one every time you use it …

Since the absolute location of the kernel images on each partition of a random machine cannot be known in advance, and LILO does not know much about the different filesystems, it has to be a two step process.

Which Partition / Boot Manager is best??

Newsgroups: 24hoursupport.helpdesk,alt.os.windows-xp,comp.os.linux.setup,microsoft.public.win98.gen_discussion
Date: Wed, 4 Dec 2002 22:22:59 -0000

> Which Partition/Boot manager is the best?
>
> I need to rebuild my hard drive.  I am primarily a Windows user but
> want to build a triple boot system and include a version of Linux.
> So, I think that I am looking for a Windows-focused product that will
> also support Linux.  This is for a home system so I want to keep cost
> down but would like a more elegant and robust product than freeware
> typically provides (and probably need the support of a commercial
> product also).
>
> There seem to be several good candidates:
>
> 1.  TeraByte Unlimited BootIt
> 2.  PowerQuest Partition Magic/Boot Magic
> 3.  V-Com System Commander/Partition Commander
> 4.  OSL2000 Boot Manager
> 5.  Paragon Bootmanager/Partition Manager
>
> Can you point me to a thoroughly detailed comparative review of these
> products?

Go for: TeraByte Unlimited BootIt.

If! You know what you are doing ;-)

CRF

Which Partition / Boot Manager is best??

> > If! You know what you are doing ;-)

> Why do you add this caveat?  Does this mean it won't hold the user's
> hand (like System Commander will)?

That is precisely what it means.

BootIT NG is an extremely functional partitioning and boot utility that works outside of any OS. It can be installed to its own EMBRL partition or run straight from a floppy. This keeps you from being dependent on any OS working. Also includes imaging (direct to hdd or atapi CDRW). But, it will not hold your hand, you need to know what you are doing.

Its other good selling point is very good newsgroup support from the author and a few others. Server: terabyteunlimited.com, login as "guest" with the password "guest".

Rick Rogers

Which Partition / Boot Manager is best??

Terabyte is three things: Boot manager, partitioner and versatile backup tool. It can all be run from a floppy, but it does a lot. It can also be installed to the HDD, best in a tiny partition of it's own, (which I have yet to do). It can shrink/expand a partition w/o data loss. Mine was shrunk, has gone to HD1 & back and is running well.

PCR

Which Partition / Boot Manager is best??

>Can you point me to a thoroughly detailed comparative review of these
>products?

As I'm sure you expected, you're getting lots of opinions about what various people *like*, but not a lot of meat about why or what the differences are. (One good point, though, was that paying for something doesn't make it better.)

Give some thought to how you're going to partition your hard drive to support your chosen os's (you indicate triple-booting but mention only two os's). Consider that a single hard drive can normally (see below *) only support four primary partitions, one of which may be an "extended" partition which can be subdivided into additional volumes (aka, partitions) — the partition scheme would look something like ([1] [2] [3] [4a,4b,4c,…]). Linux requires at least two partitions (one being its swap partition), so if you have a Windows system and like to keep your data on a separate partition (e.g., "D:"), you could use up all four partition table entries just between these two os's. However, not everything requires its own primary partition — while DOS and Win9x must be installed on primary partitions, XP and both linux partitions can live in volumes within an extended partition. An example with 5 os's might be ([DOS] [W95] [W98] [XP,linux,linux-swap,DOSext]).

Why is this material? Because ideally you want only certain partitions visible depending on which os you boot, and some boot managers provide more control over hiding/unhiding the various partitions. For example, Powerquest's BootMagic is a good, easy-to-use program (and free, if you've already got PartitionMagic), but it will only hide primary partitions, not individual volumes of the extended partition. In the above 5-os example, you could configure BM to boot W98 while hiding the DOS and W95 partitions, but BM would not be able to hide the XP partition and leave the DOSext (for example, a "D:" drive for W98) visible because they're both within the extended partition. W98 won't be able to read the linux partitions anyway, nor the XP partition if it's formatted as ntfs, but that's another issue, my point is the boot manager is not controlling whether or not those partitions are visible. This would be a problem if the XP partition was fat32.

My experience with System Commander was with an old version, but I remember that program also could not selectively control the volumes in the extended partition.

TeraByte's BootitNG does allow fine-tuning the visibility of all partitions, including individual volumes within the extended partition. I believe (though I haven't confirmed this) that it can also permit XP to completely reside within an extended partition. (Normally if you install XP into an extended partition, it still needs to boot from a primary partition that can't be hidden). In reference to (*) above, BootitNG can also allow you to install more than 4 primary partitions, giving you the ability to install huge numbers of os's, but it does so by converting your hard disk's partition table to a proprietary format, which personally would make me uncomfortable. Fortunately, you don't have to enable that feature.

Another possibility you might look at is XOSL (www.xosl.org), which I haven't tried but appears to be full featured and free, as well. I'm not really familiar with linux boot managers, but I'm not sure grub or lilo can provide this kind of control over the boot options for the DOS or Win os's. I'm also not familiar with the other boot managers you've mentioned.

I hope my notes here will spur others to post constructive details or correct errors in my notes.

Also, beware that some (many?) os's must boot from a partition physically within the first 1024 cylinders of the hard disk, regardless of how you manage their visibility. ("Physically" is used loosely here, as modern disks translate the real geometry, but typically this means the first 8GB).

And lastly, my personal preferences: BootitNG for complex setups, or Powerquest's BootMagic if you don't need BootitNG's enhancements.

I'm Dan

cmd:AiR-BOOT - The ultimate Boot-Loader

Info

As of 2002.09.08 Sun, current version of AiR-BOOT is Release Candidate 2 [still beta]. This means that the product is still being built and it may contain bugs.

The terms and conditions of usage: - Any non-commercial private use is *FREE*

100% in MBR (does not need any real space on harddisc)

Source

http://en.ecomstation.ru/kiewitzsoft/air-boot.php http://kiewitzsoft.ath.cx/cgi-bin/download.cmd?FileID=softw_airboot

A 'local' boot loader

Newsgroups: comp.os.linux.setup
Date: Mon, 2 Dec 2002 02:32:42 GMT

> I'm wondering if there are simple 'local' boot loader out there for
> linux, which reside only in the 1st sector of linux, and care only
> about booting current linux. The reasons being:
>
> 1st, I don't wan't to put my linux boot loader in MBR -- too
> dangerous there. So many tools want to take possession of it. Some
> monopoly just possesses it without any choices...
>
> 2nd, The problem with lilo is that it keeps too many irrelevant
> information, like which HD it is on, which partition it is on, etc,
> whenever these info is changed, lilo refuses to boot. I unfortunately
> changes those quite a lot and lilo failed on me all the time.
>
> 3rd, I don't want to use grub. Too complicated for a simple job.
>
> All I want is a simple, local boot loader, just like the MS DOS
> boot -- count everything from its logical address, not worrying
> about anything that is outside the current partition. So it will
> work regardless which HD it is on, or which partition it is on, or
> even works after I moved my Linux partition to somewhere else, just
> like what partition magic does to DOS partitions.

FYI, I found the solution. The answer comes from (ironically) DOS. In short, use loadlin in W95/98, or native Windows Boot Loader under W2k.

All above problem will disappear, with a simple and neat solution, unfortunately under DOS.

cmd:XOSL

Basic Info

Info

Description

Extended Operating System Loader (XOSL) is the world's only full-featured free boot manager with a real, easy-to-use and full-blown graphical user interface. distributed under GPL.