>> Not practical? Come on, it's one line of code: >> >> `find /`.split(/\n/) >> >> > I started running that command on my VM a few minutes ago, and I'm still > waiting for it to return. >
This is really weird. It seems I can say the most absurd things today and people will take me quite seriously. If only I could figure out to harness this new found power... Basically (and joking aside) I don't like having a dead spot in a language >> based on "oh but you couldn't possibly want that" reasoning. > > > We've long said that you can't model an entire system state using puppet > resources - that most of it is unmanaged, and only few things are explicitly > managed. Listing all files on a system seems uncomfortably close to trying > to capture the entire machine state to me. > That's why I'm suggesting we provide some way of indicating which files we consider "managed" for the purpose of this ral operation; either that or we should eliminate the analogous functionality of "ralsh host", "ralsh user", "ralsh package" etc. My objection is to the rule being "we can discover resources unless there might be more than some arbitrary number of them in which we get serious about not talking about unmanaged resources." Or, to put it another way, how would you feel if the find command refused to enumerate all the files on your system because there might be too many of them? -- M ----------------------------------------------------------- The power of accurate observation is commonly called cynicism by those who have not got it. ~George Bernard Shaw ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
