Re: Tracking sarge

[Kurt Yoder <ktydeb@richard-group.com>]

On Feb 15, 2005, at 11:44 AM, Goswin von Brederlow wrote:

> Hi, me again:
>
> Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> writes:
>
> > Kurt Yoder <ktydeb@richard-group.com> writes:
> > > Unpacking kernel-image-2.6-amd64-generic (from
> > > .../kernel-image-2.6-amd64-generic_100_i386.deb) ...
> > > Setting up kernel-image-2.6.8-9-amd64-generic (2.6.8-8) ...
> > > cpio: (0x00000000): No such file or directory
> > > cp: cannot stat `(0x00000000)': No such file or directory
> > > run-parts: /usr/share/initrd-tools/scripts/e2fsprogs exited with 
> > > return
> > > code 1
> > > Failed to create initrd image.
> >
> > Can you test the sid mkinitrd or is that the same version. That bug
> > was reported some time ago and should have been fixed by now.
>
> Actualy the real culprit for that file is e2fsprogs. You need at least
> 1.35-7. From the changelog:
>
>   * Filter out linux-gate.so, which is a pseudo entry for the 32->64bit
>       translation for amd64 systems, in the initrd creation script.
>       (Closes: #253595)
>
> MfG
>         Goswin


I installed current sid/unstable e2fsprogs (1.36release-1), and the 
initrd installation problem seems to have been resolved. I do still see 
a warning "cpio: (0x00000000): No such file or directory", but now it 
doesn't seem to be fatal. Thanks for your help!

Should there be something added to the amd64 documentation? Or maybe 
dependencies for the amd64 kernels such that e2fsprogs must be at least 
version 1.35-7?

--

Kurt Yoder