11-02-2010
Hi,
Thanks a lot for your reply.
I am not exactly sure why there are seven partitions on the hard disk. The system earlier had windows XP professional installed on it. On my request, the internal IT team, installed Fedora 10 on it for my testing purposes.
Sure, I will try booting with rescue CD and let you know the results.
Thanks again,
Siva
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want to upgrade from Red Hat Linux 8.0 to Fedora Core 3. I have already downloaded FC3 on CD's. My current config. on my PC is that I have Win XP on primary hard drive and Red Hat 8.0 on another hard drive. Because my Compaq Presario reserves the first cylinder of my primary hard drive, I... (1 Reply)
Discussion started by: Mark McWilliams
1 Replies
2. Linux
Hi everyone,
I hope this question goes here. Anyways, I have a unique situation where my friend's comp has Fedora installed and wants to add Win XP as a dual boot without formatting the drive. Is it possible to create a partition on the current hard drive and then install win xp? I couldn't find... (4 Replies)
Discussion started by: eltinator
4 Replies
3. UNIX for Advanced & Expert Users
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
4. Linux
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
5. Red Hat
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
6. Red Hat
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
7. Red Hat
Hello, everyone.
I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command:
yum update kernel* --releasever=16
yum groupupdate Base --releasever=16
reboot
After reboot, OS... (2 Replies)
Discussion started by: 915086731
2 Replies
8. Red Hat
hi guys,
I was using kernel-3.1.2-1 in fedora 16. then updated to kernel-3.1.4-1. after reboot now grub shows command prompt instead of boot menu. i tried to load manually with:
set root=(hd0,msdos3)
linux /vmlinuz-3.1.4-1.fc16.x86_64
initrd /initramfs-3.1.4-1.fc16.x86_64.imgbut in the middle... (0 Replies)
Discussion started by: majid.merkava
0 Replies
9. Red Hat
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
LEARN ABOUT REDHAT
pcinitrd
PCINITRD(8) System Manager's Manual PCINITRD(8)
NAME
pcinitrd - create a PCMCIA initrd ram disk image
SYNOPSIS
pcinitrd [-v] [-a] [--all] [-d alternate-root] [--dir=alternate-root] [-r kernel-release] [--release=kernel-release] [-s image-size]
[--size=image-size] [-u] [--update] initrd-image [modules ...]
DESCRIPTION
The pcinitrd script creates an initrd ram disk image for booting with the root filesystem on a PCMCIA device. If the target is a block
special device (i.e., /dev/fd0), then the initrd image is created on that device. If the target does not already exist or if it is an
ordinary file, then pcinitrd will create the image file using the ``loopback'' device.
Modules are specified with paths relative to /lib/modules/[kernel-release]. The core PCMCIA modules (pcmcia/pcmcia_core and pcmcia/ds)
will automatically be installed in the target image. All other device-specific modules need to be listed on the command line, along with
the appropriate socket driver (pcmcia/i82365.o or pcmcia/tcic.o). Alternatively, if -a is specified, then all available PCMCIA socket
drivers and block device drivers will be included in the image. Additional files to be copied to the initrd image may also be listed on
the command line. Executable programs will be installed in /bin, shared libraries will be installed in /lib, device files will be
installed in /dev, and any other files will be placed in /etc.
The startup script in the resulting image, linuxrc, may need to be customized for a particular system. It contains the same variable defi-
nitions as the normal PCMCIA startup scripts (i.e., PCIC=, PCIC_OPTS=, and CORE_OPTS= variables). The /etc/config.opts file may also need
to be edited. Any changes to linuxrc or config.opts will be preserved if pcinitrd is executed in ``update'' mode.
Another feature of the generated linuxrc is that if the DEBUG variable is set to a non-blank string at the boot prompt, then cardmgr will
echo all its status messages to the console, and after linuxrc executes, it will fire up a shell on the console. This can be helpful for
debugging initrd problems. However, few commands are available in the normal initrd environment.
OPTIONS
-v Verbose mode. Identify files as they are copied.
-a, --all
Install all socket drivers and block-style PCMCIA device drivers, including memory card, SCSI card, and fixed-disk drivers. This is
mainly intended for use by package maintainers.
-d alternate-root, --dir=alternate-root
Specifies an alternate directory tree to search for all the files used to put together the initrd image. This may be helpful for
running pcinitrd after booting from an installation or rescue diskette.
-r kernel-release, --release=kernel-release
Specifies the kernel release number (i.e., 2.0.28) to use when looking for modules in /lib/modules. The default is the release of
the running kernel.
-s image-size, --size=image-size
Specifies the filesystem size to create on the target file or device, in 1k blocks. The default is 2400.
-u, --update
Update mode: updates cardmgr and all the kernel modules in an existing initrd image, but does not modify other files.
AUTHOR
David Hinds - dahinds@users.sourceforge.net
SEE ALSO
pcmcia(5), cardmgr(8), lilo(8).
pcmcia-cs $Date PCINITRD(8)