similar to: kernel freeze on "umount /initrd" [signed]

Hi, I hope this is the right list for initramfs questions. First I noticed: with initrd I can use real-root-device and pivot_root mechanisms. with initramfs only pivot_root works. My init (or linuxrc) scripts end like this: mount -t xfs -n -o ro /dev/mapper/root /new-root umount -n /sys || true umount -n /dev || true umount -n /proc || true cd /new-root pivot_root . initrd exec chroot .

I've been working on a buildrelease.sh script to call hg2dist.sh, export debian/ from svn and run dpkg-source for me. When I ran dpkg-source I noticed that it gave warnings regarding the *.dpatch files being chmod 0755 is there any reason to maintain this within the repository or would 0644 suffice and remove these warnings from dpkg-source? Regards, Jeremy --

I just also wanted to mention that I have the current released source tarballs downloaded and placed at http://people.debian.org/~jbouse/xen/ at this time. As the only way to get the source tarballs I've found is via bittorrent unless you want to give your email address I'll continue to keep the the current tarball located there. That is one thing that I noticed about Ralph's

Looking through the build files I'm wondering if we can't do some clean-up and remove extraneous kruft before we release. Like the config.dbs and the README.build that talks about the config.dbs. From looking through the build setup I don't see either file actually critically needed and looks like Ralph may have come to a similar conclusion by the comments added to the README.build

Hi, I've a samba server running samba-3.0.22 and a samba client running samba-2.2.3. The samba server houses the home directories of my users, registered on a W2k PDC. The home directories are mounted on the samba client and all members of the group GROUP have rwx-permissions to it. So my problem is that a group member cannot create symlinks on this mounted file system. Is there a way to get

Hi Currently I am trying to get device-mapper and dmraid ported to compile against klibc. So far there was no real issues, as the only thing they used was fscanf and feof not available presently in klibc (but easy to work around). Other than that there are really no way to easily check for installed klibc's other than trying to mangle the output of klcc (from adjusted configure.in): -----

Hi, If say ppc where LDFLAGS=, you get the problem that klcc is generated like: ----- @LDFLAGS = ( '' ) ----- which then causes '' to get passed to ld, which gives: ----- /usr/bin/ld: : No such file: No such file or directory ----- One of two ways (I tried over here at least) to fix it, namely the quick hack: ----- --- 1/makeklcc.pl 2005-03-10 00:22:03.000000000 +0200

Hi, I am getting this: ----- armv4-unknown-linux-gnu-ld -o tests/fcntl.shared -e main interp.o tests/fcntl.o -R libc.so /usr/lib/gcc-lib/armv4-unknown-linux-gnu/3.3.5/libgcc.a armv4-unknown-linux-gnu-ld: internal error: aborting at /space/var/tmp/portage/binutils-2.15.90.0.3-r4/work/binutils-2.15.90.0.3/ld/ldlang.c line 3835 in lang_place_orphans armv4-unknown-linux-gnu-ld: please report this

working fine with glibc. thanks! Andreas -- ---------------------[ Ciphire Signature ]---------------------- From: aj@ciphirelabs.com signed email body (35 characters) Date: on 19 January 2005 at 12:48:14 GMT To: klibc@zytor.com ---------------------------------------------------------------- : The message above has been secured using Ciphire Mail. : Verify this signature and download your

Hi, please correct me if I'm wrong: - the kernel needs enough ram for the compressed initramfs and the same files decompressed, so it can decompress the files and boot the /init on the initramfs. - if the kernel does not have enough ram, it will kernel panic. my tests were done on a server with 256 mb ram and a 80MB compressed initrd. I removed some packages and now it fits and the

a bit unrelated, still I wonder: does syslinux contain an mbr? or does anyone know any app that contains an mbr and can install it, without overwriting the partition table? my experience is, that is wise to have an mbr and use the active flag to select the active partition (which might have a bootmanager installed). however every linux distribution I know installed the bootloader such as

Hi, So far with the latest changes the projects I am trying to port works fine, except for a mismatch on what is considered the ansi behaviour of islower() in ctype.h: ----- i = 220 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 220, TOUPPER (i) = 220 i = 221 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 221, TOUPPER (i) = 221 i = 222 islower (i) = 0, ISLOWER (i) = 0 toupper (i) = 222, TOUPPER

I've just been trying to catch up with the posts already so figured I'd just start another thread as it seemed I would address things from multiple emails. I really need to get my sieve filter script updated to move the list emails into the proper folder now I guess :) We can play with the revision of the packaging during testing. One idea would be to use 3.0.1-0.YYYYMMDD for

Hi! Im currently trying to encrypt my harddrive and plan to boot it of a USB memory stick. Im using loop-aes to do the real work but Im having the hardest time getting syslinux to mount my initrd. Im not sure what information you need but Ill give a bit of it. VFS unable to mount root-fs on unknow-block(1,0) is the error I get. I think there was a Kernel Panic attached somewhere on there as

Is there noone who has any ideas? Ive searched google like crazy but cant find any good information... Any tips on where else I could find information? ----Ursprungligt meddelande---- Fr?n: gabriel.j at telia.com Datum: Apr 12, 2005 2:36:24 PM Till: syslinux at zytor.com ?rende: [syslinux] Syslinux on USB initrd problem Hi! Im currently trying to encrypt my harddrive and plan to boot it of a

Ive done a new initrd but got the exact same error. Should rootfs really be minix? initrd is ext2. ----Ursprungligt meddelande---- Fr?n: jbebel at ncsu.edu Datum: Apr 13, 2005 11:58:26 PM Till: gabriel <gabriel.j at telia.com> ?rende: Re: Sv: Re: Sv: [syslinux] Syslinux on USB initrd problem I've got some really old instructions on creating an initrd up at

Hi My system data: Linux alucard 2.6.24.3 #4 SMP PREEMPT Sat Apr 26 19:36:27 CEST 2008 i686 GNU/Linux I selected the experimental cifs options (but I get the same behaviour with a different kernel where they aren't selected) mount.cifs version: 1.10-3.0.28a (but I also tried an earlier version) ubuntu hardy I bought a netgear ready nas nv+ and enabled a few cifs shares. When I try to mount

Hi I had some doubts regarding what all the init application should do: >> so, that should that application do? >> - mount /dev/hda1 /new-root >> - cd /new-root >> - run-init 1. Of what I understand, before exitting, init should mount the realroot and execute the init process. Is realroot the '/' or the empty directory created (in the cpio archive) ?

__FD_SET, __FD_CLR, __FD_ISSET, __FD_ZERO are inside of __KERNEL__ in: include/asm-ia64/posix_types.h and therefore not available. I've added stuff like this to our code: #ifndef __FD_SET #define __FD_SET(d, set) ((set)->fds_bits[__FDELT(d)] |= __FDMASK(d)) #endif but it would be nice if this can be solved in klibc. Thanks, Kay

Hi I am looking at inserting functions in the early user space and want to use initramfs for this. I understand this can be achieved using 'initrd' or by making changes in the 'usr/gen_init_cpio.c' file. Can someone kindly give me pointers as to how to go about this. I am looking at the 2.6.x kernel. Thanks Rachita.