On 2004-06-26 William Lee Irwin III <[EMAIL PROTECTED]> wrote:
> On 2004-06-25 William Lee Irwin III <[EMAIL PROTECTED]> wrote:
>>> Something bizarre has gone wrong. Literally the only changes should have
>>> been package metadata and the addition of the FPU fix.
> On Sat, Jun 26, 2004 at 11:03:32AM +0200, Andreas Metzler wrote:
>> Are you sure this is a kernel-image issue at all? This looks like the
>> 20th instance of either
>> 1a) #255180: module-init-tools: removal of modprobe.conf breaks
>> mkinitrd
>> 1b) #255390: mkinitrd does not find modprobe.conf
>> or
>> 2) #254950: module-init-tools complains about read only filesystem at
>> boot time
>> Both 1a and 2 have been fixed in module-init-tools 3.1-pre2-2.
> Is this on the build system, host system, or target system?
It would break mkinitrd, i.e. the system the kernel-image is installed
on.
cu andreas
