Your message dated Tue, 25 Jan 2005 15:56:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line fixed in initrd-tools 0.1.76
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Sep 2004 18:12:37 +0000
>From [EMAIL PROTECTED] Fri Sep 17 11:12:37 2004
Return-path: <[EMAIL PROTECTED]>
Received: from chiark.greenend.org.uk [193.201.200.170] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1C8NDp-0008OD-00; Fri, 17 Sep 2004 11:12:37 -0700
Received: from [192.168.124.112] (helo=riva.lab.dotat.at)
        by chiark.greenend.org.uk (Debian Exim 3.35 #1) with esmtp
        for [EMAIL PROTECTED]
        (return-path [EMAIL PROTECTED])
        id 1C8NDm-0007O2-00; Fri, 17 Sep 2004 19:12:35 +0100
Received: from cjwatson by riva.lab.dotat.at with local (Exim 3.35 #1 (Debian))
        for [EMAIL PROTECTED]
        id 1C8NDh-00020b-00; Fri, 17 Sep 2004 19:12:29 +0100
Date: Fri, 17 Sep 2004 19:12:29 +0100
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: /sys/block names are mangled with '!' in current 2.6 kernels, not '.'
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: initrd-tools
Version: 0.1.74
Severity: important

Devices such as /dev/cciss/c0d0p1 used to have their names mangled in
/sys/block with '.' in place of '/', producing paths like
/sys/block/cciss.c0d0/cciss.c0d0p1/dev. However, current kernels use '!'
rather than '.' as the mangling character, so you get
/sys/block/cciss!c0d0/cciss!c0d0p1/dev. See
http://mail.nl.linux.org/linux-mm/2003-12/msg00087.html for some related
comments, fixing another part of the kernel to cope with this.

The upshot is that initrds generated by initrd-tools fail to figure out
how to mount root filesystems on CCISS devices.

/usr/share/initrd-tools/init copes with the old naming, like this:

        IFS=/
        set -f
        set +f ${root#/dev/}
        IFS=.
        root=$*
        unset IFS
        try_name "$root" && return

It's probably best for us to try both. The following patch (actually
against 0.1.70 rather than 0.1.74, but should still apply) works for me:

  http://www.no-name-yet.com/patches/initrd-tools.sys-block.diff

Cheers,

-- 
Colin Watson                                       [EMAIL PROTECTED]

---------------------------------------
Received: (at 272139-done) by bugs.debian.org; 25 Jan 2005 20:54:24 +0000
>From [EMAIL PROTECTED] Tue Jan 25 12:54:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42] (postfix)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CtXhg-0003Fi-00; Tue, 25 Jan 2005 12:54:24 -0800
Received: from dragon.kitenet.net (unknown [66.168.94.144])
        (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
        (Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
        by kitenet.net (Postfix) with ESMTP id 04DCD18321;
        Tue, 25 Jan 2005 20:54:24 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
        id 6CA386E10B; Tue, 25 Jan 2005 15:56:30 -0500 (EST)
Date: Tue, 25 Jan 2005 15:56:30 -0500
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED]
Subject: fixed in initrd-tools 0.1.76
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 3


--wac7ysb48OaltWcw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

These bugs were fixed in initrd-tools 0.1.76, which included the changes
made in version 0.1.75, which was uploaded only to experimental. The
changelog reads:

   * Jeff Bailey
     - Turn error into a warning on modprobe failure.  Add extra text
       explaining that sometimes this warning might be erroneous.
       (Closes: #263216)
     - new kernels don't list scsi modules in /proc/scsi (Closes: #271038)
       Patch from Harald Dunkel <[EMAIL PROTECTED]>
   * Simon Horman
     - Create ida devices (Closes: Bug#276591)
   * Martin Michlmayr
     - Deal with block name manging in 2.6, thanks Colin Watson.
       (Closes: #272139)
   * Simon Horman
     - Only activate the VG that contain the root device to avoid
       tyring to activate VGs that include partitions on devices
       whose device drivers are not yet available. (Closes: #280571)

--=20
see shy jo

--wac7ysb48OaltWcw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB9rJ9d8HHehbQuO8RArghAKC5Pw98UIMzSdnEBlnIZvaKbKwK3gCghaGl
MY6x0s0LpS2VPmni5Be8JJc=
=a9IQ
-----END PGP SIGNATURE-----

--wac7ysb48OaltWcw--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to