Re: cvs stupid user problem, please help me debug
Lo, on Friday, February 22, Paul E Condon did write: > I saved a cvs repository of personal programs in RedHat some time ago, > before I discovered Debian. Now I'm trying install it and access the > files in it. I used tar to save the whole repository as cvs.tgz. When > I untar it, I discover that the permissions are wrong and the group > assignment of the files is different from the Debian convention. So I > set about to make them right for Debian, but I can't get it to work. To which Debian convention are you referring? The numeric GIDs should have shifted, but other than that, I'm not aware of any Debian convention for ownership of files in a CVS repository. In fact, due to the way CVS repositories work, such a convention would most likely be counterproductive. > First question: Debian uses "src" as the conventional group name for > cvs internal files. Granted, I've customized my repository pretty heavily, but I don't see this: [ankh-morpork:/var/cvs]$ /bin/ls -ld /var/cvs drwxr-xr-x4 root root 4096 Feb 10 2001 /var/cvs [ankh-morpork:/var/cvs]$ /bin/ls -l /var/cvs total 8 drwxrwxr-x3 root cvsadmin 4096 Feb 13 2001 CVSROOT drwxr-xr-x 10 cobbecobbe4096 Feb 6 21:08 cobbe IIRC, I created the cvsadmin group, but the permissions on /var/cvs seem to indicate that the group permissions just default to whatever's appropriate for the user who created the repository. Which version of CVS are you using? The above results are from 1.10.7-7, the version in potato. > Second question: What permissions do I need to set? I've done > chmod g+w * > everywhere that there is a directory, but I still get these error > messages when I try to checkout a sample program directory, e.g.: While Debian and RedHat may have default groups that they use for CVS repositories, this isn't reallly all that relevant. As long as all of the CVS users have write access to the appropriate directories, everything should work out. Typically, one does this by manipulating the group ownerships and permissions of the files in the repository. I'm assuming that you want all-or-none access: each user can access either the entire repository or none of the repository. (More finely-grained access controls are possible, but they complicate the process somewhat.) I'm also assuming a `local' or `ext' access method, as opposed to `pserver'. I'll use two metavariables to make the explanation easier: $CVS_GROUP is to the name of the group controlling CVS access, and $REPOSITORY is the name of the directory which contains the repository files (e.g., where you untarred your archived repository). - addgroup $CVS_GROUP - Use adduser to ensure that all of the appropriate users are in $CVS_GROUP. - chgrp $CVS_GROUP $REPOSITORY - chmod g+ws $REPOSITORY ## The setgid bit is crucial. - find $REPOSITORY -print | xargs chgrp $CVS_GROUP ## Make everything owned by the CVS group. - find $REPOSITORY -type d -print | xargs chmod g+ws ## Make all directories group-writable and setgid. Make sure that you're running in $CVS_GROUP (you may need to log out and log back in), and you should be good to go. (If you don't understand what all of the above does or why you're doing it, please ask. That understanding will help you deal with other repository problems later on.) > [EMAIL PROTECTED]:~/co$ cvs co hello > cvs checkout: warning: cannot write to history file > /var/lib/cvs/CVSROOT/history: Permission denied > cvs checkout: Updating hello > cvs checkout: failed to create lock directory for `/var/lib/cvs/hello' > (/var/lib/cvs/hello/#cvs.lock): Permission denied > cvs checkout: failed to obtain dir lock in repository > `/var/lib/cvs/hello' > cvs [checkout aborted]: read lock failed - giving up > [EMAIL PROTECTED]:~/co$ Yeah. User pecondon doesn't have write access to the repository directory. The above process should fix this. HTH, Richard
cvs stupid user problem, please help me debug
I saved a cvs repository of personal programs in RedHat some time ago, before I discovered Debian. Now I'm trying install it and access the files in it. I used tar to save the whole repository as cvs.tgz. When I untar it, I discover that the permissions are wrong and the group assignment of the files is different from the Debian convention. So I set about to make them right for Debian, but I can't get it to work. First question: Debian uses "src" as the conventional group name for cvs internal files. RedHat uses "staff". Do I need to change this? Or just add myself to the "staff" group? I've changed them all to 'src' and added myself to group 'src', but I'm curious. Second question: What permissions do I need to set? I've done chmod g+w * everywhere that there is a directory, but I still get these error messages when I try to checkout a sample program directory, e.g.: [EMAIL PROTECTED]:~/co$ cvs co hello cvs checkout: warning: cannot write to history file /var/lib/cvs/CVSROOT/history: Permission denied cvs checkout: Updating hello cvs checkout: failed to create lock directory for `/var/lib/cvs/hello' (/var/lib/cvs/hello/#cvs.lock): Permission denied cvs checkout: failed to obtain dir lock in repository `/var/lib/cvs/hello' cvs [checkout aborted]: read lock failed - giving up [EMAIL PROTECTED]:~/co$ I have a feeling I will be shown to be really ignorant when this is resolved but I'm past caring about egg on my face! Thanks. -- Paul E Condon| Failure is not an option. [EMAIL PROTECTED] | It's bundled with the software.
Re: Stupid user...
On Thu, 11 Feb 1999 [EMAIL PROTECTED] wrote: On Thu, 11 Feb 1999, William Schwartz wrote: >> Well, I did something stupid, and I don't know how I did it or how to make >> it stop... >> I added a package that when debian starts up, it proceeds right into a GUI >> login screen (with a penguin head). Now, the problem is that I don't like >> it, and I want it to go away. I don't remember what package it is or >> remember even what it is called. Now, since updating my packages. my it is > xdm < >I have the same problem with updating to x..._3.3.2.3a-9. >It seems to come from the "xdm"-packege. >Possibly we'll get a new update right soon. Until then you could get around the >problem moving (until the next update) /etc/init.d/xdb to, say, >/etc/init.d/xdm.sav, >then you need to start your X manually e.g. startx or so ... continued ... According to the mail From: Peter Iannarelli <[EMAIL PROTECTED]> it really seems that xdm waits forever on 'xbanner', which was was not installed here. You may install the xbanner packege or comment out those lines ... -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Stupid user...
Thanks to all who replied... getting rid of my "xdm" did it. I was concerned that my keyboard had gone bad, but it was just the gui login / xdm giving it fits. Thanks for the help! will - Original Message - From: <[EMAIL PROTECTED]> To: William Schwartz <[EMAIL PROTECTED]> Cc: [list] Debian Users Sent: Thursday, February 11, 1999 8:49 AM Subject: Re: Stupid user... >On Thu, 11 Feb 1999, William Schwartz wrote: > >> Well, I did something stupid, and I don't know how I did it or how to make >> it stop... > >> I added a package that when debian starts up, it proceeds right into a GUI >> login screen (with a penguin head). Now, the problem is that I don't like >> it, and I want it to go away. I don't remember what package it is or >> remember even what it is called. Now, since updating my packages. my >it is > xdm < > >I have the same problem with updating to x..._3.3.2.3a-9. >It seems to come from the "xdm"-packege. >Possibly we'll get a new update right soon. Until then you could get around the >problem moving (until the next update) /etc/init.d/xdb to, say, /etc/init.d/xdm.sav, >then you need to start your X manually e.g. startx or so ... > > > >-- >Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > >
Re: Stupid user...
Hell William: I think the offending package is xbanner. I'm assuming you have installed xdm. SO /etc/X11/xdm/Xsetup_0 holds the offending line. ie. # XBanner - begin /usr/X11R6/bin/freetemp /usr/X11R6/bin/xbanner -file /etc/X11/XBanner.ad # XBanner - end Just comment it out. Peter William Schwartz wrote: > > Well, I did something stupid, and I don't know how I did it or how to make > it stop... > > I added a package that when debian starts up, it proceeds right into a GUI > login screen (with a penguin head). Now, the problem is that I don't like > it, and I want it to go away. I don't remember what package it is or > remember even what it is called. Now, since updating my packages. my > keyboard will not work with this gui thing, and I cant login to me system. > Luckly I do have telnet access to the box. > > Anyone? > > will > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/nullbegin:vcard n:Iannarelli;Peter tel;fax:1+ 416 929 1056 tel;work:1+ 416 929 1885 x-mozilla-html:FALSE url:http://www.GenXl.com org:GenX Internet Labs adr:;;20 Madison Ave.;Toronto;ON;;CA version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Engineer fn:Peter Iannarelli end:vcard
Re: Stupid user...
On Thu, 11 Feb 1999, William Schwartz wrote: > Well, I did something stupid, and I don't know how I did it or how to make > it stop... > I added a package that when debian starts up, it proceeds right into a GUI > login screen (with a penguin head). Now, the problem is that I don't like > it, and I want it to go away. I don't remember what package it is or > remember even what it is called. Now, since updating my packages. my it is > xdm < I have the same problem with updating to x..._3.3.2.3a-9. It seems to come from the "xdm"-packege. Possibly we'll get a new update right soon. Until then you could get around the problem moving (until the next update) /etc/init.d/xdb to, say, /etc/init.d/xdm.sav, then you need to start your X manually e.g. startx or so ...
Re: Stupid user...
> > Well, I did something stupid, and I don't know how I did it or how to make > it stop... > > I added a package that when debian starts up, it proceeds right into a GUI > login screen (with a penguin head). Now, the problem is that I don't like > it, and I want it to go away. I don't remember what package it is or > remember even what it is called. Now, since updating my packages. my > keyboard will not work with this gui thing, and I cant login to me system. > Luckly I do have telnet access to the box. > > Anyone? Don't fear the penguins :) I don't know the package, but if you login through telnet, you should be able to find out what is running typing `ps ax', or better even, `pstree'. Then see to which package the executable belongs with `dpkg -S ', and take further action. HTH, Eric -- E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189 Eindhoven Univ. of Technology | tel. lab. +31 40 2475032 Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax+31 40 2455054
Stupid user...
Well, I did something stupid, and I don't know how I did it or how to make it stop... I added a package that when debian starts up, it proceeds right into a GUI login screen (with a penguin head). Now, the problem is that I don't like it, and I want it to go away. I don't remember what package it is or remember even what it is called. Now, since updating my packages. my keyboard will not work with this gui thing, and I cant login to me system. Luckly I do have telnet access to the box. Anyone? will
