search for: aaronmgriffin

remove 'NFS-Root' from an error message, and get rid of the old_root check, as it's unused and fails if the target filesystem is mounted 'ro' for no good reason. --- kinit.c 2006-03-21 23:48:15.000000000 -0600 +++ kinit.c 2006-03-22 01:09:39.000000000 -0600 @@ -191,7 +191,7 @@ } } else if (!S_ISDIR(st.st_mode)) { - fprintf(stderr, "NFS-Root:

Hey all, bug report time. I started tracking this down, but am at a bit of a loss for time, so I figured I'd report over this list to see if anyone else has the time to fix this or at least find the error. When calling nfsmount on it's own, say "nfsmount 1.2.3.4:/home/nfs /root" it works just fine, however, when calling nfsmount_main from within kinit (via nfsroot=), things get

...[ ! -d $$r/$$d ] && continue; \ + mkdir -p $(INSTALLROOT)$(INSTALLDIR)/$(KLIBCCROSS)include/$$d ; \ + cp -rfL $$r/$$d/. \ $(INSTALLROOT)$(INSTALLDIR)/$(KCROSS)include/$$d/. ; \ done ; \ done commit 9a6c1084bf4296840c0ed3877839af91c4ac2de3 Author: Aaron Griffin <aaronmgriffin at gmail.com> Date: Tue Sep 4 12:22:43 2007 +0200 [klibc] kinit: skip md assembly if mdX exists mkinitcpio initramfs(?) tries to start root MD device twice http://bugs.archlinux.org/task/4938 Belows patch shipped for one year in Archlinux, which seems to be an he...

...near future, is klibc open to accepting patches for "basic C features", such as fnmatch and/or getopt_long? ---------- Forwarded message ---------- From: Kay Sievers <kay.sievers at vrfy.org> Date: Aug 14, 2006 9:46 AM Subject: Re: [ANNOUNCE] udev 097 release To: Aaron Griffin <aaronmgriffin at gmail.com> Cc: Tobias Powalowski <t.powa at gmx.de>, linux-hotplug-devel at lists.sourceforge.net On Mon, 2006-08-14 at 09:27 -0500, Aaron Griffin wrote: > On 8/14/06, Kay Sievers <kay.sievers at vrfy.org> wrote: > > Klibc is not officially supported, but udev should sti...

...[ ! -d $$r/$$d ] && continue; \ + mkdir -p $(INSTALLROOT)$(INSTALLDIR)/$(KLIBCCROSS)include/$$d ; \ + cp -rfL $$r/$$d/. \ $(INSTALLROOT)$(INSTALLDIR)/$(KCROSS)include/$$d/. ; \ done ; \ done commit 9a6c1084bf4296840c0ed3877839af91c4ac2de3 Author: Aaron Griffin <aaronmgriffin at gmail.com> Date: Tue Sep 4 12:22:43 2007 +0200 [klibc] kinit: skip md assembly if mdX exists mkinitcpio initramfs(?) tries to start root MD device twice http://bugs.archlinux.org/task/4938 Belows patch shipped for one year in Archlinux, which seems to be an he...

Hello all, I'm a bit of a lurker on this list, so don't mind me. It appears that klibc-1.1.1 fails when 'cp-to-kernel'ed, using linux-2.6.15. Is it possible to produce another 'Stable' version? Call me a stickler, but I just don't like using something of this grade when marked 'Testing' or 'Unstable' by the developers themselves. Thanks, Aaron

Can someone please moderate the list and ban/remove: ssqd <asqqi@yahoo.co.jp> Thanks, Aaron

Hey all, I'm curious if any of you know decent way to test this sort of thing over ssh. That is, I have little experience with Xen/UML/VMware/etc etc, but the ones I have attempted were X-only apps, and thus not suited nicely to testing remotely. The rationale behind this is that my headless fileserver has a decent amount of 'juice' and idle clock cycles, so I've taken to

Looking at do_mounts.c, it does not seem to support the "major:minor" syntax exported in 'newer' sysfs (according to linux-2.6.15.6/init). The following is untested, but might work nicely... I will fully test this when I get home later today. PS, I also added some error output when it fails to parse the device number, just for kicks. As I said, I can't test this, so feel

I'm curious, and perhaps a bit naive about this stuff. I'd like to know the reason for having a klibc-$HASH.so version which the shared apps are linked against. It makes it less simple to build a static initramfs file list to use. Currently, one has to read the libc.so.hash file to build the filename, something that can't be done in a file list passed to gen_init_cpio unless it's

I'm not sure when exactly this started, but currently when I specify a ramfs image via the initrd line in grub, kinit picks it up as an initrd and tries (and fails) to unpack it and run linuxrc from it. I'm assuming this is not the intended behavior. Can anyone point me into the proper direction for unpacking an initramfs image ontop of the in-kernel image? Currently, I am using kernel

The attached patch breaks out the /dev/root device node creation from do_mounts, placing it in it's own utility (called mkrootdev). This is worthwhile, as certain setups will need the device node there to run fstype and load a proper module (or other things). No, it does not currently configure raid devices.... I didn't know if that made sense in there or not.... Let me know what you

As the title suggests, udev no longer compiles under klibc versions > 1.3.5 It may partially be udev's fault, however, certain symbols, such as SOCK_DGRAM, are no longer visible when compiling under klcc, which is causing this issue. A simple check of the linux/net.h header shows some ARCH_HAS_SOCKET_TYPES define, which is not set internally by udev's source. Where would be the most

I'm just curious. The older klibc tarballs had a syslinux dir used to build a syslinux image with klibc. While I haven't used it, I was planning on messing with it at some point in the future. However, the syslinux stuff was removed from recent klibc images. Is there a technical reson for this, or would is still be acceptable to use the old Makefiles from that dir to build syslinux?

The following patch will ignore already configured md devices in kinit. The rationale is that, if an md device already exists, it was previously assembled by some other tool (e.g. mdadm) and should remain there. Currently, kinit removes it and attempts to recreate it, which can cause all sorts of issues, especially in the situation that, the md device is further encrypted and/or is an lvm

I must profane ignorance of complicated filesystem stuff, so feel free to call me out here. Booting a root ext3 drive produces the following message at boot: kinit: trying to mount /dev/root on /root with type ext2 EXT2-fs warning (device hda3): ext2_fill_super: warning: mounting ext3 filesystem as ext2 When remounted rw by init, everything looks fine: $ mount | grep hda3 /dev/hda3 on / type

kinit.c contains the following lines before calling ipconfig_main: #ifdef INI_DEBUG args[a++] = (char *)"-n"; #endif In my attempts to debug the NFS mounting, this threw me off for a bit. (The -n parameter runs a "dry run" and does not actually configure the network). Thus, it seems it's actually impossible to debug NFS mounting with the stock, unpatched klibc. It

I don't really understand the necessity of the /arch.cmd file to be parsed before /proc/cmdline. It seems simpler to just parse the program args first before /proc/cmdline. The whole point, as far as I see, is to composite kernel params based on scripts and/or the bootloader params. It makes sense to say "arg1=a" should override (come before) any other arg1, but I see no need to

Hello, I don't know if this is bug-worthy or not It can be fixed in numerous places, but I think it might make the most sense to do it here.... kinit uses /dev/root to mount the rootfs. In normal userspace, this causes the root system to be displayed twice in apps like Nautilus, as /proc/mounts lists rootfs on /dev/root, in addition to the real info (e.g. ext3 on /dev/hda3). This is

Hey guys, in case you have spam filters to handle this stuff, I've seen quite alot of spam come across this ML in the past week or so (7 or so). Just a "heads up" really. Thanks, Aaron Griffin