Bug#336514: yaird: falls down when new scsi/sata disks are added
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 1 Nov 2005 09:04:35 +0100
Sven Luther <sven.luther@wanadoo.fr> wrote:
> On Mon, Oct 31, 2005 at 03:48:44PM -0500, Daniel Jacobowitz wrote:
> > On Mon, Oct 31, 2005 at 09:45:54PM +0100, Erik van Konijnenburg
> > wrote:
> > > Interesting to experiment with, but not a quick fix for today.
> >
> > Sure. I'd just like to point out that, today, there is no way to
> > add a drive to a configuration like mine, while using yaird, that
> > is not extremely painful, manual, and awkward. Even if I had known
> > that yaird would be such a problem before I did it, there's no
> > obvious way to generate a new initrd for any configuration other
> > than my current one.
>
> The plan for this is to modify the d-i rescue mode to be able to
> regenerate the yaird initrd (BTW, Jonas, maybe you could already add
> a yaird .udeb for that), so you add your disk, boot into the d-i
> rescue mode, the ramdisk gets regenerated, and all works fine.
Is that plan documented somewhere?
I seem to remember sceptical voices when that approach was mentioned on
#debian-kernel. One point raised was with remote-controlled systems.
What I would like is a kernel-install-helper extended to provide the
user with a choice of ramdisk tool similar to choice of default
dictionaries today. Read the draft here:
wiki.debian.org/FlexibleKernelHandling
Regarding udeb: Could someone provide me a good reference for that - I
have never packaged a udeb.
- Jonas
- --
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
- Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDZ0B1n7DbMsAkQLgRArEPAJ9E7iIHS4x0wt/5IKKLbKTyHGcQEgCfTdSN
QZ3V2H6++YbO14WhxtnpAhQ=
=sywv
-----END PGP SIGNATURE-----
Reply to: