11-15-2018
Thanks you for that info! That makes it much easier than having to specify the path each time
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello ,
I just installed openssh in my system . I actually tried to man sshd but it says no entry , though there is a man directory in the installation which have the man pages for sshd .
Can anyone tell me how should i install these man pages .
DP (2 Replies)
Discussion started by: DPAI
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I've written now a man pages, but I don't knwo how to get 'man' to view them. Where have I to put this files, which directories are allowed??
THX Bensky (3 Replies)
Discussion started by: bensky
3 Replies
3. UNIX for Dummies Questions & Answers
Hello,,,
can I use any command in order to be able to see man pages,,, page per page instead for running too fast???:confused: (6 Replies)
Discussion started by: spyros
6 Replies
4. UNIX for Dummies Questions & Answers
Hi folks,
I want to know all the commands for which man pages are available. How do i get it?
Cheers,
Nisha (4 Replies)
Discussion started by: Nisha
4 Replies
5. UNIX for Dummies Questions & Answers
When reading man pages, I notice that sometimes commands are follwed by a number enclosed in parenthesis. such as:
mkdir calls the mkdir(2) system call.
What exactly does this mean? (4 Replies)
Discussion started by: dangral
4 Replies
6. Solaris
Hi,
I am using solaris. I have to load the some man pages on different node from solaris. I have no basic idea regarding this. can anyone plz give me some basic ideas so that i can proceed.
Thanks in advance. (3 Replies)
Discussion started by: ravi rajeev
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I want to install man pages package from solaris 10.
Solaris 10 has already been installed on my servor but I have to add the man pages packages. I search for a long time on internet this package but I didn't find a compatible one... So I downloaded Solaris 10 from Sun site to get this... (1 Reply)
Discussion started by: MasterapocA
1 Replies
8. Fedora
Hello sir,
I am using FEDORA 9.
I wanted to know why do we have ".1" extension in the archives of man pages. I know we are giving format.
I want to know the importance or purpose of this format.
Can you please tell me :confused: (2 Replies)
Discussion started by: nsharath
2 Replies
9. Solaris
Hi everyone,
I have a small query, in solaris the man pages get displayed on half of the terminal , can i get a full terminal or full screen display ?:) (2 Replies)
Discussion started by: M.Choudhury
2 Replies
10. HP-UX
Can anyone supply me with the man pages for:
omnidatalist
omnibarlist
omnisap.exe
I prefer the source man pages in nroff format.
A clue about the software bundles which supply these man pages is fine as well.
OS: HP-UX
TIA (11 Replies)
Discussion started by: sb008
11 Replies
LEARN ABOUT OSX
svk::command::info
SVK::Command::Info(3) User Contributed Perl Documentation SVK::Command::Info(3)
NAME
SVK::Command::Info - Display information about a file or directory
SYNOPSIS
info [PATH | DEPOTPATH]...
OPTIONS
-R [--recursive] : descend recursively
DESCRIPTION
For example, here's the way to display the info of a checkout path:
% svk info ~/dev/svk
Checkout Path: /Users/gugod/dev/svk
Depot Path: //svk/local
Revision: 447
Last Changed Rev.: 447
Last Changed Date: 2006-11-28
Copied From: /svk/trunk, Rev. 434
Merged From: /svk/trunk, Rev. 445
You can see the result has some basic information: the actual depot path, and current revision. Next are advanced information about copy
and merge source for this depot path.
The result of "svk info //svk/local" is almost the same as above, except for the "Checkout Path:" line is not there, because you are not
referring to a checkout path.
Note that the revision numbers on "Copied From:" and "Merged From:" lines are for the source path (//svk/trunk), not the target path
(//svk/local). The example above state that, //svk/local is copied from the revision 434 of //svk/trunk, and //svk/local was merged from
the revision 445 of //svk/trunk. Hence if you do a "svk log -r 434 //svk/local", svk would tell you that //svk/local does not exist at
revision 434.
So far there is no easy way to tell the actual revision number of //svk/local right after a copy or merge.
If the target is a depot path, or the corresponding depot path of the target checkout path is actually a mirroring path, the output of this
command will look like this:
% svk info //svk/trunk
Depot Path: //svk/trunk
Revision: 447
Last Changed Rev.: 445
Mirrored From: svn://svn.clkao.org/svk, Rev. 1744
So you can see this depot path is mirrored from a remote repository, and so far mirrored up to revision 1744.
perl v5.10.0 2008-08-04 SVK::Command::Info(3)