That makes sense to me. I've gotten used to the convenience of su'ing and then proceeding with everything from step one, since I'm going to need to su anyway, but technically, you're absolutely right about root being reserved only until needed.
On 09/29/11 13:14, David Baelde wrote: > Hi, > > To put it simply: when it is about being root, the question should not > be "why not be root" but "why be root". If you can do it as a normal > user, you should. > > Concretely, there is a bug somewhere in the generated configure script > that erases /dev/null. If run as root, this is REALLY annoying. If run > as a normal user, nothing happens. > > Building (make && make doc) should also be done as non-priviledged > user. Only make install requires root priviledges. > > Cheers, ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
