Re: running cvs update as root (was: Re: New install)
On June 10, 2014 6:24:17 AM CEST, Miod Vallat m...@online.fr wrote: http://www.openbsd.org/anoncvs.html shows the 'cvs update' command being run by root (# shell prompt), and I wouldn't expect any non-root user to have write permission to /usr/src anyway. So... why is doing the cvs-update as root a bad idea? Is this a kind of bad joke? Running anything as root unless it absolutely requires root privileges is a bad idea. Put yourself in the wsrc group, and you'll be able to write into /usr/src. Miod Indeed, however I agree that '#' suggests that the command is to be run as root, and could be confusing. /Alexander
Re: running cvs update as root (was: Re: New install)
On 2014-06-10, Alexander Hall alexan...@beard.se wrote: On June 10, 2014 6:24:17 AM CEST, Miod Vallat m...@online.fr wrote: http://www.openbsd.org/anoncvs.html shows the 'cvs update' command being run by root (# shell prompt), and I wouldn't expect any non-root user to have write permission to /usr/src anyway. So... why is doing the cvs-update as root a bad idea? Is this a kind of bad joke? Running anything as root unless it absolutely requires root privileges is a bad idea. Put yourself in the wsrc group, and you'll be able to write into /usr/src. Miod Indeed, however I agree that '#' suggests that the command is to be run as root, and could be confusing. Agreed, but this needs more work than just s/#/$/, as the suggested method to extract src.tar.gz etc don't leave the files with suitable ownership/perms. Diffs (to www/build/mirros/anoncvs.html.head please) are welcome :)
running cvs update as root (was: Re: New install)
In message http://marc.info/?l=openbsd-miscm=140224659303522w=1, Miod Vallat wrote (about an anoncvs update to /usr/src) you should not run this command as root http://www.openbsd.org/anoncvs.html shows the 'cvs update' command being run by root (# shell prompt), and I wouldn't expect any non-root user to have write permission to /usr/src anyway. So... why is doing the cvs-update as root a bad idea? ciao, -- -- Jonathan Thornburg [remove -animal to reply] jth...@astro.indiana-zebra.edu Dept of Astronomy IUCSS, Indiana University, Bloomington, Indiana, USA currently on the west coast of Canada There was of course no way of knowing whether you were being watched at any given moment. How often, or on what system, the Thought Police plugged in on any individual wire was guesswork. It was even conceivable that they watched everybody all the time. -- George Orwell, 1984
Re: running cvs update as root (was: Re: New install)
On Mon, Jun 09, 2014 at 03:07:17PM -0700, Jonathan Thornburg wrote: In message http://marc.info/?l=openbsd-miscm=140224659303522w=1, Miod Vallat wrote (about an anoncvs update to /usr/src) you should not run this command as root http://www.openbsd.org/anoncvs.html shows the 'cvs update' command being run by root (# shell prompt), and I wouldn't expect any non-root user to have write permission to /usr/src anyway. So... why is doing the cvs-update as root a bad idea? I'd like to hear from the experts, as well. That being said, if you make /usr/src, /usr/xenocara, usr/ports owned by root:wsrc, and chmod g+rwx all the directories, a regular user in that group seems to be able to do everything but install. With the caveat that if root has built previously in the same tree, you might have to clean up some stuff by hand. For example, I can build a kernel as a regular user, but I had to have root clear out the compile dir made by config, as this was last invoked by root. -- John D. Verne j...@clevermonkey.org
Re: running cvs update as root (was: Re: New install)
http://www.openbsd.org/anoncvs.html shows the 'cvs update' command being run by root (# shell prompt), and I wouldn't expect any non-root user to have write permission to /usr/src anyway. So... why is doing the cvs-update as root a bad idea? Is this a kind of bad joke? Running anything as root unless it absolutely requires root privileges is a bad idea. Put yourself in the wsrc group, and you'll be able to write into /usr/src. Miod
