Sponsored Content
Full Discussion: Grub Issues ; Prominent.
Special Forums Hardware Boot Loaders Grub Issues ; Prominent. Post 302554588 by Corona688 on Monday 12th of September 2011 11:54:28 AM
Old 09-12-2011
Quote:
Originally Posted by fpmurphy
Probably because the added OS is on a different disk or partition.
Agreed... never blindly copy data from config files -- always understand its meaning first.

theKbStockpiler: It'd really help if you could post the entire file, as well as which entries do and don't work, so we don't have to guess.
 

10 More Discussions You Might Find Interesting

1. Linux

GRUB and windows XP

After playing a bit with GRUB I got it to boot my windows XP and my Fedora (yeay!). But now my windows became awfully slow (hd seems to be the problem). Does anybody have an idea what could cause this? settings: default=1 timeout=10 splashimage=(hd1,0)/grub/splash.xpm.gz title Fedora... (1 Reply)
Discussion started by: Micky
1 Replies

2. Linux

Remove GRUB

hello i just uninstall fedora core 4 and would like to remove the GRUB from my system. i try to use windows xp startup disk and tryout the fixmbr command. however the system warn me that my computer do not have a proper mbr and performing this action may make all partition in my harddisk... (5 Replies)
Discussion started by: wsc
5 Replies

3. Linux

grub help

in dual os grub will ask like this (linux 9 (red hat)) linux(bigmem) linux(smallmem) dos so i want that grub will ask like this dos linux(bigmem) linux(smallmem) how to do this (8 Replies)
Discussion started by: seshumohan
8 Replies

4. UNIX for Dummies Questions & Answers

grub problem- keeps rebooting as soon as it tries to do grub

Hi, I installed solaris 10 a few weeks ago. It was working fine during the past two weeks. However, now when I start to load to the drive, I get this problem: The BIOS screen comes up like normal, then screen goes blank and a message "Grub loading stage 2" flashes real quick then the computer... (1 Reply)
Discussion started by: moesays
1 Replies

5. Linux

Grub.Conf

Hi, During the Initial startup of the Linux machine. Grub.conf has a entry to mount the root partition as read only after the initialistation of the Kernel. Is there any specific reason for this or the root partition can be made to mounted with read write options. Regards Arun (1 Reply)
Discussion started by: Arun.Kakarla
1 Replies

6. Solaris

grub problem

hi , was using solaris in dual boot with xp , then I ' ve installed ubuntu too . The solaris grub has been in some way damaged , maybe because during the linux installation i've delete an old partition that I was not using by some months. It's normal that the solaris grub has been overriden by... (7 Replies)
Discussion started by: freeware
7 Replies

7. Red Hat

Can we specify which grub.conf to use in grub-install.

Hi, Can we specify which grub.conf to use while installing grub on RHEL. We are working on application which requires different grub configurations needed, depending on certain criteria we need to update grub with correct grub.conf. Can we use grub-install for this purpose? (4 Replies)
Discussion started by: successlin
4 Replies

8. UNIX for Dummies Questions & Answers

"/boot/grub/grub.conf" VS "/etc/grub.conf"

can someone please explain me the difference between these two files: "/boot/grub/grub.conf" and "/etc/grub.conf" .. (7 Replies)
Discussion started by: stunn3r
7 Replies

9. Debian

Cannot install GRUB

Hello, I cannot install grub to my ESP it seems. I have a PC with both Windows 8.1 and Debian installed and I can only boot into Windows since GRUB is not installed on my PC. I am using a Ubuntu Live USB to install GRUB on /dev/sda1 (my ESP). I am using the following commands from Ubuntu... (12 Replies)
Discussion started by: sreyan32
12 Replies

10. Linux

Grub password

what if grub had a password and prevented you from getting in, what should I do, regards (2 Replies)
Discussion started by: abbya
2 Replies
GRUBBY(8)						      System Manager's Manual							 GRUBBY(8)

NAME
grubby - command line tool for configuring grub, lilo, and elilo SYNOPSIS
grubby [--add-kernel=kernel-path] [--args=args] [--bad-image-okay] [--boot-filesystem=bootfs] [--bootloader-probe] [--config-file path] [--copy-default] [--default-kernel] [--grub] [--info=kernel-path] [--initrd=initrd-path] [--lilo] [--make-default] [-o path] [--remove-kernel=kernel-path] [--set-default=kernel-path] [--title=entry-title] DESCRIPTION
grubby is a command line tool for updating and displaying information about the configuration files for the grub, lilo, elilo (ia64), and yaboot (powerpc) boot loaders. It is primarily designed to be used from scripts which install new kernels and need to find information about the current boot environment. On Intel x86 platforms, grub is the default bootloader and the configuration file is in /boot/grub/grub.conf. On Intel ia64 platforms, elilo mode is used and the default location for the configuration file is /boot/grub/grub.conf. On PowerPC platforms, yaboot parsing is used and the configuration file should be in /etc/yaboot.conf. There are a number of ways to specify the kernel used for --info, --remove-kernel, and --update-kernel. Specificying DEFAULT or ALL selects the default entry and all of the entries, respectively. If a comma separated list of numbers is given, the boot entries indexed by those numbers are selected. Finally, the title of a boot entry may be specified by using TITLE=title as the argument; all entries with that title are used. OPTIONS
--add-kernel=kernel-path Add a new boot entry for the kernel located at kernel-path. --args=kernel-args When a new kernel is added, this specifies the command line arguments which should be passed to the kernel by default (note they are merged with the arguments from the template if --copy-default is used). When --update-kernel is used, this specifies new arguments to add to the argument list. Multiple, space separated arguments may be used. If an argument already exists the new value replaces the old values. The root= kernel argument gets special handling if the configuration file has special handling for specifying the root filesystem (like lilo.conf does). --bad-image-okay When grubby is looking for a entry to use for something (such as a template or a default boot entry) it uses sanity checks, such as ensuring that the kernel exists in the filesystem, to make sure entries that obviously won't work aren't selected. This option over- rides that behavior, and is designed primarily for testing. --boot-filesystem=bootfs The grub boot loader expects file paths listed in it's configuration path to be relative to the top of the filesystem they are on, rather then relative to the current root filesystem. By default grubby searches the list of currently mounted filesystems to deter- mine this. If this option is given grubby acts as if the specified filesystem was the filesystem containing the kernel (this option is designed primarily for testing). --bootloader-probe grubby tries to determine if grub or lilo is currently installed. When one of those bootloaders is found the name of that bootloader is displayed on stdout. Both could be installed (on different devices), and grubby will print out the names of both bootloaders, one per line. The probe for grub requires a commented out boot directive grub.conf identical to the standard directive in the lilo configuration file. If this is not present grubby will assume grub is not installed (note that anaconda places this directive in grub.conf files it creates). This option is only available on ia32 platforms. --config-file=path Use path as the configuration file rather then the default. --copy-default grubby will copy as much information (such as kernel arguments and root device) as possible from the current default kernel. The kernel path and initrd path will never be copied. --default-kernel Display the full path to the current default kernel and exit. --elilo Use an elilo style configuration file. --grub Use a grub style configuration file instead of lilo style. This is the default on ia32 platforms. --info=kernel-path Display information on all boot entries which match kernel-path. I --initrd=initrd-path Use initrd-path as the path to an initial ram disk for a new kernel being added. --lilo Use a lilo style configuration file. --make-default Make the new kernel entry being added the default entry. --remove-args=kernel-args The arguments specified by kernel-args are removed from the kernels specified by --update-kernel. The root argument gets special handling for configuration files that support separate root filesystem configuration. --remove-kernel=kernel-path Removes all boot entries which match kernel-path. This may be used along with --add-kernel, in which case the new kernel being added will never be removed. --set-default=kernel-path The first entry which boots the specified kernel is made the default boot entry. --title=entry-title When a new kernel entry is added entry-title is used as the title (lilo label) for the entry. If entry-title is longer then maximum length allowed by the bootloader (15 for lilo, unlimited for grub and elilo) the title is shortened to a (unique) entry. --update-kernel=kernel-path The entries for kernels matching kernel-path are updated. Currently the only items that can be updated is the kernel argument list, which is modified via the --args and --remove-args options. --version Display the version of grubby being run and then exit immediately. --yaboot Use an yaboot style configuration file. BUGS
The command line syntax is more then a little baroque. This probably won't be fixed as grubby is only intended to be called from shell scripts which can get it right. SEE ALSO
grub(8), lilo(8), yaboot(8), mkinitrd(8) AUTHOR
Erik Troan <ewt@redhat.com> 4th Berkeley Distribution Thu Jun 21 2002 GRUBBY(8)
All times are GMT -4. The time now is 01:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy