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
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
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
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
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
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
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
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
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
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
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
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:
> >
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
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,
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
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
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 /
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]
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
> >
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 ];
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 "
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:
>
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
23 matches
Mail list logo
