07-25-2009
The . and .. are special directory names. If you create a single The single dot means the directory you are in. The double dots means up one level in the directory tree. Also a heads up, if this is a homework question there is a special forum for that. There is a rule on this site stating homework questions are not allowed except in the homework questions forum. The moderators here are very good about enforcing the rules.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hey. i am a bit new to unix and i am trying to figure out how to list the names of the 'dot' files that are in my account.
what command does this?
thank you very much for your help. (4 Replies)
Discussion started by: Jakeman1086
4 Replies
2. UNIX for Dummies Questions & Answers
Hi
I've got a trivial question on using ed (yes, I know, other editors are better!)
How do I insert a line that is just a single dot? (That is, how do I insert a line that starts with a dot and then new line)
Thanks
Peter (4 Replies)
Discussion started by: peterl
4 Replies
3. Programming
HI
I have a messaging s/w daemon(TIBCO rvrd) provided by vendor which will accept connections from various clients and routes messages to the destinations. In order to route it internally uses two ports(one tcp adn one udp).
I want to know on which port(tcp/udp) it is transmitting... (3 Replies)
Discussion started by: axes
3 Replies
4. Programming
I'm writing a monitoring application. I'd like to periodically get the information provided by the 'top' command line utility from within my code and write the output of 'top' to a file. Wondering if anyone has already done something like this.
Doing
system("top > someFile");
does not create... (6 Replies)
Discussion started by: antoniomorandi
6 Replies
5. Shell Programming and Scripting
Hi every one,
i have to dot pc files. One have main function but one dont have.I have to call dot pc file using system () cmd.File is being call have main function.Please let me know how i can call .pc file with two arguments from other dot pc file.I want some thing like
sprintf(buf,... (1 Reply)
Discussion started by: goraya430
1 Replies
6. Shell Programming and Scripting
To read/write to a DB from Java or Perl, you usually have to install/reference several drivers and write a whole bunch of boilerplate DB access code.
I'm curious if someone has written a command line utility for Unix/Linux for simple database access for the major providers, something like:
... (3 Replies)
Discussion started by: furashgf
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
Using command-line utility "ftp or sftp", I want to transfer files across Windows and UNIX.
Can you please tell me from where I need to connect to ftp and how do I specify the hostname, credentials and how do I get and put files between DOS and UNIX?
Please provide me as much... (10 Replies)
Discussion started by: Dev_Dev
10 Replies
8. Shell Programming and Scripting
Hi,
I'm running a rdt (run dot tcl) command, and come accross this line:
alias abc 'set ARGS =(\!*); source home123/abc/$ARGS/setup'
What does the command exactly do?
Please help. (6 Replies)
Discussion started by: mar85
6 Replies
9. Shell Programming and Scripting
Hi Everyone!
I am facing an issue in running a command line utility from the CRON.
This utility displays IPC statistics on UNIX message queues: The "queue name" and the "count" of messages in the queue.
When running this utility from prompt, it will provide an output on the screen, like the... (4 Replies)
Discussion started by: vai_sh
4 Replies
NcdT(1) General Commands Manual NcdT(1)
NAME
ncdt - directory tree printer with extended capabilities
SYNOPSIS
ncdt [-db?] [--dirs] [--bitrate] [--prefix text ] [--help] [ directory [ name ]]
DESCRIPTION
ncdt is a small utility for printing directory trees. It has some additional features not found in tree(1). Additional capabilities are:
- size field for directories displays the summary size of directory subtree instead of the size of the special file (which is somewhat
more useful)
- sizes are displayed in a more readable format (that's a minor improvement, but it helps a little)
- MP3 files are detected; additional info is displayed for them (which is probably the nicest thing about NcdT) The info is displayed
in a compact form, like <2:53 v168JR+> where 2:53 is play time, v (if present) means the file is encoded using VBR, 168 is bitrate
(average bitrate for VBR files), J describes channel encoding (Mono, Stereo, Joint-Stereo, Dual channel), R (if present) means the
file has a RIFF header at the beginning, + (if present) means the file has ID3v2 tag attached - (if present) means there's no ID3
tag at all (none of these means there's only ID3v1 tag present).
NcdT is particularily nice for indexing CDs.
OPTIONS
-d --dirs
Print only directories, omit files. This mode is a rough equivalent of du(1).
-b --bitrate
Print bitrate info for directories. Bitrates are displayed both for ordinary files and directories. If all MP3 files in a given
directory subtree have the same bitrate only one number is printed, if they have various bitrates the range is printed.
--prefix text
Prefix listing with given text. This option is not intended for general use. It might be used by programs using NcdT to index CDsor
doing similar operations to record additional information.
-? --help
Display usage summary.
USAGE
When called without any parameters ncdt displays directory tree for current directory (.).
When called with one parameter ncdt displays directory tree for specified directory.
When called with two parameters ncdt displays directory tree for the directory specified as its first parameter. Second parameter is used
as directory label for the top level directory (instead of directory name from parameter 1).
EXAMPLES
ncdt prints directory tree for the current directory. It will be labeled .
ncdt /usr
prints directory tree of /usr. It will be labeled /usr
ncdt /cdrom 'CD #21'
prints directory tree of /cdrom. It will be labeled CD #21
ncdt -db /cdrom
lists directory sizes, play times and bitrate ranges
SEE ALSO
tree(1), du(1)
BUGS
NcdT uses quite a lot of memory. It's also not very fast, but on a decent CPU it should not be noticeable.
There are no real bugs I'm aware of. I don't think there are any now.
AUTHOR
Pawel Wiecek <coven@vmh.net>
NcdT(1)