Re: Dynamically defining classes, ordering, hardware detection

2003-01-16 Thread Niall Young
On Thu, 16 Jan 2003, Thomas Lange wrote: > > On Wed, 15 Jan 2003 14:53:21 -0500 (EST), AUSTIN MURPHY ><[EMAIL PROTECTED]> said: > > > On Wed, 15 Jan 2003, Niall Young wrote: > >> > >> How about overriding other class behaviour with hooks and > >> files, I guess that gets back

Re: Dynamically defining classes, ordering, hardware detection

2003-01-16 Thread Thomas Lange
> On Wed, 15 Jan 2003 14:53:21 -0500 (EST), AUSTIN MURPHY ><[EMAIL PROTECTED]> said: > On Wed, 15 Jan 2003, Niall Young wrote: >> >> How about overriding other class behaviour with hooks and >> files, I guess that gets back to the order in which everything >> is defined an

Re: Dynamically defining classes, ordering, hardware detection

2003-01-15 Thread Niall Young
On Wed, 15 Jan 2003, AUSTIN MURPHY wrote: > On Wed, 15 Jan 2003, Niall Young wrote: > > > > How about overriding other class behaviour with hooks and files, I > > guess that gets back to the order in which everything is defined > > and run - e.g. class FOO installs /etc/lilo.conf but if class BAH

Re: Dynamically defining classes, ordering, hardware detection

2003-01-15 Thread AUSTIN MURPHY
On Wed, 15 Jan 2003, Niall Young wrote: > > How about overriding other class behaviour with hooks and files, I > guess that gets back to the order in which everything is defined > and run - e.g. class FOO installs /etc/lilo.conf but if class BAH > also has one, how can I guarantee that BAH replaces

Re: Dynamically defining classes, ordering, hardware detection

2003-01-15 Thread Mate Kosor
On Wed, 15 Jan 2003, Niall Young wrote: > Has anyone looked into dynamically defining new classes based on > hardware detection routines like kudzu? > I don't know if this will help but I get some things from proc filesystem (like does machine have a CD or DVD). I did't found out how to detact

Dynamically defining classes, ordering, hardware detection

2003-01-14 Thread Niall Young
Has anyone looked into dynamically defining new classes based on hardware detection routines like kudzu? How about overriding other class behaviour with hooks and files, I guess that gets back to the order in which everything is defined and run - e.g. class FOO installs /etc/lilo.conf but if class