10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I would like to use basename with wc .. I know I can use awk, but want to use basename.
Change this
wc -l txt*
106 /home/popeye/txt1
154 /home/popeye/txt2
159 /home/popeye/txt3
420 total
to this
wc -l txt*
106 txt1
154 txt2
159 txt3
420 total (4 Replies)
Discussion started by: popeye
4 Replies
2. Shell Programming and Scripting
what is the meaning of "script_name=$(basename $0)", can someone please explain? (1 Reply)
Discussion started by: abhi200389
1 Replies
3. UNIX for Dummies Questions & Answers
im trying to extract the basename of a process running on a host
processx is running at host1 as /applications/myapps/bin/processx
i wanted to check if its running, then extract the basename only using:
$ ssh host1 "ps aux | grep -v 'grep' | grep 'processx'" | awk '{ print basename $11}'
... (10 Replies)
Discussion started by: kaboink
10 Replies
4. Shell Programming and Scripting
I have a file
fileinput.txt:
File home/me/fileA.doc is size 232
File home/you/you/fileB.doc is size 343
File /directory/fileC.doc is size 433
File /directory/filed.doc cannot find file size
I want to use the basename command (or any other command) to output:
File fileA.doc is... (3 Replies)
Discussion started by: linuxkid
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
can anyone let me know how to interpret the below third line in the following code.
Gone through the man pages of "basename", but no go.
for f in *.foo;
do
base=`basename $f .foo`
mv $f $base.bar
done
Thanks. (2 Replies)
Discussion started by: venkatesht
2 Replies
6. Shell Programming and Scripting
Hi all,
/home/test/test 123.txt
i want exact file name like "test 123.txt"
basename shows wrong output
how can i cut text from 1st charaster to last "/".....? (5 Replies)
Discussion started by: jagnikam
5 Replies
7. Shell Programming and Scripting
Hello All,
I am trying to remove all tabspaces and all blankspaces from my file using sed & awk, but not getting proper code. Please help me out.
My file is like this (<b> means one blank space, <t> means one tab space)-
$ cat file
NARESH<b><b><b>KUMAR<t><t>PRADHAN... (3 Replies)
Discussion started by: NARESH1302
3 Replies
8. Shell Programming and Scripting
hi,
can anyone help me by saying what is basename..
i have seen this in many programs where the basename is used....
thanks,
Krips (4 Replies)
Discussion started by: kripssmart
4 Replies
9. Shell Programming and Scripting
Hi guys if i do
a=`basename -e -s /home/j/john/*`
du -k -h $a | sort -nr | head -10
why when i run the script does it work but also say usage basename string
any ideas thanks (9 Replies)
Discussion started by: musicmancanora4
9 Replies
10. Shell Programming and Scripting
Hi,
Can someone let me know how to find the reverse of the basename i.e
i have /apps/tiv/pmon/xxxx.dat and I want /apps/tiv/pmon/
Thanks (7 Replies)
Discussion started by: braindrain
7 Replies
File::Basename(3pm) Perl Programmers Reference Guide File::Basename(3pm)
NAME
File::Basename - Parse file paths into directory, filename and suffix.
SYNOPSIS
use File::Basename;
($name,$path,$suffix) = fileparse($fullname,@suffixlist);
$name = fileparse($fullname,@suffixlist);
$basename = basename($fullname,@suffixlist);
$dirname = dirname($fullname);
DESCRIPTION
These routines allow you to parse file paths into their directory, filename and suffix.
NOTE: "dirname()" and "basename()" emulate the behaviours, and quirks, of the shell and C functions of the same name. See each function's
documentation for details. If your concern is just parsing paths it is safer to use File::Spec's "splitpath()" and "splitdir()" methods.
It is guaranteed that
# Where $path_separator is / for Unix, for Windows, etc...
dirname($path) . $path_separator . basename($path);
is equivalent to the original path for all systems but VMS.
"fileparse"
my($filename, $directories, $suffix) = fileparse($path);
my($filename, $directories, $suffix) = fileparse($path, @suffixes);
my $filename = fileparse($path, @suffixes);
The "fileparse()" routine divides a file path into its $directories, $filename and (optionally) the filename $suffix.
$directories contains everything up to and including the last directory separator in the $path including the volume (if applicable).
The remainder of the $path is the $filename.
# On Unix returns ("baz", "/foo/bar/", "")
fileparse("/foo/bar/baz");
# On Windows returns ("baz", 'C:fooar', "")
fileparse('C:fooaraz');
# On Unix returns ("", "/foo/bar/baz/", "")
fileparse("/foo/bar/baz/");
If @suffixes are given each element is a pattern (either a string or a "qr//") matched against the end of the $filename. The matching
portion is removed and becomes the $suffix.
# On Unix returns ("baz", "/foo/bar/", ".txt")
fileparse("/foo/bar/baz.txt", qr/.[^.]*/);
If type is non-Unix (see "fileparse_set_fstype") then the pattern matching for suffix removal is performed case-insensitively, since
those systems are not case-sensitive when opening existing files.
You are guaranteed that "$directories . $filename . $suffix" will denote the same location as the original $path.
"basename"
my $filename = basename($path);
my $filename = basename($path, @suffixes);
This function is provided for compatibility with the Unix shell command basename(1). It does NOT always return the file name portion
of a path as you might expect. To be safe, if you want the file name portion of a path use "fileparse()".
"basename()" returns the last level of a filepath even if the last level is clearly directory. In effect, it is acting like "pop()"
for paths. This differs from "fileparse()"'s behaviour.
# Both return "bar"
basename("/foo/bar");
basename("/foo/bar/");
@suffixes work as in "fileparse()" except all regex metacharacters are quoted.
# These two function calls are equivalent.
my $filename = basename("/foo/bar/baz.txt", ".txt");
my $filename = fileparse("/foo/bar/baz.txt", qr/Q.txtE/);
Also note that in order to be compatible with the shell command, "basename()" does not strip off a suffix if it is identical to the
remaining characters in the filename.
"dirname"
This function is provided for compatibility with the Unix shell command dirname(1) and has inherited some of its quirks. In spite of
its name it does NOT always return the directory name as you might expect. To be safe, if you want the directory name of a path use
"fileparse()".
Only on VMS (where there is no ambiguity between the file and directory portions of a path) and AmigaOS (possibly due to an
implementation quirk in this module) does "dirname()" work like "fileparse($path)", returning just the $directories.
# On VMS and AmigaOS
my $directories = dirname($path);
When using Unix or MSDOS syntax this emulates the dirname(1) shell function which is subtly different from how "fileparse()" works. It
returns all but the last level of a file path even if the last level is clearly a directory. In effect, it is not returning the
directory portion but simply the path one level up acting like "chop()" for file paths.
Also unlike "fileparse()", "dirname()" does not include a trailing slash on its returned path.
# returns /foo/bar. fileparse() would return /foo/bar/
dirname("/foo/bar/baz");
# also returns /foo/bar despite the fact that baz is clearly a
# directory. fileparse() would return /foo/bar/baz/
dirname("/foo/bar/baz/");
# returns '.'. fileparse() would return 'foo/'
dirname("foo/");
Under VMS, if there is no directory information in the $path, then the current default device and directory is used.
"fileparse_set_fstype"
my $type = fileparse_set_fstype();
my $previous_type = fileparse_set_fstype($type);
Normally File::Basename will assume a file path type native to your current operating system (ie. /foo/bar style on Unix, fooar on
Windows, etc...). With this function you can override that assumption.
Valid $types are "MacOS", "VMS", "AmigaOS", "OS2", "RISCOS", "MSWin32", "DOS" (also "MSDOS" for backwards bug compatibility), "Epoc"
and "Unix" (all case-insensitive). If an unrecognized $type is given "Unix" will be assumed.
If you've selected VMS syntax, and the file specification you pass to one of these routines contains a "/", they assume you are using
Unix emulation and apply the Unix syntax rules instead, for that function call only.
SEE ALSO
dirname(1), basename(1), File::Spec
perl v5.16.3 2013-03-04 File::Basename(3pm)