similar to: Using ramdisks on CentOS

I am running isolinux 4.02 and ramdisk_size does not seem to have an effect on the ramdisk size. No matter what I set it to in the isolinux.cfg file it seems the limit is 32768. I get the error: ram0: rw=0, want=360456, limit=32768 EXT2-fs error (device ram0): My isolinux.cfg file: LABEL EB KERNEL vmlinuxE APPEND initrd=bos.img root=/dev/ram0 rw ramdisk_size=545000 I am running the 2.6.38.2

Hi All, I am using Centos4.0 and running Squid Reverse Proxy for image caching , i have configured RAMDISK of 265 MB for one cache folder in preproduction environment for testing now i have upgraded RAM upto 8GB, but when i change ramdisk_size parameter in grub.conf and rebooted the server when i tried to format and mount it doesn't work. Can anyone please help me how to increase RAMDISK

Hi! Some bootloaders (eg. syslinux) have to ability to load multiple ramdisks, effectively concatenating them. This makes it very easy to augment ramdisks, like eg. customizing an installer. Can I do something similar with XEN? Separating the ramdisk cpio arhives with commas in the config file didn''t work... -- Thanks, Feri. _______________________________________________ Xen-users

Hey All, I'am using pxelinux to try and boot a 200meg uncompressed (approx 50 compressed) ramdisk onto a machine with 512meg of ram. It looks as though I'am running out of memory (attempt to access beyond end of device error). Is there a limit on what we put for ramdisk_size? Or Is there other limitations? thanks -- Jeff Geddes, BSc(UNB) Computer Systems Specialist University of

Hi, I am trying to load kernel 2.6.6 on a Soekris net4521 from the network using PXE. I built my initrd with mkinitrd. RedHat nash (while running linuxrc) hangs after mounting /proc and says "Creating block devices". I am using the pxelinux.0 from the syslinux-2.10 distribution and the kernel and initrd were built on redhat 9.0. I built my kernel with BLK_DEV_RAM, RAMFS, TMPFS,

Hello, I have a problem with a 2.5.62 kernel and ramdisk. I am using isolinux to create a cd that loads some of its partition in ramdisk. The script involves mounting a ramdisk (e2fs) on /fake/ramdisk, copying part of the cd to that mount point, unmounting it, and remounting it on /fake/needwrite. The problem is that, although the content of /fake/needwrite gets correctly copied, the content of

Hi, to install current PC models (with new Intel NICs) via Kickstart/PXE, I wanted to add the newest e1000e-Treiber to initrd.img. With this modified image, the Kickstart kernel crashes with the following error messages: [...] md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (20480 != 32768) 6062080

isoconfig.sys file below - Only change from past is adding stuff after the bz28.7 kernel. DEFAULT vesamenu.c32 Prompt 0 menu color screen 37;40 #80ffffff #00000000 menu color border 30;44 #40000000 #00000000 menu color title 1;33;44 #c0fdd017 #00000000 menu color unsel 37;44 #90ffffff #00000000 menu color hotkey 1;37;44 #ffffffff #00000000 menu color sel 7;37;40

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have done some additional testing, and gotten it a bit close to what I was looking for. I had to modify the cat.c to eliminate the printing of the arguments and file name, and added a Press Enter to return menu line. With the below isolinux.cfg the options do display the files, and pressing enter than returns to the vesamenu. DEFAULT

I want to upgrade a 5.4 box with the 2.618 kernel to a shiny new 2.6.32 kernel. Anyone done it? Is it possible? Are there gotcha's to watch out for? Any advice is appreciated. A link to a decent howto would be awesome. -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Centos 4.x 32 I want to create like a 64Mbyte ramdisk. Is there a problem putting 30k to 80k empty files on a ramdisk? Is there a simple howto on creating a ramdisk that anyone knows of off the top of there head? Matt

I am having a problem with setting up diskless clients under CentOS 5.2. I have everything working under CentOS 4.7. This is an adaptation of the (somewhat old) Diskless Linux with PXE HOWTO by Gerd v. Egidy, originally at the URL http://www.intra2net.com/opensource/diskless-howto/, which is now defunt (there is a mirror of it at http://blog.chinaunix.net/u/2389/showart_82438.html). What I am

On 06/23/2015 08:10 PM, Marko Vojinovic wrote: > Ok, you made me curious. Just how dramatic can it be? From where I'm > sitting, a read/write to a disk takes the amount of time it takes, the > hardware has a certain physical speed, regardless of the presence of > LVM. What am I missing? Well, there's best and worst case scenarios. Best case for file-backed VMs is

Hi. I have cloned a RHEL 5.6 physical server over to a ESXi 5.0 Virtual Machine. Using a live CD on the new Virtual Machine I created 3 partition /boot (/dev/sda1), / (/dev/sda2) and swap (/dev/sda3), I then mounted the / (sda2) partition and created the /boot directory and mount the boot partition partition /dev/sda1 into /boot. I then used rsync to copy the source machine over to the Virtual

Have been trying some things, but something isn't working at least with using Virtual Box with EFI option. With it off, the cd boots as normal, and works, but with EFI on, it has an error that flashes on screen, and then it drops to a shell prompt. I'm hoping it is just a dumb mistake I am making, and can be resolved. Perhaps I've named the directories incorrectly, or there is a

I''m continuing to work on making a new XenCD as previously discussed here. In the course of that work, I''ve generated (actually, currently stuck on) the enclosed crash dump. Thought I''d forward it for interest. To head off questions, you''ll see references to a very large initrd (~114 Mb). The Xen dump may or not be related to this unusual usage.

On Tuesday 03 October 2017 18:24:01 Mark Haney wrote: > What issue? That the PID is dropped on reboot?? What else are you > putting in there?? I'm beginning to question whether you know what > you're doing or not.? Lighttpd doesn't store any persistent info in > /var/run/ because, like everything else, /var/run isn't for persistent > data. Mark, Many Non-Centos

The simplest solution and the one already implemented in linux, tmpfs. It would be best to allocate 4-8GB to tmpfs on /tmp and let the kernel do the work it was designed to do. And you would not be limited to PCI bus speeds. The DDR2800 is about 12GB/sec. Some would say "overheads, etc, etc". Agreed, even at 95% loss (doubtful) you still get higher badwitch then PCI bus/hard rive could

Hi! Here is my isolinux.cfg. It's slackware based. ====================== default Kernels/bare.i/bzImage initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=8192 rw root=/dev/ram ZILIX_KERNEL=bare.i prompt 1 timeout 1200 font lat1-16.psfu display mensagem.msg F1 mensagem.msg F2 opcoes.msg F3 help.msg label linux kernel Kernels/bare.i/bzImage append - label adaptec.s kernel

I''ve followed the howto at virtuatopia.com<http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_on_a_Disk_Image_%28Cloning_Host_System%29>to clone existing machines, then create them as PV guests. It has worked a couple of times for me, but I''ve run into a problem I don''t understand. When I run "xm create name", I get an error that