Hello, guys !
Long time no seen. I have a question about Linux web servers. I guess it is a more general question, but in my case it is a Linux web server. I want to know how much RAM memory should I put on my servers. Do you have some formula or guidelines on how should I calculate the amount... (1 Reply)
hi,
currently we have SAP application running on a solaris machine that has 8 dual core CPUs @ 2.4 GHZ and the performance of the system is perfectly normal. We plan to migrate the app to a suse linux VM image on a vmware box now. So my questions are:
1) Should i size the linux image to... (2 Replies)
We have a system with 4 Xeon Processors each with 10 cores, total 512 GB RAM and 10 TB Hard Drive.
we want to create multiple user accounts with different resource limitations as :
User 1: RAM : 50GB, PROCESSOR: 10 Cores , User folder in home directory of 10GB space.
User 2: RAM :... (5 Replies)
Hi,
I will be creating a process myself and I want to know the average CPU and RAM used by the process over the lifetime of the process. I see that there are various tools available(pidstat) for doing , I was wondering if it possible to do it in a single command while creation.
Thanks in... (3 Replies)
Hi
i have 2 esxi. one is amd based cpu and the other is intel based cpu.
i have a redhat linux machine that was created in amd cpu esxi, now i need to migrate it (powered off) to INTEL based esxi. will the redhat machine will be OK with that?
Thanks (2 Replies)
Discussion started by: guy3145
2 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)