I don't know what I am doing
 

So I have a VM setup, and trying to setup a dualboot Slackware and Solaris 11.2. I partitioned the drive like so:

Sda1 and sda3 has a boot flag set.

I installed Solaris first, then installed Linux, and added the following in LILO:

But I get this error when trying to update lilo:

So, how do I proceed to get lilo to boot my Solaris partition? :scratch:

When I installed Debian alongside my Slackware I learned from a member here that you have to tell LILO about the other os.
You'll have to edit your lilo configuration file. (lilo.conf)

The entry that I made in lilo.conf looked like this:
In your case it would be /dev/sda3 and the label would be Solaris; which I see you have already done.
However as soon as you make that change you should re-run LILO right away if you haven't already.


This only worked for me because I installed Grub to the master boot record of Debian.
And booting Debian for the first time I had to run:

I noticed that the EXT 4 partition that you created:
is only 10 GB's. Any time that I have created a EXT 4 journaling fs/partiton I created at least 20 GB as a base and than created a 1-2 GB swap partition. You may want to resize your partitions and include at least one swap for both os's to use.

This link should help:-
You can use the Solaris Boot Manager, LILO or Grub. I use Grub because I had trouble figuring our LILO-
http://www.tldp.org/HOWTO/Linux+Solaris-5.html

http://www.linuxquestions.org/questi...ng-4175468199/

Hope that helps:-

If I remember correctly lilo nor grub that is supplied with linux is zfs(solaris 11 filesystem) aware, there for will not
be able to boot solaris 11.

old, may help:
https://github.com/zfsonlinux/pkg-zf...ware-GRUB-0.97

Well you can set MSDOS partition boot flag for one partition only.

Like this?

I guess I could go the other way and just let Grub be the default bootloader. Still I would have thought that since Solaris uses grub, it would have noticed the Linux partition and give me an option to have grub load it. Of course that would be too easy. I am not too familiar with grub though.

Googled and found a few howtos that may help with solaris 11:

https://blogs.oracle.com/Hartmut/ent...cle_solaris_11

http://docs.oracle.com/cd/E36784_01/...html#scrolltoc

Yes, you could do that.
-:-To install the bootloader to the MBR of /dev/sda just run grub-install as "root"
Than run grub-update.-:-

When your installing another os you don't get the partition in the Grub Menu you can run:
By doing that it invokes 'os-prober.'


If a new kernel is updated or installed you will have to update Grub.

**The GRUB Manual**
http://www.gnu.org/software/grub/man...l-boot-methods

Maybe this makes a difference but I installed the livecd version of Solaris11.2 , so when I run that command I just get 'command not found' :scratch:

Well I decided to reinstall Solaris using the 'text' installer ISO. It seems that 11.2 you only get a text iso , unlike Solaris 10 where you have an iso that allows either a text option or install using CDE as the gui. Oh well, no big deal the install went fine but when I rebooted it just hangs and I get this:

I guess if you install the text option it doesn't automatically go to a gui? Still it won't even go to a command-line either. What did I do wrong? :scratch:

The solaris 11.2 livecd has a gui installer and desktop.
you can try make it continue booting to a login screen when it hangs by pressing ctrl+c keys.

So the text installer is just that then, Solaris without a desktop?

Ok I will stick with the livecd, but that still does not solve my multiboot issue, since 'grub' or any grub-related command just doesn't exist. :scratch:

Is your multiboot all on one drive or 3 different drives?

-:- Slackware uses LILO so you will have to tell LILO about Solaris and any other distro's by editing the lilo.config file with a chain-load entry.-:- Than re-run LILO-

To solve the grub bootloader issue try running these commands as root and it should find your other distro and add it to your GNU Grub Menu-

suggest to read bootadm man page, (however not sure if it will work
in a multiboot configuration).
within solaris grub file '/rpool/boot/grub/menu.conf'
add:

If you do decide give it to try, it appears those settings need to be added to the solaris's menu.conf by
using the bootadm command and not editing the file directly with
an editor.

@edwardm:

Do you think editing the grub.d file with a Solaris entry will help?


--:-This link might help- Jeebizz-:--
http://gotoanswer.stanford.edu/?q=Ho...x%2Csolaris%3F

I have read some articles, but never really did any tests to comfirmed them.
that neither Grub or lilo that comes with linux distros are able to boot
ZFS filesystems.

Ok, I understand now. FreeBSD, Solaris are ZFS fs-

After reading the Wikipedia WiKi I see that the distribution that your running, DragonFlyBSD, is a ZFS fs as well.
http://en.wikipedia.org/wiki/ZFS#Limitations

How did you manage to get your Dragon Fly distro to boot?

-:- -:- -:- -:-
This looks like this might work. At this point you know more than I do.

This Oracle WiKi looks like a start, Jeebizz-
http://docs.oracle.com/cd/E19082-01/...bbb/index.html

Hope it helps.

I've been at war myself with LILO and Grub for the last few days.
So far what I found out that a chainload menu entry in lilo.conf might work. (might)
If it does I'll let you know but it may not work for you because of the ZFS fs.

Has any of the Solaris documentation made any mention of how to work with the bootloader?

DragonFly uses HAMMER filesystem not ZFS.
.
http://www.dragonflybsd.org/hammer/

Probably a ZFS port for Dragonfly may be in the works,
Installed Dragonfly on its own dedicated system
and use Dragonfly's own bootloader.

Got it:-