topic title: Installing a frugal install of Antix
-
Posts: 177
- Joined: 04 Mar 2014
#1
I have a Dell 3000 computer. At the moment I am booted into the Antix Live CD. I have four partitions on my internal HD. sda1 (Crunchbang), sda2 (Manjaro openbox), sda3 (swap), sda4 (Manjaro xfce). I plan on using one of the Manjaro partitions for the frugal install. If you need any more info, please let me know. So, what are the steps involved? Thanks!! __{{emoticon}}__
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#2
1 - Make sure that you know which of those distros is controlling grub and which version of grub is used ie grub-legacy or grub2?
2 - Go to /live/boot-dev/antiX on the cd/dvd and copy initrd.gz, linuxfs and vmlinuz to a folder called antiX-13.2 (or whatever) on the partition you want to run frugal on. You can, for example, create a folder in sda2 (not /home. but /) called antiX-13.2 and copy initrd.gz, linuxfs and vmlinuz off the live cd/dvd to there).
3. Once done you need to edit the grub menu used to boot your installed distros. It is different depending on whether grub-legacy or grub2 is used.
2 - Go to /live/boot-dev/antiX on the cd/dvd and copy initrd.gz, linuxfs and vmlinuz to a folder called antiX-13.2 (or whatever) on the partition you want to run frugal on. You can, for example, create a folder in sda2 (not /home. but /) called antiX-13.2 and copy initrd.gz, linuxfs and vmlinuz off the live cd/dvd to there).
3. Once done you need to edit the grub menu used to boot your installed distros. It is different depending on whether grub-legacy or grub2 is used.
-
Posts: 177
- Joined: 04 Mar 2014
#3
Manjaro is controlling Grub so I would imagine it is Grub2? Not sure how to edit Grub2.
Thanks!
I will do this tomorrow and post back.
Thanks!
I will do this tomorrow and post back.
-
Posts: 177
- Joined: 04 Mar 2014
#4
I deleted the Manjaro partitions along with the Grub menu. I created a new grub legacy menu but am not sure what to add when it comes to the Antix entry.
-
Posts: 177
- Joined: 04 Mar 2014
#5
This is the entry I have in my menu.lst file. It doesn't work. When I boot up and select it, all I get is a reboot or shutdown option.
Code: Select all
title AntiX Linux (sda4/antiX)
uuid 71d533e4-184d-44f2-972b-3bf07754df26
kernel /antiX/vmlinuz root=/dev/sda4 ro
initrd /antiX/initrd.gz
-
Posts: 1,308
- Joined: 31 Aug 2009
#6
First, I suggest you use any directory name *except* /antiX. AntiC's suggestion of using /antiX-13.2 was good. So make that directory and copy or move these files into it: linuxfs, vmlinuz and initrd.gz.
Here is a legacy grub entry that should work (or at least be close to working):
The"root(0,3)" line tells Grub to look for the kernel and the initrd on /dev/sda4. Legacy grub should create a file like
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.gnu.org/software/grub/manual/legacy/Device-map.html"
linktext was:"/boot/grub/device.map"
====================================
that will verify which root() command to use for /dev/sda4.
Using a directory other than /antiX helps avoid future conflicts when you are booting other antiX Live media. The kernel and initrd lines explicitly tell the bootloader where to find the kernel and initrd.gz files on /dev/sda4. The"bdir=antiX-13.2" and"from=hd" parameters tell our live-init script where to find the linuxfs file.
A slight improvement to this would be to replace"from=hd" with either"blab=xxx" or"buuid=yyy" where"xxx" is the disk label of /dev/sda4 and"yyy" is the UUID of /dev/sda4. The difference is that with"from=hd" we will scan every hard drive partition looking for /antiX-13.2/linuxfs. If you give us the label or the UUID then we will only look on partitions that have that label or that UUID.
The"antiX=MLX" parameter turns off some startup services for faster booting. It is shorthand for"mean lean Xtralean".
Once you get an entry like this to work, it will be easy to show you had to modify it to add persistence or other tricks.
Here is a legacy grub entry that should work (or at least be close to working):
Code: Select all
title AntiX Linux (sda4/antiX)
root(0,3)
kernel /antiX-13.2/vmlinuz quiet bdir=antiX-13.2 from=hd antiX=MLX
initrd /antiX-13.2/initrd.gz
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.gnu.org/software/grub/manual/legacy/Device-map.html"
linktext was:"/boot/grub/device.map"
====================================
that will verify which root() command to use for /dev/sda4.
Using a directory other than /antiX helps avoid future conflicts when you are booting other antiX Live media. The kernel and initrd lines explicitly tell the bootloader where to find the kernel and initrd.gz files on /dev/sda4. The"bdir=antiX-13.2" and"from=hd" parameters tell our live-init script where to find the linuxfs file.
A slight improvement to this would be to replace"from=hd" with either"blab=xxx" or"buuid=yyy" where"xxx" is the disk label of /dev/sda4 and"yyy" is the UUID of /dev/sda4. The difference is that with"from=hd" we will scan every hard drive partition looking for /antiX-13.2/linuxfs. If you give us the label or the UUID then we will only look on partitions that have that label or that UUID.
The"antiX=MLX" parameter turns off some startup services for faster booting. It is shorthand for"mean lean Xtralean".
Once you get an entry like this to work, it will be easy to show you had to modify it to add persistence or other tricks.
-
Posts: 177
- Joined: 04 Mar 2014
#7
Here is what my menu.lst file looks like so far based on your recomendations. I'm going to see if it works.
Code: Select all
# menu.lst produced by grub4dosconfig-v1.7.2
color white/blue black/cyan white/black cyan/black
timeout 10
default 0
# Full installed Linux
title Linux (sda2)
uuid 8dd05fe1-471c-4c8e-972e-ff0549c9a810
kernel /vmlinuz root=/dev/sda2 ro
initrd /initrd.img
title AntiX Linux (sda4/antiX)
root(0,3)
kernel /antiX-13.2/vmlinuz quiet bdir=antiX-13.2 buuid=71d533e4-184d-44f2-972b-3bf07754df26 antiX=MLX
initrd /antiX-13.2/initrd.gz
# Frugal installed Puppy
title Lupu 528 (sda2/pup528)
find --set-root --ignore-floppies --ignore-cd /pup528/initrd.gz
kernel /pup528/vmlinuz psubdir=pup528 pmedia=atahd pfix=fsck
initrd /pup528/initrd.gz
title Lupu 528 (sda2/pup528) RAM mode\nBoot up Puppy without pupsave
find --set-root --ignore-floppies --ignore-cd /pup528/initrd.gz
kernel /pup528/vmlinuz psubdir=pup528 pmedia=atahd pfix=ram,fsck
initrd /pup528/initrd.gz
title Puppy precise 5.7 (sda2/puppre3000)
find --set-root --ignore-floppies --ignore-cd /puppre3000/initrd.gz
kernel /puppre3000/vmlinuz psubdir=puppre3000 pmedia=atahd pfix=fsck
initrd /puppre3000/initrd.gz
# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on
# Boot from Partition Boot Sector
title Linux (sda2:PBS)
uuid 8dd05fe1-471c-4c8e-972e-ff0549c9a810
chainloader +1
# additionals
title Find Grub2\nBoot up grub2 if installed
find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
kernel /boot/grub/core.img
title Grub4Dos commandline\n(for experts only)
commandline
title Reboot computer
reboot
title Halt computer
halt
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#8
grub4dos is what Puppy uses right?
I hope it works, but the syntax may be differenr from ordinary grub. Roky is our puppy /antiX man.
I hope it works, but the syntax may be differenr from ordinary grub. Roky is our puppy /antiX man.
-
Posts: 177
- Joined: 04 Mar 2014
#9
It's not working but that's OK because I am learning. I have to tell you that the way I created the menu.lst file was by booting into Puppy Linux from CD and letting Grub4Dos build the file. Grub4Dos saves the menu.lst file in sda1. Am I going about it the wrong way? I don't mind starting all over again with whatever suggestions you can give me.
At the moment this is what I have done:
I have a partition (sda4) labelled Antix. On that partition I have a directory names antix-13.2 that contain the files initrd.gz, vmlinuz and linusfs.
I am currently in Crunchbang (sda2).
At the moment this is what I have done:
I have a partition (sda4) labelled Antix. On that partition I have a directory names antix-13.2 that contain the files initrd.gz, vmlinuz and linusfs.
I am currently in Crunchbang (sda2).
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#10
When you boot the laptop, the boot menu belongs to which OS? That is the one that needs editing.
-
Posts: 177
- Joined: 04 Mar 2014
#11
The boot menu was created with Grub4Dos when I was booted into the Puppy Linux CD.
I just thought of something else, and I want your feedback on this. What if I do a full Antix install on sda4 instead of a frugal one for now. This will generate a new grub menu that we can use to modify when I do the frugal install. Does that sound viable? This way, Puppy Linux and Grub4Dos are out of the picture and just Antix is involved.
I just thought of something else, and I want your feedback on this. What if I do a full Antix install on sda4 instead of a frugal one for now. This will generate a new grub menu that we can use to modify when I do the frugal install. Does that sound viable? This way, Puppy Linux and Grub4Dos are out of the picture and just Antix is involved.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#12
Yes, you can do that. Make sure you install grub to MBR and then it will be its (antiX) grub-legacy controlling the booting. Do keep a copy of your old grub since the antiX grub may not pick up all the entries.
MX-14 uses grub2 and if you decide to install that, it should pick up all the OS installed.
MX-14 uses grub2 and if you decide to install that, it should pick up all the OS installed.
-
Posts: 177
- Joined: 04 Mar 2014
#13
OK. I will install Antix 13.2 on the Dell 3000. It should pick up my Crunchbang installation as well.
I will post back once I have this working fine and then we can procedd with the Frugal install. Thanks for helping me with this!
I will post back once I have this working fine and then we can procedd with the Frugal install. Thanks for helping me with this!
-
Posts: 177
- Joined: 04 Mar 2014
#14
I was able to successfully install Antix Full 13.2 into sda4. The boot menu works fine as well for both Antix and Crunchbang.
I also created a folder called antix13.2 at the root level of sda4 and put the required files from the Antix CD into the folder. Now, where do we go from here? Where does Antix install the Grub menu? I selected sda MBR as the options when installing Antix.
I also created a folder called antix13.2 at the root level of sda4 and put the required files from the Antix CD into the folder. Now, where do we go from here? Where does Antix install the Grub menu? I selected sda MBR as the options when installing Antix.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#15
Ok, you need to edit /boot/grub/menu.lst on the antiX partition (sda4)
Add:
title AntiX Linux Frugal
root(0,3)
kernel /antiX-13.2/vmlinuz quiet bdir=antiX-13.2 from=hd antiX=MLX
initrd /antiX-13.2/initrd.gz
Or if that doesn't work, try this
title AntiX Linux Frugal
root(0,3)
kernel /antiX-13.2/vmlinuz quiet bdir=antiX-13.2 bdev=sda4 antiX=MLX
initrd /antiX-13.2/initrd.gz
bdev=sda4 could also be changes to buuid=XXXXX (the uuid for sda4 -see blkid)
Add:
title AntiX Linux Frugal
root(0,3)
kernel /antiX-13.2/vmlinuz quiet bdir=antiX-13.2 from=hd antiX=MLX
initrd /antiX-13.2/initrd.gz
Or if that doesn't work, try this
title AntiX Linux Frugal
root(0,3)
kernel /antiX-13.2/vmlinuz quiet bdir=antiX-13.2 bdev=sda4 antiX=MLX
initrd /antiX-13.2/initrd.gz
bdev=sda4 could also be changes to buuid=XXXXX (the uuid for sda4 -see blkid)