On Sun, 23 Dec 2001, Omer Zak wrote: > > While this is true, the person who is given the duty of high-level > > administration and security policy (rather than short-term work like "just > > write a script that does '....'") will have to come with a considerable > > amount of Linux/Unix experience - e.g., from administering a personal Linux > > machine. > > Would it save Guy's time (and the time of other busy volunteers) if newbie > volunteer/s join and perform more routine tasks (if necessary, under the > supervision of the oldtimers)?
great. so now i'll have to: 1. explain to people who to do stuff. 2. fix their mistakes. 3. run after them, checking what they did and that it's ok. 4. go to actcom's offices every time someone breaks the system. sorry, i veto that, unless you do all the mentoring work, and find someone else to go fix the machine after it breaks (and it will). i'm willing to go fix the machine after it breaks only in 2 cases: 1. i broke it. 2. i trust the person who broke it, and thus assume this breaking was a possible (yet rare) accident. 3. it was broken due to hardware problems. so far, each of these things happened once (plus visiting actcom for the initial physical installation of the machine - that is a given) - i think it totaled 5-6 visits to the machine - usually for several hours per visit. we have a mixed situation here - on one hand, this machine is supposed to give a service, and people expect it to work. on the other hand - its a sever for the community, and part of this is allowing the community to learn about system administration. you're combining the worst of both worlds :) > How feasible is to keep a backup of the scripts and config files to be > able to recover from newbie's screwups (except for the mirror disks, of > course)? its feasible only if you're in a workplace, and cleaning up after newbies is part of your job. its not feasible for remote administration on one's spare time, unless one realy wants to do this cleaning up. so what this all comes to: 1. root password should only be given to people with experience, or those that have proved useful and donated enough of their time, that others will feel ok with cleaning up after them. 2. less-experienced users could be given a responsibility of maintaining something that does NOT require root password, and that is rather secluded. in this case, they still need to have experience as linux users, and to be dependable. so i repeat - are there volunteers, or aren't there? so far all i see is talking and general talking. behdad offered to write the run-rsync shell script, and thus i'll forward the description of the script to him. this still doesn't resolve the issue of actually maintaining the mirror itself (and i'm reluctant to open accounts for people whose sysadmining abilities i've never experienced - source code i can still read before installing). -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
