similar to: initramfs gunzip problems.

Last patch for now. This gets gen_init_cpio into a state where it can pick up a "kinit" binary from usr and stuff it into the cpio archive as /sbin/init. This is obviously a crock, but it suffices for testing until something sane is done about integrating klibc into the kernel tree. The patch also adds a bit of instrumentation to initramfs.c, to try to help flush out bug 740.

Hi all I'm trying to boot with initramfs I build my own root fs, and the kernel build links it, I have double checked this when the kernel boots unpack_to_rootfs() returns no error, so it continues and .... when It tries to mount the rootfs it tries to mount from an IDE device (where the kernel was built from), and not from the initramfs "image" I think this is not documented

Export initrd in debugfs when retained. As a side effect, initrd_start and initrd_end are not cleared when the initrd is retained. After this patch, one can then copy the initrd space from debugfs and pass it to kexec as the initrd, or do something else with it (maybe it was an initrd not an initramfs). Signed-off-by: Milton Miller <miltonm at bga.com> --- This is a lot more reliable

Hi, The attached patch is an update to the latest klibc (I just checked a few bits into CVS) which adds support for initramfs. Since it contains bits that aren't available yet on the main site, I've also put a tarball up which contains only what's in the latest CVS. The initramfs stuff is what I use here to boot one of my machines; it works for me, but probably won't work

HPA, is it possible to add GZ support in syslinux itself? Some standalone software compresses very well, but is not compressed. Example is the Memtest86+ binary (90KB uncompressed --> 35KB gzip'd) and maybe Smart Boot Manager (gzip'd COM32 binary instead of normal COM32 binary?). I'm using both on a simple bootdisk, and all space savings are welcome. a workaround could ofcourse

HI All, I have a directory tree that when the user un-gzips/untars it does into /opt by default. The directory tree is like: ugui | |-- <misc files> |-- source |-----framework |------ <misc files> so when unzipped I want to end it with /opt/ugui and all the stuff below it. How do I do this? Can I also issue one command that will unzip and untar the archive at the same time?

Hello, I would like to know if initrd is here to stay, now that klibc and initramfs are ready. As the multipath-tools maintainer, I'm facing the choice to 1) put the multipath configuration tool in the initrd * dynamic binary is possible * storage hba drivers as modules loaded * no klibc limitations (no mntent for libsysfs ...) 2) put the multipath configuration tool in the initramfs *

I'm triggering this BUG_ON during boot, which happens while freeing initrd memory: EIP is at free_init_pages+0x37/0xac [<c01143f1>] free_initrd_mem+0x11/0x13 [<c03ce259>] free_initrd+0x13/0x29 [<c03cf647>] populate_rootfs+0xdc/0xe2 [<c01003af>] init+0x42/0x253 [<c0103bbb>] kernel_thread_helper+0x7/0x10 I'm not sure why this memory isn't aligned

I'm triggering this BUG_ON during boot, which happens while freeing initrd memory: EIP is at free_init_pages+0x37/0xac [<c01143f1>] free_initrd_mem+0x11/0x13 [<c03ce259>] free_initrd+0x13/0x29 [<c03cf647>] populate_rootfs+0xdc/0xe2 [<c01003af>] init+0x42/0x253 [<c0103bbb>] kernel_thread_helper+0x7/0x10 I'm not sure why this memory isn't aligned

Would it be possible to make rsync capable to sync gziped source (at server) with non gziped detination file? PROBLEM: The rsyncd server provides a few *frequently* accessed, slow changing, *big* text files (DNS RBL zones). It seems that the source files are too big to stay in memory caches and rsync sessions cause to many hard disk I/O operations. Making rsynd capable to "ungzip"

Hello, is there a way to extract an initramfs from a running kernel? and from a kernel lying on a disk? If yes, how? Thanks Eurolines : Voyagez au meilleur prix : http://www.alinto.com/pub/

http://bugzilla.mindrot.org/show_bug.cgi?id=125 ------- Additional Comments From jrj at purdue.edu 2003-01-04 06:29 ------- The following attachment updates the suggested patch to 3.5p1. The attachment is a gzip'd tar file. Once you download it, ungzip it and then untar it into a temp directory (or use the 'z' option of GNU tar). Then look at the README for more information.

If the gzip utilities are built without support for compression, they will always attempt to carry out decompression even if the command name and options don't imply that. Instead they should fail with an explicit error in this case. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- usr/gzip/gzip.c | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13

Commit-ID: 0016a343f734cfe002dd45ab97a67b857ffe2e6d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0016a343f734cfe002dd45ab97a67b857ffe2e6d Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 6 Jan 2016 01:21:27 +0000 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Tue, 5 Jan 2016 17:51:26 -0800 [klibc] gzip: Fix silent fallback

Hi, I seem to have a problem with compiling the kernel 2.4.13 on redhat 7.2? It would compile fine but have errors about ext3 support on reboot. I download ext3-2.4-0.9.13-2413.gz to my linux machine to enable it be useful with ext3 support but when I try to gunzip it with the instructions gunzip < ~/ext3-2.4-0.9.13-2413.gz | patch -p1 i get gunzip: stdin: not in gzip format I get an

Hi, I'm sure this is a really stupid question, but when I type in the line: gunzip < ~/ext3-***extraStuffHere***.gz | patch -p1 as in the installation guide, it tells me that the patch is not a proper gzip file. What do I do??? Also, when it says "make menuconfig", does the menuconfig file appear once the patch is ungzipped, or should it be there already? I'm kinda worried

This allows other boot loaders such as the Xen domain builder the opportunity to extract the ELF file. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: virtualization@lists.linux-foundation.org ---

This allows other boot loaders such as the Xen domain builder the opportunity to extract the ELF file. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: virtualization@lists.linux-foundation.org ---

This allows other boot loaders such as the Xen domain builder the opportunity to extract the ELF file. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: virtualization@lists.linux-foundation.org ---

This allows other boot loaders such as the Xen domain builder the opportunity to extract the ELF file. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Ingo Molnar <mingo@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Jeremy Fitzhardinge <jeremy@goop.org> Cc: virtualization@lists.linux-foundation.org ---