Re: fai/class separation
On Thu, 16 Jan 2003 14:44:57 +0800 (WST), Niall Young [EMAIL PROTECTED] said: 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?!? After you've installed fai using apt-get or dpkg and you have called fai-setup you have no scripts in FAI_CONFIGDIR (/usr/local/share/fai). Then fai suggests to copy examples of scripts and config files from usr/share/fai/templates to FAI_CONFIGDIR. But you can also create all theses files by your own. So you have the freedom to write your own scripts in ../class/ which defines classes. But I recommend to use the template scripts which defines the classes. One important feature of theses scripts is, that the class mechanism is very simple. It's just a ordered list of class names, which defines a priority inside the classes. Using more complex scripts and using inheritance or dependencies makes the whole configuration task complex. I think it will be very hard to have controll over all the dependencies you are creating inside the classes and scripts. What about testing (oooh testing takes a lot of time) this huge moster of classes and scripts in /fai/scripts. Do you think these scripts will work in all situations of defined classes when classes create dependencies? My preference is: Keep it simple! I'd like to keep my own classes as separate as possible and not touch the builtin classes and scripts if possible. Something like: But you will always have the freedom to define the classes as you like. It you dislike fai-class, just write a hook task_defclass.DEFAULT and you can do whatever you want. -- Gruss Thomas
Re: fai/class separation
Thomas Lange wrote: My preference is: Keep it simple! I'd like to keep my own classes as separate as possible and not touch the builtin classes and scripts if possible. Something like: But you will always have the freedom to define the classes as you like. It you dislike fai-class, just write a hook task_defclass.DEFAULT and you can do whatever you want. Nested classes work fine to define dependencies and hierarchy anyway with package_config/*, class/[CLASS].var and class/[CLASS] files. To order the operation of things, write hooks at different points to do things that need ordered operation. It would be nice to specify a root class defined on the floppy via make-fai-bootfloppy, so I didn't have to change nis-domain in /etc/dhcpd.conf every time I want to stamp a different configuration. I converted to dynamic IP because MAC addresses are not constant here. Yes, testing does take a lot of time! With business-minded fai-users among you in Euroland and elsewhere near computer surplus supply, I am interested in a co-operative arrangement between our respective 'companies' to share methods and effort. After all, I cannot re-export code I imported(?) We can take advantage of the planned obsolescence of commercial operating systems. --mark-- -- Recycle Computer -- Your b2b Linux computer factory! 2260 Chanticleer Ave. Suite 10-A+1-831-AKA-SBOX Santa Cruz, CA 95062 USA +1-831-464-3008
