On Tue, Jan 13, 2004 at 12:09:24PM -0500, Mark Seger wrote: > I created an autoinstall script using the --scripts option to build a > custom script for my image, let's call it foo. I would expect for the > image and overrides directory to be named foo, but in fact I'm seeing > the image named foo but the overrides directory taking on the name > specified in --scripts.
correct - the main reason for override directories is to allow different types of clients to layer files on top of a shared image. for example, you can have an image X, with corresponding scripts X-ide and X-scsi. however, fstab and lilo.conf need to be different for each image, since one will need to reference hda, the other sda. so, the override directory for X-ide would contain the versions that reference hda, while X-ide's override directory would contain config files that reference sda. you can have multiple override directories pulled during an install, and there's no reason some of your configs can't share a set of these override directories. ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
