Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Dual Boot between UNIX and Windows Post 101713 by Neo on Saturday 11th of March 2006 09:48:18 PM
Old 03-11-2006
If you install, for example, Linux, you can use lilo to configure the boot-time configuration.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

dual boot windows 2000 and solaris 8

Hello I recently purchased solaris 8 and I want to dual boot with windows 2000. What is the easiest way to install the solaris OS with the existing windows 2000? mogfog (4 Replies)
Discussion started by: mogfog
4 Replies

2. UNIX for Dummies Questions & Answers

Loading windows on a dual boot

I want to dual-boot Windows 98 and Redhat 7. My scheme for doing this is to partition into: A FAT32 partition for windows A Linux partition for root A swap partition A boot partition My question is: At what point do I setup windows on the FAT partition? Would I do it from the command line... (5 Replies)
Discussion started by: Furtoes00
5 Replies

3. UNIX for Dummies Questions & Answers

Dual boot Redhat with Windows 2k or XP

I know this is a common question, but.... I am working on 2 seperate computers. Each machine has one hdd. I want to Install Redhat with Win2k on one machine, and Redhat with Xp on the other. I know there are some issues with the install sequence to get Grub to work with both, but I am a little... (4 Replies)
Discussion started by: jeremiebarber
4 Replies

4. UNIX for Advanced & Expert Users

windows -linux dual boot............

I am trying to implement a dual boot on my laptop ... using a small xp partition and fedora core 269.1-fc2 i686 linux kernel.. so far I have had to log off and reboot to enter the other partition... but this is getting frustrating.. windows is on /dev/hda1 and 1-5 is on the linux partition. I have... (8 Replies)
Discussion started by: moxxx68
8 Replies

5. UNIX for Dummies Questions & Answers

Windows And Unix, Dual Boot

Hello! I must find a way to use unix in my PC. I have a Dell Intel Pentium 4 CPU 3.2GHz, 1Gb RAM.It came with windows xp but in order to get some software running I have to be able to work on unix! Is it posible to set up a unix and Windows dual boot configuration? I was sure it was posible but... (2 Replies)
Discussion started by: isidora10
2 Replies

6. Solaris

Dual Boot WIndows 2003 and Solaris 10

Hi, I have a dual boot server with Windows on C0t0d0 and Solaris 10 on C1t0d0. When I do a reboot it automatically boots with Windows as default without an option to boot onto Solaris. I want to set Solaris as my default boot. any ideas? Thanks, Suresh (6 Replies)
Discussion started by: gunnervarma
6 Replies

7. Ubuntu

Fedora Windows XP Prof dual boot

Faced with a "learn the new platform at your own expense or lose your job" ultimatum, I bought a Maxtor internal HD and added it to my older HP desktop which had been upgraded from Windows to Windows Professional. I installed Fedora on the new 500 GB HD and tried putting the Fedora boot partition... (5 Replies)
Discussion started by: dba18
5 Replies

8. UNIX for Dummies Questions & Answers

How to run linux in windows 7 without dual boot?

tell me in steps if its virtual box (2 Replies)
Discussion started by: mahor1989
2 Replies

9. UNIX for Dummies Questions & Answers

UNIX based / like OS suggestions to dual boot with Windows

Hello everybody! I'm a long-time windows user with some very limited experience with some Linux distributions. I'm a programmer (in training), but I've worked mostly with .NET stuff. I started a new job a couple of weeks ago and was issued a MacBook Pro to work on. I have fallen in love with the... (3 Replies)
Discussion started by: egill
3 Replies
GRUBBY(8)						      System Manager's Manual							 GRUBBY(8)

NAME
grubby - command line tool for configuring grub, lilo, elilo, yaboot and zipl SYNOPSIS
grubby [--add-kernel=kernel-path] [--args=args] [--bad-image-okay] [--boot-filesystem=bootfs] [--bootloader-probe] [--config-file path] [--copy-default] [--debug] [--default-kernel] [--default-index] [--default-title] [--grub] [--lilo] [--yaboot] [--silo] [--zipl] [--info=kernel-path] [--initrd=initrd-path] [--make-default] [-o path] [--version] [--remove-kernel=kernel-path] [--remove-args=args] [--set-default=kernel-path] [--set-default-index=entry-index] [--title=entry-title] [--add-multiboot=multiboot-path] [--mbargs=args] [--remove-multiboot=multiboot-path] [--remove-mbargs=args] DESCRIPTION
grubby is a command line tool for updating and displaying information about the configuration files for the grub, lilo, elilo (ia64), yaboot (powerpc) and zipl (s390) 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. --debug Display extra debugging information for failures. --default-kernel Display the full path to the current default kernel and exit. --default-index Display the numeric index of the current default boot entry and exit. --default-title Display the title of the current default boot entry 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. --set-default-index=entry-index Makes the given entry number 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. --zipl Use an zipl style configuration file. MULTIBOOT OPTIONS
The Multiboot Specification provides a genreic interface for boot loaders and operating systems. It is supported by the GRUB bootloader. --add-multiboot=multiboot-path Add a new boot entry for the multiboot kernel located at multiboot-path. Note that this is generally accompanied with a --add-ker- nel option. --remove-multiboot=multiboot-path Removes all boot entries which match multiboot-path. --mbargs=multiboot-args When a new multiboot kernel is added, this specifies the command line arguments which should be passed to that kernel by default 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. --remove-mbargs=multiboot-args The arguments specified by multiboot-args are removed from the kernels specified by --update-kernel. BUGS
The command line syntax is more than 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) AUTHORS
Erik Troan Jeremy Katz Peter Jones Tue Jan 18 2005 GRUBBY(8)
All times are GMT -4. The time now is 07:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy