I'm new to classes :-) but as an extension to bundling all of a class's components together - what would be the best way to separate the builtin FAI classes from user defined classes? Or is it assumed that the whole FAI_CONFIGDIR/* will be customised completely?!?
I'd like to keep my own classes as separate as possible and not touch the builtin classes and scripts if possible. Something like: FIRST custom1 custom2 ... DEFAULT LAST where FIRST and LAST are never modified, class/S* are never modified but instead of defining custom classes in the default scripts we provide an *environment* from which our custom classes and DEFAULT can base decisions on to define further classes. e.g. instead of modifying and defining classes in class/S01alias.sh and S03hwdetect.source etc. this type of thing is moved inside each individual class. What I'm driving at is to separate and modularise as much as possible, keep FAI scripts separate to class definitions, and bundle the class definitions and scripts together. Provide an environment in which classes can be easily defined and moved to other FAI servers easily. You could then `make-fai-class <name>` which would fill in an empty class template for you to complete, similar to dh_make. It could do anything, but here's a few common solutions with the guts commented out for you to expand on... Niall Young Chime Communications Pty Ltd [EMAIL PROTECTED] Level 6, 263 Adelaide Terrace Ph: (+61) 08 9213 1330 / 0408 192 797 Perth, Western Australia 6000 "there's a lot of movement in my trousers at the moment" -- Dennis Kristofich, Sep 2002