anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#1
I need some testers.

Run latest version of antiX-12 live, download the antix-installer.deb from here:


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepisimo.com/antix/Testing/"
linktext was:"http://www.mepisimo.com/antix/Testing/"
====================================


Install the .deb

Code: Select all

dpkg -i antix-installer_0.2.8_all.deb
Run the installer.

Now when you get to the part about installing grub.

1. If you use a bootloader already and do not want to install grub at all, do so and post what you do to get antiX to boot. (Let me know if you use grub2 for example).

2. If you use a bootloader already and want to install to root partition, just unclick MBR and grub should install to root partition. Check that this actually works on reboot and again let me know what bootloader you are using. Especially useful is feedback from those not using grub.

3. Install grub to MBR.

You can do this in virtualbox or to an installed hard drive.
Posts: 279
afab4
Joined: 17 Oct 2009
#2
anticapitalista wrote: 2. If you use a bootloader already and want to install to root partition, just unclick MBR and grub should install to root partition. Check that this actually works on reboot and again let me know what bootloader you are using. Especially useful is feedback from those not using grub.
I installed to sda2 partition. Unclicked MBR to install to root.
The installer indicated it was installing grub to sda2.
I found /boot/grub/ but no menu.lst in the grub directory, only menu.lst.example.
edit:
I modified my menu.lst on the sda1 partition to boot sda2 and the 3.3.5 kernel and when I booted into my new install on sda2, menu.lst was present.
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#3
afab4, if the menu.lst had been created at installation, would you have needed to modify grub on sda1 or would it have been picked up?
Posts: 279
afab4
Joined: 17 Oct 2009
#4
anticapitalista wrote:afab4, if the menu.lst had been created at installation, would you have needed to modify grub on sda1 or would it have been picked up?

I still would have to modify grub on sda1. It would be a simple copy/paste as root though. I have never been able to get the legacy grub in antiX to pick up any installs on my other partitions. i have installed some grub2 stuff like debian mint and i believe aptosid & siduction to root and update-grub on my sda1 didn't pick those up either. I had to look at their configurations and figure out how to modify menu.lst to get them to boot.
Posts: 279
afab4
Joined: 17 Oct 2009
#5
anticapitalista wrote: 3. Install grub to MBR.

You can do this in virtualbox or to an installed hard drive.
On my second sda2 test install. grub installed OK to my MBR.
It did not pick up my sda1 installation. I had to edit menu.lst to do so.
Once i was able to boot up my sda1 install I then ran grub-install /dev/sda to get me back to square one.
grub install didn't pick up the sda2 installation either.
Posts: 325
male
Joined: 04 Nov 2011
#6
Unfortunately I have no time to press for free antiX12 ...
afab4 wrote: I had to look at their configurations and figure out how to modify menu.lst to get them to boot.
My entry in the menu.lst of antiXM11 to start the aptosid-Grub2 is:

Code: Select all

timeout 30
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title       Chainload into GRUB v2
root        (hd1,0)
kernel      /boot/grub/core.img

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
...
successfully
For a quick overview helps me a script:

Code: Select all

root@antiXM11:/home/male# ./Grub_finden.sh
----------------------------------
/dev/sda    GRUB gefunden
/dev/sda1    Kein GRUB gefunden
/dev/sda2    Kein GRUB gefunden
/dev/sda5    Kein GRUB gefunden
/dev/sda6    Kein GRUB gefunden
/dev/sda7    Kein GRUB gefunden
/dev/sda8    GRUB gefunden
----------------------------------
/dev/sdb    Kein GRUB gefunden
/dev/sdb1    GRUB gefunden
/dev/sdb2    Kein GRUB gefunden
/dev/sdb3    Kein GRUB gefunden
/dev/sdb5    Kein GRUB gefunden
/dev/sdb6    GRUB gefunden
----------------------------------
If someone wants it ... __{{emoticon}}__

The sets chainload always precedes another bootloader in the partition to be started.

In contrast, Grub2 v1.99-22, either automatically or manually in the / etc/grub.d/40_custom
or your own script
easy to use. __{{emoticon}}__
Posts: 15
meandean
Joined: 14 Jul 2012
#7
see below....
Last edited by meandean on 21 Jul 2012, 00:04, edited 1 time in total.
Posts: 15
meandean
Joined: 14 Jul 2012
#8
lenovo thinkpad R61e laptop
sda1 20g stuff
sda2 30g debian wheezy
sda3 30g antix

I used a usb stick not a cd.

1. If you use a bootloader already and do not want to install grub at all, do so and post what you do to get antiX to boot. (Let me know if you use grub2 for example).
I boot into debian and run update-grub.


3. Install grub to MBR.
It picks up my debian install and adds a title, kernel, and initrd line but no root line.

Code: Select all

title debian
kernel /vmlinuz root=/dev/sda2 ro quiet
initrd /initrd.img
but to work it needs to be

Code: Select all

title debian
root (hd0,1)
kernel /vmlinuz root=/dev/sda2 ro quiet
initrd /initrd.img
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#9
meandean

3 - So Debian needs the root (hdx,y) line. antiX doesn't need it.
Posts: 15
meandean
Joined: 14 Jul 2012
#10
I would think any linux would need a root entry if it is not on the same partition where the grub configs file (grub root) are located.
Posts: 516
oldhoghead
Site Admin
Joined: 01 Oct 2007
#11
when I installed antiX-12 rc2 via cd, I also had to change my menu.lst to reflect the

Code: Select all

root (hd0,1)
for antiX 11

and one for antiX 8.5

otherwise I got a file 15 error

cheers,
ohh
Posts: 1,139
masinick
Joined: 26 Apr 2008
#12
For what it is worth, when I use antiX, I invoke it from a boot loader in the MBR associated with Debian Sid, and I use GRUB 2. Seems to work fine, though I believe that once or twice, I have had to run an update-grub on antiX in order to see a new kernel, but that was back when we were testing kernels; not sure whether that even applies any more or not. I'll keep my eyes open if I see any unusual behavior or anything that may need tweaking, but other than a few testing quirks like that, everything has functioned exactly as I would expect, and it has been VERY good.
Posts: 325
male
Joined: 04 Nov 2011
#13
Of course, an update-grub2 grub in the MBR is the necessary, if a new kernel to be loaded into antiX.

Is with me otherwise. __{{emoticon}}__