Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2006 06:43 PM
тАО01-27-2006 06:43 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2006 06:54 PM
тАО01-27-2006 06:54 PM
Re: cvs
No, CVS is the oldest version control system on HP-UX. CVS is open source tool.
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2006 07:15 PM
тАО01-27-2006 07:15 PM
SolutionYes CVS is a very old versioning system on HPUx. It is a open source tool.
http://www.nongnu.org/cvs/
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2006 09:30 PM
тАО01-27-2006 09:30 PM
Re: cvs
CVS is built on top of RCS and GNU's diff. I think, RCS is the oldest versioning system available on HP-UX. You can download CVS from,
http://hpux.connect.org.uk/hppd/hpux/Development/Tools/cvs-1.11.21/
Make sure you install zlib too as a runtime dependency.
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2006 03:58 PM
тАО01-29-2006 03:58 PM
Re: cvs
You can also try with "Subverion" which is a compelling replacement for CVS in the open source community. Some features of Subversion are,
Most current CVS features
Commits are truly atomic
Standalone server option
Apache network server option, with WebDAV/DeltaV protocol
etc.. etc..
More at, http://subversion.tigris.org/
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2006 09:49 PM
тАО01-29-2006 09:49 PM
Re: cvs
Some good link about Subversion, http://subversion.tigris.org/faq.html
http://svnbook.red-bean.com/
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2006 12:59 AM
тАО01-30-2006 12:59 AM
Re: cvs
RCS is a set of utilities which will allow you to backup and retrieve
versions of a file, as well as share them with others without clobbering
each others' work. This accomplished by "surrendering" your files to
the RCS system, and then asking RCS to get them for you whenever you want them. RCS is a little like using the public library: to "borrow"
a file, you "check it out"; when you are done with it you "check it in".
Using RCS is very easy -- you only need to learn 2 commands, and only
one option!
SUMMARY of RCS commands:
co check-out a read-only copy of the file. This command always
succeeds if the file exists in RCS, and gives you the latest
version that has been checked-in.
co -l check-out a read/write copy of the file and lock it so noone
else can make changes to it. This command fails if someone else
has the file locked.
ci check-in a read/write version of the file which has already been
locked by you. RCS removes your read/write version of the file,
to emphasize that it now has the file. This command is also
used to give a new file to RCS.
rlog list information about the file
rcs -u unlock a file without checking it in.
Practical Example
Ok, lets say you've got a handful of sysadmins administrating one HP-UX machine. RCS is a decent way of keeping people from stepping on toes. Lets get things rolling with something like this:
# cd /usr/local/bin# mkdir RCS
Lets continue by adding a $Header$ and a $Log$ tag to the file. Crack open your TextEditorOfChoice and add the following to the top of a file
# $Header$
# $Log$
These are RCS tags, and will by modified by RCS everytime you check a file in. Go ahead and initially register the file in the RCS repository.
# ci -u testfile
RCS/testfile,vinitial revision: 1.1
enter description, terminated with ^D or '.':
NOTE: This is NOT the log message!
>> This is a test file
>> .
done
Now we've created a RCS repository, and initialized a file into it. We use the "-u" flag which leaves a copy in the working directory. Now, through some unknown form of magic, the $Header$ and $Log$ tags have been changed to something along these lines:
# $Header: testfile,v 1.1 2004/05/27 08:50:26 root Exp $
# $Log: testfile,v $
# Revision 1.1 2004/05/27 04:12:26 root ()
# Initial revision
#
Amazing isn't it? Now the only major catch is, you HAVE to check-out (co) and LOCK the file before you make any changes to it, like so:
# co -l testfile
RCS/testfile,v --> testfile
revision 1.1 (locked)
done
This is where you whip out TextEditorOfChoice and go to town on your modifications. Once done, be sure to check the file back in, and in this case you WILL want to use the "-u" flag again. So after edits are made and tested, and your completely satisfied with them, check-in the files.
# ci -u testfile
RCS/testfile,v <-- testfile
new revision: 1.2; previous revision: 1.1
enter log message(terminate with ^D or single '.')
>> Added stuff
>> .
done
Once again, the RCS tags have magically been changed, here is the full output of the example file before and after!
2.1 Revision 1.1
# $Header: testfile,v 1.1 2004/05/27 08:50:26 root Exp $
# $Log: testfile,v $
# Revision 1.1 2004/05/27 08:50:26 root ()
# Initial revision
#
2.2 Revision 1.2
# $Header: testfile,v 1.1 2004/05/27 08:50:26 root Exp $
# $Log: testfile,v $
# Revision 1.2 2004/05/27 08:55:26 root ()
# Added stuff #
# Revision 1.1 2004/05/27 08:50:26 root ()
# Initial revision
#
Rgds...Geoff