MREN(1) General Commands Manual MREN(1)NAME
mren - rename an existing MSDOS file
mren [ -v ] sourcefile targetfile
Mren renames an existing file on an MSDOS filesystem.
Mren will allow the following command line option:
v Verbose mode. Display the new filename if the name supplied is invalid.
Reasonable care is taken to create a valid MSDOS filename. If an invalid MSDOS target name is specified, mren will change the name (and
prompt the user to accept or reject the new name if the verbose mode is set).
The path component of the target filename (if supplied) is ignored. In other words, you may not use mren to move a file from one subdirec-
tory to another.
Mren may be used to rename directories.
MSDOS subdirectory names are supported with either the '/' or '' separator. The use of the '' separator or wildcards will require the
names to be enclosed in quotes to protect them from the shell.
The mcd command may be used to establish the device and the current working directory (relative to MSDOS), otherwise the default is A:/.
SEE ALSO mcd(1)BUGS
MSDOS can't use REN to rename directories.
Check Out this Related Man Page
mren(1) General Commands Manual mren(1)Name
mren - rename an existing MSDOS file
Note of warning
This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the
end of this man page for details.
The mren command is used to rename or move an existing MS-DOS file or subdirectory. Its syntax is:
mren [-voOsSrRA] sourcefile targetfile
Mren renames an existing file on an MS-DOS file system.
In verbose mode, Mren displays the new filename if the name supplied is invalid.
If the first syntax is used (only one source file), and if the target name doesn't contain any slashes or colons, the file (or subdirec-
tory) is renamed in the same directory, instead of being moved to the current mcd directory as would be the case with mmove. Unlike the MS-
DOS version of REN, mren can be used to rename directories.
Mtools' texinfo doc
Viewing the texi doc
This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate repre-
sentation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you
to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips mtools.dvi
* To generate a html copy, run:
./configure; make html
A premade html can be found at `http://www.gnu.org/software/mtools/manual/mtools.html'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
mtools-4.0.13 28Feb10 mren(1)
I am trying to connect to my Solaris 8 system with X-win. However, when i try to connect, a black screen comes up, then closes up immediatley.
I have checked /var/dt/Xerrors, and I am getting the folllowing:
Warning: Missing charsets in String to FontSet conversion
Warning:... (2 Replies)
OS X 10.3.9
I downloaded RealPlayer into my
folder, clicked install and everything works just fine.
My question has to do with just my trying to understand where OS X keeps the files.
So, I opened terminal and said:
find / -name RealPlayer 2>/dev/null
To my utter... (0 Replies)
I had posted few days back and got replies on how to extract patterns from a file.
I had another question. I want to count the number of lines a particular pattern. I thought of somethings like using NF variable, etc, but they didnt work.
Here is sample input.
... (9 Replies)
I have a server AIX 5.3
Few people have the root password and somebody used the root login to erase a file (command rm in the .sh_history of root). :mad:
I would like to know if a file exist with what ip address has been connected.
I want to find the guilty!!! :D
Thanks guys (2 Replies)