Hi folks,
I have to modify my initial bug report: initramfs-tools did
not actually attempt to take over a yaird generated ramfs.
Normally, on this machine, I need yaird generated initramfs,
but had not set yaird as the default, since I had no other ramdisk
generator. The sequence of events was this:
a) I install initramfs-tools
b) I compile and install a new kernel-image -- and yaird does not
run, but I fail to notice.
c) I run aptitude upgrade
d) I notice initramfs trying to regenerate my initrd, and failing.
e) I use yaird to generate an initrd, just to be safe, not noticing
that it had really been previously created by initramfs-tools
However, I still think that a ramdisk compiler automatically,
and without any notice or question, overwriting something as critical
as a booting mechanism, is a grave bug: the human needs to be kept in
the loop.
manoj
--
It is Mr. Mellon's credo that $200,000,000 can do no wrong. Our
offense consists in doubting it. -- Justice Robert H. Jackson
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
