| Author |
Message |
|
|
Post subject:
 Posted: Jul 19, 2008 - 01:43 AM
|
|
Team Member
Joined: Nov 27, 2006
Posts: 1962
Location: underworld
Status: Offline
|
|
| ** Some ** of my grub entries takin from that distro's grub, but, chainloading is easier, faster, Never have I had a problem with grub or adding distro's to it
Code:
### END DEBIAN AUTOMAGIC KERNELS LIST
title Sidux64
root (hd0,5)
kernel /boot/vmlinuz-2.6.25-9.slh.1-sidux-amd64 root=UUID=2e168ca8-f88a-4490-8f89-0e9862f11ab6 ro quiet vga=791
initrd /boot/initrd.img-2.6.25-9.slh.1-sidux-amd64
### ISO boot
title sidux Live
kernel (hd2,9)/sidux/vmlinuz-2.6.25-7.slh.2-sidux-686 boot=fll quiet noeject vga=791 fromiso=/sidux/sidux.iso
initrd (hd2,9)/sidux/initrd.img-2.6.25-7.slh.2-sidux-686
title Dreamlinux
root (hd2,1)
kernel /boot/vmlinuz-2.6.23.12-dream root=/dev/sdb2 ro quiet vga=791 splash resume=/dev/sda5
initrd /boot/initrd.img-2.6.23.12-dream
title Mandriva
kernel (hd2,7)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=fe529c9c-eaaf-40fa-bab3-87191978d47b resume=/dev/sda5 splash=silent vga=788
initrd (hd2,7)/boot/initrd.img
title=Sabayon
root (hd2,8)
kernel /boot/kernel-genkernel-x86-2.6.24-sabayon root=/dev/ram0 ramdisk=8192 real_root=/dev/sdb9 quiet init=/linuxrc splash=silent,theme:sabayon vga=791 CONSOLE=/dev/tty1 dolvm
initrd /boot/initramfs-genkernel-x86-2.6.24-sabayon
title Kanotix
root (hd0,7)
kernel /boot/vmlinuz-2.6.22-10-kanotix root=UUID=cd8fe181-e4ef-4a63-83bb-a2cbc701c031 ro noapic noapm vga=791 quiet
initrd /boot/initrd.img-2.6.22-10-kanotix
title Lenny-fvwm-crystal (no kde/gnome)
root (hd2,2)
kernel /boot/vmlinuz-2.6.21-2-486 root=/dev/sdb3 ro
initrd /boot/initrd.img-2.6.21-2-486
savedefault
title Bugnux
kernel (hd0,8)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/sda9 acpi=on resume=/dev/sda5 splash=silent vga=788
initrd (hd0,8)/boot/initrd.img
What I boot with at the moment besides the above
Code:
Kanotix
Kanotix CPX-Mini
Alien
Buffalo
Underground
Wolvix
Utopian
Elive16/17
Berry
Zenwalk
|
_________________
.... _
... (0)>
... / / \
.. / / . )
.. V_/_sidux powered
|
| |
|
|
|
 |
|
|
|
Post subject:
Posted: Jul 22, 2008 - 10:09 PM
|
|
Joined: Jan 16, 2008
Posts: 90
Status: Offline
|
|
Okay, I'm chainloading now but when I installed sidux, I had options which made me confused.
For e.g., when I am at the page for installing grub to either MBR or the root-partition, I have as choices:
mbr
partition
sda or sdb (I assume this means I have a choice of one of the drives)
Which should I choose for installing to the root partition?
I specified previously (in the page before which I could call the 'Partitioning' page) of /dev/sda10 (which is where sidux would install). So, if I select install to 'partition' in the next page (described scenario above), does that mean it will install grub to the root partition (if I choose 'partition')?
Btw, if I had selected sda (therefore, the 1st drive), for e.g., what would have happened? Would it 'remember' the selection of the previous page, sda10 and installed Grub there or would something else occur? Perhaps, 'partition' and 'sda' is the same thing (in this case), installing grub to the root partition since I chose to install (sidux OS) in sda10 (which is the 1st drive)?
Second question: concerning menu.lst
I noticed that there are only two entries. Doesn't sidux scan for other operating systems or did I select an option to 'disregard' other Linux OS's? It detected Windows XP so it's included.
It doesn't matter since I am using a dedicated/separate partition for Grub so I just had to install sidux's grub to the root partition.
Thanks for any answers and recommendations (for that matter). |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jul 22, 2008 - 11:45 PM
|
|
Joined: Apr 18, 2008
Posts: 23
Status: Offline
|
|
Partition means root partition in the installer.
Other operating systems usually have to be chainloaded. Or other special steps need to be taken. |
_________________
A man needs only to be turned around once with his eyes shut in this world to be lost ~ Thoreau
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 05, 2008 - 12:50 PM
|
|
Joined: Apr 15, 2008
Posts: 129
Location: Australia
Status: Offline
|
|
I consider myself very experienced at grub so forgive me for telling you how to suck eggs.
1) your post 5 has this line in it.....For a live cd
# grub
grub> root (hda0,0)
grub> setup (hd0)
grub> quit
# reboot
Pretending you did not know that will fail for linux....try...if you have only one drive
Code:
su
grub
root (hd0,0)
setup (hd0)
quit
Grub counts from zero so change those numbers based on where your /boot folder or partition that contain /boot is.
Of course if grub is in mbr and you get some grub error message....grub can be used to trouble shoot you way out of the mess.
Most people put /boot as first partition or as a sub-folder to / and / as first partition.
But the above grub command will report ....succeeded....if it finds the balance of the booting files on your damaged system....and if not you know you have not got all the files or you used the wrong numbers.
I have written a tutorial elsewhere on the net....but there are plenty of tutorials on grub.
2) Forgive if I explain too much but...each drive has an mbr and not all are bootable. Your bios normally has a boot order to follow and when it finds a bootable drive....it jumps to that mbr....but the mbr is tiny so has only a very small code....that says....hey I am a bootloader...whether its ms or linux etc....and then tells the sytem to jump to the balance of the booting files.
In ms land those files are on C:/ or c root eg ntldr* boot.ini
In linux those files are always in /boot
In linux...some distro have a symbolic link to /etc/grub.conf....which is their choice but if you have grub....stuff should all be in /boot/grub
3) When installing....and you asked to install grub in mbr or root partition.....
it is best to install to mbr.....unless that partiton is a raid partition or a lvm partition.
and root is a confusing word....in context it means where is the /boot partition and is different context from the kernel line ....root=/dev/blah blah or root=label=blah blah or root=UUID=blah blah
I have moved from a rpm distro and I am currently in love with sidux so I hope you enjoy the ride as well
good luck |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 05, 2008 - 01:26 PM
|
|
Joined: Apr 15, 2008
Posts: 129
Location: Australia
Status: Offline
|
|
ohh forgot to add to prev post
if your format as ext2 or ext3....sidux uses a modified grub so to use a live cd....you need to use sidux.
I just did a test and I have a ext3 format for / and its all good. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 07, 2008 - 08:05 PM
|
|
Joined: Jun 03, 2007
Posts: 11
Status: Offline
|
|
I've been happily running sidux for some time and I decided to also install Debian stable on the same machine, in case it was ever needed.
Stable included sidux in its grub, but the following error is given at boot when sidux is chosen:
Code:
kernel .. vga=791
Error 2: Bad file or directory type
Also, when using the sidux live CD,
Code:
grub-install /dev/sda
gives an error message. "No such block," I believe it said.
Is there a way I can modify Etch's grub and boot with it? |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 07, 2008 - 11:49 PM
|
|
Joined: Apr 15, 2008
Posts: 129
Location: Australia
Status: Offline
|
|
titan in another thread said
Code:
/usr/sbin/grub-install --recheck --no-floppy /dev/sda
was good....but of course you may have to verfiy sda is the correct target drive.
And that other thread is talking about the change in inode size. So you would use sidux as a live cd or live dvd to issue that command. With su or sudo su.
w
cheerio |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Aug 08, 2008 - 02:55 AM
|
|
Joined: Jun 03, 2007
Posts: 11
Status: Offline
|
|
It was using sda. Thank you, aus.  |
|
|
| |
|
|
|
|
|
|
