The following message is a courtesy copy of an article
that has been posted to gmane.linux.debian.devel.kernel as well.
severity 358397 grave
thanks
On 26 Mar 2006, maximilian attems wrote:
> severity 358397 important
> stop
>
> hello Manoj,
>
> On Wed, 22 Mar 2006, Manoj Srivastava wrote:
>
>> The package fails to install (failure to check if the image is
>> modifiable), is the first part. Failure to install makes is
>> unuseable.
>
> ro /boot is not a standard debian config.
> initramfs-tools need to error out or full /boot would allow the
> linux-image to stay configured without having a correct initrd.img
Err, failing to change my initrd is not the grave bug. Trying
to overwrite my yaird created initrd is. Indeed, changing a working
boot sequence by changing an initrd while installing the initrd
generator is the grave bug.
If gcc recompiled every binary on my machine on install, or
installing kernel sources recompiled the running kernel, it would be
a similar grave bug.
In this case, if I did not have an alternate kernel image, or
knoppix, had initramfs-tools been able to write to /boot, I would
have had an unbootable machine. This is not something we should be
doing in Sid by design. If initramfs-tools needs this much debugging,
move it to experimental.
>> ,----
>>> Errors were encountered while processing: initramfs-tools E:
>>> Sub-process /usr/bin/dpkg returned an error code (1) A package
>>> failed to install. Trying to recover: Setting up initramfs-tools
>>> (0.57b) ... touch: cannot touch
>>> `/boot/initrd.img-2.6.15.4-skas3-v9-pre8': Read-only file system
>>> /usr/sbin/mkinitramfs: line 218:
>>> /boot/initrd.img-2.6.15.4-skas3-v9-pre8: Read-only file system
>>> cpio: write error: Broken pipe dpkg: error processing
>>> initramfs-tools (--configure): subprocess post-installation script
>>> returned error exit status 1 Errors were encountered while
>>> processing: initramfs-tools
>> `----
>>
>> The init ram fs was not created using initramfs-tools, and yet
>> it tries to recreate the initramfs on upgrade, without asking the
>> admin, which is an problem in its own right: Why is automated
>> regeneration of the initramfs being done? If I want to, I should be
>> able to refresh the initrd when I wish it should be updated.
>
> ok so an upgrade of initramfs-tools tried to alter an yaird
> generated initramfs. i'm sorry but i can't reproduce that: $ egrep
> ramdisk /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitrd.yaird
> /usr/sbin/mkinitrd
Err, that is not my setup.
manoj
--
Don't lose heart ... they might want to cut it out ... and they want
to avoid a lengthy search. --anonymous
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]
