Posts: 10
abcdelix
Joined: 08 Oct 2012
#1
Hi all !
I'm trying to install AntiX12-core as a frugal install on a logical partition /dev/sda5 with the Grub2 bootloader from Debian Squeeze.
I used the"frugal" How-To article of the wiki and modified it to Grub2. I put the content of the /antiX directory in the top directory / of the logical partition. The kernel image and the initrd are found and the booting starts. In the cheat code line I used root=UUID=...... and skipped bdev=sda5.
However, I got the error message/warning that with bdir=/ the /linuxfs file is not found.

So, my questions are :
-- do I have to skip the root=UUID=... cheat code in the linux .... line of the menuentry ?
-- must I set or skip the bdev=sda5 code and is this the correct code for the logical device /dev/sda5 ?
-- what is the correct bdir= cheat code I need that the linuxfs is found ?

Thanks in advance,
abcdelix
Posts: 10
abcdelix
Joined: 08 Oct 2012
#2
after spending several hours on it and trying again and again, I figured it out....

IT WAS A TYPO __{{emoticon}}__

so I can answer the questions by myself :
-- the root=UUID= is okay
-- bdev=sda5 is okay
-- bdir=/ works in my configuration

just hope, nobody spent much time on this questions..
this is really not the best start on this forum __{{emoticon}}__
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#3
abcdelix wrote:-- do I have to skip the root=UUID=... cheat code in the linux .... line of the menuentry ?
the root= parameter should have no (positive) effect on a frugal install. the equivalent would be buuid=... which I suggest you use.
-- must I set or skip the bdev=sda5 code and is this the correct code for the logical device /dev/sda5 ?
Actually buuid= blabel= would be slightly preferred over bdev in case you add more disks or something but if bdev works then it is fine.
-- what is the correct bdir= cheat code I need that the linuxfs is found ?

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.mepis.org/index.php?title=Frugal_install"
linktext was:"This wiki article"
====================================
on frugal installs suggests that you create a directory on the target partition and put the contents of the /antiX directory into that directory.

There are several advantages to using a directory with a unique name:
  1. You can have more than one frugal install on the same partition
  2. Booting is"safer" in the sense that there is less room for finding the wrong kernel, etc
  3. There is less chance of you confusing a future LiveCD/USB (from antiX or other distros)
  4. Years later you will still know what the vmlinuz, initrd.gz, and linuxfs files are for
To do a Live/Frugal boot, you only need three files: vmlinuz (the kernel), initrd.gz (initial filesystem and instructions), and linuxfs (the real Linux filesystem). You usually cannot mix and match these files. They come as a matched set. It makes sense to put all three in one directory. It also makes sense for the name of that directory to contain the antiX version information such as:

Code: Select all

antiX-12-base
if nothing else, this lets people down the road know what is in the vmlinuz, initrd.gz, and linuxfs files in that directory without having to do a bunch of detective work.

My suggestions for a frugal install are:
  1. Use a unique boot directory (bdir) that includes the antiX version info
  2. Use a boot label (blab) or boot uuid (buuid) to specify the boot partition
Over the past few years there have been significant improvements in how antiX Live/Frugal systems boot. Now there is seldom a need to scan all partitions to look for a particular file (/antiX/antiX) which caused so much trouble in the past. Using bdir= together with blab= or buuid= lets you take full advantage of those improvements.

BTW: You can still scan for a boot device if you provide a from= boot parameter and no bdev, blab, or buuid. There are three valid options for the from= parameter: cd, usb, and hd. You can combine them with a comma. For example:

Code: Select all

from=usb,cd
will cause us to first scan usb devices and then removable devices. Internal hard drives won't be touched.

You can also combine the from= with bdev, blab, or buuid but it only really makes sense to combine from= with blab because disk labels are not unique. For example:

Code: Select all

from=usb blab=LiveUSB
will look for a partition on a usb drive that has the label"LiveUSB". Any partitions on an internal hard drive will be ignored even if they are labelled"LiveUSB". This should be useful for LiveUSBs. For example, if something else is wrong and the boot directory can't be found on a usb drive, we won't start looking at all partitions on all the internal drives.
Posts: 10
abcdelix
Joined: 08 Oct 2012
#4
thanks for the detailed infos.
I'll change my setup accordingly.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#5
I didn't mean to pick on you (you aren't reacting like I was). This stuff is not well documented yet so I wanted to put it here in case other people doing a frugal install read this thread.