[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mkvmlinuz, boot-loaders and powerpc kernels.



On Sat, Jun 19, 2004 at 01:26:13PM +0200, Jens Schmalzing wrote:
> Hi,
> 
> Sven Luther writes:
> 
> > Some kind of alternative dependency on yaboot | quik | mkvmlinuz
> > would take care of fullfilling the dependency, without allowing
> > cruft to be installed, at least without needing yaboot and quik
> > where they are not needed, or letting mkvmlinuz pull in the binutils
> > dependency ?
> 
> This does not cover the case where a system uses a method outside its
> own Debian packaging system, such as BootX or a BootP/TFTP server.

Well, yes and no. BootX is non-free and we don't officially support it :)
As for BootP, TFTP, i believe you need either remote yaboot or an
mkvmlinuz generated vmlinuz for it to happen, right ? 

> Still, it's probably the best one can do with the control file.

Yep.

> > Jens, would that be an acceptable solution ?
> 
> To me this looks like the way to go.  I already exchanged a few
> messages with Manoj about a similar issue, namely packaging the boot
> glue into /usr/lib/kernel-image-<release>, which is now done by the
> debian/rules file of kernel-patch-powerpc.  We ended here:

Oh, you mean the bootloader choosing arch ? putting this script into
kernel-image-powerpc ? I am not sure this would work well, but don't
understand fully, also my proposal would work the same way for debian
and self-built packages, which is rather a good addition.

> Jens:
> 
> | May I suggest the following: We take care of the above two points by
> | adding a sub-architecture `generic' or `official' to powerpc and put
> | the necessary commands there.
> 
> Manoj:
> 
> | 	Sounds like a plan.

Huh, could you perhaps forward me the whole proposal also ? 

Friendly,

Sven Luther



Reply to: