Add something like this to your /etc/lilo.conf file under linux and rerun /sbin/lilo. Note that Solaris *MUST* be the active partition, on either the primary or another another hard drive. To use LILO with Solaris on the primary partition, install LILO in the MBR and mark the solaris partition as active. In this example Solaris is on your second hard drive (hence the "loader" line): other = /dev/hdb1 loader = /boot/chain.

Follow the instructions for the previous question substituting /dev/hdc as directed. An alternate, much-more-difficult method follows that doesn't involve the "switch drives with /boot/chain.b" trick. These are basically the steps I 'discovered' through countless failed attempts to get Solaris to boot from the secondary master. I got LILO to boot Solaris/x86 2.5.1 from the master disk of the secondary IDE. Solaris was initially installed in the primary-master disk, i.e.

Basically, the Linux LILO boot loader is used to fool solaris into thinking the slave is the master and vice versa (with the chain.b line) Add this in your Linux /etc/lilo.conf: use /dev/hdc instead of /dev/hdb if your second drive is the secondary IDE master instead of the primary IDE slave drive) Solaris had a bit of trouble because for some reason it had the default boot device as the primary HD and couldn't mount the root filesystem off of it (because it wasn't there).

If you have FreeBSD and Linux on the same disk, just follow LILO's installation instructions for booting a non-Linux operating system. Very briefly, these are: Boot Linux, and add the following lines to /etc/lilo.conf: other=/dev/hda2 table=/dev/hda label=FreeBSD the above assumes that your FreeBSD slice is known to Linux as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. If FreeBSD resides on another disk, you need to add loader=/boot/chain.

The general idea is that you copy the first sector of your native root Solaris/x86 partition into a file in the DOS/NT partition. Assuming you name that file something like c:\bootsect.sun (inspired by c:\bootsect.dos) you can then edit the c:\boot.ini file (copy boot.ini to boot.

DISCLAIMER: Messing around with boot loader issues can make your harddisks unbootable. Please make backups before doing so. Please install a new boot loader only when you really now what you do. We reject any responsibility for damages that may occur on your system. GRUB - the GRand Unified Bootloader - needs to access some files in order to run. Its best you place them on a small - 50MB is enough even for further extensions - FAT 16/32 partition.

Add this entry to /etc/lilo.conf, then rerun lilo. other = /dev/hda1 table = /dev/hda label = Windows The other points to the partition containing Windows and table points to the partition table of the disk.

The general idea is that you copy the first sector of your native root FreeBSD partition into a file in the DOS/NT partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.

You can also use the dd command to copy the backup saved by LILO to the boot sector. Refer to the LILO documentation if you wish to do this. FDISK /MBR MBR stands for Master Boot Record. This command replaces the boot sector with a clean DOS one, without affecting the partition table. Some purists disagree with this, but even the author of LILO, Werner Almesberger, suggests it. It is easy, and it works.

To use System Commander to dual boot both Win NT and Solaris, make these two configuration changes to System Commander: Use System Commander's local setup (Alt-s, Local config) to hide all other partitions from NT and Solaris (so they can't see each other's partitions).

Grab OS-BS [a free boot manager distributed with FreeBSD] from: ftp://ftp.freebsd.org/pub/FreeBSD/tools/osbs135.exe Or (newer) from: http://www.prz.tu-berlin.de/~wolf/os-bs.html Assuming you've already got Linux installed and enough free space for Solaris, go ahead and install the latter. Solaris then becomes the Active partition. Follow that installation with OS-BS and configure to "set startup id", which changes the Active partition on-the-fly.

From kernel versions 1.1.80 on, the compressed kernel image, which is what LILO needs to find, is in arch/i386/boot/zImage, or arch/i386/boot/bzImage when it is built, and is normally stored in the /boot/ directory. The /etc/lilo.conf file should refer to the vmlinuz symbolic link, not the actual kernel image. This was changed to make it easier to build kernel versions for several different processors from one source tree.

The general idea is that you copy the first sector of your native root FreeBSD partition into a file in the DOS/Windows NT partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.

Any washing detergent recommended by Fuzzi Bunz should be adequate; however using 1/6 of the recommended amount is required for a front loader. If there are too many suds, reduce your amount of liquid, if the diapers are not getting clean enough, increase your liquid.

Booting into Linux is easy, all you need is a recent copy of Penguin (the booter) and a kernel. (Both of which can be found on this site under "Downloads".) Before you can boot into Linux, you will need to turn off Virtual Memory and you may need Mode32 (see the section on Mode32, later). Start up Penguin, select the kernel that you want to boot from in the configuration screen, and then use the boot option from the file menu. If it works, you'll get a message about rarp requests.

Yes. Read-only access is available. You need to have Linux 2.1.x or greater. To see if your Linux kernel recognizes Solaris partitions, type the following on Linux: dmesg | grep solaris You should get something like this: hda: hda1 hda2 <solaris: [s0] hda5 [s1] hda6 [s2] hda7 [s3] hda8 [s5] hda9 [s6] hda10 [s7] hda11 > This says that Solaris lives in the 2nd partition (hda2), slices 0 to 7. These Solaris slices are mapped to virtual partitions hda5 to hda11.

It may, but do not have to. You may put your kernel image at a fixed MTD partition at the beginning of the flash chip and feed the rest of the flash to UBI. The point is that you do not have to give UBI whole flash chip, you just give it some MTD partition.

Here's one way of doing it. Solaris/x86 requires it's partition to be active and uses it's own boot manager with it hard-coded to boot to Solaris on timeouts.