On Wed, 7 Mar 2007, Jeffrey Law wrote:
During the boot process, after setup of the union and bind mounts, the client contacts the puppetmaster to download any configuration information appropriate for the client.
I think part of my problem is a lack of understanding of puppet. Is there a good guide I should read up on before bugging people any more.
Also note that without some form of persistent storage you can get into situations where you lose data. Consider mail or print spooling as an example. If the client reboots while mail or print jobs are in the spool directory and the client has no persistent storage, then those jobs will simply be lost into the ether. If the client has some persistent storage, then those jobs will be flushed out of the spool directory when the client comes back up.
Losing data is A okay with me ;)
Out of curiosity, what are you trying to do with stateless?
In many ways I'm just having a play to see what it can do. I'm installing this on a display wall where you have a stateful headnode, shared home directories, plus 6 stateless slaves that are powering the displays. Slaves are entirely storage free. jh -- "I think it is well also for the man in the street to realise that there is no power on earth that will protect him from being bombed. Whatever people may tell him, the bomber will always get through. The only defence is in offence which means you have to kill more women and children more quickly than the enemy if you want to save yourselves." -- Stanley Baldwin _______________________________________________ Stateless-list mailing list [email protected] http://www.redhat.com/mailman/listinfo/stateless-list
