Hey everyone, it's been awhile since I posted in here! I've been running antiX on my laptop (triple boot) for a few years now. Unfortunately, the motherboard died. So I bought a new laptop and I have Windows 7 Ultimate and Ubuntu 12.04 running on it. I left a partition for antiX so I could install it eventually and that's what I want to do. However, I'd like to keep using the GRUB that Ubuntu installed. My question is, when I choose not to install GRUB during the antix install, what exactly do I have to add to the Ubuntu GRUB and how do I do that?
I know it used to be editing /boot/grub/menu.lst, is this still the case? I haven't done this for awhile. Also, what exactly do I need to put in the entry? UUID? If so, how do I find the antiX UUID?
Any help would be much appreciated since I'm not sure what I'm doing!
Thanks!
topic title: Adding antiX to Ubuntu GRUB
9 posts
• Page 1 of 1
-
Posts: 251
- Joined: 16 Mar 2008
-
Posts: 1,062
- Joined: 20 Jan 2010
#2
ubuntu with grub 2 has been very good IMO at detecting other distros / operating systems. If you install antix, reboot into ubuntu, open terminal as root, run update-grub, it should fix the grub entries by itself.
-
Posts: 325
- Joined: 04 Nov 2011
#3
Which to me here is the question, how do I get antiX to the HDD when the installer with Grub in the / root partition is denied?
Even if I try to leave out Grub, no install antiX.
As expected from the Grub2 Ubuntu update-grub adjust anything.
Where there is nothing, nothing! A KO criterion for antiX11 and 12 so far. Or what I've missed?
See Silver Bear Post 2] post24869.html#p24869
Even if I try to leave out Grub, no install antiX.
As expected from the Grub2 Ubuntu update-grub adjust anything.
Where there is nothing, nothing! A KO criterion for antiX11 and 12 so far. Or what I've missed?
See Silver Bear Post 2] post24869.html#p24869
-
Posts: 325
- Joined: 04 Nov 2011
#4
@JawsThemeSwimming428
f you want to do this to you ...
Complete installations (multiboot)
First Windows 7
Second Antix
Third Ubuntu 12:04
This order of installation with the boot-managers in each of the MBR of the HDD.
This should also restart the Ubuntu Grub 2 of the other two. __{{emoticon}}__
f you want to do this to you ...
Complete installations (multiboot)
First Windows 7
Second Antix
Third Ubuntu 12:04
This order of installation with the boot-managers in each of the MBR of the HDD.
This should also restart the Ubuntu Grub 2 of the other two. __{{emoticon}}__
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#5
Just to get this right __{{emoticon}}__
For those wanting to boot antiX with a distro running grub2 and wanting to keep grub2, in order for grub2 to boot/detect antiX, antiX grub must be installed to the root partition where antiX is installed. Is this true?
If it isn't true, then how to boot antiX if no grub is installed into its root partition?
For those wanting to boot antiX with a distro running grub2 and wanting to keep grub2, in order for grub2 to boot/detect antiX, antiX grub must be installed to the root partition where antiX is installed. Is this true?
If it isn't true, then how to boot antiX if no grub is installed into its root partition?
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#6
To answer my own question(s).
I did this in Virtualbox, so I presume it should work on a real hard drive.
Test 1
1. Installed latest siduction to sda1.
2. Installed latest antiX-base to sda4 and chose to uncheck the install grub option.
3. Rebooted into siduction, ran update-grub as root user and rebooted and antiX appears in the grub options and boots successfully.
Test 2.
1. Installed latest siduction to sda1.
2. Installed latest antiX-base to sda4 and chose to uncheck the install to MBR option, got an error and then chose to uncheck the install grub option. (The grub stuff did get installed to root of antiX partition despite the error)
3. Rebooted into siduction, ran update-grub as root user and rebooted and antiX appears in the grub options and boots successfully.
Test 3.
1. Installed latest antiX-base to sda4 and chose to uncheck the install grub option.
2. Installed latest siduction to sda1.
3. siduction grub2 picks up antiX and labels it correctly.
Test 4.
1. Installed latest antiX-base to sda4 and chose to uncheck the install to MBR option, got an error and then chose to uncheck the install grub option. (The grub stuff did get installed to root of antiX partition despite the error)
2. Installed latest siduction to sda1.
3. siduction grub2 picks up antiX and labels it correctly.
So it seems that grub does not need to be installed anywhere for grub2 to pick it up after an upgrade-grub (or alternatively I suppose manually adding antiX to grub2 menu)
Now, as I don't have windows on any of my boxes, is it possible to boot linux from a windows bootloader?
I did this in Virtualbox, so I presume it should work on a real hard drive.
Test 1
1. Installed latest siduction to sda1.
2. Installed latest antiX-base to sda4 and chose to uncheck the install grub option.
3. Rebooted into siduction, ran update-grub as root user and rebooted and antiX appears in the grub options and boots successfully.
Test 2.
1. Installed latest siduction to sda1.
2. Installed latest antiX-base to sda4 and chose to uncheck the install to MBR option, got an error and then chose to uncheck the install grub option. (The grub stuff did get installed to root of antiX partition despite the error)
3. Rebooted into siduction, ran update-grub as root user and rebooted and antiX appears in the grub options and boots successfully.
Test 3.
1. Installed latest antiX-base to sda4 and chose to uncheck the install grub option.
2. Installed latest siduction to sda1.
3. siduction grub2 picks up antiX and labels it correctly.
Test 4.
1. Installed latest antiX-base to sda4 and chose to uncheck the install to MBR option, got an error and then chose to uncheck the install grub option. (The grub stuff did get installed to root of antiX partition despite the error)
2. Installed latest siduction to sda1.
3. siduction grub2 picks up antiX and labels it correctly.
So it seems that grub does not need to be installed anywhere for grub2 to pick it up after an upgrade-grub (or alternatively I suppose manually adding antiX to grub2 menu)
Now, as I don't have windows on any of my boxes, is it possible to boot linux from a windows bootloader?
-
Posts: 75
- Joined: 18 Jan 2012
#7
I dual boot Windows 7 - update-grub on GRUB2 also adds a menu entry for Windows.
-
Posts: 325
- Joined: 04 Nov 2011
#8
Test antiX12 and grub2
(It's no fun if the forum software designed characters and words are not accepted - such as @dark-D I wrote)
Hi anti,
the antiX-base-486-installation of 2012 5, on partition 10 of my multi-boot system, I have now successfully fitted with Grub 2.
What have I done:
apt-get update && apt-get dist-upgrade (very important)
reboot
rm-rf .... grub
apt-get purge grub-gfxboot (non-functioning Grub1 away)
apt-get install grub2
the question of the place: dev sda10 selected
ignored because of the gripe of block lists
update-grub
Restart with sda1 = siduction
nano-w etc grub.d 40_custom > to test chainload entry complements theseRestart with sda
the menu item > antiX is ok and starts
the menu item > chainload antiX is ok and starts
with the chain-load antiX12 I get to the boot menu and can launch the new Grub2 all registered systems here, even retroactively back to sda = siduction.
(@ anti,
maybe they can put the signs up? I do not know what else to do. __{{emoticon}}__ )
(It's no fun if the forum software designed characters and words are not accepted - such as @dark-D I wrote)
Hi anti,
the antiX-base-486-installation of 2012 5, on partition 10 of my multi-boot system, I have now successfully fitted with Grub 2.
What have I done:
apt-get update && apt-get dist-upgrade (very important)
reboot
rm-rf .... grub
apt-get purge grub-gfxboot (non-functioning Grub1 away)
apt-get install grub2
the question of the place: dev sda10 selected
ignored because of the gripe of block lists
update-grub
Restart with sda1 = siduction
nano-w etc grub.d 40_custom > to test chainload entry complements these
Code: Select all
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry"Mageia2 chainloaded" {
root=(hd0,7)
chainloader +1
}
menuentry"antiX12 chainloaded" {
root=(hd0,10)
chainloader +1
}
the menu item > antiX is ok and starts
the menu item > chainload antiX is ok and starts
with the chain-load antiX12 I get to the boot menu and can launch the new Grub2 all registered systems here, even retroactively back to sda = siduction.
(@ anti,
maybe they can put the signs up? I do not know what else to do. __{{emoticon}}__ )
-
Posts: 325
- Joined: 04 Nov 2011
#9
he grub.cfg can not send (because of the characters)