Your IP : 216.73.216.170
etc/init.d/README 0000666 00000004573 15077126552 0007413 0 ustar 00 Configuration of System V init under Debian GNU/Linux
Most Unix versions have a file here that describes how the scripts
in this directory work, and how the links in the /etc/rc?.d/ directories
influence system startup/shutdown.
For Debian, this information is contained in the policy manual, chapter
"System run levels and init.d scripts". The Debian Policy Manual is
available at:
http://www.debian.org/doc/debian-policy/#contents
The Debian Policy Manual is also available in the Debian package
"debian-policy". When this package is installed, the policy manual can be
found in directory /usr/share/doc/debian-policy. If you have a browser
installed you can probably read it at
file://localhost/usr/share/doc/debian-policy/
Some more detailed information can also be found in the files in the
/usr/share/doc/sysv-rc directory.
Debian Policy dictates that /etc/init.d/*.sh scripts must work properly
when sourced. The following additional rules apply:
* /etc/init.d/*.sh scripts must not rely for their correct functioning
on their being sourced rather than executed. That is, they must work
properly when executed too. They must include "#!/bin/sh" at the top.
This is useful when running scripts in parallel.
* /etc/init.d/*.sh scripts must conform to the rules for sh scripts as
spelled out in the Debian policy section entitled "Scripts" (§10.4).
Use the update-rc.d command to create symbolic links in the /etc/rc?.d
as appropriate. See that man page for more details.
All init.d scripts are expected to have a LSB style header documenting
dependencies and default runlevel settings. The header look like this
(not all fields are required):
### BEGIN INIT INFO
# Provides: skeleton
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Should-Start: $portmap
# Should-Stop: $portmap
# X-Start-Before: nis
# X-Stop-After: nis
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# X-Interactive: true
# Short-Description: Example initscript
# Description: This file should be used to construct scripts to be
# placed in /etc/init.d.
### END INIT INFO
More information on the format is available from insserv(8). This
information is used to dynamicaly assign sequence numbers to the
boot scripts and to run the scripts in parallel during the boot.
See also /usr/share/doc/insserv/README.Debian.
etc/rc5.d/README 0000666 00000001245 15077127465 0007136 0 ustar 00 The scripts in this directory are executed each time the system enters
this runlevel.
The scripts are all symbolic links whose targets are located in
/etc/init.d/ .
To disable a service in this runlevel, rename its script in this
directory so that the new name begins with a 'K' and a two-digit
number, and run 'update-rc.d script defaults' to reorder the scripts
according to dependencies. A warning about the current runlevels
being enabled not matching the LSB header in the init.d script will be
printed. To re-enable the service, rename the script back to its
original name beginning with 'S' and run update-rc.d again.
For a more information see /etc/init.d/README.
etc/rc6.d/README 0000666 00000000537 15077127502 0007132 0 ustar 00 The scripts in this directory are executed once when entering
runlevel 6.
The scripts are all symbolic links whose targets are located in
/etc/init.d/ .
Generally it is not necessary to alter the scripts in this directory.
Their purpose is to stop all services and to make the system ready
for reboot.
For more information see /etc/init.d/README.
etc/rc3.d/README 0000666 00000001245 15077146270 0007127 0 ustar 00 The scripts in this directory are executed each time the system enters
this runlevel.
The scripts are all symbolic links whose targets are located in
/etc/init.d/ .
To disable a service in this runlevel, rename its script in this
directory so that the new name begins with a 'K' and a two-digit
number, and run 'update-rc.d script defaults' to reorder the scripts
according to dependencies. A warning about the current runlevels
being enabled not matching the LSB header in the init.d script will be
printed. To re-enable the service, rename the script back to its
original name beginning with 'S' and run update-rc.d again.
For a more information see /etc/init.d/README.
etc/alternatives/README 0000666 00000000144 15077146737 0010724 0 ustar 00 Please read the update-alternatives(8) man page for information on this
directory and its contents.
etc/rc0.d/README 0000666 00000000541 15077147537 0007131 0 ustar 00 The scripts in this directory are executed once when entering
runlevel 0.
The scripts are all symbolic links whose targets are located in
/etc/init.d/ .
Generally it is not necessary to alter the scripts in this directory.
Their purpose is to stop all services and to make the system ready
for shutdown.
For more information see /etc/init.d/README.
etc/rc1.d/README 0000666 00000000561 15077147656 0007136 0 ustar 00 The scripts in this directory are executed each time the system enters
this runlevel.
The scripts are all symbolic links whose targets are located in
/etc/init.d/ .
Generally it is not necessary to alter the scripts in this directory.
Their purpose is to stop all services and thus to put the system in
single-user mode.
For more information see /etc/init.d/README.
etc/rc4.d/README 0000666 00000001245 15077147670 0007135 0 ustar 00 The scripts in this directory are executed each time the system enters
this runlevel.
The scripts are all symbolic links whose targets are located in
/etc/init.d/ .
To disable a service in this runlevel, rename its script in this
directory so that the new name begins with a 'K' and a two-digit
number, and run 'update-rc.d script defaults' to reorder the scripts
according to dependencies. A warning about the current runlevels
being enabled not matching the LSB header in the init.d script will be
printed. To re-enable the service, rename the script back to its
original name beginning with 'S' and run update-rc.d again.
For a more information see /etc/init.d/README.
etc/rc2.d/README 0000666 00000001245 15077147732 0007132 0 ustar 00 The scripts in this directory are executed each time the system enters
this runlevel.
The scripts are all symbolic links whose targets are located in
/etc/init.d/ .
To disable a service in this runlevel, rename its script in this
directory so that the new name begins with a 'K' and a two-digit
number, and run 'update-rc.d script defaults' to reorder the scripts
according to dependencies. A warning about the current runlevels
being enabled not matching the LSB header in the init.d script will be
printed. To re-enable the service, rename the script back to its
original name beginning with 'S' and run update-rc.d again.
For a more information see /etc/init.d/README.
etc/rcS.d/README 0000666 00000000677 15077166215 0007200 0 ustar 00 The scripts in this directory whose names begin with an 'S' are
executed once when booting the system, even when booting directly into
single user mode.
The scripts are all symbolic links whose targets are located in
/etc/init.d/ .
To disable a script in this directory, rename it so that it begins
with a 'K' and run 'update-rc.d script defaults' to update the order
using the script dependencies.
For more information see /etc/init.d/README.
etc/fonts/conf.d/README 0000666 00000001677 15077166432 0010531 0 ustar 00 conf.d/README
Each file in this directory is a fontconfig configuration file. Fontconfig
scans this directory, loading all files of the form [0-9][0-9]*.conf.
These files are normally installed in ../conf.avail and then symlinked here,
allowing them to be easily installed and then enabled/disabled by adjusting
the symlinks.
The files are loaded in numeric order, the structure of the configuration
has led to the following conventions in usage:
Files begining with: Contain:
00 through 09 Font directories
10 through 19 system rendering defaults (AA, etc)
20 through 29 font rendering options
30 through 39 family substitution
40 through 49 generic identification, map family->generic
50 through 59 alternate config file loading
60 through 69 generic aliases, map generic->family
70 through 79 select font (adjust which fonts are available)
80 through 89 match target="scan" (modify scanned patterns)
90 through 99 font synthesis
etc/terminfo/README 0000666 00000000236 15077201044 0010027 0 ustar 00 This directory is for system-local terminfo descriptions. By default, ncurses
will search this directory first, then /lib/terminfo, then /usr/share/terminfo.
usr/lib/mc/extfs.d/README 0000666 00000016352 15077270762 0011005 0 ustar 00 Writing scripts for Midnight Commander's external vfs
IMPORTANT NOTE: There may be some bugs left in extfs. Enjoy.
Starting with version 3.1, the Midnight Commander comes with so called
extfs, which is one of the virtual filesystems. This system makes it
possible to create new virtual filesystems for the GNU MC very easily.
To handle requests, create a shell/perl/python/etc script/program
(with executable permissions) in $(libexecdir)/mc/extfs.d
or in ~/.mc/extfs.d.
(Note: $(libexecdir) should be substituted for actual libexecdir path
stored when configured or compiled, like /usr/local/libexec or /usr/libexec).
Assign a vfs suffix. For example, if you have .zip file, and would like
to see what's inside it, path will be
/anypath/my.zip#uzip/some_path/...
In this example, .zip is suffix, but I call vfs 'uzip'. Why? Well,
what this vfs essentially does is UNzip. UN is too long, so I choosed
U. Note that sometime in future filesystem like zip may exist: It will
take whole tree and create .zip file from it. So /usr#zip will be
zipfile containing whole /usr tree.
If your vfs does not require file to work on, add '+' to the end of name.
Note, that trailing '+' in file name is not a part of vfs name, it is
just an vfs attribue. So you have not use it in vfs commands:
cd #rpms
is correct command, and
cd #rpms+
is incorrect command.
* Commands that should be implemented by your shell script
----------------------------------------------------------
Return zero from your script upon completion of the command, otherwise
nonzero for failure or in case of an unsupported command.
$libdir/extfs/prefix command [arguments]
* Command: list archivename
This command should list the complete archive content in the following format
(a little modified ls -l listing):
AAAAAAA NNN OOOOOOOO GGGGGGGG SSSSSSSS DATETIME [PATH/]FILENAME [-> [PATH/]FILENAME[/]]]
where (things in [] are optional):
AAAAAAA is the permission string like in ls -l
NNN is the number of links
OOOOOOOO is the owner (either UID or name)
GGGGGGGG is the group (either GID or name)
SSSSSSSS is the file size
FILENAME is the filename
PATH is the path from the archive's root without the leading slash (/)
DATETIME has one of the following formats:
Mon DD hh:mm, Mon DD YYYY, Mon DD YYYY hh:mm, MM-DD-YYYY hh:mm
where Mon is a three letter English month name, DD is day
1-31, MM is month 01-12, YYYY is four digit year, hh hour is
and mm is minute.
If the -> [PATH/]FILENAME part is present, it means:
If permissions start with an l (ell), then it is the name that symlink
points to. (If this PATH starts with a MC vfs prefix, then it is a symlink
somewhere to the other virtual filesystem (if you want to specify path from
the local root, use local:/path_name instead of /path_name, since /path_name
means from root of the archive listed).
If permissions do not start with l, but number of links is greater than one,
then it says that this file should be a hardlinked with the other file.
* Command: copyout archivename storedfilename extractto
This should extract from archive archivename the file called
storedfilename (possibly with path if not located in archive's root
[this is wrong. current extfs strips paths! -- pavel@ucw.cz])
to file extractto.
* Command: copyin archivename storedfilename sourcefile
This should add to the archivename the sourcefile with the name
storedfilename inside the archive.
Important note: archivename in the above examples may not have the
extension you are expecting to have, like it may happen that
archivename will be something like /tmp/f43513254 or just
anything. Some archivers do not like it, so you'll have to find some
workaround.
* Command: rm archivename storedfilename
This should remove storedfilename from archivename.
* Command: mkdir archivename dirname
This should create a new directory called dirname inside archivename.
* Command: rmdir archivename dirname
This should remove an existing directory dirname. If the directory is
not empty, mc will recursively delete it (possibly prompting).
* Command: run
Undocumented :-)
---------------------------------------------------------
Don't forget to mark this file executable (chmod 755 ThisFile, for example)
For skeleton structure of executable, look at some of filesystems
similar to yours.
---------------------------------------------------------
In constructing these routines, errors will be made, and mc will not display
a malformed printing line. That can lead the programmer down many false
trails in search of the bug. Since this routine is an executable shell script
it can be run from the command line independently of mc, and its output will
show on the console or can be redirected to a file.
* Putting it to use
----------------------------------------------------------
The file .mc.ext in a home directory, and in mc's user directory (commonly
/usr/local/lib/mc), contains instructions for operations on files depending
on filename extensions. It is well documented in other files in this
distribution, so here are just a few notes specifically on use of the
Virtual File System you just built.
There are entries in .mc.ext defining a few operations that can be done on a
file from an mc panel. Typically they are annotated with a hash mark and a
file extension like this:
# zip
There must be a way to find the file by extension, so the next line does
that. In essence it says "identify the string ".zip" or (|) ".ZIP" at the
end ($) of a filename":
regex/\.(zip|ZIP)$
The operations themselves follow that. They must be indented by at least a
space, and a tab works as well. In particular, the Open operation will
now use your new virtual file system by cd'ing to it like this:
Open=%cd zip:%d/%p
This is the line used when a file is highlighted in a panel and the user
presses <Enter> or <Return>. The contents of the archive should show just
as if they were in a real directory, and can be manipulated as such.
The rest of the entry pertains to use of the F3 View key:
View=%view{ascii} unzip -v %f
And perhaps an optional icon for X:
Icon=zip.xpm
And perhaps an operation to extract the contents of the file, called from
a menu selection:
Extract=unzip %f '*'
This is just an example. The current entry for .zip files has a menu selection
of 'Unzip' which could be used in place of 'Extract'. What goes here depends
on what items you have in, or add to, the menu system, and that's another
subject. The sum of this is the .mc.ext entry:
# zip
regex/\.(zip|ZIP)$
Open=%cd zip:%d/%p
View=%view{ascii} unzip -v %f
Icon=zip.xpm
Extract=unzip %f '*'
Add an entry like this to the .mc.ext file in a user's home directory, If you
want others to have it, add it to the mc.ext file in the mc system directory,
often /usr/local/lib/mc/mc.ext. Notice this file is not prepended with a dot.
Once all this is done, and things are in their proper places, exit mc if you
were using it, and restart it so it picks up the new information.
That's all there is to it. The hardest part is making a listing function
that sorts the output of a system listing command and turns it into a form
that mc can use. Currently awk (or gawk) is used because nearly all systems
have it. If another scripting language is available, like perl, that could
also be used.