Sponsored Content
Operating Systems Linux SuSE Dual booting suse 11.1 and XP Post 302308267 by mark54g on Friday 17th of April 2009 02:11:42 PM
Old 04-17-2009
You will need grub or some other intelligent boot loader to do this. There is a hack to make it work but it is more trouble than it is worth.

HowTo Multiboot with Windows Bootloader - openSUSE Forums
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dual booting :-)

I have some problems with LILO/Grub... When I try to start Linux it says> EBDA too big How can I fix this problem? //Nevsky (2 Replies)
Discussion started by: Nevsky
2 Replies

2. UNIX for Dummies Questions & Answers

question about dual booting

question: 1. Which partioning wizard is better to use, System Commander V7.0, or Partition Magic V7.0? 2. Which version of linux is better to start with for beginners Mandrake, SuSe, or Corel? :) (4 Replies)
Discussion started by: CmpKillr
4 Replies

3. Solaris

Dual booting Linux and Solaris

Ok, so I'm a bit new to the whole Unix/Linux thing, but I'm no stranger to dual booting... However, the problem that I am having is that I am unable to create a dual boot with Unix (in this case I's using Sun Solaris 9.0 x86) and for linux either RH 9 or Mandrake 9.1, but for the purpose of just... (1 Reply)
Discussion started by: AndroidI6
1 Replies

4. Red Hat

Dual boot (Booting Windows from Linux MBR)

Hi , I have two disk installed with Linux(disk 1) and WinXP(disk 2) .Now i am changing Hardisk jumbper manualy to get in to Linux/Windows .I want to configure my REDHAT linux boot manager to list Linux and WindowXP and wanna boot according to my choice . Here is what my fdisk -l shows (Only... (2 Replies)
Discussion started by: gkrishn
2 Replies

5. Solaris

Dual Booting with UNIX

Dear All, I want use Unix (Sun Solaris 10) in my PC, and now I'm using windows, can Unix intalled to My PC and make dual booting like linux?? any one have experienced about this..? please help me..? Thank you for your help Regards, Heru (4 Replies)
Discussion started by: heru_90
4 Replies

6. Linux

Dual Booting issue

Hi Experts, I have windows XP and fedora core 3 in a PC i.e dual booting. I want to share some of the files in Windows Operating system to Linux(the other OS in the PC). How can i do it Thanks Shaan (2 Replies)
Discussion started by: shaan_dmp
2 Replies

7. UNIX for Dummies Questions & Answers

Dual Booting

I first had windows xp 64-bit installed on my system, and then installed fedora 10 on a partition (partition was created while installing fedora). When installation was completed, I could not boot on Windows or Fedora, I keep on getting this disc error and system asking to press ctrl+alt+del to... (0 Replies)
Discussion started by: lucianvibz
0 Replies

8. Ubuntu

Dual booting problem with XP-Pro

Hi Everyone, I was using XP-Home along with Ubuntu (dual booting) in my laptop. At the booting screen the Grub loader used to show me like this- Ubuntu Other operating system Inside 'Other operating system' I used to find 'XP- Home'. Oflate I installed XP-Professional and there I faced the... (2 Replies)
Discussion started by: adc22
2 Replies

9. Linux

Problem in dual booting installation of linux on windows

Dear friends, I am experiencing the trouble while installing the Red Hat Linux 4 on top of windows XP, after booting its asking "What type of media contains the packages to be installed". Steps I followed: Step 1: left the free space as unpartitioned, (I also tried with the FAT32... (1 Reply)
Discussion started by: suneelieg
1 Replies

10. Red Hat

Dual booting problem

Hi all, I have an problem with dual booting. I installed windows7 and i want to install redhat linux on same system. When i insert the cd and boot with the cd it is not showing the hard drive. If i boot with hard disk its booting with windows7. But, if i boot with cdrom it is showing an... (7 Replies)
Discussion started by: mastansaheb
7 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 12:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy