Bug#369965: [Yaird-devel] Bug#369965: Fixed.

[Jonas Smedegaard]

On Thu, 15 Jun 2006 01:50:33 +0530 Rohan Dhruva wrote:

> Well, very sorry, it was not a yaird problem at all. Somehow my
> /dev/null in the static /dev had been replaced with a file, and hence
> the errors. The problem did not occur with the initrd created by
> initramfs-tools since it starts udev from within the initrd. Would the
> be feasible for yaird ? Anyway, I am closing the bug, since yaird
> works perfectly as it is expected to :) Sorry for the 'spam' ;)

Thanks for following up on this.

No, it really does not make sense for yaird to use udev: The very
approach of yaird is to be smart at ramdisk build time, and exact at
runtime - which is more or less the opposite of initramfs-tools+udev.

If I somehow misunderstood your suggestion, or you have other ideas for
possible improvements of yeaird, please file wishlist bugs about them
(instead of discussing them in this - now closed - bugreport).

Input is very welcome - no question or suggestion is too stupid!


 - 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/yaird-devel/attachments/20060622/235e5c20/attachment.pgp