question about mkinitcpio wiki

erastus · 2006-10-02 17:12:36

I finally made the switch to kernel 2.6.18 and mkinitcpio this weekend. All is well as far as I know, but a part of the wiki was a little confusing at first. I'd like to edit the section, but being fairly new here, I want to be careful about messing with stuff! Here is the section I'd like edit:

Modifying fallback image
To change the defaults for the fallback images edit the following files:
kernel26 --> '/boot/mkinitcpio-kernel26.conf'
kernel26beyond --> '/boot/mkinitcpio-kernel26beyond.conf
and set them to NoUpgrade = in '/etc/pacman.conf'. Note that these should be sane unless you require a special setup such as lvm or raid.

I think for clarity it might be better said like this:

To change the defaults for the fallback images, go to the NoUpgrade section in /etc/pacman.conf, and add one of the following lines (depending on which kernel you are using):
NoUpgrade = /boot/mkinitcpio-kernel26.conf
... or
NoUpgrade = /boot/mkinitcpio-kernel26beyond.conf

Does that make sense?

Also, I searched the wiki and forum for a definition of "sane", and every reference to it involved configuring a scanner. So I didn't understand what "Note that these should be sane" means. Can you explain, please.

I'm not complaining -- just trying to put my inexperience to good use so that future newbies benefit. I'd like to contribute if it's ok to do so.

Thanks.

lucke · 2006-10-02 17:42:14

"Sane" is simply an antonym (word of opposite meaning) of "insane" (which you are probably familiar with) and in this example it denotes "reasonable". Well, that's if you're asking for a dictionary definition ;-)

As for the changes, I think your reasoning is sane. And so is the will to contribute, that's the basis of such communities like ours ;-)

phrakture · 2006-10-02 17:55:54

Side note though. The fallback stuff should probably not be edited... the fallback should "just work" whenever possible. If you need to make changes, they should be in /etc/mkinitcpio.conf

erastus · 2006-10-02 21:00:32

lucke:
> As for the changes, I think your reasoning is
> sane. And so is the will to contribute,

So I was over-analyzing about "sane". I'll have to talk with my analyst about this.

prakture:
> If you need to make changes, they should be
> in /etc/mkinitcpio.conf

Ok, well good thing I asked. I don't know that I _need_ to make changes; just wanted to make existing directions more clear. I'll have a look at that file and see what's in there. Thanks.

tomk · 2006-10-02 22:06:46

Your suggested alternative text is incorrect - in summary, it says that adding the NoUpgrade line changes the fallback defaults. Notwithstanding phrakture's sound advice, the only way to change the fallback defaults is to edit the file, and you have omitted that step. Personally, I find the original version quite clear, although adding your "depending which kernel..." phrase would probably be helpful.

erastus · 2006-10-03 02:52:42

I think since you guys are working with this stuff intimately, you're not seeing my question from a non-expert point of view.

First of all, I don't know how 'fallback' works. I'm used to Debian-based distros, where I keep the old kernel available in my GRUB menu.lst. Each kernel and img file has a unique name. That is my "fallback".

As an Arch newbie I have to read the Wiki literally -- it's all I have to go on. Please explain what this means:

Modifying fallback image
To change the defaults for the fallback images edit the following files:
kernel26 --> '/boot/mkinitcpio-kernel26.conf'
kernel26beyond --> '/boot/mkinitcpio-kernel26beyond.conf

Just exactly what am I editing in /boot/mkinitcpio-kernel26.conf ? There's nothing in there about 'kernel26', and nothing about 'fallback'. (I'm including the file below.)

and set them to NoUpgrade = in '/etc/pacman.conf'.

It says "and". So there are 2 steps here? First edit /boot/mkinitcpio-kernel26.conf, and then add a NoUpgrade line in pacman.conf?

I hope this explains my question better. Thanks.

Here is my /boot/mkinitcpio-kernel26.conf :

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES=""

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish.  This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
#BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
#    FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
#    This setup specifies all modules in the MODULES setting above.
#    No raid, lvm, or encrypted root is needed.
#    HOOKS="base"
#
#    This setup will autodetect all modules for your system and should
#    work as a sane default
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
#    This setup will generate a 'full' image which supports most systems.
#    No autodetection is done.
#    HOOKS="base udev ide scsi sata usb filesystems"
#
#    This setup assembles an ide raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev ide filesystems raid encrypt"
#
#    This setup loads an LVM volume group on a usb device.
#    HOOKS="base udev usb filesystems lvm"
HOOKS="base udev ide scsi sata usbinput raid filesystems"

tomk · 2006-10-03 08:34:54

erastus wrote:

First of all, I don't know how 'fallback' works.

In this context, fallback refers to an initcpio image which includes every possible module that could be required at boot time, as opposed to the customised image that you would normally use.

erastus wrote:

Please explain what this means:
Modifying fallback image
To change the defaults for the fallback images edit the following files:
kernel26 --> '/boot/mkinitcpio-kernel26.conf'
kernel26beyond --> '/boot/mkinitcpio-kernel26beyond.conf
Just exactly what am I editing in /boot/mkinitcpio-kernel26.conf ?

Most likely nothing, as mentioned above. In the highly unlikely situation where you would need to edit this file, you would change the MODULES=, BINARIES=, FILES=, and/or HOOKS= lines.

erastus wrote:

and set them to NoUpgrade = in '/etc/pacman.conf'.
It says "and". So there are 2 steps here? First edit /boot/mkinitcpio-kernel26.conf, and then add a NoUpgrade line in pacman.conf?

Yes.

As you are a self-proclaimed Arch newbie, I would highly recommend familiarising yourself with Arch basics. In this case, a quick read of the pacman man page would have clarified the second point for you.

erastus · 2006-10-03 12:00:35

Ok, fair enough. I admit I haven't read man pacman, although I did read the pacman wiki, and many other others, looking for answers to this question. I thought the section labeled "Modifying fallback image" was the next step in a series of steps for properly installing and configuring mkinitcpio.

kozaki · 2006-11-13 18:26:55

A fallback image should have been created when you installed kernel26 or kernel26beyond but in case you want to re-generate it
mkinitcpio -c /boot/mkinitcpio-kernel26.conf -g /boot/kernel26.img
for beyond
mkinitcpio -c /boot/mkinitcpio-kernel26beyond.conf -g /boot/kernel26beyond.img

Am I dumb or it should be

mkinitcpio -c /boot/mkinitcpio-kernel26.conf -g /boot/kernel26-fallback.img
and/or for beyond :
mkinitcpio -c /boot/mkinitcpio-kernel26beyond.conf -g /boot/kernel26beyond-fallback.img

veek · 2006-11-13 19:42:40

kozaki, I think you're right about that.

Arch Linux

#1 2006-10-02 17:12:36

question about mkinitcpio wiki

#2 2006-10-02 17:42:14

Re: question about mkinitcpio wiki

#3 2006-10-02 17:55:54

Re: question about mkinitcpio wiki

#4 2006-10-02 21:00:32

Re: question about mkinitcpio wiki

#5 2006-10-02 22:06:46

Re: question about mkinitcpio wiki

#6 2006-10-03 02:52:42

Re: question about mkinitcpio wiki

#7 2006-10-03 08:34:54

Re: question about mkinitcpio wiki

#8 2006-10-03 12:00:35

Re: question about mkinitcpio wiki

#9 2006-11-13 18:26:55

Re: question about mkinitcpio wiki

#10 2006-11-13 19:42:40

Re: question about mkinitcpio wiki

Board footer