Sponsored Content
Operating Systems Linux Dual Boot Win XP And Fedora with Fedora Installed First Post 302177161 by reborg on Thursday 20th of March 2008 08:39:19 AM
Old 03-20-2008
yes, it is possible, but it really is a lot easier the other way around becasue most modern linux installers are quite happy to coexist with windows, but windows is not so accommodating.

Assuming that the disk is fully allocated to partitions you will need to use something like the GParted -- LiveCD in order to resize the partitions. You will then install windows on the new partition, and then boot back to fedora and reconfigure and reinstall grub on the MBR.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Lesson Learned: Dual boot XP and Fedora 9

This post captures my recent experience in getting my Dell XPS Gen 3 to support dual boot of Windows XP (Professional) and the Fedora 9 Linux distribution. I searched quite a bit on the internet and found, of course, a variety of opinions regarding how to setup this type (dual boot) of... (1 Reply)
Discussion started by: rlandon@usa.net
1 Replies

2. Linux

How to boot Fedora 8 from USB

Hi, friends, can anyone suggest me how to boot fedora 8 from USB flash drive? thanks. :confused: (3 Replies)
Discussion started by: MULTIVERSE
3 Replies

3. 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

4. Red Hat

how to undo the last installed update on fedora.

Hi All, I'm a newbie to system administration, I'd like to know how to check the logs (what update was installed last) , and I'd like to know how to undo the last update on the fedora 9 system ( kindof an equivalent to system restore in windows). I have a HP 22 inch monitor, when I installed... (3 Replies)
Discussion started by: ramky79
3 Replies

5. Red Hat

Unable to boot Fedora 10

Hello, I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning. But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies

6. Red Hat

boot floppy for fedora 13

Is there a way to create a boot floppy for a fedora 13 system? Rescue disk image from the official boot.iso is too big. (1 Reply)
Discussion started by: druidmatrix
1 Replies

7. Red Hat

fedora grub help, moving to tri boot (XP, ubuntu, fedora soemething)

I will shortly be adding a fedora flavor to my devel box. I currently have XP (installed first on an ssd), ubuntu 10.04 (installed second on the first partition of a platter drive), and I want to add either Cent or SL on the second partition of the platter drive. I will probably also want to... (0 Replies)
Discussion started by: LMHmedchem
0 Replies

8. Red Hat

Fedora 17 - No video after boot

Hi, I'm new to the Linux world and I'm having issues. Screen goes blank after Fedora boots up. I can see the POST and Fedora Grub screen but afterwards, goes blank. I believe I installed something but I cant remember what....its been a couple days. (0 Replies)
Discussion started by: gps1976
0 Replies

9. Hardware

Fedora 16 dual monitor - dual head - automatic monitor shutdown

Hi, I am experiencing troubles with dual monitors in fedora 16. During boot time both monitors are working, but when system starts one monitor automatically shut down. It happend out of the blue. Some time before when I updated system this happend but then I booted older kernel release and... (0 Replies)
Discussion started by: wakatana
0 Replies
BOOTCD2DISK.CONF(5)						   bootcd utils 					       BOOTCD2DISK.CONF(5)

NAME
bootcd2disk.conf - configuration file for bootcd2disk DESCRIPTION
The file bootcd2disk.conf contains configuration option for the bootcd2disk(1) program of the same named package. The file must be located in the configuration directory which is usually /etc/bootcd. Blank lines are ignored and lines with leading # are comments. Values have to be set with name=value You can use a wildcard named DISK<number> to specify partitions instead of e.g. /dev/hda<number>. DISK was replaced by $DISK, which can be set by the same named parameter. FORMAT
ERRLOG=<path> Write all errors to this file. Required. DISK=<device|auto> Specify the disk you want to use for the installation, e.g. /dev/hda for the first IDE drive in the system. If you use "auto", bootcd2disk automatically try to use the first hard disk in the system. Required. SFDISK=<partitions in sfdisk syntax|auto> Configuration options for sfdisk, which creates the partitions for us. If you use "auto", we create default partitions "/", "/boot" and a swap partition. Required. VFAT=<partitions separated by spaces> Configure vfat partitions there, if you need some. Optional. EXT2FS=<partitions separated by spaces|auto> Specify the partitions with ext2 or ext3 (see next parameter) here. This partitions would be created and formated. If you use "auto", the "/" and the "/boot" partition would be created. Required. EXT3FS=<yes|no> Enter "yes" If you want ext3 partitions. If you use "auto", the systems use ext3 partition, if the kernel supports it. Required. SWAP=<partitions separated by spaces|auto> The partitions configured there are created as swap. If you use "auto", one swap partition is been created. Required. MOUNT=<mount <partition> <mountpoint>; ... |auto> Insert here the mount command line to mount your partitions or use "auto". Required. UMOUNT=<umount <mountpoint>; ... |auto> Insert here the mount command line to umount your partitions or use "auto". Required. FSTAB=<entries for the systems fstab |auto> Configure here all partitions you need to mount after target systems startup in the fstab syntax or use "auto". Required. LILO=<entries for the systems lilo.conf |auto> This variable includes the complete configuration file for the lilo bootloader on the target system. Use "auto" for automatically generated file. Only required, if you want LILO. Make sure GRUB and GRUB2 are defined as empty if you want to use LILO. GRUB=<entries for the systems grub/menu.lst |auto> This variable includes the complete configuration file for the grub bootloader on the target system. Use "auto" for automatically generated file. Only required, if you want GRUB. GRUB2=<entries for the systems grub/grub.cfg |auto> This variable includes the complete configuration file for the grub2 bootloader on the target system. Use "auto" for automatically generated file. Only required, if you want GRUB 2. GRUBBOOTDIR=<number of partition which contains grub-dir | 0> This variable defines the partition where the grub bootloader information is stored. You want to use this if you have defined your own partition layout and the grub information is not on the first partition. Remember that grub starts counting partitions at 0. So if you decided that /boot is on partition /dev/sda2 you need to set the parameter to 1. GRUBBOOTDISK=<grub disk> This should be "hd0". Only if your BIOS sees another disk as the first disk you may have to change it. GRUBDEVICEMAP=<auto|no|<value>> GRUBDEVICEMAP="auto" means, bootcd2disk deletes the original device.map, so that it will be auto-created by grub again. This should work also when installing on different hardware with different disks. GRUBDEVICEMAP="no" means bootcd2disk does not change device.map. This should work if a bootcd is installed on the original hardware Everything else will be used as new value for device.map. ELILO=<entries for the systems elilo.conf |auto> Same as LILO but for the elilo bootloader on ia64 systems. Use "auto" for automatically generated file. Only required, if you want ELILO. SSHOSTKEY=<yes|no> If you are using ssh it is helpful to have a unique ssh hostkey for each system installed with bootcd2disk. This will be generated if this option is set to "yes". Required. UDEV_FIXNET=<yes|no> If you are using the udev filesystem and want to install the image on other machines, you need to set this to "yes" because the net- work interfaces are hardwired in /etc/udev/rules.d/z25_persistent-net.rules (etch) or in /etc/udev/rules.d/70-persistent-net.rules (lenny) and we must remove them. Required. IMAGEURL=<url> If bootcd2disk is slow on your system (because of a slow CD/DVD drive or the HP ILO virtual CD interface), you can use a image server to get the bootcdimage from. bootcd2disk use the swap partition of your upcoming system as temporary space and copy the image from the configured image server to this partition and use it as image. May be overwritten from command line "-url". Need the following parameter "IMAGEURL". Required. The <url> is used with wget, all url syntax from wget are possible. Please use a ip because of failed DNS and you need also the con- figured ip interface. May be overwritten from command line (-url). Required. example: IMAGEPURL="https://192.168.1.1:81/cdimage.iso" function before_copy() { return } If you want some action before copying the system to the target disk, like remount or other thinks, you can write this action to the body of this function. Optional. function after_copy() { return } If you want some action after copying the system to the target disk, like remount or other thinks, you can write this action to the body of this function. Optional. SEE ALSO
bootcd2disk(1), bootcd(1), bootcdflopcp(1), bootcdwrite(1) AUTHOR
This manual page was written by Carsten Dinkelmann <carsten.dinkelmann@foobar-cpa.de>, for the Debian GNU/Linux system (but may be used by others). bootcd2disk.conf 2007-04-04 BOOTCD2DISK.CONF(5)
All times are GMT -4. The time now is 07:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy