On Mon, Nov 26, 2001 at 04:53:07PM -0500, rpjday wrote:
> On Mon, 26 Nov 2001, Chris Rouch wrote:
>
> > In an excellent ks custom CD document, rpjday@xxxxxxxxxxxxxx said:
> >
> > > NOTE: It's not hard to see how to customize the *existing* software
> > > components, but it's not as easy to add new components that you might want to
> > > define. That's (at least for now) beyond the scope of this mini-doc since it
> > > requires customizing aspects of the anaconda loader. I'm working on that and,
> > > when I figure it out, I'll let you know.
> >
> > Unless I've completely mis-understood what you mean, then this also is
> > simple. Just use the same format as for the existing ones, e.g.
> >
> > 0 Scanner {
> > sane-backends
> > sane-frontends
> > xsane
> > }
>
> it's not quite that simple, since you have the option of putting
> a cute graphic next to that software component, and this is where,
> i believe, you get into wanting to run "buildinstall" to add a
> new pixmap to the pixmap directory where python can find it once
> the loader starts to run.
>
> it may be that the default is just to have a blank graphic, but
> you can see that just adding a new software component adds a
> new level of complexity.
Actually the graphic is not to difficult. No need to modify ananconda.
The graphic needs to be added in the pixmap dir with the naming convention
of converting all chars to lowercase and replacing spaces with dashes.
e.g. comps section "Scanner" shown above would look for graphic
pixmap/scanner.png
comps section "This Is A Test Section" would look for
pixmap/this-is-a-test-section.png
I think this is correct based on my notes and recollection. If it doesn't
work you can find out what file name the install was looking for on one of
the virtual consoles.
Chuck.
>
> rday
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
