WOWWWWW! did:
mv .xinitrc .xinitrc.BAK cvs update .xinitrc # thit worked Buy I always did cvs co ... Why did this work? Do I need to do 'update' or 'checkout' to pull the file back out? Anywhooooo, thanks. On Thu, Jun 11, 2026 at 9:34 AM Stephen Borrill <[email protected]> wrote: > > On Thu, 11 Jun 2026, Todd Gruhn wrote: > > I think I did it correct ... "cva log .xinitrc" was huge > > > > > > cd /usr/tmp/DOT-FILES > > > > echo $CVSROOT > > /usr/cvsroot > > > > cat CVS/Repository > > DOT-FILES > > So your repo (a.k.a. module) is DOT-FILES, yet you are trying to checkout > a module called .xinitrc (hence the error cvs checkout: cannot find > module '.xinitrc'). > > As mentioned when you asked previously, to update a file, you need to use > cvs update. To checkout a repo, you use cvs checkout. The clue's in the > name... > > You are trying to update a single file called .xinitrc within the repo you > have previously checked out. It is therefore entirely wrong for you to use > cvs checkout. Use cvs update (or cvs up). > > > cat CVS/Root > > /usr/cvsroot > > > > cvs log .xinitrc > > > > RCS file: /usr/cvsroot/DOT-FILES/.xinitrc,v > [snip] > > >>>> What does this mean? Where and what is .xinitrc? What does it have to do > >>>> with CVS? How did you update its revision number? > >>>> > >>>>> cvs co .xinitrc > >>>>> cvs checkout: cannot find module '.xinitrc' > >>>> > >>>> The cvs program is a client that speaks to a CVS server. The checkout > >>>> command (here abbreviated to co) retrieves a whole module stored on that > >>>> server (e.g. src on anoncvs.netbsd.org) which may contains thousands of > >>>> subdirectories and files. It is NOT used to deal with individual files. > >>>> > >>>> What do the following say in the directory that you are trying to do > >>>> this? > >>>> > >>>> echo $CVSROOT > >>>> cat CVS/Repository > >>>> cat CVS/Root > >>>> cvs log .xinitrc > >>>> > >>>>> Why does cvs hate .xinitrc? How do I fix this? > >>>> > >>>> cvs co doesn't know anything about .xinitrc as it is not a module on the > >>>> server you are trying to connect to. > >>>> > >>>> This is no different to: > >>>> % ls .nonexistent > >>>> ls: .nonexistent: No such file or directory > >>>> > >>>> That doesn't mean ls hates .nonexistent - it just doesn't exist. > >>>> > >>>> -- > >>>> Stephen > > > >
