Grub-mkconfig Menu Changes

hiiii all

I had installed Windows 7 on /dev/sda1 and /dev/sda2 and then I installed Centos 7.
Since then I cant find Windows entry in the Grub.
And i had tried to use all kind of solution found on the net I still cant see any entry.
I had edited 40_custom script adding:

cat <<EOF
menuentry "windows 7" {
insmod part_msdos
insmod ntfs
set root='hd0,msdos1'
search --no-floppy --fs-uuid --set=root FCDAE998DAE95006
chainloader +1
}
EOF

then this command grub2-mkconfig -o /boot/grub2/grub2.cfg

[root@localhost]# grub2-mkconfig -o /boot/grub2/grub2.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-123.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-123.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-93890f189dec4b309c004fdce969ca5a
Found initrd image: /boot/initramfs-0-rescue-93890f189dec4b309c004fdce969ca5a.img

then this
[root@localhost]# tail -10 /boot/grub2/grub.cfg
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
[root@localhost]#


Still cant find windows in grub
please help me with this guys
thanks

Ubuntu 12.04

I installed updates, which included a new kernel. I went to remove one of the older kernels and got:

Code:

jnojr@DEV:~$ sudo apt-get purge linux-image-3.13.0-46-generic
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-3.13.0-46-generic gir1.2-ubuntuoneui-3.0 wireless-regdb iw
  linux-headers-3.13.0-46 crda linux-headers-3.5.0-23-generic lesstif2
  linux-headers-3.5.0-23 libubuntuoneui-3.0-1 thunderbird-globalmenu
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  linux-image-3.13.0-46-generic*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 197 MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 340656 files and directories currently installed.)
Removing linux-image-3.13.0-46-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
update-initramfs: Deleting /boot/initrd.img-3.13.0-46-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.13.0-51-generic
Found initrd image: /boot/initrd.img-3.13.0-51-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found Windows Vista (loader) on /dev/sda1
Found CentOS release 6.6 (Final) on /dev/sdb1
Found linux image: /boot/vmlinuz-3.13.0-51-generic
Found initrd image: /boot/initrd.img-3.13.0-51-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found Windows Vista (loader) on /dev/sda1
Found CentOS release 6.6 (Final) on /dev/sdb1
Found memtest86+ image: /boot/memtest86+.bin
error: syntax error.
error: Incorrect command.
error: syntax error.
error: Incorrect command.
error: syntax error.
error: line no: 146
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
done
Purging configuration files for linux-image-3.13.0-46-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic

I have no idea how I'd "ensure there are no errors" in the /etc/grub related files... I have no idea what's supposed to be there. Looking at the line it's complaining about in /boot/grub/grub.cfg.new doesn't tell me anything. How do i find out what it's unhappy about?

I have setup a dual boot system with Fedora 21 and Arch Linux. The problem is that Fedora doesn't see my encrypted Arch installation. The installations are on separate partitions and do not share anything apart from hard disk space. I have run the following commands as root in Fedora:

Code:

grub2-install /dev/sda

Code:

os-prober

Code:

grub2-mkconfig -o /boot/grub2/grub.cfg

When I rebooted, Fedora was the only OS entry showing in the GRUB menu.

There was a suggestion from one of the members of the Arch forums that I should write the entry myself into /etc/grub.d/40_custom and then re-build the grub configuration or take the Arch entry from Arch's /boot/grub/grub.cfg and just paste it into the 40_custom in Fedora and rebuild.

How do I boot from a live Arch USB stick into the installed Arch and do as stated above? How would it work? Thanks in advance for your replies.

These instructions originate from https://www.linkedin.com/pulse/20140...nvidia-drivers, but I modified them slightly for my desktop environment (64-bit HP Envy Phoenix 810-135qe w/Intel i7-4770 and HP ZR2440w monitor, nVidia GeForce GTX645, Red Hat Enterprise Linux 7.1 w/Gnome3).

The following procedures replace the nouveau drivers with kmod-nvidia drivers from ElRepo.

Install the repository ElRepo from: http://elrepo.org/tiki/tiki-index.php

Install the package nvidia-detect from within Applications>SystemTools>Software

From within the terminal, enter the command nvidia-detect.
Example:
[anthony@hp810135qe ~]$ nvidia-detect
Output is...
Probing for supported NVIDIA devices...
[10de:11c4] NVIDIA Corporation GK106 [GeForce GTX 645 OEM]
This device requires the current 346.59 NVIDIA driver kmod-nvidia

For my system the following software packages will apply (yours maybe slightly different, the key is to note the ###.## version identified for your system using nvidia-detect as explained above): kmod-nvidia-346.59-1.el7.elrepo (64-bit), nvidia-x11-drv-32bit-346.59-1.el7.elrepo (64-bit), nvidia-x11-drv-346.59-1.el7.elrepo (64-bit)

Now do the following steps in the sequence indicated:

1. Disable X Windows

a) open a terminal and "su" or "sudo -i"

b) ln -fs /lib/systemd/system/multi-user.target /etc/systemd/system/default.target

Note: Another way to disable X Windows is to do the following from within the Terminal # systemctl set-default multi-user.target

To later change back to booting into graphical mode, substitute 'graphical.target' for 'multi-user.target' in the above commands.

c) reboot

2. Remove Nouveau

a) rpm -e xorg-x11-drivers xorg-x11-drv-nouveau

Note: Another way to remove Nouveau is to do the following from within the Terminal

$ yum remove xorg-x11-drivers xorg-x11-drv-nouveau xorg-x11-glamor

See http://elrepo.org/tiki/kmod-nvidia which discusses that glamor still causes a conflict with nVidia in RHEL 7

3. Blacklist Nouveau

a) edit /etc/modprobe.d/blacklist.conf and add line:

blacklist nouveau

Note: A way to edit this file is by doing the following:

# vi /etc/modprobe.d/blacklist.conf
(use INSERT key to make changes in vi; add the line

blacklist nouveau

Hit Esc key to escape INSERT mode, then hit SHIFT Z Z to save and exit with the changes. Hitting :q ENTER leaves vi without saving changes.

b) edit /etc/default/grub and append to GRUB_CMDLINE_LINUX:

rd.driver.blacklist=nouveau

Note: A way to edit this file is by doing the following:

# vi /etc/default/grub and append to GRUB_CMDLINE_LINUX:
(use INSERT key to make changes in vi; add the line

rd.driver.blacklist=nouveau

Hit Esc key to escape INSERT mode, then hit SHIFT Z Z to save and exit with the changes. Hitting :q ENTER leaves vi without saving changes.

IMPORTANT NOTE IF YOU HAVE AN ENCRYPTED BOOTUP DRIVE -

If you have an encrypted root drive, remove "rhgb" from GRUB_CMDLINE_LINUX. This will allow you to interact with the encryption passphrase prompt, since Plymouth doesn't seem to run without a framebuffer friendly video driver loaded. IF YOU DON'T THIS, WHEN YOU BOOTUP YOU WILL GET STUCK AT A BLINKING CURSOR AND BLACKSCREEN THAT HAS THE FOLLOWING ERROR MESSAGES:


[5.757276] scsi 7:0:0:0: alua: not attached
[5.759625] sd 7:0:0:0: [sdg] no caching made page found
[5.759668] sd 7:0:0:0: [sdg] assuming drive cache: write through

WHEN THIS HAPPENS IT MEANS PLYMOUTH IS NOT ABLE TO SHOW YOU THE PROMPT FOR ENTERING THE PASSPHRASE FOR THE ENCRYPTED DRIVES. WITHOUT THE PROMPT THE SYSTEM CAN'T ACCEPT THE PASSPHRASE AND YOU ARE STUCK. IF THIS HAPPENS TO YOU, YOU CAN DO CTRL-ALT-DELETE TO REBOOT - THIS ALLOWS YOU TO HIT 'e' AT THE KERNEL LINE IN GRUB TERMINAL TO EDIT (MOST LIKELY THE TOP KERNEL) AND THEN REMOVE 'rhgb' (which stands for Red Hat Graphical Bootsplashcreen or something like that). WHEN DONE HIT THE KEYS 'CTRL X' TO REBOOT - YOU'LL THEN SEE TEXT MESSAGES SCROLLING AND GET AN OPPORTUNITY TO ENTER THE PASSPHRASE. ENTER THE PASSPHRASE AND YOU SHOULD BE GOOD TO GO.

4. Reconfigure the grub.cfg files

Two options for booting nowadays are BIOS and EFI

-If you chose BIOS boot run this command:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Note: I also have this one being auto-updated-configured in my system (?why? It's EFI).

-If EFI boot on CentOS:
# grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg

-If EFI boot on RHEL:
# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
Note: Mine is an EFI system. But I did both this and the BIOS grub.cfg above since it too is being updated by RHEL updates concurrently with the EFI grub.cfg

5. Reboot and Install NVidia Driver - I use ElRepo's kmod-nvidia for this step.

Steps by me to install ElRepo's kmod-nvidia (You should still be in Text mode at this time):

If in multi-user.target mode (text, runlevel 3), then do the following
$ su -
enter root password
# yum install kmod-nvidia - version from above
# yum install nvidia-x11-drv-32bit - version from above (this is for 32bit compatibility)
# yum install nvidia-x11-drv - version from above (this is for Open GL X11 display driver and to be done if kmod didn't already include doing it with the kmod-nvidia installation above)
# exit
$

If still in graphics.target mode (you shouldn't be but if you are) (GUI, runlevel 5),
Use Applications > Software > kmod-nvidia - version from above
Install kmod-nvidia - version from above
Install nvidia-x11-drv-32bit - version from above (this is for 32bit compatibility)
Install nvidia-x11-drv - version from above (this is for Open GL X11 display driver)

6. At this point rebuild initramfs. This recreates initrd w/o nouveau. The existing initrd still has the embedded nouveau drivers if this step is not performed) :

Back up the current initramfs keeping nouveau
# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
Build the new one without nouveau
# dracut /boot/initramfs-$(uname -r).img $(uname -r)

7. Re-Enable X Windows

# systemctl set-default graphical.target

8. Reboot

If you have an encrypted bootup drive, when you bootup you may notice that Plymouth doesn't look so good with its text in a lower resolution and you'll see lines of text scrolling until you get to a stopped cursor waiting for you to enter the passphrase to unencrypt your drive. Maybe eventually there'll be a solution for this to keep things moving with a graphical bootsplash all throughout. Until then, this is a minor inconvenience for me.

Just did an update via terminal:

Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
linux-headers-3.13.0-49 linux-headers-3.13.0-49-generic
linux-image-3.13.0-49-generic linux-image-extra-3.13.0-49-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
fglrx-core linux-headers-3.13.0-53 linux-headers-3.13.0-53-generic
linux-image-3.13.0-53-generic linux-image-extra-3.13.0-53-generic
The following packages will be upgraded:
accountsservice apport apport-gtk fglrx fglrx-amdcccle fuse
libaccountsservice0 libfuse2 liboxideqt-qmlplugin liboxideqtcore0
liboxideqtquick0 libspice-server1 linux-firmware linux-headers-generic
linux-image-generic linux-libc-dev oxideqt-codecs-extra python3-apport
python3-problem-report
19 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 227 MB of archives.
After this operation, 490 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y

It downloaded and unpacked files, everything was automated until it asked for my input before replacing the following files:
I backed them up then chose to replace them:

DKMS: install completed.
update-initramfs: deferring update (trigger activated)
Setting up fglrx (2:15.200-0ubuntu0.3) ...

Configuration file '/etc/ati/amdpcsdb.default'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** amdpcsdb.default (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/amdpcsdb.default ...

Configuration file '/etc/ati/atiapfxx'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** atiapfxx (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/atiapfxx ...

Configuration file '/etc/ati/control'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** control (Y/I/N/O/D/Z) [default=N] ? ^[Y

Configuration file '/etc/ati/control'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** control (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/control ...

Configuration file '/etc/ati/signature'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** signature (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/signature ...

Configuration file '/etc/ati/atiapfxx.log'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** atiapfxx.log (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/atiapfxx.log ...

Configuration file '/etc/ati/atiapfxx.blb'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** atiapfxx.blb (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/atiapfxx.blb ...
Creating backups for the fglrx-core transition
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/fglrx/ld.so.conf because link group x86_64-linux-gnu_gl_conf is broken
Restoring backups for the fglrx-core transition
Setting up fglrx-amdcccle (2:15.200-0ubuntu0.3) ...
Setting up linux-firmware (1.127.12) ...
Setting up linux-headers-3.13.0-53 (3.13.0-53.89) ...
Setting up linux-headers-3.13.0-53-generic (3.13.0-53.89) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic

Good news! Module version for fglrx.ko
exactly matches what is already found in kernel 3.13.0-53-generic.
DKMS will not replace this module.
You may override by specifying --force.
Setting up linux-headers-generic (3.13.0.53.60) ...
Setting up linux-image-extra-3.13.0-53-generic (3.13.0-53.89) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
Generating grub configuration file ...
Found theme: /boot/grub/themes/Zorin/theme.txt
Found linux image: /boot/vmlinuz-3.13.0-53-generic
Found initrd image: /boot/initrd.img-3.13.0-53-generic
Found linux image: /boot/vmlinuz-3.13.0-52-generic
Found initrd image: /boot/initrd.img-3.13.0-52-generic
Found linux image: /boot/vmlinuz-3.13.0-51-generic
Found initrd image: /boot/initrd.img-3.13.0-51-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found linux image: /boot/vmlinuz-3.13.0-46-generic
Found initrd image: /boot/initrd.img-3.13.0-46-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
No volume groups found
Found Windows XP Professional x64 Edition on /dev/sda1
done
Setting up linux-image-generic (3.13.0.53.60) ...
Setting up oxideqt-codecs-extra:amd64 (1.7.8-0ubuntu0.14.04.1) ...
Setting up liboxideqtcore0:amd64 (1.7.8-0ubuntu0.14.04.1) ...
Setting up liboxideqtquick0:amd64 (1.7.8-0ubuntu0.14.04.1) ...
Setting up liboxideqt-qmlplugin:amd64 (1.7.8-0ubuntu0.14.04.1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-53-generic
W: Operation was interrupted before it could finish

Finally the error in red immediately above pops up.
I searched the net and found a site with an article dated back in 2010 that said to fix the error before rebooting or I'd probably not be able to boot to Linux.
Which I'm doing right now, I've not yet rebooted.

How should I recover from such an error before I reboot.

The site had several solutions depending upon other variables, one of which was to delete and/or re-run something. But none of the solutions seemed to fit my case.

I'm running the Zorin OS 9 Theme on top of Ubuntu 14.04 LTS, an AMD PhenomII 64bit 4 core processor on an ASUS MB. The video card is also an AMD/ATI, hence the need for the fglrx drivers listed above.

I'm not sure if the overwriting of the ATI/AMD driver config files shown above are responsible for the error or not. I did nothing that I was aware of that might have caused it, except close another instance of terminal that was runnning, and a libre office writer window.

Any ideas on how to solve this before I reboot would be greatly appreciated.

TIA

Hello

I have installed a CentOS 6.4 on VmWare.

Now, after several days of using it, it suddenly does not boots. There is a problem with its initialization, here is the error:

Kernel Panic : Unalble to init. Try passing init= option to the kernel.
Pid 1 : Swapper not tainted.

I have used CentOS.iso to rescue it, but it still does not solve it.

My grub.conf contains:

PHP Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/sda2
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.32-358.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-358.el6.x86_64 ro root=UUID=6082bcf5-00ba-4bf8-86ea-9821d774cb6f rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
 initrd /initramfs-2.6.32-358.el6.x86_64.img 



How should I solve it then? Thanks in advance

The hard disk inside my laptop looks like this

[ Win 8 ][ SWAP ][ Linux ][ Data ]

What are the steps to configure the GRUB2 to give me the option to dual-boot when I turn my laptop on?

I have made a change to GRUB2 bootloader in etc/default/grub.
Now I need to run 'update grub' for the change to take effect.
However, the 'update grub' command on the terminal is giving this error message:
Code:

root@debian:/# update grub
bash: update: command not found

Can someone please explain why this command is no longer working?

I've had to make a change to grub because I tried to install a new distro which meant I had to alter grub.
The install wasn't successful so I deleted the grub file and then re-installed it.
The re-installed grub needs a change so I can get sound on my pc.
However, I can't add these changes because the 'update grub' command doesn't work.

I've checked the grub file with another debian distro and they are both the same.
So now I don't know if I need to check if a different grub file is the problem or anything else.
Can someone help?

Hello,

I am new to Linux images (pxe, livecd). I would like to add files to a linux image, like something under etc or var, and have the files be available on the client.
The server I am working on was already configured with a pxe image, and only 2 files are present under the pxe client folder: initrd and vmlinuz. So I am wondering if either of these files contain the dirs /etc, /var, etc..., and how I could add files to them.

To give some background, I have done the same thing in Windows. An image in Windows is typically either boot.img or install.img. You can mount either of these to a folder using the Windows SDK tool imagex.exe /mountrw <img file> 1 <mount point>. From here you can add/remove/modify any files you want. Then commit the changes with imagex.exe /unmount <mountpoint> /commit.

Can someone provide insight to the linux image creation process, which of the files (initrd, vmlinuz/vmlinux, etc...) contain what for the client boot, or something similar to the Windows Image editing process?

I know I'm asking for a range of info, but pointers to any material to help my understanding will be greatly appreciated.

Thanks,
Jon

I've just compiled my own kernel (debian), but I have no idea how to boot it. I don't know how to get to the grub menu. I've tried holding shift down at start up but it doesn't work! When I hold down esc it asks me what I want to boot?

I've read that I have to edit the file /etc/default/grub - but I can't since don't have it..

Does anyone know how?