Bug#343042: [Yaird-devel] Bug#343042: #343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat

2005-12-14 Thread Erik van Konijnenburg
On Wed, Dec 14, 2005 at 10:42:58AM +, Richard Antony Burton wrote: > Package: yaird > Version: 0.0.12-1 > Followup-For: Bug #343042 > > FYI the above workaround does not work for machines with SATA drives. I > couldn't > find a combination of modules that would get it to boot. > > Switching

Bug#343048: linux-image-2.6.14-2-k7: same proble, kernel fails to load ide drive.. in my case the drive is under /sys/block/hdb/dev

2005-12-13 Thread Erik van Konijnenburg
On Tue, Dec 13, 2005 at 01:44:34PM -0500, Scott James Williamson wrote: > FYI: > > if you use a nvidia nforce 2 based motherboard, to get DMA on your > drives, add the following "MODULE amd74xx" after evdev and before > ide-generic to the /etc/yaird/Default.cfg file: > >MODULE evdev

Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (patch results, amended)

2005-12-13 Thread Erik van Konijnenburg
On Tue, Dec 13, 2005 at 12:48:41PM -0200, Paulo Marcel Coelho Aragao wrote: > Paulo Marcel Coelho Aragao wrote on Dec, 13: > > > > > http://arch.debian.org/arch/yaird/[EMAIL > > > > > PROTECTED]/yaird/yaird--devo/yaird--devo--0.1/patch-131/ > > > > > Could you give it a try and let me know if it

Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (applying the patch)

2005-12-12 Thread Erik van Konijnenburg
On Tue, Dec 13, 2005 at 07:23:41AM +0100, Erik van Konijnenburg wrote: > **Save the attached patch. Oops, patch attached for real now. --- orig/perl/Hardware.pm +++ mod/perl/Hardware.pm @@ -234,7 +234,10 @@ # The above error persists in 2.6.12, and is solved # in 2.6

Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (applying the patch)

2005-12-12 Thread Erik van Konijnenburg
On Mon, Dec 12, 2005 at 09:18:01PM -0200, Paulo Marcel Coelho Aragao wrote: > Erik van Konijnenburg wrote on Dec, 12: > > http://arch.debian.org/arch/yaird/[EMAIL > > PROTECTED]/yaird/yaird--devo/yaird--devo--0.1/patch-131/ > > Could you give it a try and let me know

Bug#329319: yaird: swsusp not all that hard

2005-12-12 Thread Erik van Konijnenburg
On Fri, Dec 09, 2005 at 11:12:05AM -0500, C. Scott Ananian wrote: > Package: yaird > Version: 0.0.11-12 > Followup-For: Bug #329319 > > It's not all that hard to prevent log replay: just don't mount the file > systems! Resume should happen *after* the modules required to access the > swap partiti

Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

2005-12-12 Thread Erik van Konijnenburg
On Mon, Dec 12, 2005 at 08:47:30PM +0200, Aapo Rista wrote: > On Mon, 12 Dec 2005, Erik van Konijnenburg wrote: > > To help pin down the cause, could you post the output of: > > yaird -v -o crap.img 2.6.14-4-686 > > yaird -v -o crap.img 2.6.14-5-686 > > (assumin

Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

2005-12-11 Thread Erik van Konijnenburg
On Mon, Dec 12, 2005 at 08:07:21AM +0200, Aapo Rista wrote: > Package: linux-image-2.6.14-2-686 > Version: 2.6.14-5 > Followup-For: Bug #343048 > > > After upgrading linux-image-2.6.14-2-686 from 2.6.14-4 to 2.6.14-5, > IBM Thinkpad X40 fails to boot. Last lines before the end of > initializing p

Bug#343042: [Yaird-devel] Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

2005-12-11 Thread Erik van Konijnenburg
On Mon, Dec 12, 2005 at 04:33:29AM +0100, Cesare Leonardi wrote: > Paulo Marcel Coelho Aragao wrote: > > Package: linux-image-2.6.14-2-686 > > Version: 2.6.14-5 > > Severity: critical > > Justification: breaks the whole system > > > > Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and

Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'

2005-12-11 Thread Erik van Konijnenburg
On Mon, Dec 12, 2005 at 12:34:11AM -0200, Paulo Marcel Coelho Aragao wrote: > Package: linux-image-2.6.14-2-686 > Version: 2.6.14-5 > Severity: critical > Justification: breaks the whole system > > Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, > boot > is interrupted

Bug#342904: [Yaird-devel] Bug#342904: yaird: Error creating initrd on Sparc64

2005-12-11 Thread Erik van Konijnenburg
On Sun, Dec 11, 2005 at 08:11:57PM +0100, Frans Pop wrote: > On Sunday 11 December 2005 19:57, Erik van Konijnenburg wrote: > > http://arch.debian.org/arch/yaird/[EMAIL PROTECTED]/yaird/yaird > >--devo/yaird--devo--0.1/patch-129/ > > Thanks for the quick reaction. > With

Bug#342904: [Yaird-devel] Bug#342904: yaird: Error creating initrd on Sparc64

2005-12-11 Thread Erik van Konijnenburg
On Sun, Dec 11, 2005 at 06:54:02PM +0100, Frans Pop wrote: > On Sunday 11 December 2005 17:12, Frans Pop wrote: > > During installation of linux-image-2.6.14-2-sparc64 (2.6.14-5), yaird > > failed with the following error: > > yaird error: unrecognised legacy device: /sys/devices/serio1 > > Additi

Bug#342905: [Yaird-devel] Bug#342905: yaird: barfs when dpkg tries to recover after earlier failure

2005-12-11 Thread Erik van Konijnenburg
On Sun, Dec 11, 2005 at 05:12:28PM +0100, Frans Pop wrote: > When configuration of a package fails, dpkg in some cases tries to recover > by running the postinst scripts again. For yaird this resulted in the > following error: > yaird error: destination /boot/initrd.img-2.6.14-2-sparc64.new alrea

Bug#342652: yaird missed support for CRYPTO_AES_586 and CRYPTO_AES_X86_64

2005-12-10 Thread Erik van Konijnenburg
On Fri, Dec 09, 2005 at 12:05:10PM +0100, Stefan Schmidt wrote: > Since kernel version 2.6.8 there are also config option > CRYPTO_AES_586. With version 2.6.13 CRYPTO_AES_X86_64 was added. > > So it would be good to add support also to perl/KConfig.pm > Otherwise you have a problem with compiled

Bug#341273: Doesn't understand install and remove directives in modprobe.conf

2005-12-08 Thread Erik van Konijnenburg
On Thu, Dec 08, 2005 at 04:42:51PM -0500, Norbert Veber wrote: > On Sat, Dec 03, 2005 at 07:46:34PM +0100, Erik van Konijnenburg wrote: > > The reason is that install lines in the modprobe configuration are complete > > shell scripts: they can invoke every executable, access every

Bug#341738: linux-image-2.6.14-2-686: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.14-2-686 auto (fatal)

2005-12-07 Thread Erik van Konijnenburg
On Tue, Dec 06, 2005 at 02:28:01PM +0200, Jari Aalto wrote: > > Following my other posts: Here is install report from another machine, > with exactly the same results. I've tried to reproduce as much debug > as I know. Let me know how can I help more. Thanks, very clear report. > /dev/hda7

Bug#341738: linux-image-2.6.14-2-686: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.14-2-686 auto (fatal)

2005-12-04 Thread Erik van Konijnenburg
On Sun, Dec 04, 2005 at 10:38:37AM +0200, Jari Aalto wrote: > Erik van Konijnenburg <[EMAIL PROTECTED]> writes: > | -- hack /usr/sbin/mkinitrd.yaird to echo the yaird command line > | and its own arguments to some scratch file, then do > | dpkg-reconfigure linux-

Bug#341273: Doesn't understand install and remove directives in modprobe.conf

2005-12-03 Thread Erik van Konijnenburg
On Tue, Nov 29, 2005 at 01:57:32PM -0500, Norbert Veber wrote: > yaird error: modprobe psmouse requires install /sbin/modprobe mousedev > && /sbin/modprobe --ignore-install psmouse (fatal) > Failed to create initrd image. > > from my modprobe configuration: > alias /dev/psaux psmouse > install psm

Bug#341738: linux-image-2.6.14-2-686: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.14-2-686 auto (fatal)

2005-12-03 Thread Erik van Konijnenburg
On Sat, Dec 03, 2005 at 10:18:53AM +0200, Jari Aalto wrote: > Erik van Konijnenburg <[EMAIL PROTECTED]> writes: > | On Fri, Dec 02, 2005 at 06:36:41PM +0200, Jari Aalto wrote: > | > Setting up linux-image-2.6.14-2-686 (2.6.14-4) ... > | > Using /usr/sbin/mkinitrd.ya

Bug#341738: linux-image-2.6.14-2-686: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.14-2-686 auto (fatal)

2005-12-02 Thread Erik van Konijnenburg
On Fri, Dec 02, 2005 at 06:36:41PM +0200, Jari Aalto wrote: > Setting up linux-image-2.6.14-2-686 (2.6.14-4) ... > Using /usr/sbin/mkinitrd.yaird to build the ramdisk. > Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd > /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. > yaird erro

Bug#341559: yaird: fails to create initrd

2005-12-01 Thread Erik van Konijnenburg
On Thu, Dec 01, 2005 at 11:25:34PM +0100, Hans Ekbrand wrote: > On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote: > > On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote: > > > On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote: > > Attached is a patch that made it mat

Bug#340344: yaird: Fail to create initrd on s390/s390x

2005-12-01 Thread Erik van Konijnenburg
On Thu, Dec 01, 2005 at 12:03:58PM +0100, Ivan Warren wrote: > 1) Hardware.pm was missing "load CcwDev" and "load CcwMap" (easy fix) Oops, thanks for the fix, is in the repo now. > 2) The initramfs gets built : OK, looks normal. > 3) Boot fails : > Device /sys/block/dasda/dev seems to be down. >

Bug#340344: yaird: Fail to create initrd on s390/s390x

2005-11-30 Thread Erik van Konijnenburg
On Thu, Dec 01, 2005 at 02:49:03AM +0100, Ivan Warren wrote: > The build went ok.. however, here is what I get : > > deb390-1:/tmp# /home/ivan/local/sbin/yaird -v -o junk.img > yaird: goal: template, prologue (/home/ivan/local/etc/yaird/Default.cfg:52) > yaird: action: prologue, {} > yaird: goal

Bug#336688: ide-generic in yaird

2005-11-30 Thread Erik van Konijnenburg
After further testing: the issue that ide-generic creates /sys/devices/ide0/0.0, which leads to ide-generic being selected as appropriate driver by yaird, instead of a faster via82cxxx is real. Workaround for old versions of yaird is to place via82cxxx early in Default.cfg. The point that via82cx

Bug#340344: yaird: Fail to create initrd on s390/s390x

2005-11-30 Thread Erik van Konijnenburg
On Wed, Nov 23, 2005 at 12:00:31AM +0100, Ivan Warren wrote: > > > # yaird -o /tmp/a 2.6.14-2-s390x > > > yaird error: unsupported device required: dasda (fatal) > > > > > Could you post > > .. Most certainly... Thanks, that helps. After looking at your output and a debian kernel for s390 it se

Bug#336688: yaird also add [permanent] ide-generic

2005-11-22 Thread Erik van Konijnenburg
On Wed, Nov 23, 2005 at 12:02:17AM +0100, Mau wrote: > Frederik Schueler wrote: > >On other boxes, notably amd74xx and piix based ones I have access to, > >this was not needed. > > > > > Probably it wasn't needed because in those setups the piix module was > correctly detected as "needed for ac

Bug#340344: yaird: Fail to create initrd on s390/s390x

2005-11-22 Thread Erik van Konijnenburg
On Tue, Nov 22, 2005 at 09:39:50PM +0100, Ivan S. Warren wrote: > > # yaird -o /tmp/a 2.6.14-2-s390x > yaird error: can't open /proc/bus/input/devices (fatal) > > I therefore removed the "INPUT" goal from /etc/yaird/Default.cfg > (since input devices on S/390 z/Arch is irrelevant) as well > as an

Bug#336688: yaird also add [permanent] ide-generic

2005-11-21 Thread Erik van Konijnenburg
On Mon, Nov 21, 2005 at 02:21:57PM +0100, Frederik Schueler wrote: > on my via82cxxx box, I had to load the via driver before the ide-generic > one since I switched to a 2.6. kernel, configured manually first in > /etc/mkinitrd/modules and now in /etc/yaird/Default.cfg. > > On other boxes, notabl

Bug#336688: yaird also add [permanent] ide-generic

2005-11-20 Thread Erik van Konijnenburg
On Sun, Nov 20, 2005 at 11:40:00PM +0100, Sven Luther wrote: > On Sun, Nov 20, 2005 at 10:19:19PM +0100, Erik van Konijnenburg wrote: > > On Fri, Nov 18, 2005 at 03:36:52AM +0100, Mau wrote: > > > ide-generic should probably not be permanent as it's not needed to boot &g

Bug#336688: yaird also add [permanent] ide-generic

2005-11-20 Thread Erik van Konijnenburg
On Fri, Nov 18, 2005 at 03:36:52AM +0100, Mau wrote: > Yaird also adds to the initrd the [permanent] ide-generic module, > which then prevents piix from loading. The result are the messages > "PIIX4: port 0x01f0 already claimed by ide0" and "PIIX4: port 0x0170 > already claimed by ide1" at boot and

Bug#336392: Acknowledgement (linux-image-2.6.14-1-686: 2.6.14 doesn't boot after dist-upgrade from 2.6.12)

2005-11-11 Thread Erik van Konijnenburg
On Fri, Nov 11, 2005 at 08:16:43AM +0100, Olaf van der Spek wrote: > Erik van Konijnenburg wrote: > > On Thu, Nov 10, 2005 at 11:25:43PM +0100, Olaf van der Spek wrote: > >>yaird: goal: mountdir, / (/usr/lib/yaird/conf/Default.cfg:143) > >>yaird: action: insmod, &g

Bug#336392: Acknowledgement (linux-image-2.6.14-1-686: 2.6.14 doesn't boot after dist-upgrade from 2.6.12)

2005-11-10 Thread Erik van Konijnenburg
On Thu, Nov 10, 2005 at 11:25:43PM +0100, Olaf van der Spek wrote: > Erik van Konijnenburg wrote: > > Could you do > > > > yaird --verbose --output=/tmp/pindakaas.img 2.6.14-1-686 > > lspci > > debian:~# yaird --verbose --output=/tmp/pindakaas.img 2.6

Bug#336392: Acknowledgement (linux-image-2.6.14-1-686: 2.6.14 doesn't boot after dist-upgrade from 2.6.12)

2005-11-10 Thread Erik van Konijnenburg
On Thu, Nov 10, 2005 at 10:28:50PM +0100, Jonas Smedegaard wrote: > On Sun, 30 Oct 2005 12:01:28 +0100 Olaf van der Spek <[EMAIL PROTECTED]> > wrote: > > > Try do a 'dpkg-reconfigure linux-image-2.6.14-1-686' and see if it > > > spews out any errors or warnings. > > > > # dpkg-reconfigure linux-i

Bug#336988: yaird: ignoring 'mesh' doesn't allow root device to be found

2005-11-10 Thread Erik van Konijnenburg
On Mon, Nov 07, 2005 at 08:13:05PM +0100, Sven Luther wrote: > On Mon, Nov 07, 2005 at 07:48:32PM +0100, Erik van Konijnenburg wrote: > > On Sat, Nov 05, 2005 at 03:30:26PM -0800, Beiad Dalton wrote: > > > 'mesh' is the onboard oldworld SCSI host adapter; my install

Bug#338228: yaird error: unrecognised line in /proc/bus/input/devices: S: Sysfs=/class/input/input0 (fatal)

2005-11-09 Thread Erik van Konijnenburg
ch-log/patch-96 * modified files --- orig/ChangeLog +++ mod/ChangeLog @@ -2,6 +2,20 @@ # arch-tag: [EMAIL PROTECTED]/yaird--devo--0.1 # +2005-11-09 14:12:07 GMT Erik van Konijnenburg <[EMAIL PROTECTED]> patch-96 + +Summary: + pre 0.0.12 +Revision: + yaird

Bug#337479: yaird: should use /usr/bin/perl, not /usr/local/bin/perl

2005-11-09 Thread Erik van Konijnenburg
On Wed, Nov 09, 2005 at 10:20:47PM +0100, Mattia Dongili wrote: > On Wed, Nov 09, 2005 at 08:16:08PM +0100, Laurent Bonnaud wrote: > > On sam, 2005-11-05 at 16:31 +0100, Mattia Dongili wrote: > [...] > > > I's like > > > configuring a package with silly ./configure options and pretending it > > > w

Bug#337479: yaird: should use /usr/bin/perl, not /usr/local/bin/perl

2005-11-09 Thread Erik van Konijnenburg
On Wed, Nov 09, 2005 at 08:16:08PM +0100, Laurent Bonnaud wrote: > On sam, 2005-11-05 at 16:31 +0100, Mattia Dongili wrote: > > > and you probably have /usr/local/bin before /usr/bin in your path > > Yes as on all unmodified Debian systems. > > > I'd say this is a problem in the submitter's buil

Bug#337293: linux-image-2.6.14-1-k7: kernel doesn't boot...

2005-11-07 Thread Erik van Konijnenburg
On Mon, Nov 07, 2005 at 09:49:53PM +0100, Erik van Konijnenburg wrote: > On Mon, Nov 07, 2005 at 10:54:37AM +0100, Bruno Boettcher wrote: > > On Thu, Nov 03, 2005 at 09:09:34PM +0100, Erik van Konijnenburg wrote: > > Hello! > > > > > Underneath the tmpfs mounted on

Bug#337855: yaird fails with error "Could not read output for /usr/bin/ldd ... (fatal)"

2005-11-07 Thread Erik van Konijnenburg
On Sun, Nov 06, 2005 at 11:22:35PM +0100, Walter Hofmann wrote: > I have a yaird configuration which includes /bin/busybox, a statically > linked executable. yaird calls "/usr/bin/ldd /bin/busybox", which > returns with exit status 1 because the file is not a dynamic executable. > yaird checks for

Bug#336988: yaird: ignoring 'mesh' doesn't allow root device to be found

2005-11-07 Thread Erik van Konijnenburg
On Sat, Nov 05, 2005 at 03:30:26PM -0800, Beiad Dalton wrote: > 'mesh' is the onboard oldworld SCSI host adapter; my installation > happens to be on this, so when I boot 2.6.14-1-powerpc, I have no root > filesystem. Could you post 'ls -lR /sys' to see what kind of input we have to recognise this

Bug#335230: More Code also Random, but less :-)

2005-11-03 Thread Erik van Konijnenburg
Progress update: Script started on Thu 03 Nov 2005 09:55:57 PM CET [EMAIL PROTECTED]:~$ uptime 21:56:01 up 2 min, 2 users, load average: 1.64, 1.17, 0.47 [EMAIL PROTECTED]:~$ df -k Filesystem 1K-blocks Used Available Use% Mounted on

Bug#337279: yaird: /boot != /tmp

2005-11-03 Thread Erik van Konijnenburg
On Thu, Nov 03, 2005 at 09:20:55PM +0100, Sven Luther wrote: > On Thu, Nov 03, 2005 at 09:12:35PM +0100, Jonas Smedegaard wrote: > > On Thu, 3 Nov 2005 20:31:40 +0100 Sven Luther <[EMAIL PROTECTED]> wrote: > > > On Thu, Nov 03, 2005 at 11:44:23AM -0500, Anthony DeRobertis wrote: > > > > /boot is fo

Bug#337293: linux-image-2.6.14-1-k7: kernel doesn't boot...

2005-11-03 Thread Erik van Konijnenburg
On Thu, Nov 03, 2005 at 07:11:56PM +0100, Bruno Boettcher wrote: > > i installed the kernel through dselect, when i reboot the whole things > comes to a grinding halt with: > Switching root > /usr/lib/yaird/exec/run_init: opening console: No such file or directory > Kernel panic _ not syncing: Att

Bug#337168: (no subject)

2005-11-02 Thread Erik van Konijnenburg
On Wed, Nov 02, 2005 at 07:01:48PM -0500, Michael Stroucken wrote: > yaird gives an error when it parses my fstab, saying that label () > wasn't found. My fstab contains the lines > LABEL=/ / ext3defaults,errors=remount-ro 0 1 > LABEL=/boot /boot

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-11-02 Thread Erik van Konijnenburg
On Wed, Nov 02, 2005 at 12:23:15AM +0100, Erik van Konijnenburg wrote: > On Tue, Nov 01, 2005 at 12:39:13PM +0100, Jonas Smedegaard wrote: > > On Tue, 1 Nov 2005 07:14:45 +0100 Erik van Konijnenburg <[EMAIL PROTECTED]> > > wrote: > > > On Mon, Oct 31, 2005 at 10:4

Bug#337065: yaird: fails with error: uuid '472dd55c-c2ab-462b-a7b1-2cc890b2d074' not found

2005-11-02 Thread Erik van Konijnenburg
On Wed, Nov 02, 2005 at 03:42:20PM +0200, Antonio Kanouras wrote: > yaird error: uuid '472dd55c-c2ab-462b-a7b1-2cc890b2d074' not found > (/etc/fstab:5) (fatal) > I attached a copy of my /etc/fstab. > UUID=472dd55c-c2ab-462b-a7b1-2cc890b2d074 / xfs > defaults0

Bug#335601: compaq arrays with ida

2005-11-02 Thread Erik van Konijnenburg
On Wed, Nov 02, 2005 at 05:16:48PM +0100, Erich Schubert wrote: > Hi, > the compaq smart arrays I have use "ida": > /dev/ida/c0d0p5 on / type ext3 (rw,errors=remount-ro) > /dev/ida/c0d0p1 on /boot type ext2 (rw) > /dev/ida/c0d0p6 on /home type ext3 (rw,nodev) > as well as /sys/block/ida!c0d0 > The

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-11-01 Thread Erik van Konijnenburg
On Tue, Nov 01, 2005 at 12:39:13PM +0100, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, 1 Nov 2005 07:14:45 +0100 > Erik van Konijnenburg <[EMAIL PROTECTED]> wrote: > > > On Mon, Oct 31, 2005 at 10:42:13AM +0100, Jonas Smed

Bug#336567: postinst fails runnng modprobe on 'ext3,ext2'

2005-11-01 Thread Erik van Konijnenburg
On Tue, Nov 01, 2005 at 11:07:06PM +0100, Sven Luther wrote: > On Tue, Nov 01, 2005 at 10:28:05PM +0100, Jonas Smedegaard wrote: > > On Tue, 1 Nov 2005 22:00:34 +0100 Sven Luther <[EMAIL PROTECTED]> wrote: > > > > Well, using debconf is packaging. > > > Well, i disagree > > > > > You are makind de

Bug#336518: yaird: document using NFS Root

2005-11-01 Thread Erik van Konijnenburg
On Tue, Nov 01, 2005 at 10:38:56PM +0100, Jonas Smedegaard wrote: > Erik: Would it make sense to allow static IP, and only choke on non-IP > value before the colon in fstab? Finding the server would be easier. Now to figure out a way to decide whether client should have a hard-coded IP address or

Bug#336518: yaird: document using NFS Root

2005-11-01 Thread Erik van Konijnenburg
On Tue, Nov 01, 2005 at 10:24:05PM +0100, Sven Luther wrote: > On Tue, Nov 01, 2005 at 09:03:37PM +0100, Erik van Konijnenburg wrote: > > On Tue, Nov 01, 2005 at 06:02:57PM +0100, Jonas Smedegaard wrote: > > > On Mon, 31 Oct 2005 19:52:52 -0700 Vagrant Cascadian <[EMAIL PRO

Bug#336636: fails on fstab line without optional fields

2005-11-01 Thread Erik van Konijnenburg
s -x configure -x aclocal.m4 -x depcomp -x missing -x Makefile -x Makefile.in -x install-sh -x INSTALL p79/ChangeLog p83/ChangeLog --- p79/ChangeLog 2005-11-01 22:55:04.0 +0100 +++ p83/ChangeLog 2005-11-01 22:55:16.0 +0100 @@ -2,6 +2,62 @@ # arch-tag: [EMAIL PROTECTED]/yair

Bug#336518: yaird: document using NFS Root

2005-11-01 Thread Erik van Konijnenburg
On Tue, Nov 01, 2005 at 06:02:57PM +0100, Jonas Smedegaard wrote: > On Mon, 31 Oct 2005 19:52:52 -0700 Vagrant Cascadian <[EMAIL PROTECTED]> > wrote: > > On Sun, Oct 30, 2005 at 11:51:11PM +0100, Jonas Smedegaard wrote: > > > Currently, MOUNTDIR does not support nfsroot so needs to be > > > commen

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-31 Thread Erik van Konijnenburg
On Mon, Oct 31, 2005 at 10:42:13AM +0100, Jonas Smedegaard wrote: > On Mon, 31 Oct 2005 00:08:24 + "Richard Burton" <[EMAIL PROTECTED]> wrote: > > > So, I have a workaround. Not sure how this should be fixed > > permanently though? Easiest way would seem to be to change the yaird > > Default.c

Bug#335230: More Code also Random, but less :-)

2005-10-31 Thread Erik van Konijnenburg
On Mon, Oct 31, 2005 at 11:00:45AM +0100, Mattia Dongili wrote: > On Mon, October 31, 2005 1:00 am, Erik van Konijnenburg said: > > On Fri, Oct 28, 2005 at 08:12:57PM +0200, Marco Amadori wrote: > >> Diff attached, diffed to extracted yaird-0.11-9, but should not differs to

Bug#336514: yaird: falls down when new scsi/sata disks are added

2005-10-31 Thread Erik van Konijnenburg
On Mon, Oct 31, 2005 at 01:20:32PM -0500, Daniel Jacobowitz wrote: > On Mon, Oct 31, 2005 at 07:18:01PM +0100, Jonas Smedegaard wrote: > > On Mon, 31 Oct 2005 12:47:58 -0500 Daniel Jacobowitz <[EMAIL PROTECTED]> > > wrote: > > > On Mon, Oct 31, 2005 at 06:09:28PM +0100, Jonas Smedegaard wrote: > >

Bug#336599: please support dm-crypt devices

2005-10-31 Thread Erik van Konijnenburg
On Mon, Oct 31, 2005 at 12:46:27PM +, Martin Michlmayr wrote: > Package: yaird > Version: 0.0.11-10 > Severity: wishlist > > Please support dm-crypt devices. Given that initrd-tools handles this fine, > yaird should really support it if it wants to be a replacement... > > | yaird error: encr

Bug#336598: cannot parse /etc/fstab file with SMB share

2005-10-31 Thread Erik van Konijnenburg
On Mon, Oct 31, 2005 at 06:19:56PM +0100, Mattia Dongili wrote: > merge 336585 336598 > thanks > > On Mon, Oct 31, 2005 at 12:45:25PM +, Martin Michlmayr wrote: > > Package: yaird > > Version: 0.0.11-10 > > Severity: grave > > > > yaird fails when /etc/fstab contains a SMB share, such as: > >

Bug#336585: yaird: The fs_freq and fs_passno fields in /etc/fstab are optional

2005-10-31 Thread Erik van Konijnenburg
On Mon, Oct 31, 2005 at 04:51:11PM +, Ian Campbell wrote: > On Mon, 2005-10-31 at 17:45 +0100, Jonas Smedegaard wrote: > > And upstream knew about it? > > The comment in the code is a bit vague, he could be talking about these > fields, or perhaps some other optional extra fields... The comm

Bug#336585: yaird: The fs_freq and fs_passno fields in /etc/fstab are optional

2005-10-31 Thread Erik van Konijnenburg
omp -x missing -x Makefile -x Makefile.in -x install-sh -x INSTALL p77/ChangeLog p78/ChangeLog --- p77/ChangeLog 2005-10-31 20:59:00.0 +0100 +++ p78/ChangeLog 2005-10-31 20:59:07.0 +0100 @@ -2,6 +2,23 @@ # arch-tag: [EMAIL PROTECTED]/yaird--devo--0.1 # +2005-10-31

Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

2005-10-30 Thread Erik van Konijnenburg
On Sun, Oct 30, 2005 at 10:21:39PM +0100, Jonas Smedegaard wrote: > On Sun, 30 Oct 2005 15:25:33 + "Richard Burton" <[EMAIL PROTECTED]> wrote: > > > >This could be changes to video drivers in the kernel. Please describe > > >your graphics card used. > > > > Oops, I did intened to mention that

Bug#335230: More Code also Random, but less :-)

2005-10-30 Thread Erik van Konijnenburg
On Fri, Oct 28, 2005 at 08:12:57PM +0200, Marco Amadori wrote: > Diff attached, diffed to extracted yaird-0.11-9, but should not differs to > much I think. > > I tried to go more in deep into this project, but I still needed a lot of > pseudocode comments. > > Please comments my doubts and ques

Bug#336378: yaird fails to prepare an initrd image when vesafb-tng is present

2005-10-29 Thread Erik van Konijnenburg
On Sat, Oct 29, 2005 at 11:49:56PM +0300, Er?in EKER wrote: > Package: yaird > Version: 0.0.11-9 > > I have compiled linux-2.6.14 with kernel-package and when i wanted to > install the Deb packages yaird complains about the strange video mode > given in kernel configuration. > > command line fail

Bug#335230: More stub code

2005-10-27 Thread Erik van Konijnenburg
On Wed, Oct 26, 2005 at 09:49:13AM +0200, Mattia Dongili wrote: > On Tue, October 25, 2005 10:13 pm, Erik van Konijnenburg said: > > On Tue, Oct 25, 2005 at 08:09:06PM +0200, Mattia Dongili wrote: > > The init() function looks OK. Detail: you're doing a fork/exec of > >

Bug#335230: More stub code

2005-10-25 Thread Erik van Konijnenburg
On Tue, Oct 25, 2005 at 08:09:06PM +0200, Mattia Dongili wrote: > I've been able to setup an almost-working evms box (at least evms_query > reports useful data). > > I tried following Erik's suggestions and also implemented part of the > init() method and reworked some of Marco's code. > Some part

Bug#335601: compaq smart array controller support in yaird

2005-10-24 Thread Erik van Konijnenburg
0-24 23:51:03.0 +0200 +++ p74/ChangeLog 2005-10-24 23:50:57.0 +0200 @@ -2,6 +2,27 @@ # arch-tag: [EMAIL PROTECTED]/yaird--devo--0.1 # +2005-10-22 15:03:19 GMT Erik van Konijnenburg <[EMAIL PROTECTED]> patch-74 + +Summary: + 0.0.12 - preparing for .

Bug#335230: Random Code so far to be cleaned

2005-10-24 Thread Erik van Konijnenburg
0 +0100 > +++ yaird-0.0.11-evms/perl/Evms.pm2005-10-24 18:31:24.0 +0200 > @@ -0,0 +1,70 @@ > +#!perl -w > +# > +# Evms -- encapsulate evms_gather output > +# Copyright (C) 2005 Erik van Konijnenburg, Marco Amadori > +# > +# This program is free software; you

Bug#335315: yaird: vgchange does not find logical volumes on a dm-crypt device

2005-10-23 Thread Erik van Konijnenburg
On Sun, Oct 23, 2005 at 12:20:04PM +0200, Tino Keitel wrote: > my root partition is located in a LVM2 on a dm-crypt device. vgchage > doesn't find any VGs during boot. > > The reason is that vgchange doesn't look for VGs on other device mapper > devices per default. To enable this, this line has

Bug#335230: [#335230] How to actually support EVMS in an initrd

2005-10-23 Thread Erik van Konijnenburg
On Sun, Oct 23, 2005 at 01:07:26PM +0200, Mattia Dongili wrote: > On Sat, Oct 22, 2005 at 10:01:02PM +0200, Sven Luther wrote: > > On Sat, Oct 22, 2005 at 09:47:12PM +0200, Marco Amadori wrote: > > > Alle 21:18, sabato 22 ottobre 2005, Steinar H. Gunderson ha scritto: > > > > > > > EVMS support in

Bug#335264: yaird fails with older (titanium) powerbooks.

2005-10-23 Thread Erik van Konijnenburg
On Sun, Oct 23, 2005 at 01:31:54AM +0200, Sven Luther wrote: > On my titanium powerbook, yaird fails with : > > yaird error: unrecognised device: > /sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io > yaird error: unrecognised device: > /sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-

Bug#335230: [#335230] How to actually support EVMS in an initrd

2005-10-22 Thread Erik van Konijnenburg
On Sat, Oct 22, 2005 at 09:54:54PM +0200, Steinar H. Gunderson wrote: > On Sat, Oct 22, 2005 at 09:47:12PM +0200, Marco Amadori wrote: > >> - Make sure /dev/ is writable, and mkdir /dev/evms. > > Translate this in perl plz :-) > > Well, the "make sure" part depends on how yaird works. You may hav

Bug#329319: swsusp2 in initramfs risks disk corruption

2005-10-19 Thread Erik van Konijnenburg
Changing the init script to do swsusp is easy, but without other changes you risk data corruption; see for references http://www.suspend2.net/HOWTO-4.html A more robust solution requires not replaying the journal from initramfs in logbased filesystems. libblkid helps here. I'm still examining the

Bug#333858: initrd/initramfs: we discussed enough, let's take some action now :)

2005-10-15 Thread Erik van Konijnenburg
On Sat, Oct 15, 2005 at 06:15:04PM +0200, Jonas Smedegaard wrote: > On Sat, 15 Oct 2005 16:34:57 +0200 Erik van Konijnenburg <[EMAIL PROTECTED]> > wrote: > > On Sat, Oct 15, 2005 at 08:57:31AM +0200, Sven Luther wrote: > > > On Sat, Oct 15, 2005 at 08:47:57AM +0200,

Bug#333858: initrd/initramfs: we discussed enough, let's take some action now :)

2005-10-15 Thread Erik van Konijnenburg
On Sat, Oct 15, 2005 at 08:57:31AM +0200, Sven Luther wrote: > On Sat, Oct 15, 2005 at 08:47:57AM +0200, Erik van Konijnenburg wrote: > > On Fri, Oct 14, 2005 at 12:53:41PM +0200, Jonas Smedegaard wrote: > Hey, i didn't know the mkinitrd wrapper was shell, or i would have do

Bug#333196: Default settings for yaird are unsuitable for initrd replacement.

2005-10-10 Thread Erik van Konijnenburg
On Mon, Oct 10, 2005 at 10:47:21PM +0200, Sebastien Bernard wrote: > Yaird package has a poor choice for default Template.cfg. > 2 different set of files are provided in the /usr/lib/yaird/conf > directory. > One named Debian.cfg (the Template.cfg is a copy of this file). > One named Debian-initrd.

Bug#327762: yaird: includes (unnecessary?) psmouse module in generated image.

2005-09-18 Thread Erik van Konijnenburg
On Sun, Sep 11, 2005 at 09:16:42PM -0300, Diego Essaya wrote: > I may be wrong, but I think that the 'psmouse' module is unnecessary. > In fact, I don't have a PS/2 mouse (I have a USB one). > > The 'evdev' and 'mousedev' modules may be unnecessary as well... In the meantime 0.0.11 is published,

Bug#325768: yaird: "can't open blacklist /etc/hotplug/blacklist (fatal)"

2005-09-01 Thread Erik van Konijnenburg
On Wed, Aug 31, 2005 at 03:32:19AM -0500, Peter Samuelson wrote: > [Erik van Konijnenburg] > > The upstream 0.0.11 tarball has the attached fix to make the blacklist > > optional; workaround obvious. > > I hope it's not *exactly* the attached fix: > > > - par

Bug#325768: yaird: "can't open blacklist /etc/hotplug/blacklist (fatal)"

2005-08-30 Thread Erik van Konijnenburg
On Tue, Aug 30, 2005 at 02:58:12PM -0500, Peter Samuelson wrote: > I don't have a /etc/hotplug/blacklist file. I do have a > /etc/hotplug/blacklist.d/ which other packages have installed things > into. Since I don't have hotplug installed, I am not sure if hotplug > is supposed to create and main

Bug#324774: yaird: does not work with current mdadm

2005-08-25 Thread Erik van Konijnenburg
> > On Tue, Aug 23, 2005 at 07:03:49PM -0400, Daniel Jacobowitz wrote: > > > When I installed a kernel using yaird to create the ramdisk, I got an > > > error > > > that there were no listed devices in the mdadm output. I edited > > > RaidTab.pm > > > to invoke mdadm with -v (--verbose), and the

Bug#324774: yaird: does not work with current mdadm

2005-08-24 Thread Erik van Konijnenburg
On Tue, Aug 23, 2005 at 07:03:49PM -0400, Daniel Jacobowitz wrote: > When I installed a kernel using yaird to create the ramdisk, I got an error > that there were no listed devices in the mdadm output. I edited RaidTab.pm > to invoke mdadm with -v (--verbose), and then things seemed to work OK. T

Bug#317504: Spurious build-dependency on build-essential

2005-07-09 Thread Erik van Konijnenburg
On Sat, Jul 09, 2005 at 12:43:17PM +0200, Jonas Smedegaard wrote: > On 09-07-2005 09:56, Jeroen van Wolffelaar wrote: > > Package: yaird > > Severity: normal > > Your package has a spurious build-depends on build-essential. > > Build-essential packages are already guaranteed to be installed, and >

Bug#315549: kernel-image-2.6.8-2-sparc64: Fails to recognize and start md2 during boot

2005-06-23 Thread Erik van Konijnenburg
On Thu, Jun 23, 2005 at 02:50:32PM +0200, Henrik Stoerner wrote: > Package: kernel-image-2.6.8-2-sparc64 > Version: 2.6.8-15 > Severity: normal > > This kernel fails to recognize all LVM RAID-1 devices. It will > automatically detect md0 and md1, but fails to detect md2. > > During bootup it ther

Bug#294404: Bug#273182: a possible fix/workaround

2005-05-22 Thread Erik van Konijnenburg
On Sun, May 22, 2005 at 12:06:27PM +0200, Marco d'Itri wrote: > On May 22, martin f krafft <[EMAIL PROTECTED]> wrote: > > > Erik said that if initrd brings up /dev/md0, partitions from other > > software RAID devices (e.g. /dev/md7) cannot be brought up since the > > above code skips the MAKEDEV c

Bug#301560: Bug#273182: a possible fix/workaround

2005-05-22 Thread Erik van Konijnenburg
On Sun, May 22, 2005 at 02:58:04AM -0700, Steve Langasek wrote: > On Sat, May 21, 2005 at 07:17:21PM +0200, Erik van Konijnenburg wrote: > > Mdadm is of course perfectly capable of creating it's own /dev/md0, > > provided auto=md is given for the relevant device in /

Bug#294404: Bug#273182: a possible fix/workaround

2005-05-21 Thread Erik van Konijnenburg
The reworked patch is in wishlist #310126, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=310126 Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310126: mdadm auto processing with patch

2005-05-21 Thread Erik van Konijnenburg
Package:mdadm Version:1.9.0-2.1 Severity: wishlist The mdadm package can automatically create device files when assembling drives, provided the auto=md or auto=part7 option is added to the relevant drives in the configuration file. It turns out these configuration options ar

Bug#294404: Bug#273182: a possible fix/workaround

2005-05-21 Thread Erik van Konijnenburg
On Sat, May 21, 2005 at 08:58:46PM +0200, martin f krafft wrote: > (taking unrelated bugs out of the loop.) > > also sprach Erik van Konijnenburg <[EMAIL PROTECTED]> [2005.05.21.1957 +0200]: > > * at S40 or so, you come along, see that /dev/md0 exists, and decide > >

Bug#294404: Bug#273182: a possible fix/workaround

2005-05-21 Thread Erik van Konijnenburg
On Sat, May 21, 2005 at 07:29:55PM +0200, martin f krafft wrote: > also sprach Erik van Konijnenburg <[EMAIL PROTECTED]> [2005.05.21.1917 +0200]: > > > - echo "Starting raid devices: " > > > + if [ -d /dev/.udevdb -a ! -e /dev/md0 -a ! -e /dev/md/0 ];

Bug#273182: a possible fix/workaround

2005-05-21 Thread Erik van Konijnenburg
On Sat, May 21, 2005 at 05:35:48PM +0200, martin f krafft wrote: > - echo "Starting raid devices: " > + if [ -d /dev/.udevdb -a ! -e /dev/md0 -a ! -e /dev/md/0 ]; then > +echo -n "Creating raid device nodes: " > +cd /dev && WRITE_ON_UDEV=1 ./MAKEDEV md > +echo "

Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built

2005-05-19 Thread Erik van Konijnenburg
On Thu, May 19, 2005 at 06:39:35PM -0700, rds wrote: > > --- Erik van Konijnenburg <[EMAIL PROTECTED]> wrote: > > Oops, there's indeed one other point you'll need to check: > > you'll also need to make sure AUTOSTART is set correctly > > in /etc/defa

Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built

2005-05-19 Thread Erik van Konijnenburg
On Thu, May 19, 2005 at 05:50:06AM -0700, rds wrote: > > > Quick question: why not add an auto=md clause to /etc/mdadm/mdadm.conf? > > That way you have the option of *not* assembling some md drives if > > necessary. > > I can't try this right now but I doubt this would help. The reason is that

Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition on raid1 when initrd.img is built

2005-05-18 Thread Erik van Konijnenburg
On Wed, May 18, 2005 at 04:52:55PM -0700, rds wrote: > > Re: Bug#304483: mkinitrd does not create "mdadm -A" record for /boot partition > on raid1 when initrd.img is built > > > i'm a bit puzzled why you expect from initrd to mount all the mdadm > > partitions, from your report i see that the ini

Bug#295412: initrd-tools: Fails to ignore 32bit emulation layer on ldd calls

2005-02-23 Thread Erik van Konijnenburg
On Wed, Feb 23, 2005 at 05:58:59AM +0100, Harald Dunkel wrote: > Joshua Kwan wrote: > > Harald Dunkel wrote: > > > >> Assuming that valid shared library paths start with '/' > >> I would suggest to apply this patch to mkinitrd: > > > > > > Hmm, maybe not if LD_LIBRARY_PATH is being used. Beware. >

Bug#281591: cannot hit Return at DELAY prompt on SunBlade 100

2005-02-19 Thread Erik van Konijnenburg
On Sat, Feb 19, 2005 at 07:00:31PM +0100, Frans Pop wrote: > It is not very likely that this is an initrd-tools problem. > We have several installation reports for SunBlade 100 that mention that > the USB keyboard does not work correctly after booting debian-installer. > > So it is much more like

Bug#288150: multipath-tools: initrd script breaks booting lvm root

2005-01-16 Thread Erik van Konijnenburg
criptor 1 - echo required files to fd 4 - echo required script fragment to fd 5 - echo names of required executables and libraries to fd 6 Regards, Erik On Thu, Jan 13, 2005 at 01:59:22PM +0100, Guido Guenther wrote: > On Wed, Jan 12, 2005 at 11:02:50PM +0100, Erik van Konijnenburg wrote: >

Bug#288150: multipath-tools: initrd script breaks booting lvm root

2005-01-12 Thread Erik van Konijnenburg
Package: multipath-tools Version: 0.4.1-1 Severity: critical Justification: breaks the whole system Tags: patch If multipath-tools-0.4.1-1 is installed, the initrd generated by initrd-tools-0.1.76 is non-bootable for systems using an LVM root device. Symptoms: pivot_root: no such file or director