Category Archives: Linux Man Pages - Page 2

MV

MV(1) User Commands MV(1)

NAME
mv – move (rename) files

SYNOPSIS
mv [OPTION]… [-T] SOURCE DEST
mv [OPTION]… SOURCE… DIRECTORY
mv [OPTION]… -t DIRECTORY SOURCE…

DESCRIPTION
Rename SOURCE to DEST, or move SOURCE(s) to DIRECTORY.

Mandatory arguments to long options are mandatory for short options
too.

–backup[=CONTROL]
make a backup of each existing destination file

-b like –backup but does not accept an argument

-f, –force
do not prompt before overwriting

-i, –interactive
prompt before overwrite

–strip-trailing-slashes
remove any trailing slashes from each SOURCE argument

-S, –suffix=SUFFIX
override the usual backup suffix

-t, –target-directory=DIRECTORY
move all SOURCE arguments into DIRECTORY

-T, –no-target-directory
treat DEST as a normal file

-u, –update
move only when the SOURCE file is newer than the destination
file or when the destination file is missing

-v, –verbose
explain what is being done

–help display this help and exit

–version
output version information and exit

The backup suffix is `~’, unless set with –suffix or SIM-
PLE_BACKUP_SUFFIX. The version control method may be selected via the
–backup option or through the VERSION_CONTROL environment variable.
Here are the values:

none, off
never make backups (even if –backup is given)

numbered, t
make numbered backups

existing, nil
numbered if numbered backups exist, simple otherwise

simple, never
always make simple backups

AUTHOR
Written by Mike Parker, David MacKenzie, and Jim Meyering.

REPORTING BUGS
Report bugs to <bug-coreutils@gnu.org>.

COPYRIGHT
Copyright © 2008 Free Software Foundation, Inc. License GPLv3+: GNU
GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

SEE ALSO
rename(2)

The full documentation for mv is maintained as a Texinfo manual. If
the info and mv programs are properly installed at your site, the com-
mand

info coreutils ‘mv invocation’

should give you access to the complete manual.

GNU coreutils 6.12 December 2008 MV(1)

Technorati Tags: ,

MODPROBE

MODPROBE(8) MODPROBE(8)

NAME
modprobe – program to add and remove modules from the Linux Kernel

SYNOPSIS
modprobe [ -v ] [ -V ] [ -C config-file ] [ -n ] [ -i ] [ -q ] [ -o
modulename ] [ modulename ] [ module parameters … ]

modprobe [ -r ] [ -v ] [ -n ] [ -i ] [ modulename … ]

modprobe [ -l ] [ -t dirname ] [ wildcard ]

modprobe [ -c ]

modprobe [ –dump-modversions ]

DESCRIPTION
modprobe intelligently adds or removes a module from the Linux kernel:
note that for convenience, there is no difference between _ and – in
module names. modprobe looks in the module directory /lib/mod-
ules/`uname -r` for all the modules and other files, except for the
optional /etc/modprobe.conf configuration file and /etc/modprobe.d
directory (see modprobe.conf(5)). modprobe will also use module options
specified on the kernel command line in the form of <module>.option>.

Note that this version of modprobe does not do anything to the module
itself: the work of resolving symbols and understanding parameters is
done inside the kernel. So module failure is sometimes accompanied by
a kernel message: see dmesg(8).

modprobe expects an up-to-date modules.dep file, as generated by depmod
(see depmod(8)). This file lists what other modules each module needs
(if any), and modprobe uses this to add or remove these dependencies
automatically. See modules.dep(5)).

If any arguments are given after the modulename, they are passed to the
kernel (in addition to any options listed in the configuration file).

OPTIONS
-v –verbose
Print messages about what the program is doing. Usually mod-
probe only prints messages if something goes wrong.

This option is passed through install or remove commands to
other modprobe commands in the MODPROBE_OPTIONS environment
variable.

-C –config
This option overrides the default configuration file (/etc/mod-
probe.conf or /etc/modprobe.d/ if that isn’t found).

This option is passed through install or remove commands to
other modprobe commands in the MODPROBE_OPTIONS environment
variable.

-c –showconfig
Dump out the configuration file and exit.

-n –dry-run
This option does everything but actually insert or delete the
modules (or run the install or remove commands). Combined with
-v, it is useful for debugging problems.

-i –ignore-install –ignore-remove
This option causes modprobe to ignore install and remove com-
mands in the configuration file (if any), for the module on the
command line (any dependent modules are still subject to com-
mands set for them in the configuration file). See mod-
probe.conf(5).

-q –quiet
Normally modprobe will report an error if you try to remove or
insert a module it can’t find (and isn’t an alias or
install/remove command). With this flag, modprobe will simply
ignore any bogus names (the kernel uses this to opportunisti-
cally probe for modules which might exist).

-r –remove
This option causes modprobe to remove, rather than insert a mod-
ule. If the modules it depends on are also unused, modprobe
will try to remove them, too. Unlike insertion, more than one
module can be specified on the command line (it does not make
sense to specify module parameters when removing modules).

There is usually no reason to remove modules, but some buggy
modules require it. Your kernel may not support removal of mod-
ules.

-w –wait
This option is applicable only with the -r or –remove option.
It causes modprobe to block in the kernel (within the kernel
module handling code itself) waiting for the specified modules’
reference count to reach zero. Default operation is for modprobe
to operate like rmmod, which exits with EWOULDBLOCK if the mod-
ules reference count is non-zero.

-V –version
Show version of program, and exit. See below for caveats when
run on older kernels.

-f –force
Try to strip any versioning information from the module, which
might otherwise stop it from loading: this is the same as using
both –force-vermagic and –force-modversion. Naturally, these
checks are there for your protection, so using this option is
dangerous.

This applies to any modules inserted: both the module (or alias)
on the command line, and any modules it depends on.

–force-vermagic
Every module contains a small string containing important infor-
mation, such as the kernel and compiler versions. If a module
fails to load and the kernel complains that the “version magic”
doesn’t match, you can use this option to remove it. Naturally,
this check is there for your protection, so this using option is
dangerous.

This applies to any modules inserted: both the module (or alias)
on the command line, and any modules it depends on.

–force-modversion
When modules are compiled with CONFIG_MODVERSIONS set, a section
is created detailing the versions of every interface used by (or
supplied by) the module. If a module fails to load and the ker-
nel complains that the module disagrees about a version of some
interface, you can use “–force-modversion” to remove the ver-
sion information altogether. Naturally, this check is there for
your protection, so using this option is dangerous.

This applies any modules inserted: both the module (or alias) on
the command line, and any modules it depends on.

-l –list
List all modules matching the given wildcard (or “*” if no wild-
card is given). This option is provided for backwards compati-
bility: see find(1) and basename(1) for a more flexible alterna-
tive.

-a –all
Insert all module names on the command line.

-t –type
Restrict -l to modules in directories matching the dirname
given. This option is provided for backwards compatibility: see
find(1) and basename(1) or a more flexible alternative.

-s –syslog
This option causes any error messages to go through the syslog
mechanism (as LOG_DAEMON with level LOG_NOTICE) rather than to
standard error. This is also automatically enabled when stderr
is unavailable.

This option is passed through install or remove commands to
other modprobe commands in the MODPROBE_OPTIONS environment
variable.

–set-version
Set the kernel version, rather than using uname(2) to decide on
the kernel version (which dictates where to find the modules).
This also disables backwards compatibility checks (so mod-
probe.old(8) will never be run).

–show-depends
List the dependencies of a module (or alias), including the mod-
ule itself. This produces a (possibly empty) set of module
filenames, one per line, each starting with “insmod”. Install
commands which apply are shown prefixed by “install”. It does
not run any of the install commands. Note that modinfo(8) can
be used to extract dependencies of a module from the module
itself, but knows nothing of aliases or install commands.

-o –name
This option tries to rename the module which is being inserted
into the kernel. Some testing modules can usefully be inserted
multiple times, but the kernel refuses to have two modules of
the same name. Normally, modules should not require multiple
insertions, as that would make them useless if there were no
module support.

–first-time
Normally, modprobe will succeed (and do nothing) if told to
insert a module which is already present, or remove a module
which isn’t present. This is backwards compatible with the
modutils, and ideal for simple scripts. However, more compli-
cated scripts often want to know whether modprobe really did
something: this option makes modprobe fail for that case.

–dump-modversions
Print out a list of module versioning information required by a
module. This option is commonly used by distributions in order
to package up a Linuxx kernel module using module versioning
deps.

–use-blacklist
Apply a matchin blacklist entry also to a request by module
name, not only to a request by an alias.

–allow-unsupported-modules
Load unsupported modules even if disabled in configuration.

RETURN VALUE
modprobe returns 0 on success, 1 on an unspecified error and 2 if the
module is not supported. Use the –allow-unsupported-modules option to
force using an unsupported module.

BACKWARDS COMPATIBILITY
This version of modprobe is for kernels 2.5.48 and above. If it
detects a kernel with support for old-style modules (for which much of
the work was done in userspace), it will attempt to run modprobe.old in
its place, so it is completely transparent to the user.

ENVIRONMENT
The MODPROBE_OPTIONS environment variable can also be used to pass
arguments to modprobe.

COPYRIGHT
This manual page Copyright 2002, Rusty Russell, IBM Corporation.

SEE ALSO
modprobe.conf(5), lsmod(8), modprobe.old(8)

01 December 2008 MODPROBE(8)

Technorati Tags: ,

MKDIRHIER

MKDIRHIER(1) MKDIRHIER(1)

NAME
mkdirhier – makes a directory hierarchy

SYNOPSIS
mkdirhier directory …

DESCRIPTION
The mkdirhier command creates the specified directories. Unlike mkdir
if any of the parent directories of the specified directory do not
exist, it creates them as well.

SEE ALSO
mkdir(1)

X Version 11 imake 1.0.2 MKDIRHIER(1)

Technorati Tags: ,

MODINFO

MODINFO(8) MODINFO(8)

NAME
modinfo – program to show information about a Linux Kernel module

SYNOPSIS
modinfo [ -0 ] [ -F field ] [ -k kernel ] [ modulename|filename … ]

modinfo -V

modinfo -h

DESCRIPTION
modinfo extracts information from the Linux Kernel modules given on the
command line. If the module name is not a filename, then the /lib/mod-
ules/version directory is searched, as done by modprobe(8).

modinfo by default lists each attribute of the module in form fieldname
: value, for easy reading. The filename is listed the same way
(although it’s not really an attribute).

This version of modinfo can understand modules of any Linux Kernel
architecture.

OPTIONS
-V –version
Print the modinfo version. Note BACKWARDS COMPATIBILITY below:
you might be printing the version of modinfo.old.

-F –field
Only print this field value, one per line. This is most useful
for scripts. Field names are case-insenitive. Common fields
(which may not be in every module) include author, description,
license, param, depends, and alias. There are often multiple
param, alias and depends fields. The special field filename
lists the filename of the module.

-k kernel
Provide information about a kernel other than the running one.
This is particularly useful for distributions needing to extract
information from a newly installed (but not yet running) set of
kernel modules. For example, you wish to find which firmware
files are needed by various modules in a new kernel for which
you must make an initrd image prior to booting.

-0 –null
Use the ASCII zero character to separate field values, instead
of a new line. This is useful for scripts, since a new line can
theoretically appear inside a field.

-a -d -l -p -n
These are shortcuts for author, description, license. param and
filename respectively, to ease the transition from the old modu-
tils modinfo.

BACKWARDS COMPATIBILITY
This version of modinfo is for kernel modules 2.5.48 and above. If it
detects a kernel with support for old-style modules, it will attempt to
run modprobe.old in its place, so it is completely transparent to the
user.

Note that the output of this version of modinfo is simpler and more
regular than the older version: scripts attempting to use the default
output may get confused with complex fields.

You can force the new modinfo to always be used, by setting the
NEW_MODINFO environment variable.

COPYRIGHT
This manual page Copyright 2003, Rusty Russell, IBM Corporation.

SEE ALSO
modprobe(8), modinfo.old(8)

22 August 2008 MODINFO(8)

Technorati Tags: ,

MKFS

MKFS(8) MKFS(8)

NAME
mkfs – build a Linux file system

SYNOPSIS
mkfs [ -V ] [ -t fstype ] [ fs-options ] filesys [ blocks ]

DESCRIPTION
mkfs is used to build a Linux file system on a device, usually a hard
disk partition. filesys is either the device name (e.g. /dev/hda1,
/dev/sdb2). blocks is the number of blocks to be used for the file
system.

The exit code returned by mkfs is 0 on success and 1 on failure.

In actuality, mkfs is simply a front-end for the various file system
builders (mkfs.fstype) available under Linux. The file system-specific
builder is searched for in a number of directories like perhaps /sbin,
/sbin/fs, /sbin/fs.d, /etc/fs, /etc (the precise list is defined at
compile time but at least contains /sbin and /sbin/fs), and finally in
the directories listed in the PATH environment variable. Please see
the file system-specific builder manual pages for further details.

OPTIONS
-V Produce verbose output, including all file system-specific com-
mands that are executed. Specifying this option more than once
inhibits execution of any file system-specific commands. This
is really only useful for testing.

-t fstype
Specifies the type of file system to be built. If not speci-
fied, the default file system type (currently ext2) is used.

fs-options
File system-specific options to be passed to the real file sys-
tem builder. Although not guaranteed, the following options are
supported by most file system builders.

-c Check the device for bad blocks before building the file system.

-l filename
Read the bad blocks list from filename

-v Produce verbose output.

BUGS
All generic options must precede and not be combined with file system-
specific options. Some file system-specific programs do not support
the -v (verbose) option, nor return meaningful exit codes. Also, some
file system-specific programs do not automatically detect the device
size and require the blocks parameter to be specified.

AUTHORS
David Engel (david@ods.com)
Fred N. van Kempen (waltje@uwalt.nl.mugnet.org)
Ron Sommeling (sommel@sci.kun.nl)
The manual page was shamelessly adapted from Remy Card’s version for
the ext2 file system.

SEE ALSO
fs(5), badblocks(8), fsck(8), mkdosfs(8), mke2fs(8), mkfs.bfs(8),
mkfs.ext2(8), mkfs.ext3(8), mkfs.minix(8), mkfs.msdos(8), mkfs.vfat(8),
mkfs.xfs(8), mkfs.xiafs(8)

AVAILABILITY
The mkfs command is part of the util-linux-ng package and is available
from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.

Version 1.9 Jun 1995 MKFS(8)

Technorati Tags: ,