Re: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root']
don't know if you all know this or not but it helps me when I can't find what I need (which is often) on a particualr site: at google.com's input field: __ | site:cvshome.org error messages |and hit enter --- site: is a command and so it searches for the keywords at the site specified You will be amazed at the jewels of wisdom a org/com keeps hidden from it's users unintentionally... - Original Message - From: Greg A. Woods [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 10, 2001 9:33 PM Subject: Re: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root'] [ On Tuesday, July 10, 2001 at 16:40:04 (+0200), Pascal Bourguignon wrote: ] Subject: Re: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root'] Well, you're not alone having difficulties with the CVS manual. Either a good number of CVS users like me are dumb or indeed there's a problem with the manual. I think part of the problem is with this word read. It's been quite a long time since I sat down and actually read the manual. I tend to use the 's' key in info a lot, and that can result in worse side-tracking and unapplicable references than typing sex into Google. I think that if people (including even me!) actually _read_ the manual then there would be far less complaint. Texinfo manuals are, after all, generally written in such a way as to lend themselves far more to being read than to being used as a reference, and the CVS manual is no different in this respect. I still use (not read, exactly) the old troff manual sometimes simply because it's a better reference despite being effectively deprecated and out-of-date. -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root']
[ On Monday, July 9, 2001 at 20:22:56 (-0700), David Taylor wrote: ] Subject: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root'] When someone who has long chanted RTFM! as the panacea for countless ills can't find what he wants in the manual (and is thus led to proclaim its absence a failing of the manual), though it exists in the manual...we can all agree that there is a problem here. Oh, I hope I've never really claimed the fine manual was the only panacea for all ills! ;-) I recant if I did! Of course my inability to find something in the manual isn't necessarily due to a failing in the manual either. My self analysis was an attempt to discover why *I* had a problem finding a particular reference. Whether my experiences would match those of anyone else is a very different question, the answer to which is left as an excercise for the reader! ;-) -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root']
[EMAIL PROTECTED] (Greg A. Woods) wrote: [ On Monday, July 9, 2001 at 20:22:56 (-0700), David Taylor wrote: ] Subject: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root'] When someone who has long chanted RTFM! as the panacea for countless ills can't find what he wants in the manual (and is thus led to proclaim its absence a failing of the manual), though it exists in the manual...we can all agree that there is a problem here. Oh, I hope I've never really claimed the fine manual was the only panacea for all ills! ;-) I recant if I did! Of course my inability to find something in the manual isn't necessarily due to a failing in the manual either. My self analysis was an attempt to discover why *I* had a problem finding a particular reference. Whether my experiences would match those of anyone else is a very different question, the answer to which is left as an excercise for the reader! ;-) Well, you're not alone having difficulties with the CVS manual. Either a good number of CVS users like me are dumb or indeed there's a problem with the manual. -- __Pascal_Bourguignon__ (o_ Software patents are endangering () ASCII ribbon against html email //\ the computer industry all around /\ and Microsoft attachments. V_/ the world http://lpf.ai.mit.edu/ 1962:DO20I=1.100 2001:my($f)=`fortune`; http://petition.eurolinux.org/ -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS/IT d? s++:++(+++)++ a C+++ UB+++L$S+X$ P- L+++ E++ W++ N++ o-- K- w-- O- M++$ V PS+E++ Y++ PGP++ t+ 5? X+ R !tv b++(+) DI+++ D++ G++ e+++ h+(++) r? y---? UF --END GEEK CODE BLOCK-- ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root']
[ On Tuesday, July 10, 2001 at 16:40:04 (+0200), Pascal Bourguignon wrote: ] Subject: Re: RTFM? [ was Re: cvs [commit aborted]: cannot commit files as 'root'] Well, you're not alone having difficulties with the CVS manual. Either a good number of CVS users like me are dumb or indeed there's a problem with the manual. I think part of the problem is with this word read. It's been quite a long time since I sat down and actually read the manual. I tend to use the 's' key in info a lot, and that can result in worse side-tracking and unapplicable references than typing sex into Google. I think that if people (including even me!) actually _read_ the manual then there would be far less complaint. Texinfo manuals are, after all, generally written in such a way as to lend themselves far more to being read than to being used as a reference, and the CVS manual is no different in this respect. I still use (not read, exactly) the old troff manual sometimes simply because it's a better reference despite being effectively deprecated and out-of-date. -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
[ On Monday, July 9, 2001 at 01:03:36 (-0400), Lenny Foner wrote: ] Subject: cvs [commit aborted]: cannot commit files as 'root' In that time, you've come across as basically a reactionary force, in the original meaning of that term---in other words, just about any change to CVS has launched you on a crusade to preserve the One True Original Implementation, even in the face of lots of people who might rather it behaved otherwise. You're obviously not paying attention to what I'm writing. Please try again. -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
You know.. something I've noticed... On one side there are the people who will never read the manual, but will expect the mailing list, forums, et. al. to answer every little question they have whether it's I can't get my webserver to run cgi scripts or how do I import a new project or I don't understand my algebra homework. On the other side... the manual just plain sucks. It's confusing, poorly organized, badly written, and as you pointed out.. it's sorely lacking a full list of error messages. In short.. it needs to be rewritten very badly. I have a hard time being upset at someone who doesn't RTFM the cvs manual because it's painful to read. Daniel ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Attention CVS Zealots (was Re: cvs [commit aborted]: cannot commit files as 'root')
[EMAIL PROTECTED] wrote: cowed by the thought of having Greg yell at them for days that they're unwilling to start, or if I'm told that no such patch will be accepted to CVS, then it will die here. I generally ignore rants, especially from Mr. Greg Woods. Greg - you're obviously very smart, and very well-informed about CVS, networking and general computing - but STFU already. You have become NOISE. Are you this boorish off-line? I want to see CVS improve and will gladly host / administer any such efforts. In fact, I have planned to do so for quite some time in the context of my plans for freepository. Anyone who desires to improve CVS - behavior, error messages, user interface, bells, whistles or documentation - please reply directly to me off this list. I have the time, desire, knowledge, hardware, and network infrastructure to make this happen. Bullies and weasels Need Not Apply. -- John Minnihan mailto:[EMAIL PROTECTED] http://www.freepository.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
Greg A. Woods writes: It isn't even in the manual, as far as I can see. That's maybe the worst failing of the manual -- there's no (even partial) list of the error messages in one place with links to nodes containing their explanations. Excuse me? http://cvshome.org/docs/manual/cvs_21.html#SEC181 -Larry Jones What this games needs are negotiated settlements. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
Has anyone considered coding a little helper, say, an animated paper clip, that'll help people through the index of the manual? All right! Who threw the tomato? Regards, Mike Klinke - Original Message - From: Larry Jones [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 09, 2001 10:40 AM Subject: Re: cvs [commit aborted]: cannot commit files as 'root' | Greg A. Woods writes: | | It isn't even in the manual, as far as I can see. That's maybe the | worst failing of the manual -- there's no (even partial) list of the | error messages in one place with links to nodes containing their | explanations. | | Excuse me? | | http://cvshome.org/docs/manual/cvs_21.html#SEC181 | | -Larry Jones | | What this games needs are negotiated settlements. -- Calvin | | ___ | Info-cvs mailing list | [EMAIL PROTECTED] | http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
[ On Monday, July 9, 2001 at 11:40:28 (-0400), Larry Jones wrote: ] Subject: Re: cvs [commit aborted]: cannot commit files as 'root' Greg A. Woods writes: It isn't even in the manual, as far as I can see. That's maybe the worst failing of the manual -- there's no (even partial) list of the error messages in one place with links to nodes containing their explanations. Excuse me? http://cvshome.org/docs/manual/cvs_21.html#SEC181 Ah, so there is! Sorry! Maybe what the manual needs more than anything else is a top-level complete table of contents listing every node in the menu (much like the The Detailed Node Listing in the Emacs manual and so many other wonderful texinfo-based manuals). The texinfo index is wonderful, and all, but it's just an index. I've come to expect the detailed listing and given there's no obvious way to restrict a search in 'info' to the current node, or to headings only, it's hard to find a node that you don't know exists. I don't know if there are any existing tools to help build the menu and detailed node listing, or not... -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
[ On Sunday, July 8, 2001 at 11:16:40 (-0400), Matthew Von-Maszewski wrote: ] Subject: cvs [commit aborted]: cannot commit files as 'root' Is this an intended security feature ... or am I just being stupid again? VERY intended! -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
Matthew Von-Maszewski writes: cvs [commit aborted]: cannot commit files as 'root' [...] Is this an intended security feature ... or am I just being stupid again? It's an intended feature, but it has more to do with maintaining accountability than security. Since root is usually a shared account, CVS won't allow you to commit as root unless it can figure out who you really are. Logging in as yourself and then su'ing to root will usually allow CVS to figure out who you are, logging in as root won't. If you're sure you want to be able to commit as root, see CVS_BADROOT in src/options.h. -Larry Jones Mr. Subtlety drives home another point. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: cvs [commit aborted]: cannot commit files as 'root'
su to root worked like a champ. Thanks for the work-around. Matthew -Original Message- From: Larry Jones [mailto:[EMAIL PROTECTED]] Sent: Sunday, July 08, 2001 3:27 PM To: Matthew Von-Maszewski Cc: [EMAIL PROTECTED] Subject: Re: cvs [commit aborted]: cannot commit files as 'root' Matthew Von-Maszewski writes: cvs [commit aborted]: cannot commit files as 'root' [...] Is this an intended security feature ... or am I just being stupid again? It's an intended feature, but it has more to do with maintaining accountability than security. Since root is usually a shared account, CVS won't allow you to commit as root unless it can figure out who you really are. Logging in as yourself and then su'ing to root will usually allow CVS to figure out who you are, logging in as root won't. If you're sure you want to be able to commit as root, see CVS_BADROOT in src/options.h. -Larry Jones Mr. Subtlety drives home another point. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
Matthew Von-Maszewski writes: su to root worked like a champ. Thanks for the work-around. Perhaps I understated things a bit in my original response. There *are* security concerns with committing as root -- be very sure you know what you're doing. Even better, just don't do it. -Larry Jones The surgeon general should issue a warning about playing with girls. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
[ On Sunday, July 8, 2001 at 16:00:55 (-0400), Lenny Foner wrote: ] Subject: cvs [commit aborted]: cannot commit files as 'root' You know, given how often people ask this question, maybe some paragraph of your response here should be put INTO THE ERROR MESSAGE ITSELF. Well actually I would have thought the message was already very very clear all by itself -- if maybe a bit terse for anyone with English as a second language. It does, after all, say exactly what it means. Maybe if it said You, whomever you are, cannot commit files as 'root'! (complete with the explanation mark :-) That's not a real suggestion though -- CVS error messages should remain as stable as possible so as to facilitate ease of maintenance of wrapper and front-end programs. I think what maybe surprises people about this is that usually 'root' can do anything and usually error messages say you must be root to Obviously though a source code control system has different security requirements than a filesystem. Yeah, I know, I know, everyone will say that's why you're supposed to read the manual!, but it's obvious that either (a) people aren't reading it well enough, or (b) it's a little too buried. It isn't even in the manual, as far as I can see. That's maybe the worst failing of the manual -- there's no (even partial) list of the error messages in one place with links to nodes containing their explanations. My basic point here is that, industry-wide, far too many error messages are far too terse. They should include paragraphs of prose, pointers to manual sections, URLs for further clarification---and probably all -three- of them. Why not? Why? What a waste of space, energy, resources, time, effort, etc.! All that's really necessary is that the documentation contain descriptions of the error messages. With 'info' documentation the searching for the meaning is extremely simple. I really rather dislike execessive verbosity in error messages. Specifically for CVS though error messages should be kept as stable as possible and short enough that when fully formatted with an average filename they don't exceed 80 characters in length. After all, we're no longer using 300 baud teletypes where a long error message takes a minute to sit through. Nor does it matter if the executable is 10K larger because the error messages actually tell you what's wrong---not in an era of 1G OS's and 10M applications... Size and speed aren't everything (though they're certainly still very very important -- far more important than you seem to think!). Maintenance is also incredibly important. I think it's far better to have very good documentation and to keep it up-to-date with lists and descriptions of error messages rather than to have to maintain the same text in both the code and the documentation (or come up with some convoluted scheme to try to merge one from the other). -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs [commit aborted]: cannot commit files as 'root'
[ On Sunday, July 8, 2001 at 19:27:07 (-0400), Lenny Foner wrote: ] Subject: cvs [commit aborted]: cannot commit files as 'root' No, it only says that you can't. It doesn't explain WHY, which was precisely the question that was asked. Well of course not! RTFM! Nor, apparently, does it help anyone who ever gets it---they say, Yeah, so, I'm root. What's the big deal? And then (a) they waste their time asking the list, and (b) they waste all -our- time reading their question, and (c) they waste a few peoples' time who answer them. Seems suboptimal to me... You'll never eliminate RTFM answerable questions, not even if you put the whole stinking manual right into the code so every message is as verbose as humanly possible. Maybe if it said You, whomever you are, cannot commit files as 'root'! (complete with the explanation mark :-) That doesn't help the users, whose immediate next question is, why not? The immediate response of any sane person who asks such a question should be to RTFM! That's not a real suggestion though -- CVS error messages should remain as stable as possible so as to facilitate ease of maintenance of wrapper and front-end programs. You're kidding, right? Nope, not at all. Not one iota. That's a very very serious concern. I dare you to write a front-end to CVS (as it is today) and say otherwise! You're actually arguing that error messages must remain fixed for all time because someone might have based a wrapper on them? No, I'm not saying that either -- I'm saying they must not change without due cause. Whatever happened to the concept of exit codes? What about them? They serve an entirely separate purpose. Whatever happened to the concept of the localization of all text emitted by a program for the user's native language? What indeed! Do you have patches to implement this feature in CVS? Whatever happened to any pretense of design, not to mention professionalism? You should learn some more about the history of CVS and its development. I'm sure such knowledge will enlighten you significantly! ;-) If that's -really- the concern, then I submit that a much more stable mechanism would be to number all the error messages uniquely, and emit that number (perhaps surrounded by some sequence of characters not ever used elsewhere in error messages---though be careful of filenames! This is a viable scheme, but it would take quite some doing to make CVS (as we know it today) implement it. UNIX System V took a similar approach, though I don't know exactly how far they got. Sounds like sanity.sh should be amended to do a grep for every error message through the manual and at least make sure that it appears -somewhere-. Hmm I think it would be easier to analyse the code and create REs from the printf format strings At least then you know where the variable bits of the messages are, and even what type of data to expect in those places Such a tool would have much wider application than just CVS, of course! Why? What a waste of space, energy, resources, time, effort, etc.! Because one implementor's effort saves n thousand people's time, that's why. I think you vastly under-estimate the needs of the maintainer. This is no small problem we're talking about here! I would submit that it simply cannot ever succeed without at least partial automation, and of course such a drastic change would require a very significant amount of up-front work, even if one did draw upon existing practice (eg. have a look at the code in Postfix). I know of what I speak -- I've been around this block more than once myself! Why force the user through an extra step? He's already staring at the message. Why not help him to understand what he's looking at? Why force an expert user (not to mention a front-end driver program) through all the extra verbiage? Why not help the user learn to become an expert user? I really rather dislike execessive verbosity in error messages. Is telling the user what he did wrong, and why, excessive? Yes, absolutely. A simple error number is insufficient except for the most expert user (or front-end program). An error message must give just enough information to provide context and memory/search clues, and absolutely no more. We're not talking about some kind of fancy GUI-driven DWIM application here! If you want all that extra crud all the time then please put it only int he fancy GUI DWIM thing, not in the underlying _tool_. You sound like you're saying that all CVS error messages should simply be ?, like a certain well-known text editor from the early 70's, when memory was many cents/bit. Or perhaps they should just be abend 34117; after all, that's what the manual is for, right? There was a significant UI advantage to that scheme, but of course it can only be taken so far! ;-) Inscrutible error messages may be -your- preference, Now just hold on one
Re: cvs [commit aborted]: cannot commit files as 'root'
Don't run cvs as root. donald On Mon, Apr 03, 2000 at 04:42:47PM +0300, Crosby wrote: Hello ! I'm a beginner user of CVS and I don't know to resolve this error.I've setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root. I've import a project but I can't commit the work. The error received is : cvs [commit aborted]: cannot commit files as 'root' What should I do ? Thanks ! Crosby
Re: cvs [commit aborted]: cannot commit files as 'root'
On Monday 3 April 2000, at 16 h 42, the keyboard of Crosby [EMAIL PROTECTED] wrote: I'm a beginner user of CVS and I don't know to resolve this error.I've setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root. This is certainly one of the most awful errors an Unix user can make.
Re: cvs [commit aborted]: cannot commit files as 'root'
Yes , this is the easyest solution but on my work station I'm always logged as root. The CVS server is working on our local server . I use ssh to access the remote repository.It's possible to make a map On Mon, 03 Apr 2000, you wrote: Don't run cvs as root. donald On Mon, Apr 03, 2000 at 04:42:47PM +0300, Crosby wrote: Hello ! I'm a beginner user of CVS and I don't know to resolve this error.I've setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root. I've import a project but I can't commit the work. The error received is : cvs [commit aborted]: cannot commit files as 'root' What should I do ? Thanks ! Crosby
Re: cvs [commit aborted]: cannot commit files as 'root'
Dear friends , I use my Linux from a long time and most of time like a root . If you (mr. Donald) give commands which are dangerous for your system is your problem. I know what I'm doing when press Enter after a command. For my question I don't receive a right answer. I don' t think it's a big mistake to make some changes to a project logged as root. I have thinking to a way to map the local user ( root ) to another user on server . Maybe this is possible but nobody give me a solution. Of course the easyest (to login as other user) was in my mind but I look after other solution. Anyway thanks for your (help) ! Crosby On Mon, 03 Apr 2000, you wrote: Well to put it bluntly, it's at *best* idiotic to run as root for day to day usage of unix. Your asking for a world of hurt when you do a 'rm -rf /' accidently, or any number of other things that root can do that will *KILL* your system. Change the way you are working. There is a very good reason that cvs doesn't let you commit as root, which is the very same reason that you shouldn't run as root unless you have to. Running as root all the time is like holding a gun to your head, spinning the chambers and then pulling the trigger every time you input a command. You are going to burn yourself ( or at least put a very large hole in your head, metaphorically speaking of course ) donald On Mon, Apr 03, 2000 at 05:58:43PM +0300, Crosby wrote: Yes , this is the easyest solution but on my work station I'm always logged as root. The CVS server is working on our local server . I use ssh to access the remote repository.It's possible to make a map On Mon, 03 Apr 2000, you wrote: Don't run cvs as root. donald On Mon, Apr 03, 2000 at 04:42:47PM +0300, Crosby wrote: Hello ! I'm a beginner user of CVS and I don't know to resolve this error.I've setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root. I've import a project but I can't commit the work. The error received is : cvs [commit aborted]: cannot commit files as 'root' What should I do ? Thanks ! Crosby
Re: cvs [commit aborted]: cannot commit files as 'root'
Crosby writes: I use my Linux from a long time and most of time like a root . If you (mr. Donald) give commands which are dangerous for your system is your problem. I know what I'm doing when press Enter after a command. If you insist on being stupid (and it's your right to do so), you can edit src/options.h to remove the #define of CVS_BADROOT. -Larry Jones Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. -- Calvin
Re: cvs [commit aborted]: cannot commit files as 'root'
On Monday, April 3, Crosby wrote: Dear friends , I use my Linux from a long time and most of time like a root . If you (mr. Donald) give commands which are dangerous for your system is your problem. I know what I'm doing when press Enter after a command. For my question I don't receive a right answer. I don' t think it's a big mistake to make some changes to a project logged as root. I have thinking to a way to map the local user ( root ) to another user on server . Maybe this is possible but nobody give me a solution. Of course the easyest (to login as other user) was in my mind but I look after other solution. Anyway thanks for your (help) ! Ok, there is a way. However, I hesitate to show you that way, since you are "root", obviously a power-user, and can't find the method to do so by yourself... Anyhow, using the following method, I've been able to do what you wish: export CVS_RSH=ssh export [EMAIL PROTECTED]:/cvsroot PS: Do you know *WHY* cvs will not let you run things as root? --Toby.
Re: cvs [commit aborted]: cannot commit files as 'root'
On Monday, April 3, Donald Sharp wrote: There is no right answer. cvs was designed to not allow the root user to do cvs commands. This has to do with the philosophy about why you shouldn't run as root unless you have to. It also goes into the level of trust that you are willing to let one 'root' user have on another machine. If you are so set on running as root go into the source and remove the check to see who you are running as, because obviously you know best In any event you will be running a unsupportable version of the cvs source base I may be wrong, but I believe there are other reasons that 'root' is not allowed to use cvs. I believe that they involve locking and such. --Toby.
Re: cvs [commit aborted]: cannot commit files as 'root'
on 4/3/00 12:40 PM, Crosby at [EMAIL PROTECTED] wrote: I use my Linux from a long time and most of time like a root . If you (mr. Donald) give commands which are dangerous for your system is your problem. I know what I'm doing when press Enter after a command. Generally accepted practices, such as not doing normal root as root, are generally accepted for a reason. No matter how smart you are. -- Tracy Snell Orlando Office 21st Century Telecom [EMAIL PROTECTED]
Re: cvs [commit aborted]: cannot commit files as 'root'
On Mon, Apr 03, 2000 at 16:42 +0300, Crosby wrote: I'm a beginner user of CVS and I don't know to resolve this error.I've setup a CVS server (I use SuSE Linux 6.3) and I am always logged as root. The software is trying to tell you something (and the handbook did so, too -- if you would care to have a look there). DON'T work as root if you're not doing _any_ administrative task. Running X or reading mail or doc or doing development all has nothing to do with "priviledges needed". You shoot into your own foot -- don't do that! What should I do ? Take the advise to work as a usual user, just like anyone else does. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.
