On Wed, May 25, 2005 at 01:18:34PM -0400 or thereabouts, Paul Smith wrote:
>
> db> I was the one who implemented that patch for genkernel, and I
> db> specifically implemented it for use with catalyst.
>
> db> You just need to have some process for introducing the linuxrc into
> db> the catalyst chroot during the build process(which is what I did).
>
> OK. I think it's good that genkernel has that option, definitely.
>
> But it seems to me like it would be much cleaner from a Catalyst
> perspective (and certainly simpler for the user) if there were a
> Catalyst option that took a filename, then Catalyst would handle putting
> that file into the chroot and adding --linuxrc to the argument list of
> genkernel pointing to that file.
>
> No?
>
naw, much better to put something in spec file like
livecd/linuxrc: <path to my linuxrc>
> db> The code for doing this is in the embedded build type(which I also
> db> wrote), so you just need to add those bits to the livecd_stageX
> db> module.
>
> Hm, sorry for my noobie brain, but I didn't grok that sentence :-)
>
> What's "the embedded build type" and where would I set about looking for
As andrew already mentioned it's a 'module' inside catalyst that
describes how to build a certain type of system from a spec file.
I actually implemented it as part of the 'kernel' arguments to the
spec file. My files look something like this:
boot/kernel: vanilla
boot/kernel/runscript: /usr/lib/catalyst-devel/targets/embedded/kmerge.sh
boot/kernel/vanilla/sources: =sys-kernel/vanilla-sources-2.4.26
boot/kernel/vanilla/config: /root/kernel-config
boot/kernel/vanilla/gk_kernargs: --arch-override=x86
--linuxrc=/tmp/mergeroot/linuxrc
boot/kernel/vanilla/gk_action: all
help at all ?
pgpQicJnGyPRF.pgp
Description: PGP signature
|
