[Fedora-livecd-list] Support for custom configuration using python templates

[John (J5) Palmieri]

On Wed, 2007-04-25 at 12:58 -0400, David Zeuthen wrote:
> Hi,
> 
> On Tue, 2007-04-24 at 14:53 -0400, John (J5) Palmieri wrote:
> > Any suggestions?  I am willing to do the code myself but in the lack
> > of any interest I'm going to end up creating a one off solution, so
> > mucho input is desired.
> 
> I think munging configuration files might be outside the scope of the
> livecd-tools project; sure, granted it's something people want to do but
> often it's used as a hack; for example on my system 
> 
>  $ rpm -qf /etc/issue
>  fedora-release-6.93-1

And I'm going to package that up for every daily release?  And what
about countries? Too heavy and engineered for an image based
distribution.

> so I think what you *could* do instead is to have olpc-release or
> similar on OLPC provide that file (would be based on fedora-release). Of
> course, since /etc/issue is marked as %config(noreplace) in the
> fedora-release it's still sane for you to edit it in %post. I guess it
> all depends on the configuration file in question.
> 
> So I think my point of view right now is that it's good enough to do
> this in %post for most cases; I mean, if downstreams (like OLPC) need to
> change a ton of configuration files/defaults perhaps there is something
> broken with the apps you try to include? 

No just that apps can be configured for different purposes.  For
instance gedit can be made into a development environment but requires
me to write out a bunch of gconf files.  We have Sabyon for a reason.
It basically does what I want to do in the case of gconf and some other
settings.  It is a dump of configuration files.

> Perhaps you can come up with concrete examples of what configuration
> files / defaults you need to edit /change? I think that would be useful.
> Thanks.

/etc/sysconfig/modules/olpc-1.modules for the module lists to load
/etc/rwtab for stateless tmpfs mounted stuff
/etc/asound.state to put the correct default sound levels
/etc/modprobe.d/olpc.conf.dist so we get the correct module parameters
/boot/olpc_build for build info that the bootloader uses
/etc/issue for build info the user can read
/etc/securetty for adding the serial console
/etc/inittab for removing unneeded memory waisting VT's
/usr/share/fonts/dejavu-lgc/fonts.dir for mapping legacy fonts
/usr/share/fonts/dejavu-lgc/fonts.scale same as above
/usr/share/fonts/dejavu-lgc/fonts.alias same
/etc/X11/xorg.conf and its variants for booting on any device and
getting the correct xorg config file with the correct keyboard laysouts
/home/olpc/.xinitrc for launching sugar
/boot/grub/grub.conf for the occasional qemu boot
/etc/init.d/olpc-configure init script for boot time configuration
/usr/share/X11/xkb/symbols/* for keyboard configuration that is not yet
upstream (note that these must be added to an already existing file)
/boot/olpc.fth - for booting from openfirmware

Note that we can't move a lot of these to an RPM because RPM conflict
rules would prevent them from being installed.  Some files need input
such as BUILD number and some files change so rapidly during the testing
phase that taking the time to build an rpm and place it in the right
spot and rebuild the repo would be a unneeded bottleneck.

-- 
John (J5) Palmieri <johnp at redhat.com>