<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>iTechLog &#187; Linux Man Pages</title>
	<atom:link href="http://itechlog.com/category/linux-man-pages/feed/" rel="self" type="application/rss+xml" />
	<link>http://itechlog.com</link>
	<description>Your source to IT solutions, interesting technology news and code snipets.</description>
	<lastBuildDate>Tue, 10 Jan 2012 17:06:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>SORT</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/04/sort/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/04/sort/#comments</comments>
		<pubDate>Sun, 04 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[SORT]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/03/04/sort/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT"></a>SORT(1) User Commands SORT(1) NAME sort &#8211; sort lines of text files SYNOPSIS sort [OPTION]&#8230; [FILE]&#8230; DESCRIPTION Write sorted concatenation of all FILE(s) to standard output. Mandatory arguments to long options are mandatory for short options too. Ordering options: -b, &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT"></a><p>SORT(1)                          User Commands                         SORT(1)</p>
<p>NAME<br />       sort &#8211; sort lines of text files</p>
<p>SYNOPSIS<br />       sort [OPTION]&#8230; [FILE]&#8230;</p>
<p>DESCRIPTION<br />       Write sorted concatenation of all FILE(s) to standard output.</p>
<p>       Mandatory  arguments  to  long  options are mandatory for short options<br />       too.  Ordering options:</p>
<p>       -b, &#8211;ignore-leading-blanks<br />              ignore leading blanks</p>
<p>       -d, &#8211;dictionary-order<br />              consider only blanks and alphanumeric characters</p>
<p>       -f, &#8211;ignore-case<br />              fold lower case to upper case characters</p>
<p>       -g, &#8211;general-numeric-sort<br />              compare according to general numerical value</p>
<p>       -i, &#8211;ignore-nonprinting<br />              consider only printable characters</p>
<p>       -M, &#8211;month-sort<br />              compare (unknown) &lt; `JAN&#8217; &lt; &#8230; &lt; `DEC&#8217;</p>
<p>       -n, &#8211;numeric-sort<br />              compare according to string numerical value</p>
<p>       -R, &#8211;random-sort<br />              sort by random hash of keys</p>
<p>       &#8211;random-source=FILE<br />              get random bytes from FILE (default /dev/urandom)</p>
<p>       &#8211;sort=WORD<br />              sort according to WORD: general-numeric -g,  month  -M,  numeric<br />              -n, random -R</p>
<p>       -r, &#8211;reverse<br />              reverse the result of comparisons</p>
<p>       Other options:</p>
<p>       -c, &#8211;check, &#8211;check=diagnose-first<br />              check for sorted input; do not sort</p>
<p>       -C, &#8211;check=quiet, &#8211;check=silent<br />              like -c, but do not report first bad line</p>
<p>       &#8211;compress-program=PROG<br />              compress temporaries with PROG; decompress them with PROG -d</p>
<p>       -k, &#8211;key=POS1[,POS2]<br />              start a key at POS1, end it at POS2 (origin 1)</p>
<p>       -m, &#8211;merge<br />              merge already sorted files; do not sort</p>
<p>       -o, &#8211;output=FILE<br />              write result to FILE instead of standard output</p>
<p>       -s, &#8211;stable<br />              stabilize sort by disabling last-resort comparison</p>
<p>       -S, &#8211;buffer-size=SIZE<br />              use SIZE for main memory buffer</p>
<p>       -t, &#8211;field-separator=SEP<br />              use SEP instead of non-blank to blank transition</p>
<p>       -T, &#8211;temporary-directory=DIR<br />              use  DIR  for temporaries, not $TMPDIR or /tmp; multiple options<br />              specify multiple directories</p>
<p>       -u, &#8211;unique<br />              with -c, check for strict ordering; without -c, output only  the<br />              first of an equal run</p>
<p>       -z, &#8211;zero-terminated<br />              end lines with 0 byte, not newline</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />              output version information and exit</p>
<p>       POS  is  F[.C][OPTS],  where  F is the field number and C the character<br />       position in the field; both are origin 1.  If neither -t nor -b  is  in<br />       effect,  characters  in  a  field are counted from the beginning of the<br />       preceding whitespace.  OPTS  is  one  or  more  single-letter  ordering<br />       options,  which  override  global ordering options for that key.  If no<br />       key is given, use the entire line as the key.</p>
<p>       SIZE may be followed by the following multiplicative suffixes: % 1%  of<br />       memory, b 1, K 1024 (default), and so on for M, G, T, P, E, Z, Y.</p>
<p>       With no FILE, or when FILE is -, read standard input.</p>
<p>       ***  WARNING  ***  The locale specified by the environment affects sort<br />       order.  Set LC_ALL=C to get the traditional sort order that uses native<br />       byte values.</p>
<p>AUTHOR<br />       Written by Mike Haertel and Paul Eggert.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-coreutils@gnu.org'); return false;" href="mailto:bug-coreutils@gnu.org">bug-coreutils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright  Â©  2008  Free Software Foundation, Inc.  License GPLv3+: GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This is free software: you are free  to  change  and  redistribute  it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       The  full documentation for sort is maintained as a Texinfo manual.  If<br />       the info and sort programs are properly installed  at  your  site,  the<br />       command</p>
<p>              info coreutils &#8216;sort invocation&#8217;</p>
<p>       should give you access to the complete manual.</p>
<p>GNU coreutils 6.12               December 2008                         SORT(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=af98035f-dcd4-48f7-a803-47a452bdaff5" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/SORT' rel='tag' target='_self'>SORT</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkswap/" title="MKSWAP">MKSWAP</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/04/sort/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>wvdial</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/02/wvdial/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/02/wvdial/#comments</comments>
		<pubDate>Fri, 02 Jan 2009 15:26:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[commandline]]></category>
		<category><![CDATA[Linux Man page]]></category>
		<category><![CDATA[wvdial]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/02/wvdial/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/02/wvdial/" title="wvdial"></a>WVDIAL(1) WVDIAL(1) NAME wvdial &#8211; PPP dialer with built-in intelligence. SYNOPSIS wvdial &#8211;help &#124; &#8211;version &#124; &#8211;chat &#124; &#8211;config &#124; option=value &#124; &#8211;no- syslog &#124; section&#8230; DESCRIPTION wvdial is an intelligent PPP dialer, which means that it dials a modem &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/02/wvdial/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/02/wvdial/" title="wvdial"></a><p>WVDIAL(1)                                                            WVDIAL(1)</p>
<p>NAME</p>
<p>       wvdial &#8211; PPP dialer with built-in intelligence.</p>
<p>SYNOPSIS</p>
<p>       wvdial  &#8211;help  |  &#8211;version | &#8211;chat | &#8211;config | option=value | &#8211;no-<br />
       syslog | section&#8230;</p>
<p>DESCRIPTION</p>
<p>       wvdial is an intelligent PPP dialer, which means that it dials a  modem<br />
       and  starts  PPP  in order to connect to the Internet.  It is something<br />
       like the chat(8) program, except that it uses heuristics to  guess  how<br />
       to  dial  and  log  into your server rather than forcing you to write a<br />
       login script.</p>
<p>       When  wvdial  starts,   it   first   loads   its   configuration   from<br />
       /etc/wvdial.conf and ~/.wvdialrc which contains basic information about<br />
       the modem port, speed, and init string, along  with  information  about<br />
       your  Internet  Service  Provider (ISP), such as the phone number, your<br />
       username, and your password.</p>
<p>       Then it initializes your modem and dials the server  and  waits  for  a<br />
       connection  (a  CONNECT  string  from  the  modem).  It understands and<br />
       responds to typical connection problems (like BUSY and NO DIALTONE).</p>
<p>       Any time after connecting, wvdial will start  PPP  if  it  sees  a  PPP<br />
       sequence  from  the server.  Otherwise, it tries to convince the server<br />
       to start PPP by doing the following:</p>
<p>        &#8211; responding to any login/password prompts it sees;</p>
<p>        &#8211; interpreting &#8220;choose one of the following&#8221;-style menus;</p>
<p>        &#8211; eventually, sending the word &#8220;ppp&#8221; (a common  terminal  server  com-<br />
              mand).</p>
<p>       If  all of this fails, wvdial just runs pppd(8) and hopes for the best.<br />
       It will bring up the connection, and then wait  patiently  for  you  to<br />
       drop the link by pressin CTRL-C.</p>
<p>OPTIONS</p>
<p>       Several options are recognized by wvdial.</p>
<p>       &#8211;chat Run  wvdial  as  a chat replacement from within pppd, instead of<br />
              the more normal method of having wvdial negotiate the connection<br />
              and then call pppd.</p>
<p>       &#8211;remotename<br />
              Override  the  Remote  Name  setting in the dialer configuration<br />
              section of the configuration file. This is  mainly  useful  when<br />
              you  dial  to multiple systems with the same user name and pass-<br />
              word, and you don’t want to use  inheritance  to  override  this<br />
              setting (which is the recommended way to do it).</p>
<p>       &#8211;config [configfile]<br />
              Run wvdial with configfile as the configuration file (instead of<br />
              /etc/wvdial.conf). This is mainly useful only  if  you  want  to<br />
              have  per-user configurations, or you want to avoid having dial-<br />
              up information  (usernames,  passwords,  calling  card  numbers,<br />
              etc.) in a system wide configuration file.</p>
<p>       &#8211;no-syslog<br />
              Don’t output debug information to the syslog daemon (only useful<br />
              together with &#8211;chat).</p>
<p>       &#8211;help Prints a short message describing how to use wvdial and exits.</p>
<p>       &#8211;version<br />
              Displays wvdial’s version number and exits.</p>
<p>       wvdial is normally run without command line options, in which  case  it<br />
       reads   its   configuration  from  the  [Dialer  Defaults]  section  of<br />
       /etc/wvdial.conf.  (The configuration file is described in more  detail<br />
       in wvdial.conf(5) manual page.)</p>
<p>       One  or  more sections of /etc/wvdial.conf may be specified on the com-<br />
       mand line.  Settings  in  these  sections  will  override  settings  in<br />
       [Dialer Defaults].</p>
<p>       For example, the command:<br />
              wvdial phone2</p>
<p>       will  read  default  options  from  the [Dialer Defaults] section, then<br />
       override any or all of the options with  those  found  in  the  [Dialer<br />
       phone2] section.</p>
<p>       If  more than one section is specified, they are processed in the order<br />
       they are given.  Each section will override all the sections that  came<br />
       before it.</p>
<p>       For example, the command:<br />
              wvdial phone2 pulse shh</p>
<p>       will  read  default  options  from  the [Dialer Defaults] section, then<br />
       override any or all of the options with  those  found  in  the  [Dialer<br />
       phone2] section, followed by the [Dialer pulse] section, and lastly the<br />
       [Dialer shh] section.</p>
<p>       Using this method, it is possible to easily configure wvdial to  switch<br />
       between  different  internet  providers,  modem  init  strings, account<br />
       names, and so on without specifying the same configuration  information<br />
       over and over.</p>
<p>BUGS</p>
<p>       &#8220;Intelligent&#8221;  programs  are  frustrating  when  they don’t work right.<br />
       This version of wvdial has only minimal support for disabling or  over-<br />
       riding  its &#8220;intelligence&#8221;, with the &#8220;Stupid Mode&#8221;, &#8220;Login Prompt&#8221;, and<br />
       &#8220;Password Prompt&#8221; options.  So, in general if you have a nice  ISP,  it<br />
       will probably work, and if you have a weird ISP, it might not.</p>
<p>       Still,  it’s not much good if it doesn’t work for you, right?  Don’t be<br />
       fooled by the fact that wvdial finally made  it  to  version  1.00;  it<br />
       could  well contain many bugs and misfeatures.  Let us know if you have<br />
       problems by sending e-mail to <wvdial @nit.ca>.</p>
<p>       Also, there is now a mailing list for discussion about wvdial.  If  you<br />
       are  having  problems,  or  have  anything  else to say, send e-mail to<br />
       </wvdial><wvdial -list@lists.nit.ca>.</p>
<p>       You may encounter some error messages if you don’t have write access to<br />
       /etc/ppp/pap-secrets and /etc/ppp/chap-secrets.  Unfortunately, there’s<br />
       really no nice way around this yet.</p>
<p>FILES</p>
<p>       /etc/wvdial.conf<br />
              Configuration file which  contains  modem,  dialing,  and  login<br />
              information. See</p>
<p>       /dev/ttyS*<br />
              Serial port devices.</p>
<p>       /etc/ppp/peers/wvdial<br />
              Required  for  correct  authentication  in pppd version 2.3.0 or<br />
              newer.</p>
<p>       /etc/ppp/{pap,chap}-secrets<br />
              Contains a list of usernames and  passwords  used  by  pppd  for<br />
              authentication.  wvdial maintains this list automatically.</p>
<p>AUTHORS</p>
<p>       Dave  Coombs  and  Avery  Pennarun for Net Integration Technologies, as<br />
       part of the Worldvisions Weaver project. We would like  to  thank  SuSE<br />
       and RedHat for adding a number of various cool features to Thanks guys!</p>
<p>SEE ALSO</p>
<p>       wvdial.conf(5), wvdialconf(1), pppd(8), chat(8).</p>
<p>       FAQ:   http://www.dsb3.com/wvdial/</p>
<p>Worldvisions WvDial                May 2001                          WVDIAL(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=cde9fa61-534a-4061-ac9f-e8101ed8735f" /></div>
<p></wvdial></p>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/commandline' rel='tag' target='_self'>commandline</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+page' rel='tag' target='_self'>Linux Man page</a>, <a class='technorati-link' href='http://technorati.com/tag/wvdial' rel='tag' target='_self'>wvdial</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>No Related Post</li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/02/wvdial/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MKDIRHIER</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[MKDIRHIER]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER"></a>MKDIRHIER(1) MKDIRHIER(1) NAME mkdirhier &#8211; makes a directory hierarchy SYNOPSIS mkdirhier directory &#8230; 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 &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER"></a><p>MKDIRHIER(1)                                                      MKDIRHIER(1)</p>
<p>NAME<br />       mkdirhier &#8211; makes a directory hierarchy</p>
<p>SYNOPSIS<br />       mkdirhier directory &#8230;</p>
<p>DESCRIPTION<br />       The  mkdirhier  command creates the specified directories. Unlike mkdir<br />       if any of the parent directories of  the  specified  directory  do  not<br />       exist, it creates them as well.</p>
<p>SEE ALSO<br />       mkdir(1)</p>
<p>X Version 11                      imake 1.0.2                     MKDIRHIER(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=426a54eb-d8b7-41a1-ad57-6295b57f6875" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/MKDIRHIER' rel='tag' target='_self'>MKDIRHIER</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkswap/" title="MKSWAP">MKSWAP</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MODINFO</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/modinfo/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/modinfo/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[MODINFO]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/modinfo/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO"></a>MODINFO(8) MODINFO(8) NAME modinfo &#8211; program to show information about a Linux Kernel module SYNOPSIS modinfo [ -0 ] [ -F field ] [ -k kernel ] [ modulename&#124;filename ... ] modinfo -V modinfo -h DESCRIPTION modinfo extracts information from &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO"></a><p>MODINFO(8)                                                          MODINFO(8)</p>
<p>NAME<br />       modinfo &#8211; program to show information about a Linux Kernel module</p>
<p>SYNOPSIS<br />       modinfo [ -0 ] [ -F field ] [ -k kernel ] [ modulename|filename ... ]</p>
<p>       modinfo -V</p>
<p>       modinfo -h</p>
<p>DESCRIPTION<br />       modinfo extracts information from the Linux Kernel modules given on the<br />       command line.  If the module name is not a filename, then the /lib/mod-<br />       ules/version directory is searched, as done by modprobe(8).</p>
<p>       modinfo by default lists each attribute of the module in form fieldname<br />       : value, for easy  reading.   The  filename  is  listed  the  same  way<br />       (although it&#8217;s not really an attribute).</p>
<p>       This  version  of  modinfo  can  understand modules of any Linux Kernel<br />       architecture.</p>
<p>OPTIONS<br />       -V &#8211;version<br />              Print the modinfo version.  Note BACKWARDS COMPATIBILITY  below:<br />              you might be printing the version of <a>modinfo.old</a>.</p>
<p>       -F &#8211;field<br />              Only  print this field value, one per line.  This is most useful<br />              for scripts.  Field names are  case-insenitive.   Common  fields<br />              (which  may not be in every module) include author, description,<br />              license, param, depends, and alias.  There  are  often  multiple<br />              param,  alias  and  depends  fields.  The special field filename<br />              lists the filename of the module.</p>
<p>       -k kernel<br />              Provide information about a kernel other than the  running  one.<br />              This is particularly useful for distributions needing to extract<br />              information from a newly installed (but not yet running) set  of<br />              kernel  modules.  For  example,  you wish to find which firmware<br />              files are needed by various modules in a new  kernel  for  which<br />              you must make an initrd image prior to booting.</p>
<p>       -0 &#8211;null<br />              Use  the  ASCII zero character to separate field values, instead<br />              of a new line.  This is useful for scripts, since a new line can<br />              theoretically appear inside a field.</p>
<p>       -a -d -l -p -n<br />              These are shortcuts for author, description, license.  param and<br />              filename respectively, to ease the transition from the old modu-<br />              tils modinfo.</p>
<p>BACKWARDS COMPATIBILITY<br />       This  version of modinfo is for kernel modules 2.5.48 and above.  If it<br />       detects a kernel with support for old-style modules, it will attempt to<br />       run  <a>modprobe.old</a>  in its place, so it is completely transparent to the<br />       user.</p>
<p>       Note that the output of this version of modinfo  is  simpler  and  more<br />       regular  than  the older version: scripts attempting to use the default<br />       output may get confused with complex fields.</p>
<p>       You can force the new  modinfo  to  always  be  used,  by  setting  the<br />       NEW_MODINFO environment variable.</p>
<p>COPYRIGHT<br />       This manual page Copyright 2003, Rusty Russell, IBM Corporation.</p>
<p>SEE ALSO<br />       modprobe(8), <a>modinfo.old</a>(8)</p>
<p>                                22 August 2008                      MODINFO(8)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=81a70bab-55d7-4aa7-9453-2e843dfe4444" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/MODINFO' rel='tag' target='_self'>MODINFO</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkswap/" title="MKSWAP">MKSWAP</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/modinfo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MKFS</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/mkfs/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/mkfs/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[MKFS]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/mkfs/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS"></a>MKFS(8) MKFS(8) NAME mkfs &#8211; 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 &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS"></a><p>MKFS(8)                                                                MKFS(8)</p>
<p>NAME<br />       mkfs &#8211; build a Linux file system</p>
<p>SYNOPSIS<br />       mkfs [ -V ] [ -t fstype ] [ fs-options ] filesys [ blocks ]</p>
<p>DESCRIPTION<br />       mkfs  is  used to build a Linux file system on a device, usually a hard<br />       disk partition.  filesys is either the device  name  (e.g.   /dev/hda1,<br />       /dev/sdb2).   blocks  is  the  number of blocks to be used for the file<br />       system.</p>
<p>       The exit code returned by mkfs is 0 on success and 1 on failure.</p>
<p>       In actuality, mkfs is simply a front-end for the  various  file  system<br />       builders (mkfs.fstype) available under Linux.  The file system-specific<br />       builder is searched for in a number of directories like perhaps  /sbin,<br />       /sbin/fs,  /sbin/fs.d,  /etc/fs,  /etc  (the precise list is defined at<br />       compile time but at least contains /sbin and /sbin/fs), and finally  in<br />       the  directories  listed  in the PATH environment variable.  Please see<br />       the file system-specific builder manual pages for further details.</p>
<p>OPTIONS<br />       -V     Produce verbose output, including all file system-specific  com-<br />              mands  that are executed.  Specifying this option more than once<br />              inhibits execution of any file system-specific  commands.   This<br />              is really only useful for testing.</p>
<p>       -t fstype<br />              Specifies  the  type  of file system to be built.  If not speci-<br />              fied, the default file system type (currently ext2) is used.</p>
<p>       fs-options<br />              File system-specific options to be passed to the real file  sys-<br />              tem builder.  Although not guaranteed, the following options are<br />              supported by most file system builders.</p>
<p>       -c     Check the device for bad blocks before building the file system.</p>
<p>       -l filename<br />              Read the bad blocks list from filename</p>
<p>       -v     Produce verbose output.</p>
<p>BUGS<br />       All  generic options must precede and not be combined with file system-<br />       specific options.  Some file system-specific programs  do  not  support<br />       the  -v (verbose) option, nor return meaningful exit codes.  Also, some<br />       file system-specific programs do not automatically  detect  the  device<br />       size and require the blocks parameter to be specified.</p>
<p>AUTHORS<br />       David Engel (david@ods.com)<br />       Fred N. van Kempen (waltje@uwalt.nl.mugnet.org)<br />       Ron Sommeling (sommel@sci.kun.nl)<br />       The  manual  page  was shamelessly adapted from Remy Card&#8217;s version for<br />       the ext2 file system.</p>
<p>SEE ALSO<br />       fs(5),  badblocks(8),  fsck(8),  mkdosfs(8),  mke2fs(8),   <a>mkfs.bfs</a>(8),<br />       mkfs.ext2(8), mkfs.ext3(8), <a>mkfs.minix</a>(8), <a>mkfs.msdos</a>(8), <a>mkfs.vfat</a>(8),<br />       <a>mkfs.xfs</a>(8), <a>mkfs.xiafs</a>(8)</p>
<p>AVAILABILITY<br />       The mkfs command is part of the util-linux-ng package and is  available<br />       from <a target="_blank" href="ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/">ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/</a>.</p>
<p>Version 1.9                        Jun 1995                            MKFS(8)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=59a1c7ed-1985-40ed-bfe9-274b78c25d13" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/MKFS' rel='tag' target='_self'>MKFS</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkswap/" title="MKSWAP">MKSWAP</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/mkfs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MKNOD</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/mknod/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/mknod/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[MKNOD]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/mknod/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD"></a>MKNOD(1) User Commands MKNOD(1) NAME mknod &#8211; make block or character special files SYNOPSIS mknod [OPTION]&#8230; NAME TYPE [MAJOR MINOR] DESCRIPTION Create the special file NAME of the given TYPE. -Z, &#8211;context=CTX set the SELinux security context of NAME to &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD"></a><p>MKNOD(1)                         User Commands                        MKNOD(1)</p>
<p>NAME<br />       mknod &#8211; make block or character special files</p>
<p>SYNOPSIS<br />       mknod [OPTION]&#8230; NAME TYPE [MAJOR MINOR]</p>
<p>DESCRIPTION<br />       Create the special file NAME of the given TYPE.</p>
<p>       -Z, &#8211;context=CTX<br />              set the SELinux security context of NAME to CTX</p>
<p>       Mandatory  arguments  to  long  options are mandatory for short options<br />       too.</p>
<p>       -m, &#8211;mode=MODE<br />              set file permission bits to MODE, not a=rw &#8211; umask</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />              output version information and exit</p>
<p>       Both MAJOR and MINOR must be specified when TYPE is b,  c,  or  u,  and<br />       they  must be omitted when TYPE is p.  If MAJOR or MINOR begins with 0x<br />       or 0X, it is interpreted as hexadecimal; otherwise, if it  begins  with<br />       0, as octal; otherwise, as decimal.  TYPE may be:</p>
<p>       b      create a block (buffered) special file</p>
<p>       c, u   create a character (unbuffered) special file</p>
<p>       p      create a FIFO</p>
<p>       NOTE:  your  shell  may  have  its  own version of mknod, which usually<br />       supersedes the version described here.  Please refer  to  your  shell&#8217;s<br />       documentation for details about the options it supports.</p>
<p>AUTHOR<br />       Written by David MacKenzie.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-coreutils@gnu.org'); return false;" href="mailto:bug-coreutils@gnu.org">bug-coreutils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright  Â©  2008  Free Software Foundation, Inc.  License GPLv3+: GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This is free software: you are free  to  change  and  redistribute  it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       mknod(2)</p>
<p>       The full documentation for mknod is maintained as a Texinfo manual.  If<br />       the info and mknod programs are properly installed at  your  site,  the<br />       command</p>
<p>              info coreutils &#8216;mknod invocation&#8217;</p>
<p>       should give you access to the complete manual.</p>
<p>GNU coreutils 6.12                 May 2008                           MKNOD(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=5039c369-a950-481b-acc3-6c2cee9f38c7" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/MKNOD' rel='tag' target='_self'>MKNOD</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkswap/" title="MKSWAP">MKSWAP</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/mknod/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MKSWAP</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/mkswap/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/mkswap/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[MKSWAP]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/mkswap/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mkswap/" title="MKSWAP"></a>MKSWAP(8) Linux Programmer&#8217;s Manual MKSWAP(8) NAME mkswap &#8211; set up a Linux swap area SYNOPSIS mkswap [-c] [-vN] [-f] [-p PSZ] [-L label] [-U uuid] device [size] DESCRIPTION mkswap sets up a Linux swap area on a device or in &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/mkswap/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mkswap/" title="MKSWAP"></a><p>MKSWAP(8)                  Linux Programmer&#8217;s Manual                 MKSWAP(8)</p>
<p>NAME<br />       mkswap &#8211; set up a Linux swap area</p>
<p>SYNOPSIS<br />       mkswap [-c] [-vN] [-f] [-p PSZ] [-L label] [-U uuid] device [size]</p>
<p>DESCRIPTION<br />       mkswap sets up a Linux swap area on a device or in a file.</p>
<p>       (After  creating  the  swap  area, you need the swapon command to start<br />       using it. Usually swap areas are listed in /etc/fstab so that they  can<br />       be  taken  into  use  at  boot time by a swapon -a command in some boot<br />       script.)</p>
<p>       The device argument will usually be a disk  partition  (something  like<br />       /dev/hda4  or /dev/sdb7) but can also be a file.  The Linux kernel does<br />       not look at partition Id&#8217;s, but many installation scripts  will  assume<br />       that partitions of hex type 82 (LINUX_SWAP) are meant to be swap parti-<br />       tions.  (Warning: Solaris also uses this type. Be careful not  to  kill<br />       your Solaris partitions.)</p>
<p>       The  size  parameter is superfluous but retained for backwards compati-<br />       bility.  (It specifies the desired size of the swap area  in  1024-byte<br />       blocks.  mkswap will use the entire partition or file if it is omitted.<br />       Specifying it is unwise &#8211; a typo may destroy your disk.)</p>
<p>       The PSZ parameter specifies the page size to use. It is  almost  always<br />       unnecessary  (even unwise) to specify it, but certain old libc versions<br />       lie about the page size, so it is possible that mkswap gets  it  wrong.<br />       The symptom is that a subsequent swapon fails because no swap signature<br />       is found. Typical values for PSZ are 4096 or 8192.</p>
<p>       Linux knows about two styles of swap areas, old style  and  new  style.<br />       The  last  10  bytes  of  the first page of the swap area distinguishes<br />       them: old style has `SWAP_SPACE&#8217;, new style has `SWAPSPACE2&#8242; as  signa-<br />       ture.</p>
<p>       In  the  old style, the rest of this first page was a bit map, with a 1<br />       bit for each usable page of the swap area.  Since the first page  holds<br />       this  bit  map,  the  first bit is 0.  Also, the last 10 bytes hold the<br />       signature. So, if the page size is  S,  an  old  style  swap  area  can<br />       describe  at  most 8*(S-10)-1 pages used for swapping.  With S=4096 (as<br />       on i386), the useful area is at most 133890048 bytes (almost 128  MiB),<br />       and the rest is wasted.  On an alpha and sparc64, with S=8192, the use-<br />       ful area is at most 535560992 bytes (almost 512 MiB).</p>
<p>       The old setup wastes most of this bitmap page, because zero bits denote<br />       bad blocks or blocks past the end of the swap space, and a simple inte-<br />       ger suffices to indicate the size of the  swap  space,  while  the  bad<br />       blocks,  if any, can simply be listed. Nobody wants to use a swap space<br />       with hundreds of bad blocks. (I would not even use a swap space with  1<br />       bad block.)  In the new style swap area this is precisely what is done.</p>
<p>       The maximum useful size of a swap area depends on the architecture  and<br />       the  kernel  version.  It is roughly 2GiB on i386, PPC, m68k, ARM, 1GiB<br />       on sparc, 512MiB on mips, 128GiB on alpha and 3TiB on sparc64. For ker-<br />       nels after 2.3.3 there is no such limitation.</p>
<p>       Note  that  before 2.1.117 the kernel allocated one byte for each page,<br />       while it now allocates two bytes, so that taking a swap area of  2  GiB<br />       in use might require 2 MiB of kernel memory.</p>
<p>       Presently, Linux allows 32 swap areas (this was 8 before Linux 2.4.10).<br />       The areas in use can be seen in the file /proc/swaps (since 2.1.25).</p>
<p>       mkswap refuses areas smaller than 10 pages.</p>
<p>       If you don&#8217;t know the page size that your machine uses, you may be able<br />       to  look  it up with &#8220;cat /proc/cpuinfo&#8221; (or you may not &#8211; the contents<br />       of this file depend on architecture and kernel version).</p>
<p>       To setup a swap file, it is necessary to create that file  before  ini-<br />       tializing it with mkswap , e.g. using a command like</p>
<p>              # dd if=/dev/zero of=swapfile bs=1024 count=65536</p>
<p>       Note  that  a  swap file must not contain any holes (so, using cp(1) to<br />       create the file is not acceptable).</p>
<p>OPTIONS<br />       -c     Check the device (if it is a block device) for bad blocks before<br />              creating the swap area.  If any are found, the count is printed.</p>
<p>       -f     Force &#8211; go ahead even if the command is stupid.  This allows the<br />              creation  of  a  swap  area larger than the file or partition it<br />              resides on.  On SPARC, force creation of the swap area.  Without<br />              this  option  mkswap will refuse to create a v0 swap on a device<br />              with a valid SPARC superblock, as that  probably  means  one  is<br />              going to erase the partition table.</p>
<p>       -p PSZ Specify the page size to use.</p>
<p>       -L label<br />              Specify  a label, to allow swapon by label.  (Only for new style<br />              swap areas.)</p>
<p>       -v0    Create an old style swap area.</p>
<p>       -v1    Create a new style swap area.</p>
<p>       If no -v option is given, mkswap will default to new style, but use old<br />       style  if  the  current  kernel  is  older  than  2.1.117  (and also if<br />       PAGE_SIZE is less than 2048).  The new style header does not touch  the<br />       first  block,  so  may be preferable, in case you have a boot loader or<br />       disk label there.  If you need to use both 2.0 and 2.2 kernels, use the<br />       -v0 option when creating the swapspace.</p>
<p>       Version  0  (-v0) swap space format is no longer supported in 2.5+ ker-<br />       nels.</p>
<p>       -U uuid<br />              Specify the uuid to use. The default is to generate UUIDs.</p>
<p>SEE ALSO<br />       fdisk(8), swapon(8)</p>
<p>AVAILABILITY<br />       The mkswap command is part of the util-linux-ng package and  is  avail-<br />       able from <a target="_blank" href="ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/">ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/</a>.</p>
<p>Linux 2.2.4                      25 March 1999                       MKSWAP(8)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=93a6f892-f7d8-487a-b2ec-6354b3e22c1d" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/MKSWAP' rel='tag' target='_self'>MKSWAP</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/mkswap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MORE</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/more/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/more/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[MORE]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/more/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/more/" title="MORE"></a>MORE(1) BSD General Commands Manual MORE(1) NAME more &#8211; file perusal filter for crt viewing SYNOPSIS more [-dlfpcsu] [-num] [+/ pattern] [+ linenum] [file ...] DESCRIPTION More is a filter for paging through text one screenful at a time. This &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/more/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/more/" title="MORE"></a><p>MORE(1)                   BSD General Commands Manual                  MORE(1)</p>
<p>NAME<br />     more &#8211; file perusal filter for crt viewing</p>
<p>SYNOPSIS<br />     more [-dlfpcsu] [-num] [+/ pattern] [+ linenum] [file ...]</p>
<p>DESCRIPTION<br />     More is a filter for paging through text one screenful at a time.  This<br />     version is especially primitive.  Users should realize that less(1) pro-<br />     vides more(1) emulation and extensive enhancements.</p>
<p>OPTIONS<br />     Command line options are described below.  Options are also taken from<br />     the environment variable MORE (make sure to precede them with a dash<br />     (&#8220;-&#8221;)) but command line options will override them.</p>
<p>     -num  This option specifies an integer which is the screen size (in<br />           lines).</p>
<p>     -d    more will prompt the user with the message &#8220;[Press space to con-<br />           tinue, 'q' to quit.]&#8221; and will display &#8220;[Press 'h' for instruc-<br />           tions.]&#8221; instead of ringing the bell when an illegal key is<br />           pressed.</p>
<p>     -l    more usually treats ^L (form feed) as a special character, and will<br />           pause after any line that contains a form feed.  The -l option will<br />           prevent this behavior.</p>
<p>     -f    Causes more to count logical, rather than screen lines (i.e., long<br />           lines are not folded).</p>
<p>     -p    Do not scroll.  Instead, clear the whole screen and then display<br />           the text.</p>
<p>     -c    Do not scroll.  Instead, paint each screen from the top, clearing<br />           the remainder of each line as it is displayed.</p>
<p>     -s    Squeeze multiple blank lines into one.</p>
<p>     -u    Suppress underlining.</p>
<p>     +/    The +/ option specifies a string that will be searched for before<br />           each file is displayed.</p>
<p>     +num  Start at line number num.</p>
<p>COMMANDS<br />     Interactive commands for more are based on vi(1).  Some commands may be<br />     preceded by a decimal number, called k in the descriptions below.  In the<br />     following descriptions, ^X means control-X.</p>
<p>     h or ?      Help: display a summary of these commands.  If you forget all<br />                 the other commands, remember this one.</p>
<p>     SPACE       Display next k lines of text.  Defaults to current screen<br />                 size.</p>
<p>     z           Display next k lines of text.  Defaults to current screen<br />                 size.  Argument becomes new default.</p>
<p>     RETURN      Display next k lines of text.  Defaults to 1.  Argument<br />                 becomes new default.</p>
<p>     d or ^D     Scroll k lines.  Default is current scroll size, initially<br />                 11.  Argument becomes new default.</p>
<p>     q or Q or INTERRUPT<br />                 Exit.</p>
<p>     s           Skip forward k lines of text.  Defaults to 1.</p>
<p>     f           Skip forward k screenfuls of text.  Defaults to 1.</p>
<p>     b or ^B     Skip backwards k screenfuls of text.  Defaults to 1.  Only<br />                 works with files, not pipes.</p>
<p>     &#8216;           Go to place where previous search started.</p>
<p>     =           Display current line number.</p>
<p>     /pattern    Search for kth occurrence of regular expression.  Defaults to<br />                 1.</p>
<p>     n           Search for kth occurrence of last r.e.  Defaults to 1.</p>
<p>     !&lt;cmd&gt; or :!&lt;cmd&gt;<br />                 Execute &lt;cmd&gt; in a subshell</p>
<p>     v           Start up an editor at current line.  The editor is taken from<br />                 the environment variable VISUAL if defined, or EDITOR if<br />                 VISUAL is not defined, or defaults to &#8220;vi&#8221; if neither VISUAL<br />                 nor EDITOR is defined.</p>
<p>     ^L          Redraw screen</p>
<p>     :n          Go to kth next file.  Defaults to 1.</p>
<p>     :p          Go to kth previous file.  Defaults to 1.</p>
<p>     :f          Display current file name and line number</p>
<p>     .           Repeat previous command</p>
<p>ENVIRONMENT<br />     More utilizes the following environment variables, if they exist:</p>
<p>     MORE        This variable may be set with favored options to more.</p>
<p>     SHELL       Current shell in use (normally set by the shell at login<br />                 time).</p>
<p>     TERM        Specifies terminal type, used by more to get the terminal<br />                 characteristics necessary to manipulate the screen.</p>
<p>SEE ALSO<br />     vi(1) less(1)</p>
<p>AUTHORS<br />     Eric Shienbrood, UC Berkeley<br />     Modified by Geoff Peck, UCB to add underlining, single spacing<br />     Modified by John Foderaro, UCB to add -c and MORE environment variable</p>
<p>HISTORY<br />     The more command appeared in 3.0BSD.  This man page documents more ver-<br />     sion 5.19 (Berkeley 6/29/88), which is currently in use in the Linux com-<br />     munity.  Documentation was produced using several other versions of the<br />     man page, and extensive inspection of the source code.</p>
<p>AVAILABILITY<br />     The more command is part of the util-linux-ng package and is available<br />     from <a target="_blank" href="ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/">ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/</a>.</p>
<p>Linux 0.98                     December 25, 1992                    Linux 0.98</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=9c6aba35-8e93-4cb0-9600-568e9400fdb3" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/MORE' rel='tag' target='_self'>MORE</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/more/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MV</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/mv/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/mv/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[MV]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/mv/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mv/" title="MV"></a>MV(1) User Commands MV(1) NAME mv &#8211; move (rename) files SYNOPSIS mv [OPTION]&#8230; [-T] SOURCE DEST mv [OPTION]&#8230; SOURCE&#8230; DIRECTORY mv [OPTION]&#8230; -t DIRECTORY SOURCE&#8230; DESCRIPTION Rename SOURCE to DEST, or move SOURCE(s) to DIRECTORY. Mandatory arguments to long options &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/mv/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/mv/" title="MV"></a><p>MV(1)                            User Commands                           MV(1)</p>
<p>NAME<br />       mv &#8211; move (rename) files</p>
<p>SYNOPSIS<br />       mv [OPTION]&#8230; [-T] SOURCE DEST<br />       mv [OPTION]&#8230; SOURCE&#8230; DIRECTORY<br />       mv [OPTION]&#8230; -t DIRECTORY SOURCE&#8230;</p>
<p>DESCRIPTION<br />       Rename SOURCE to DEST, or move SOURCE(s) to DIRECTORY.</p>
<p>       Mandatory  arguments  to  long  options are mandatory for short options<br />       too.</p>
<p>       &#8211;backup[=CONTROL]<br />              make a backup of each existing destination file</p>
<p>       -b     like &#8211;backup but does not accept an argument</p>
<p>       -f, &#8211;force<br />              do not prompt before overwriting</p>
<p>       -i, &#8211;interactive<br />              prompt before overwrite</p>
<p>       &#8211;strip-trailing-slashes<br />              remove any trailing slashes from each SOURCE argument</p>
<p>       -S, &#8211;suffix=SUFFIX<br />              override the usual backup suffix</p>
<p>       -t, &#8211;target-directory=DIRECTORY<br />              move all SOURCE arguments into DIRECTORY</p>
<p>       -T, &#8211;no-target-directory<br />              treat DEST as a normal file</p>
<p>       -u, &#8211;update<br />              move only when the SOURCE file is  newer  than  the  destination<br />              file or when the destination file is missing</p>
<p>       -v, &#8211;verbose<br />              explain what is being done</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />              output version information and exit</p>
<p>       The   backup   suffix   is  `~&#8217;,  unless  set  with  &#8211;suffix  or  SIM-<br />       PLE_BACKUP_SUFFIX.  The version control method may be selected via  the<br />       &#8211;backup  option  or  through the VERSION_CONTROL environment variable.<br />       Here are the values:</p>
<p>       none, off<br />              never make backups (even if &#8211;backup is given)</p>
<p>       numbered, t<br />              make numbered backups</p>
<p>       existing, nil<br />              numbered if numbered backups exist, simple otherwise</p>
<p>       simple, never<br />              always make simple backups</p>
<p>AUTHOR<br />       Written by Mike Parker, David MacKenzie, and Jim Meyering.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-coreutils@gnu.org'); return false;" href="mailto:bug-coreutils@gnu.org">bug-coreutils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright Â© 2008 Free Software Foundation, Inc.   License  GPLv3+:  GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This  is  free  software:  you  are free to change and redistribute it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       rename(2)</p>
<p>       The full documentation for mv is maintained as a  Texinfo  manual.   If<br />       the  info and mv programs are properly installed at your site, the com-<br />       mand</p>
<p>              info coreutils &#8216;mv invocation&#8217;</p>
<p>       should give you access to the complete manual.</p>
<p>GNU coreutils 6.12               December 2008                           MV(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=16abe231-6e24-4c92-9c4d-a4b76da0dc62" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/MV' rel='tag' target='_self'>MV</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/mv/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MODPROBE</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/modprobe/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/modprobe/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:11:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[MODPROBE]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/modprobe/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/modprobe/" title="MODPROBE"></a>MODPROBE(8) MODPROBE(8) NAME modprobe &#8211; program to add and remove modules from the Linux Kernel SYNOPSIS modprobe [ -v ] [ -V ] [ -C config-file ] [ -n ] [ -i ] [ -q ] [ -o modulename ] &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/modprobe/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/modprobe/" title="MODPROBE"></a><p>MODPROBE(8)                                                        MODPROBE(8)</p>
<p>NAME<br />       modprobe &#8211; program to add and remove modules from the Linux Kernel</p>
<p>SYNOPSIS<br />       modprobe  [  -v  ]  [ -V ] [ -C config-file ] [ -n ] [ -i ] [ -q ] [ -o<br />       modulename ] [ modulename ] [ module parameters ... ]</p>
<p>       modprobe [ -r ] [ -v ] [ -n ] [ -i ] [ modulename ... ]</p>
<p>       modprobe [ -l ] [ -t dirname ] [ wildcard ]</p>
<p>       modprobe [ -c ]</p>
<p>       modprobe [ --dump-modversions ]</p>
<p>DESCRIPTION<br />       modprobe intelligently adds or removes a module from the Linux  kernel:<br />       note  that  for  convenience, there is no difference between _ and &#8211; in<br />       module  names.   modprobe  looks  in  the  module  directory  /lib/mod-<br />       ules/`uname  -r`  for  all  the modules and other files, except for the<br />       optional  /etc/modprobe.conf  configuration  file  and  /etc/modprobe.d<br />       directory (see <a>modprobe.conf</a>(5)). modprobe will also use module options<br />       specified on the kernel command line in the form of &lt;module&gt;.option&gt;.</p>
<p>       Note that this version of modprobe does not do anything to  the  module<br />       itself:  the  work of resolving symbols and understanding parameters is<br />       done inside the kernel.  So module failure is sometimes accompanied  by<br />       a kernel message: see dmesg(8).</p>
<p>       modprobe expects an up-to-date <a>modules.dep</a> file, as generated by depmod<br />       (see depmod(8)).  This file lists what other modules each module  needs<br />       (if  any),  and  modprobe uses this to add or remove these dependencies<br />       automatically.  See <a>modules.dep</a>(5)).</p>
<p>       If any arguments are given after the modulename, they are passed to the<br />       kernel (in addition to any options listed in the configuration file).</p>
<p>OPTIONS<br />       -v &#8211;verbose<br />              Print  messages  about  what the program is doing.  Usually mod-<br />              probe only prints messages if something goes wrong.</p>
<p>              This option is passed through  install  or  remove  commands  to<br />              other  modprobe  commands  in  the  MODPROBE_OPTIONS environment<br />              variable.</p>
<p>       -C &#8211;config<br />              This option overrides the default configuration file  (/etc/mod-<br />              <a>probe.conf</a> or /etc/modprobe.d/ if that isn&#8217;t found).</p>
<p>              This  option  is  passed  through  install or remove commands to<br />              other modprobe  commands  in  the  MODPROBE_OPTIONS  environment<br />              variable.</p>
<p>       -c &#8211;showconfig<br />              Dump out the configuration file and exit.</p>
<p>       -n &#8211;dry-run<br />              This  option  does  everything but actually insert or delete the<br />              modules (or run the install or remove commands).  Combined  with<br />              -v, it is useful for debugging problems.</p>
<p>       -i &#8211;ignore-install &#8211;ignore-remove<br />              This  option  causes  modprobe to ignore install and remove com-<br />              mands in the configuration file (if any), for the module on  the<br />              command  line  (any  dependent modules are still subject to com-<br />              mands set  for  them  in  the  configuration  file).   See  mod-<br />              <a>probe.conf</a>(5).</p>
<p>       -q &#8211;quiet<br />              Normally  modprobe  will report an error if you try to remove or<br />              insert  a  module  it  can&#8217;t  find  (and  isn&#8217;t  an   alias   or<br />              install/remove  command).   With this flag, modprobe will simply<br />              ignore any bogus names (the kernel uses  this  to  opportunisti-<br />              cally probe for modules which might exist).</p>
<p>       -r &#8211;remove<br />              This option causes modprobe to remove, rather than insert a mod-<br />              ule.  If the modules it depends on  are  also  unused,  modprobe<br />              will  try  to remove them, too.  Unlike insertion, more than one<br />              module can be specified on the command line (it  does  not  make<br />              sense to specify module parameters when removing modules).</p>
<p>              There  is  usually  no  reason to remove modules, but some buggy<br />              modules require it.  Your kernel may not support removal of mod-<br />              ules.</p>
<p>       -w &#8211;wait<br />              This  option  is applicable only with the -r or &#8211;remove option.<br />              It causes modprobe to block in the  kernel  (within  the  kernel<br />              module  handling code itself) waiting for the specified modules&#8217;<br />              reference count to reach zero. Default operation is for modprobe<br />              to  operate like rmmod, which exits with EWOULDBLOCK if the mod-<br />              ules reference count is non-zero.</p>
<p>       -V &#8211;version<br />              Show version of program, and exit.  See below for  caveats  when<br />              run on older kernels.</p>
<p>       -f &#8211;force<br />              Try  to  strip any versioning information from the module, which<br />              might otherwise stop it from loading: this is the same as  using<br />              both  &#8211;force-vermagic and &#8211;force-modversion.  Naturally, these<br />              checks are there for your protection, so using  this  option  is<br />              dangerous.</p>
<p>              This applies to any modules inserted: both the module (or alias)<br />              on the command line, and any modules it depends on.</p>
<p>       &#8211;force-vermagic<br />              Every module contains a small string containing important infor-<br />              mation,  such  as the kernel and compiler versions.  If a module<br />              fails to load and the kernel complains that the &#8220;version  magic&#8221;<br />              doesn&#8217;t match, you can use this option to remove it.  Naturally,<br />              this check is there for your protection, so this using option is<br />              dangerous.</p>
<p>              This applies to any modules inserted: both the module (or alias)<br />              on the command line, and any modules it depends on.</p>
<p>       &#8211;force-modversion<br />              When modules are compiled with CONFIG_MODVERSIONS set, a section<br />              is created detailing the versions of every interface used by (or<br />              supplied by) the module.  If a module fails to load and the ker-<br />              nel  complains that the module disagrees about a version of some<br />              interface, you can use &#8220;&#8211;force-modversion&#8221; to remove  the  ver-<br />              sion information altogether.  Naturally, this check is there for<br />              your protection, so using this option is dangerous.</p>
<p>              This applies any modules inserted: both the module (or alias) on<br />              the command line, and any modules it depends on.</p>
<p>       -l &#8211;list<br />              List all modules matching the given wildcard (or &#8220;*&#8221; if no wild-<br />              card is given).  This option is provided for backwards  compati-<br />              bility: see find(1) and basename(1) for a more flexible alterna-<br />              tive.</p>
<p>       -a &#8211;all<br />              Insert all module names on the command line.</p>
<p>       -t &#8211;type<br />              Restrict -l to  modules  in  directories  matching  the  dirname<br />              given.  This option is provided for backwards compatibility: see<br />              find(1) and basename(1) or a more flexible alternative.</p>
<p>       -s &#8211;syslog<br />              This option causes any error messages to go through  the  syslog<br />              mechanism  (as  LOG_DAEMON with level LOG_NOTICE) rather than to<br />              standard error.  This is also automatically enabled when  stderr<br />              is unavailable.</p>
<p>              This  option  is  passed  through  install or remove commands to<br />              other modprobe  commands  in  the  MODPROBE_OPTIONS  environment<br />              variable.</p>
<p>       &#8211;set-version<br />              Set  the kernel version, rather than using uname(2) to decide on<br />              the kernel version (which dictates where to find  the  modules).<br />              This  also  disables  backwards  compatibility  checks  (so mod-<br />              <a>probe.old</a>(8) will never be run).</p>
<p>       &#8211;show-depends<br />              List the dependencies of a module (or alias), including the mod-<br />              ule  itself.   This  produces  a  (possibly empty) set of module<br />              filenames, one per line, each starting with  &#8220;insmod&#8221;.   Install<br />              commands  which  apply are shown prefixed by &#8220;install&#8221;.  It does<br />              not run any of the install commands.  Note that  modinfo(8)  can<br />              be  used  to  extract  dependencies  of a module from the module<br />              itself, but knows nothing of aliases or install commands.</p>
<p>       -o &#8211;name<br />              This option tries to rename the module which is  being  inserted<br />              into  the kernel.  Some testing modules can usefully be inserted<br />              multiple times, but the kernel refuses to have  two  modules  of<br />              the  same  name.   Normally, modules should not require multiple<br />              insertions, as that would make them useless  if  there  were  no<br />              module support.</p>
<p>       &#8211;first-time<br />              Normally,  modprobe  will  succeed  (and  do nothing) if told to<br />              insert a module which is already present,  or  remove  a  module<br />              which  isn&#8217;t  present.   This  is  backwards compatible with the<br />              modutils, and ideal for simple scripts.  However,  more  compli-<br />              cated  scripts  often  want  to know whether modprobe really did<br />              something: this option makes modprobe fail for that case.</p>
<p>       &#8211;dump-modversions<br />              Print out a list of module versioning information required by  a<br />              module.  This  option is commonly used by distributions in order<br />              to package up a Linuxx kernel  module  using  module  versioning<br />              deps.</p>
<p>       &#8211;use-blacklist<br />              Apply  a  matchin  blacklist  entry  also to a request by module<br />              name, not only to a request by an alias.</p>
<p>       &#8211;allow-unsupported-modules<br />              Load unsupported modules even if disabled in configuration.</p>
<p>RETURN VALUE<br />       modprobe returns 0 on success, 1 on an unspecified error and 2  if  the<br />       module  is not supported. Use the &#8211;allow-unsupported-modules option to<br />       force using an unsupported module.</p>
<p>BACKWARDS COMPATIBILITY<br />       This version of modprobe is  for  kernels  2.5.48  and  above.   If  it<br />       detects  a kernel with support for old-style modules (for which much of<br />       the work was done in userspace), it will attempt to run <a>modprobe.old</a> in<br />       its place, so it is completely transparent to the user.</p>
<p>ENVIRONMENT<br />       The  MODPROBE_OPTIONS  environment  variable  can  also be used to pass<br />       arguments to modprobe.</p>
<p>COPYRIGHT<br />       This manual page Copyright 2002, Rusty Russell, IBM Corporation.</p>
<p>SEE ALSO<br />       <a>modprobe.conf</a>(5), lsmod(8), <a>modprobe.old</a>(8)</p>
<p>                               01 December 2008                    MODPROBE(8)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=9b475bc5-0a6b-422a-ad61-271e471646ac" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a>, <a class='technorati-link' href='http://technorati.com/tag/MODPROBE' rel='tag' target='_self'>MODPROBE</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/modprobe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DATE</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/date/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/date/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[DATE]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/date/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/date/" title="DATE"></a>DATE(1) User Commands DATE(1) NAME date &#8211; print or set the system date and time SYNOPSIS date [OPTION]&#8230; [+FORMAT] date [-u&#124;--utc&#124;--universal] [MMDDhhmm[[CC]YY][.ss]] DESCRIPTION Display the current time in the given FORMAT, or set the system date. -d, &#8211;date=STRING display time &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/date/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/date/" title="DATE"></a><p>DATE(1)                          User Commands                         DATE(1)</p>
<p>NAME<br />       date &#8211; print or set the system date and time</p>
<p>SYNOPSIS<br />       date [OPTION]&#8230; [+FORMAT]<br />       date [-u|--utc|--universal] [MMDDhhmm[[CC]YY][.ss]]</p>
<p>DESCRIPTION<br />       Display the current time in the given FORMAT, or set the system date.</p>
<p>       -d, &#8211;date=STRING<br />              display time described by STRING, not `now&#8217;</p>
<p>       -f, &#8211;file=DATEFILE<br />              like &#8211;date once for each line of DATEFILE</p>
<p>       -r, &#8211;reference=FILE<br />              display the last modification time of FILE</p>
<p>       -R, &#8211;rfc-2822<br />              output  date  and time in RFC 2822 format.  Example: Mon, 07 Aug<br />              2006 12:34:56 -0600</p>
<p>       &#8211;rfc-3339=TIMESPEC<br />              output date and time in RFC 3339 format.  TIMESPEC=`date&#8217;, `sec-<br />              onds&#8217;,  or  `ns&#8217;  for  date and time to the indicated precision.<br />              Date and time  components  are  separated  by  a  single  space:<br />              2006-08-07 12:34:56-06:00</p>
<p>       -s, &#8211;set=STRING<br />              set time described by STRING</p>
<p>       -u, &#8211;utc, &#8211;universal<br />              print or set Coordinated Universal Time</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />              output version information and exit</p>
<p>       FORMAT  controls the output.  The only valid option for the second form<br />       specifies Coordinated Universal Time.  Interpreted sequences are:</p>
<p>       %%     a literal %</p>
<p>       %a     locale&#8217;s abbreviated weekday name (e.g., Sun)</p>
<p>       %A     locale&#8217;s full weekday name (e.g., Sunday)</p>
<p>       %b     locale&#8217;s abbreviated month name (e.g., Jan)</p>
<p>       %B     locale&#8217;s full month name (e.g., January)</p>
<p>       %c     locale&#8217;s date and time (e.g., Thu Mar  3 23:05:25 2005)</p>
<p>       %C     century; like %Y, except omit last two digits (e.g., 21)</p>
<p>       %d     day of month (e.g, 01)</p>
<p>       %D     date; same as %m/%d/%y</p>
<p>       %e     day of month, space padded; same as %_d</p>
<p>       %F     full date; same as %Y-%m-%d</p>
<p>       %g     last two digits of year of ISO week number (see %G)</p>
<p>       %G     year of ISO week number (see %V); normally useful only with %V</p>
<p>       %h     same as %b</p>
<p>       %H     hour (00..23)</p>
<p>       %I     hour (01..12)</p>
<p>       %j     day of year (001..366)</p>
<p>       %k     hour ( 0..23)</p>
<p>       %l     hour ( 1..12)</p>
<p>       %m     month (01..12)</p>
<p>       %M     minute (00..59)</p>
<p>       %n     a newline</p>
<p>       %N     nanoseconds (000000000..999999999)</p>
<p>       %p     locale&#8217;s equivalent of either AM or PM; blank if not known</p>
<p>       %P     like %p, but lower case</p>
<p>       %r     locale&#8217;s 12-hour clock time (e.g., 11:11:04 PM)</p>
<p>       %R     24-hour hour and minute; same as %H:%M</p>
<p>       %s     seconds since 1970-01-01 00:00:00 UTC</p>
<p>       %S     second (00..60)</p>
<p>       %t     a tab</p>
<p>       %T     time; same as %H:%M:%S</p>
<p>       %u     day of week (1..7); 1 is Monday</p>
<p>       %U     week number of year, with Sunday as first day of week (00..53)</p>
<p>       %V     ISO week number, with Monday as first day of week (01..53)</p>
<p>       %w     day of week (0..6); 0 is Sunday</p>
<p>       %W     week number of year, with Monday as first day of week (00..53)</p>
<p>       %x     locale&#8217;s date representation (e.g., 12/31/99)</p>
<p>       %X     locale&#8217;s time representation (e.g., 23:13:48)</p>
<p>       %y     last two digits of year (00..99)</p>
<p>       %Y     year</p>
<p>       %z     +hhmm numeric timezone (e.g., -0400)</p>
<p>       %:z    +hh:mm numeric timezone (e.g., -04:00)</p>
<p>       %::z   +hh:mm:ss numeric time zone (e.g., -04:00:00)</p>
<p>       %:::z  numeric time zone with :  to  necessary  precision  (e.g.,  -04,<br />              +05:30)</p>
<p>       %Z     alphabetic time zone abbreviation (e.g., EDT)</p>
<p>       By  default,  date  pads  numeric  fields  with  zeroes.  The following<br />       optional flags may follow `%&#8217;:</p>
<p>       &#8211;      (hyphen) do not pad the field</p>
<p>       _      (underscore) pad with spaces</p>
<p>       0      (zero) pad with zeros</p>
<p>       ^      use upper case if possible</p>
<p>       #      use opposite case if possible</p>
<p>       After any flags comes an optional field width,  as  a  decimal  number;<br />       then an optional modifier, which is either E to use the locale&#8217;s alter-<br />       nate representations if available, or O to use the  locale&#8217;s  alternate<br />       numeric symbols if available.</p>
<p>DATE STRING<br />       The  &#8211;date=STRING  is  a mostly free format human readable date string<br />       such as &#8220;Sun, 29 Feb 2004 16:21:42 -0800&#8243; or &#8220;2004-02-29  16:21:42&#8243;  or<br />       even  &#8220;next Thursday&#8221;.  A date string may contain items indicating cal-<br />       endar date, time of day, time zone, day of week, relative  time,  rela-<br />       tive date, and numbers.  An empty string indicates the beginning of the<br />       day.  The date string format is more complex than is easily  documented<br />       here but is fully described in the info documentation.</p>
<p>AUTHOR<br />       Written by David MacKenzie.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-coreutils@gnu.org'); return false;" href="mailto:bug-coreutils@gnu.org">bug-coreutils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright  Â©  2008  Free Software Foundation, Inc.  License GPLv3+: GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This is free software: you are free  to  change  and  redistribute  it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       The  full documentation for date is maintained as a Texinfo manual.  If<br />       the info and date programs are properly installed  at  your  site,  the<br />       command</p>
<p>              info coreutils &#8216;date invocation&#8217;</p>
<p>       should give you access to the complete manual.</p>
<p>GNU coreutils 6.12                 May 2008                            DATE(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=e3c048f8-555f-4aaf-bd58-1015800be29d" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/DATE' rel='tag' target='_self'>DATE</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 31, 2011 -- <a href="http://itechlog.com/web-programming/2011/01/31/it-is-not-safe-to-rely-on-the-systems-timezone-settings/" title="It is not safe to rely on the system’s timezone settings">It is not safe to rely on the system’s timezone settings</a></li><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/date/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DD</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/dd/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/dd/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[DD]]></category>
		<category><![CDATA[Linux Ma Pages]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/dd/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/dd/" title="DD"></a>DD(1) User Commands DD(1) NAME dd &#8211; convert and copy a file SYNOPSIS dd [OPERAND]&#8230; dd OPTION DESCRIPTION Copy a file, converting and formatting according to the operands. bs=BYTES force ibs=BYTES and obs=BYTES cbs=BYTES convert BYTES bytes at a time &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/dd/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/dd/" title="DD"></a><p>DD(1)                            User Commands                           DD(1)</p>
<p>NAME<br />       dd &#8211; convert and copy a file</p>
<p>SYNOPSIS<br />       dd [OPERAND]&#8230;<br />       dd OPTION</p>
<p>DESCRIPTION<br />       Copy a file, converting and formatting according to the operands.</p>
<p>       bs=BYTES<br />              force ibs=BYTES and obs=BYTES</p>
<p>       cbs=BYTES<br />              convert BYTES bytes at a time</p>
<p>       conv=CONVS<br />              convert the file as per the comma separated symbol list</p>
<p>       count=BLOCKS<br />              copy only BLOCKS input blocks</p>
<p>       ibs=BYTES<br />              read BYTES bytes at a time</p>
<p>       if=FILE<br />              read from FILE instead of stdin</p>
<p>       iflag=FLAGS<br />              read as per the comma separated symbol list</p>
<p>       obs=BYTES<br />              write BYTES bytes at a time</p>
<p>       of=FILE<br />              write to FILE instead of stdout</p>
<p>       oflag=FLAGS<br />              write as per the comma separated symbol list</p>
<p>       seek=BLOCKS<br />              skip BLOCKS obs-sized blocks at start of output</p>
<p>       skip=BLOCKS<br />              skip BLOCKS ibs-sized blocks at start of input</p>
<p>       status=noxfer<br />              suppress transfer statistics</p>
<p>       BLOCKS  and  BYTES may be followed by the following multiplicative suf-<br />       fixes: xM M, c 1, w 2,  b  512,  kB  1000,  K  1024,  MB  1000*1000,  M<br />       1024*1024,  GB 1000*1000*1000, G 1024*1024*1024, and so on for T, P, E,<br />       Z, Y.</p>
<p>       Each CONV symbol may be:</p>
<p>       ascii  from EBCDIC to ASCII</p>
<p>       ebcdic from ASCII to EBCDIC</p>
<p>       ibm    from ASCII to alternate EBCDIC</p>
<p>       block  pad newline-terminated records with spaces to cbs-size</p>
<p>       unblock<br />              replace trailing spaces in cbs-size records with newline</p>
<p>       lcase  change upper case to lower case</p>
<p>       nocreat<br />              do not create the output file</p>
<p>       excl   fail if the output file already exists</p>
<p>       notrunc<br />              do not truncate the output file</p>
<p>       ucase  change lower case to upper case</p>
<p>       swab   swap every pair of input bytes</p>
<p>       noerror<br />              continue after read errors</p>
<p>       sync   pad every input block with NULs  to  ibs-size;  when  used  with<br />              block or unblock, pad with spaces rather than NULs</p>
<p>       fdatasync<br />              physically write output file data before finishing</p>
<p>       fsync  likewise, but also write metadata</p>
<p>       Each FLAG symbol may be:</p>
<p>       append append  mode  (makes  sense  only  for output; conv=notrunc sug-<br />              gested)</p>
<p>       direct use direct I/O for data</p>
<p>              directory fail unless a directory dsync     use synchronized I/O<br />              for data sync      likewise, but also for metadata nonblock  use<br />              non-blocking I/O noatime   do  not  update  access  time  noctty<br />              do  not  assign  controlling terminal from file nofollow  do not<br />              follow symlinks</p>
<p>       Sending a USR1 signal to a running `dd&#8217;  process  makes  it  print  I/O<br />       statistics to standard error and then resume copying.</p>
<p>              $ dd if=/dev/zero of=/dev/null&amp; pid=$!<br />              $ kill -USR1 $pid; sleep 1; kill $pid</p>
<p>              18335302+0  records  in  18335302+0 records out 9387674624 bytes<br />              (9.4 GB) copied, 34.6279 seconds, 271 MB/s</p>
<p>       Options are:</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />              output version information and exit</p>
<p>AUTHOR<br />       Written by Paul Rubin, David MacKenzie, and Stuart Kemp.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-coreutils@gnu.org'); return false;" href="mailto:bug-coreutils@gnu.org">bug-coreutils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright Â© 2008 Free Software Foundation, Inc.   License  GPLv3+:  GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This  is  free  software:  you  are free to change and redistribute it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       The full documentation for dd is maintained as a  Texinfo  manual.   If<br />       the  info and dd programs are properly installed at your site, the com-<br />       mand</p>
<p>              info coreutils &#8216;dd invocation&#8217;</p>
<p>       should give you access to the complete manual.</p>
<p>GNU coreutils 6.12                 May 2008                              DD(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=aef9e218-5cf0-498a-b323-6a3dbb324f19" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/DD' rel='tag' target='_self'>DD</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Ma+Pages' rel='tag' target='_self'>Linux Ma Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/info/" title="INFO">INFO</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/dd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DEPMOD</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/depmod/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/depmod/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[DEPMOD]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/depmod/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/depmod/" title="DEPMOD"></a>DEPMOD(8) DEPMOD(8) NAME depmod &#8211; program to generate modules.dep and map files. SYNOPSIS depmod [ -b basedir ] [ -e ] [ -F System.map ] [ -n ] [ -v ] [ version ] [ -A ] depmod [ -e &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/depmod/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/depmod/" title="DEPMOD"></a><p>DEPMOD(8)                                                            DEPMOD(8)</p>
<p>NAME<br />       depmod &#8211; program to generate <a>modules.dep</a> and map files.</p>
<p>SYNOPSIS<br />       depmod  [ -b basedir ] [ -e ] [ -F <a>System.map</a> ] [ -n ] [ -v ] [ version<br />       ] [ -A ]</p>
<p>       depmod [ -e ] [ <a>-FSystem.map</a> ] [ -n ] [ -v ] [ version ] [ filename ...<br />       ]</p>
<p>DESCRIPTION<br />       Linux  kernel modules can provide services (called &#8220;symbols&#8221;) for other<br />       modules to use (using EXPORT_SYMBOL in the code).  If a  second  module<br />       uses  this symbol, that second module clearly depends on the first mod-<br />       ule.  These dependencies can get quite complex.</p>
<p>       depmod creates a list of module dependencies, by  reading  each  module<br />       under /lib/modules/version and determining what symbols it exports, and<br />       what symbols it needs.  By default this list is written to  <a>modules.dep</a><br />       in  the  same  directory.   If filenames are given on the command line,<br />       only those modules are examined (which is  rarely  useful,  unless  all<br />       modules are listed).</p>
<p>       If  a  version is provided, then that kernel version&#8217;s module directory<br />       is used, rather than the current kernel version (as returned by  &#8220;uname<br />       -r&#8221;).</p>
<p>       depmod  will also generate various map files in this directory, for use<br />       by the hotplug infrastructure.</p>
<p>OPTIONS<br />       -a &#8211;all<br />              Probe all modules. This option is enabled by default if no  file<br />              names are given in the command-line.</p>
<p>       -A &#8211;quick<br />              This  option scans to see if any modules are newer than the mod-<br />              <a>ules.dep</a> file before any work is done: if not, it silently exits<br />              rather than regenerating the files.</p>
<p>       -b basedir &#8211;basedir basedir<br />              If  your  modules  are  not  currently in the (normal) directory<br />              /lib/modules/version, but in a staging area, you can  specify  a<br />              basedir  which is prepended to the directory name.  This basedir<br />              is stripped from the resulting <a>modules.dep</a> file, so it is  ready<br />              to be moved into the normal location.</p>
<p>       -C &#8211;config file or directory<br />              This  option overrides the default configuration file (/etc/dep-<br />              <a>mod.conf</a> or /etc/depmod.d/ if that is not found).</p>
<p>       -e &#8211;errsyms<br />              When combined with the -F option, this reports any symbols which<br />              a  module  needs  which are not supplied by other modules or the<br />              kernel.  Normally, any  symbols  not  provided  by  modules  are<br />              assumed  to be provided by the kernel (which should be true in a<br />              perfect world).</p>
<p>       -F &#8211;filesyms <a>System.map</a><br />              Supplied with the <a>System.map</a> produced when the kernel was built,<br />              this allows the -e option to report unresolved symbols.</p>
<p>       -h &#8211;help<br />              Print the help message, and exit.</p>
<p>       -n &#8211;dry-run<br />              This  sends  the  resulting  <a>modules.dep</a>,  then  the various map<br />              files, to standard output, rather than  writing  them  into  the<br />              module directory.</p>
<p>       -v &#8211;verbose<br />              In  verbose  mode  depmod will print (to stdout) all the symbols<br />              each module depends on and the module&#8217;s file name which provides<br />              that symbol.</p>
<p>       -V &#8211;version<br />              Show  version  of  program, and exit. See below for caveats when<br />              run on older kernels.</p>
<p>BACKWARDS COMPATIBILITY<br />       This version of depmod is for kernels 2.5.48 and above.  If it  detects<br />       a  kernel  with support for old-style modules, or the version specified<br />       is before 2.5.48, it will attempt to run <a>depmod.old</a> in its place, so it<br />       is completely transparent to the user.</p>
<p>COPYRIGHT<br />       This manual page Copyright 2002, Rusty Russell, IBM Corporation.</p>
<p>SEE ALSO<br />       modprobe(8), <a>modules.dep</a>(5), <a>depmod.old</a>(8)</p>
<p>                                22 August 2008                       DEPMOD(8)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=908a38db-71d6-4210-95d6-9b74e92d953d" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/DEPMOD' rel='tag' target='_self'>DEPMOD</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/depmod/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DF</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/df/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/df/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[DF]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/df/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/df/" title="DF"></a>DF(1) User Commands DF(1) NAME df &#8211; report file system disk space usage SYNOPSIS df [OPTION]&#8230; [FILE]&#8230; DESCRIPTION This manual page documents the GNU version of df. df displays the amount of disk space available on the file system containing &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/df/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/df/" title="DF"></a><p>DF(1)                            User Commands                           DF(1)</p>
<p>NAME<br />       df &#8211; report file system disk space usage</p>
<p>SYNOPSIS<br />       df [OPTION]&#8230; [FILE]&#8230;</p>
<p>DESCRIPTION<br />       This  manual  page  documents  the  GNU version of df.  df displays the<br />       amount of disk space available on the file system containing each  file<br />       name  argument.   If  no file name is given, the space available on all<br />       currently mounted file systems is shown.  Disk space  is  shown  in  1K<br />       blocks  by  default, unless the environment variable POSIXLY_CORRECT is<br />       set, in which case 512-byte blocks are used.</p>
<p>       If an argument is the absolute file name of a disk device node contain-<br />       ing  a  mounted  file system, df shows the space available on that file<br />       system rather than on the file system containing the device node (which<br />       is  always  the  root file system).  This version of df cannot show the<br />       space available on unmounted file systems, because  on  most  kinds  of<br />       systems  doing  so requires very nonportable intimate knowledge of file<br />       system structures.</p>
<p>OPTIONS<br />       Show information about the file system on which each FILE  resides,  or<br />       all file systems by default.</p>
<p>       Mandatory  arguments  to  long  options are mandatory for short options<br />       too.</p>
<p>       -a, &#8211;all<br />              include dummy file systems</p>
<p>       -B, &#8211;block-size=SIZE<br />              use SIZE-byte blocks</p>
<p>       -h, &#8211;human-readable<br />              print sizes in human readable format (e.g., 1K 234M 2G)</p>
<p>       -H, &#8211;si<br />              likewise, but use powers of 1000 not 1024</p>
<p>       -i, &#8211;inodes<br />              list inode information instead of block usage</p>
<p>       -k     like &#8211;block-size=1K</p>
<p>       -l, &#8211;local<br />              limit listing to local file systems</p>
<p>       &#8211;no-sync<br />              do not invoke sync before getting usage info (default)</p>
<p>       -P, &#8211;portability<br />              use the POSIX output format</p>
<p>       &#8211;sync invoke sync before getting usage info</p>
<p>       -t, &#8211;type=TYPE<br />              limit listing to file systems of type TYPE</p>
<p>       -T, &#8211;print-type<br />              print file system type</p>
<p>       -x, &#8211;exclude-type=TYPE<br />              limit listing to file systems not of type TYPE</p>
<p>       -v     (ignored)</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />              output version information and exit</p>
<p>       SIZE may be (or may be an integer optionally followed by) one  of  fol-<br />       lowing: kB 1000, K 1024, MB 1000*1000, M 1024*1024, and so on for G, T,<br />       P, E, Z, Y.</p>
<p>AUTHOR<br />       Written by Torbj?rn Granlund, David MacKenzie, and Paul Eggert.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-coreutils@gnu.org'); return false;" href="mailto:bug-coreutils@gnu.org">bug-coreutils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright Â© 2008 Free Software Foundation, Inc.   License  GPLv3+:  GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This  is  free  software:  you  are free to change and redistribute it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       The full documentation for df is maintained as a  Texinfo  manual.   If<br />       the  info and df programs are properly installed at your site, the com-<br />       mand</p>
<p>              info coreutils &#8216;df invocation&#8217;</p>
<p>       should give you access to the complete manual.</p>
<p>GNU coreutils 6.12                 May 2008                              DF(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=837940d7-89dc-4d1c-b6e3-49489e24810e" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/DF' rel='tag' target='_self'>DF</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/df/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DIFF</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/diff/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/diff/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[DIFF]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/diff/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/diff/" title="DIFF"></a>DIFF(1) User Commands DIFF(1) NAME diff &#8211; compare files line by line SYNOPSIS diff [OPTION]&#8230; FILES DESCRIPTION Compare files line by line. -i &#8211;ignore-case Ignore case differences in file contents. &#8211;ignore-file-name-case Ignore case when comparing file names. &#8211;no-ignore-file-name-case Consider case &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/diff/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/diff/" title="DIFF"></a><p>DIFF(1)                          User Commands                         DIFF(1)</p>
<p>NAME<br />       diff &#8211; compare files line by line</p>
<p>SYNOPSIS<br />       diff [OPTION]&#8230; FILES</p>
<p>DESCRIPTION<br />       Compare files line by line.</p>
<p>       -i  &#8211;ignore-case<br />              Ignore case differences in file contents.</p>
<p>       &#8211;ignore-file-name-case<br />              Ignore case when comparing file names.</p>
<p>       &#8211;no-ignore-file-name-case<br />              Consider case when comparing file names.</p>
<p>       -E  &#8211;ignore-tab-expansion<br />              Ignore changes due to tab expansion.</p>
<p>       -b  &#8211;ignore-space-change<br />              Ignore changes in the amount of white space.</p>
<p>       -w  &#8211;ignore-all-space<br />              Ignore all white space.</p>
<p>       -B  &#8211;ignore-blank-lines<br />              Ignore changes whose lines are all blank.</p>
<p>       -I RE  &#8211;ignore-matching-lines=RE<br />              Ignore changes whose lines all match RE.</p>
<p>       &#8211;strip-trailing-cr<br />              Strip trailing carriage return on input.</p>
<p>       -a  &#8211;text<br />              Treat all files as text.</p>
<p>       -c  -C NUM  &#8211;context[=NUM]<br />              Output NUM (default 3) lines of copied context.</p>
<p>       -u  -U NUM  &#8211;unified[=NUM]<br />              Output NUM (default 3) lines of unified context.</p>
<p>       &#8211;label LABEL<br />              Use LABEL instead of file name.</p>
<p>       -p  &#8211;show-c-function<br />              Show which C function each change is in.</p>
<p>       -F RE  &#8211;show-function-line=RE<br />              Show the most recent line matching RE.</p>
<p>       -q  &#8211;brief<br />              Output only whether files differ.</p>
<p>       -e  &#8211;ed<br />              Output an ed script.</p>
<p>       &#8211;normal<br />              Output a normal diff.</p>
<p>       -n  &#8211;rcs<br />              Output an RCS format diff.</p>
<p>       -y  &#8211;side-by-side<br />              Output in two columns.</p>
<p>       -W NUM  &#8211;width=NUM<br />              Output at most NUM (default 130) print columns.</p>
<p>       &#8211;left-column<br />              Output only the left column of common lines.</p>
<p>       &#8211;suppress-common-lines<br />              Do not output common lines.</p>
<p>       -D NAME  &#8211;ifdef=NAME<br />              Output merged file to show `#ifdef NAME&#8217; diffs.</p>
<p>       &#8211;GTYPE-group-format=GFMT<br />              Similar, but format GTYPE input groups with GFMT.</p>
<p>       &#8211;line-format=LFMT<br />              Similar, but format all input lines with LFMT.</p>
<p>       &#8211;LTYPE-line-format=LFMT<br />              Similar, but format LTYPE input lines with LFMT.</p>
<p>       LTYPE is `old&#8217;, `new&#8217;, or `unchanged&#8217;.<br />              GTYPE is LTYPE or `changed&#8217;.</p>
<p>              GFMT may contain:</p>
<p>       %&lt;     lines from FILE1</p>
<p>       %&gt;     lines from FILE2</p>
<p>       %=     lines common to FILE1 and FILE2</p>
<p>       %[-][WIDTH][.[PREC]]{doxX}LETTER<br />              printf-style spec for LETTER</p>
<p>              LETTERs are as follows for new group, lower case for old group:</p>
<p>       F      first line number</p>
<p>       L      last line number</p>
<p>       N      number of lines = L-F+1</p>
<p>       E      F-1</p>
<p>       M      L+1</p>
<p>              LFMT may contain:</p>
<p>       %L     contents of line</p>
<p>       %l     contents of line, excluding any trailing newline</p>
<p>       %[-][WIDTH][.[PREC]]{doxX}n<br />              printf-style spec for input line number</p>
<p>              Either GFMT or LFMT may contain:</p>
<p>       %%     %</p>
<p>       %c&#8217;C&#8217;  the single character C</p>
<p>       %c&#8217;\OOO&#8217;<br />              the character with octal code OOO</p>
<p>       -l  &#8211;paginate<br />              Pass the output through `pr&#8217; to paginate it.</p>
<p>       -t  &#8211;expand-tabs<br />              Expand tabs to spaces in output.</p>
<p>       -T  &#8211;initial-tab<br />              Make tabs line up by prepending a tab.</p>
<p>       &#8211;tabsize=NUM<br />              Tab stops are every NUM (default 8) print columns.</p>
<p>       &#8211;suppress-blank-empty<br />              Suppress space or tab before empty output lines.</p>
<p>       -r  &#8211;recursive<br />              Recursively compare any subdirectories found.</p>
<p>       -N  &#8211;new-file<br />              Treat absent files as empty.</p>
<p>       &#8211;unidirectional-new-file<br />              Treat absent first files as empty.</p>
<p>       -s  &#8211;report-identical-files<br />              Report when two files are the same.</p>
<p>       -x PAT  &#8211;exclude=PAT<br />              Exclude files that match PAT.</p>
<p>       -X FILE  &#8211;exclude-from=FILE<br />              Exclude files that match any pattern in FILE.</p>
<p>       -S FILE  &#8211;starting-file=FILE<br />              Start with FILE when comparing directories.</p>
<p>       &#8211;from-file=FILE1<br />              Compare FILE1 to all operands.  FILE1 can be a directory.</p>
<p>       &#8211;to-file=FILE2<br />              Compare all operands to FILE2.  FILE2 can be a directory.</p>
<p>       &#8211;horizon-lines=NUM<br />              Keep NUM lines of the common prefix and suffix.</p>
<p>       -d  &#8211;minimal<br />              Try hard to find a smaller set of changes.</p>
<p>       &#8211;speed-large-files<br />              Assume large files and many scattered small changes.</p>
<p>       -v  &#8211;version<br />              Output version info.</p>
<p>       &#8211;help Output this help.</p>
<p>       FILES  are  `FILE1  FILE2&#8242;  or `DIR1 DIR2&#8242; or `DIR FILE&#8230;&#8217; or `FILE&#8230;<br />       DIR&#8217;.  If &#8211;from-file or &#8211;to-file is given, there are no  restrictions<br />       on  FILES.  If a FILE is `-&#8217;, read standard input.  Exit status is 0 if<br />       inputs are the same, 1 if different, 2 if trouble.</p>
<p>AUTHOR<br />       Written by Paul Eggert, Mike Haertel, David  Hayes,  Richard  Stallman,<br />       and Len Tower.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-gnu-utils@gnu.org'); return false;" href="mailto:bug-gnu-utils@gnu.org">bug-gnu-utils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright  Â©  2007  Free Software Foundation, Inc.  License GPLv3+: GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This is free software: you are free  to  change  and  redistribute  it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       The  full documentation for diff is maintained as a Texinfo manual.  If<br />       the info and diff programs are properly installed  at  your  site,  the<br />       command</p>
<p>              info diff</p>
<p>       should give you access to the complete manual.</p>
<p>diffutils 2.8.7-cvs              January 2008                          DIFF(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=4917c800-b139-410d-8e3d-a4c5c0c9c823" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/DIFF' rel='tag' target='_self'>DIFF</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/diff/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DIFF3</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/diff3/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/diff3/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[DIFF3]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/diff3/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/diff3/" title="DIFF3"></a>DIFF3(1) User Commands DIFF3(1) NAME diff3 &#8211; compare three files line by line SYNOPSIS diff3 [OPTION]&#8230; MYFILE OLDFILE YOURFILE DESCRIPTION Compare three files line by line. -e &#8211;ed Output unmerged changes from OLDFILE to YOURFILE into MYFILE. -E &#8211;show-overlap Output &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/diff3/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/diff3/" title="DIFF3"></a><p>DIFF3(1)                         User Commands                        DIFF3(1)</p>
<p>NAME<br />       diff3 &#8211; compare three files line by line</p>
<p>SYNOPSIS<br />       diff3 [OPTION]&#8230; MYFILE OLDFILE YOURFILE</p>
<p>DESCRIPTION<br />       Compare three files line by line.</p>
<p>       -e  &#8211;ed<br />              Output unmerged changes from OLDFILE to YOURFILE into MYFILE.</p>
<p>       -E  &#8211;show-overlap<br />              Output unmerged changes, bracketing conflicts.</p>
<p>       -A  &#8211;show-all<br />              Output all changes, bracketing conflicts.</p>
<p>       -x  &#8211;overlap-only<br />              Output overlapping changes.</p>
<p>       -X     Output overlapping changes, bracketing them.</p>
<p>       -3  &#8211;easy-only<br />              Output unmerged nonoverlapping changes.</p>
<p>       -m  &#8211;merge<br />              Output merged file instead of ed script (default -A).</p>
<p>       -L LABEL  &#8211;label=LABEL<br />              Use LABEL instead of file name.</p>
<p>       -i     Append `w&#8217; and `q&#8217; commands to ed scripts.</p>
<p>       -a  &#8211;text<br />              Treat all files as text.</p>
<p>       &#8211;strip-trailing-cr<br />              Strip trailing carriage return on input.</p>
<p>       -T  &#8211;initial-tab<br />              Make tabs line up by prepending a tab.</p>
<p>       &#8211;diff-program=PROGRAM<br />              Use PROGRAM to compare files.</p>
<p>       -v  &#8211;version<br />              Output version info.</p>
<p>       &#8211;help Output this help.</p>
<p>       If a FILE is `-&#8217;, read standard input.  Exit status is 0 if successful,<br />       1 if conflicts, 2 if trouble.</p>
<p>AUTHOR<br />       Written by Randy Smith.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-gnu-utils@gnu.org'); return false;" href="mailto:bug-gnu-utils@gnu.org">bug-gnu-utils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright Â© 2007 Free Software Foundation, Inc.   License  GPLv3+:  GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This  is  free  software:  you  are free to change and redistribute it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       The full documentation for diff3 is maintained as a Texinfo manual.  If<br />       the  info  and  diff3 programs are properly installed at your site, the<br />       command</p>
<p>              info diff</p>
<p>       should give you access to the complete manual.</p>
<p>diffutils 2.8.7-cvs              January 2008                         DIFF3(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=8683ddca-53a0-4468-b492-94adb7187969" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/DIFF3' rel='tag' target='_self'>DIFF3</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/diff3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DIG</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/dig/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/dig/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[DIG]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/dig/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/dig/" title="DIG"></a>DIG(1) BIND9 DIG(1) NAME dig &#8211; DNS lookup utility SYNOPSIS dig [@server] [-b address] [-c class] [-f filename] [-k filename] [-p port#] [-q name] [-t type] [-x addr] [-y [hmac:]name:key] [-4] [-6] [name] [type] [class] [queryopt...] dig [-h] dig [global-queryopt...] &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/dig/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/dig/" title="DIG"></a><p>DIG(1)                               BIND9                              DIG(1)</p>
<p>NAME<br />       dig &#8211; DNS lookup utility</p>
<p>SYNOPSIS<br />       dig [@server] [-b address] [-c class] [-f filename] [-k filename]<br />           [-p port#] [-q name] [-t type] [-x addr] [-y [hmac:]name:key] [-4]<br />           [-6] [name] [type] [class] [queryopt...]</p>
<p>       dig [-h]</p>
<p>       dig [global-queryopt...] [query...]</p>
<p>DESCRIPTION<br />       dig (domain information groper) is a flexible tool for interrogating<br />       DNS name servers. It performs DNS lookups and displays the answers that<br />       are returned from the name server(s) that were queried. Most DNS<br />       administrators use dig to troubleshoot DNS problems because of its<br />       flexibility, ease of use and clarity of output. Other lookup tools tend<br />       to have less functionality than dig.</p>
<p>       Although dig is normally used with command-line arguments, it also has<br />       a batch mode of operation for reading lookup requests from a file. A<br />       brief summary of its command-line arguments and options is printed when<br />       the -h option is given. Unlike earlier versions, the BIND 9<br />       implementation of dig allows multiple lookups to be issued from the<br />       command line.</p>
<p>       Unless it is told to query a specific name server, dig will try each of<br />       the servers listed in /etc/resolv.conf.</p>
<p>       When no command line arguments or options are given, will perform an NS<br />       query for &#8220;.&#8221; (the root).</p>
<p>       It is possible to set per-user defaults for dig via ${HOME}/.digrc.<br />       This file is read and any options in it are applied before the command<br />       line arguments.</p>
<p>       The IN and CH class names overlap with the IN and CH top level domains<br />       names. Either use the -t and -c options to specify the type and class<br />       or use the -q the specify the domain name or use &#8220;IN.&#8221; and &#8220;CH.&#8221; when<br />       looking up these top level domains.</p>
<p>SIMPLE USAGE<br />       A typical invocation of dig looks like:</p>
<p>            dig @server name type</p>
<p>       where:</p>
<p>       server<br />           is the name or IP address of the name server to query. This can be<br />           an IPv4 address in dotted-decimal notation or an IPv6 address in<br />           colon-delimited notation. When the supplied server argument is a<br />           hostname, dig resolves that name before querying that name server.<br />           If no server argument is provided, dig consults /etc/resolv.conf<br />           and queries the name servers listed there. The reply from the name<br />           server that responds is displayed.</p>
<p>       name<br />           is the name of the resource record that is to be looked up.</p>
<p>       type<br />           indicates what type of query is required â ANY, A, MX, SIG, etc.<br />           type can be any valid query type. If no type argument is supplied,<br />           dig will perform a lookup for an A record.</p>
<p>OPTIONS<br />       The -b option sets the source IP address of the query to address. This<br />       must be a valid address on one of the host&#8217;s network interfaces or<br />       &#8220;0.0.0.0&#8243; or &#8220;::&#8221;. An optional port may be specified by appending<br />       &#8220;#&lt;port&gt;&#8221;</p>
<p>       The default query class (IN for internet) is overridden by the -c<br />       option.  class is any valid class, such as HS for Hesiod records or CH<br />       for Chaosnet records.</p>
<p>       The -f option makes dig operate in batch mode by reading a list of<br />       lookup requests to process from the file filename. The file contains a<br />       number of queries, one per line. Each entry in the file should be<br />       organized in the same way they would be presented as queries to dig<br />       using the command-line interface.</p>
<p>       If a non-standard port number is to be queried, the -p option is used.<br />       port# is the port number that dig will send its queries instead of the<br />       standard DNS port number 53. This option would be used to test a name<br />       server that has been configured to listen for queries on a non-standard<br />       port number.</p>
<p>       The -4 option forces dig to only use IPv4 query transport. The -6<br />       option forces dig to only use IPv6 query transport.</p>
<p>       The -t option sets the query type to type. It can be any valid query<br />       type which is supported in BIND 9. The default query type is &#8220;A&#8221;,<br />       unless the -x option is supplied to indicate a reverse lookup. A zone<br />       transfer can be requested by specifying a type of AXFR. When an<br />       incremental zone transfer (IXFR) is required, type is set to ixfr=N.<br />       The incremental zone transfer will contain the changes made to the zone<br />       since the serial number in the zone&#8217;s SOA record was N.</p>
<p>       The -q option sets the query name to name. This useful do distinguish<br />       the name from other arguments.</p>
<p>       Reverse lookups â mapping addresses to names â are simplified by the -x<br />       option.  addr is an IPv4 address in dotted-decimal notation, or a<br />       colon-delimited IPv6 address. When this option is used, there is no<br />       need to provide the name, class and type arguments.  dig automatically<br />       performs a lookup for a name like <a target="_blank" href="http://11.12.13.10.in-addr.arpa/">11.12.13.10.in-addr.arpa</a> and sets the<br />       query type and class to PTR and IN respectively. By default, IPv6<br />       addresses are looked up using nibble format under the <a target="_blank" href="http://ip6.arpa/">IP6.ARPA</a> domain.<br />       To use the older RFC1886 method using the <a target="_blank" href="http://ip6.int/">IP6.INT</a> domain specify the -i<br />       option. Bit string labels (RFC2874) are now experimental and are not<br />       attempted.</p>
<p>       To sign the DNS queries sent by dig and their responses using<br />       transaction signatures (TSIG), specify a TSIG key file using the -k<br />       option. You can also specify the TSIG key itself on the command line<br />       using the -y option; hmac is the type of the TSIG, default HMAC-MD5,<br />       name is the name of the TSIG key and key is the actual key. The key is<br />       a base-64 encoded string, typically generated by dnssec-keygen(8).<br />       Caution should be taken when using the -y option on multi-user systems<br />       as the key can be visible in the output from ps(1) or in the shell&#8217;s<br />       history file. When using TSIG authentication with dig, the name server<br />       that is queried needs to know the key and algorithm that is being used.<br />       In BIND, this is done by providing appropriate key and server<br />       statements in <a>named.conf</a>.</p>
<p>QUERY OPTIONS<br />       dig provides a number of query options which affect the way in which<br />       lookups are made and the results displayed. Some of these set or reset<br />       flag bits in the query header, some determine which sections of the<br />       answer get printed, and others determine the timeout and retry<br />       strategies.</p>
<p>       Each query option is identified by a keyword preceded by a plus sign<br />       (+). Some keywords set or reset an option. These may be preceded by the<br />       string no to negate the meaning of that keyword. Other keywords assign<br />       values to options like the timeout interval. They have the form<br />       +keyword=value. The query options are:</p>
<p>       +[no]tcp<br />           Use [do not use] TCP when querying name servers. The default<br />           behavior is to use UDP unless an AXFR or IXFR query is requested,<br />           in which case a TCP connection is used.</p>
<p>       +[no]vc<br />           Use [do not use] TCP when querying name servers. This alternate<br />           syntax to +[no]tcp is provided for backwards compatibility. The<br />           &#8220;vc&#8221; stands for &#8220;virtual circuit&#8221;.</p>
<p>       +[no]ignore<br />           Ignore truncation in UDP responses instead of retrying with TCP. By<br />           default, TCP retries are performed.</p>
<p>       +domain=somename<br />           Set the search list to contain the single domain somename, as if<br />           specified in a domain directive in /etc/resolv.conf, and enable<br />           search list processing as if the +search option were given.</p>
<p>       +[no]search<br />           Use [do not use] the search list defined by the searchlist or<br />           domain directive in <a>resolv.conf</a> (if any). The search list is not<br />           used by default.</p>
<p>       +[no]showsearch<br />           Perform [do not perform] a search showing intermediate results.</p>
<p>       +[no]defname<br />           Deprecated, treated as a synonym for +[no]search</p>
<p>       +[no]aaonly<br />           Sets the &#8220;aa&#8221; flag in the query.</p>
<p>       +[no]aaflag<br />           A synonym for +[no]aaonly.</p>
<p>       +[no]adflag<br />           Set [do not set] the AD (authentic data) bit in the query. The AD<br />           bit currently has a standard meaning only in responses, not in<br />           queries, but the ability to set the bit in the query is provided<br />           for completeness.</p>
<p>       +[no]cdflag<br />           Set [do not set] the CD (checking disabled) bit in the query. This<br />           requests the server to not perform DNSSEC validation of responses.</p>
<p>       +[no]cl<br />           Display [do not display] the CLASS when printing the record.</p>
<p>       +[no]ttlid<br />           Display [do not display] the TTL when printing the record.</p>
<p>       +[no]recurse<br />           Toggle the setting of the RD (recursion desired) bit in the query.<br />           This bit is set by default, which means dig normally sends<br />           recursive queries. Recursion is automatically disabled when the<br />           +nssearch or +trace query options are used.</p>
<p>       +[no]nssearch<br />           When this option is set, dig attempts to find the authoritative<br />           name servers for the zone containing the name being looked up and<br />           display the SOA record that each name server has for the zone.</p>
<p>       +[no]trace<br />           Toggle tracing of the delegation path from the root name servers<br />           for the name being looked up. Tracing is disabled by default. When<br />           tracing is enabled, dig makes iterative queries to resolve the name<br />           being looked up. It will follow referrals from the root servers,<br />           showing the answer from each server that was used to resolve the<br />           lookup.</p>
<p>       +[no]cmd<br />           Toggles the printing of the initial comment in the output<br />           identifying the version of dig and the query options that have been<br />           applied. This comment is printed by default.</p>
<p>       +[no]short<br />           Provide a terse answer. The default is to print the answer in a<br />           verbose form.</p>
<p>       +[no]identify<br />           Show [or do not show] the IP address and port number that supplied<br />           the answer when the +short option is enabled. If short form answers<br />           are requested, the default is not to show the source address and<br />           port number of the server that provided the answer.</p>
<p>       +[no]comments<br />           Toggle the display of comment lines in the output. The default is<br />           to print comments.</p>
<p>       +[no]stats<br />           This query option toggles the printing of statistics: when the<br />           query was made, the size of the reply and so on. The default<br />           behavior is to print the query statistics.</p>
<p>       +[no]qr<br />           Print [do not print] the query as it is sent. By default, the query<br />           is not printed.</p>
<p>       +[no]question<br />           Print [do not print] the question section of a query when an answer<br />           is returned. The default is to print the question section as a<br />           comment.</p>
<p>       +[no]answer<br />           Display [do not display] the answer section of a reply. The default<br />           is to display it.</p>
<p>       +[no]authority<br />           Display [do not display] the authority section of a reply. The<br />           default is to display it.</p>
<p>       +[no]additional<br />           Display [do not display] the additional section of a reply. The<br />           default is to display it.</p>
<p>       +[no]all<br />           Set or clear all display flags.</p>
<p>       +time=T<br />           Sets the timeout for a query to T seconds. The default timeout is 5<br />           seconds. An attempt to set T to less than 1 will result in a query<br />           timeout of 1 second being applied.</p>
<p>       +tries=T<br />           Sets the number of times to try UDP queries to server to T instead<br />           of the default, 3. If T is less than or equal to zero, the number<br />           of tries is silently rounded up to 1.</p>
<p>       +retry=T<br />           Sets the number of times to retry UDP queries to server to T<br />           instead of the default, 2. Unlike +tries, this does not include the<br />           initial query.</p>
<p>       +ndots=D<br />           Set the number of dots that have to appear in name to D for it to<br />           be considered absolute. The default value is that defined using the<br />           ndots statement in /etc/resolv.conf, or 1 if no ndots statement is<br />           present. Names with fewer dots are interpreted as relative names<br />           and will be searched for in the domains listed in the search or<br />           domain directive in /etc/resolv.conf.</p>
<p>       +bufsize=B<br />           Set the UDP message buffer size advertised using EDNS0 to B bytes.<br />           The maximum and minimum sizes of this buffer are 65535 and 0<br />           respectively. Values outside this range are rounded up or down<br />           appropriately. Values other than zero will cause a EDNS query to be<br />           sent.</p>
<p>       +edns=#<br />           Specify the EDNS version to query with. Valid values are 0 to 255.<br />           Setting the EDNS version will cause a EDNS query to be sent.<br />           +noedns clears the remembered EDNS version.</p>
<p>       +[no]multiline<br />           Print records like the SOA records in a verbose multi-line format<br />           with human-readable comments. The default is to print each record<br />           on a single line, to facilitate machine parsing of the dig output.</p>
<p>       +[no]fail<br />           Do not try the next server if you receive a SERVFAIL. The default<br />           is to not try the next server which is the reverse of normal stub<br />           resolver behavior.</p>
<p>       +[no]besteffort<br />           Attempt to display the contents of messages which are malformed.<br />           The default is to not display malformed answers.</p>
<p>       +[no]dnssec<br />           Requests DNSSEC records be sent by setting the DNSSEC OK bit (DO)<br />           in the OPT record in the additional section of the query.</p>
<p>       +[no]sigchase<br />           Chase DNSSEC signature chains. Requires dig be compiled with<br />           -DDIG_SIGCHASE.</p>
<p>       +trusted-key=####<br />           Specifies a file containing trusted keys to be used with +sigchase.<br />           Each DNSKEY record must be on its own line.</p>
<p>           If not specified dig will look for /etc/trusted-key.key then<br />           <a>trusted-key.key</a> in the current directory.</p>
<p>           Requires dig be compiled with -DDIG_SIGCHASE.</p>
<p>       +[no]topdown<br />           When chasing DNSSEC signature chains perform a top-down validation.<br />           Requires dig be compiled with -DDIG_SIGCHASE.</p>
<p>       +[no]nsid<br />           Include an EDNS name server ID request when sending a query.</p>
<p>MULTIPLE QUERIES<br />       The BIND 9 implementation of dig supports specifying multiple queries<br />       on the command line (in addition to supporting the -f batch file<br />       option). Each of those queries can be supplied with its own set of<br />       flags, options and query options.</p>
<p>       In this case, each query argument represent an individual query in the<br />       command-line syntax described above. Each consists of any of the<br />       standard options and flags, the name to be looked up, an optional query<br />       type and class and any query options that should be applied to that<br />       query.</p>
<p>       A global set of query options, which should be applied to all queries,<br />       can also be supplied. These global query options must precede the first<br />       tuple of name, class, type, options, flags, and query options supplied<br />       on the command line. Any global query options (except the +[no]cmd<br />       option) can be overridden by a query-specific set of query options. For<br />       example:</p>
<p>           dig +qr <a target="_blank" href="http://www.isc.org/">www.isc.org</a> any -x 127.0.0.1 <a target="_blank" href="http://isc.org/">isc.org</a> ns +noqr</p>
<p>       shows how dig could be used from the command line to make three<br />       lookups: an ANY query for <a target="_blank" href="http://www.isc.org/">www.isc.org</a>, a reverse lookup of 127.0.0.1<br />       and a query for the NS records of <a target="_blank" href="http://isc.org/">isc.org</a>. A global query option of +qr<br />       is applied, so that dig shows the initial query it made for each<br />       lookup. The final query has a local query option of +noqr which means<br />       that dig will not print the initial query when it looks up the NS<br />       records for <a target="_blank" href="http://isc.org/">isc.org</a>.</p>
<p>IDN SUPPORT<br />       If dig has been built with IDN (internationalized domain name) support,<br />       it can accept and display non-ASCII domain names.  dig appropriately<br />       converts character encoding of domain name before sending a request to<br />       DNS server or displaying a reply from the server. If you&#8217;d like to turn<br />       off the IDN support for some reason, defines the IDN_DISABLE<br />       environment variable. The IDN support is disabled if the variable is<br />       set when dig runs.</p>
<p>FILES<br />       /etc/resolv.conf</p>
<p>       ${HOME}/.digrc</p>
<p>SEE ALSO<br />       host(1), named(8), dnssec-keygen(8), RFC1035.</p>
<p>BUGS<br />       There are probably too many query options.</p>
<p>COPYRIGHT<br />       Copyright Â© 2004-2008 Internet Systems Consortium, Inc. (&#8220;ISC&#8221;)<br />       Copyright Â© 2000-2003 Internet Software Consortium.</p>
<p>BIND9                            Jun 30, 2000                           DIG(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=4928b0d5-f63c-410d-9b20-47e8fcdf9fdb" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/DIG' rel='tag' target='_self'>DIG</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/dig/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CHROOT</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/chroot/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/chroot/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[CHROOT]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/chroot/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/chroot/" title="CHROOT"></a>CHROOT(1) User Commands CHROOT(1) NAME chroot &#8211; run command or interactive shell with special root directory SYNOPSIS chroot NEWROOT [COMMAND...] chroot OPTION DESCRIPTION Run COMMAND with root directory set to NEWROOT. &#8211;help display this help and exit &#8211;version output version &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/chroot/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/chroot/" title="CHROOT"></a><p>CHROOT(1)                        User Commands                       CHROOT(1)</p>
<p>NAME<br />       chroot &#8211; run command or interactive shell with special root directory</p>
<p>SYNOPSIS<br />       chroot NEWROOT [COMMAND...]<br />       chroot OPTION</p>
<p>DESCRIPTION<br />       Run COMMAND with root directory set to NEWROOT.</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />              output version information and exit</p>
<p>       If no command is given, run &#8220;${SHELL} -i&#8221; (default: /bin/sh).</p>
<p>AUTHOR<br />       Written by Roland McGrath.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-coreutils@gnu.org'); return false;" href="mailto:bug-coreutils@gnu.org">bug-coreutils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright  Â©  2008  Free Software Foundation, Inc.  License GPLv3+: GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This is free software: you are free  to  change  and  redistribute  it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       chroot(2)</p>
<p>       The  full  documentation  for chroot is maintained as a Texinfo manual.<br />       If the info and chroot programs are properly installed  at  your  site,<br />       the command</p>
<p>              info coreutils &#8216;chroot invocation&#8217;</p>
<p>       should give you access to the complete manual.</p>
<p>GNU coreutils 6.12                 May 2008                          CHROOT(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=291adae6-18d9-4a64-a96e-166e187e0e91" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/CHROOT' rel='tag' target='_self'>CHROOT</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/chroot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DIRNAME</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/dirname/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/dirname/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[DIRNAME]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/dirname/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/dirname/" title="DIRNAME"></a>DIRNAME(1) User Commands DIRNAME(1) NAME dirname &#8211; strip non-directory suffix from file name SYNOPSIS dirname NAME dirname OPTION DESCRIPTION Print NAME with its trailing /component removed; if NAME contains no /&#8217;s, output `.&#8217; (meaning the current directory). &#8211;help display this &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/dirname/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/dirname/" title="DIRNAME"></a><p>DIRNAME(1)                       User Commands                      DIRNAME(1)</p>
<p>NAME<br />       dirname &#8211; strip non-directory suffix from file name</p>
<p>SYNOPSIS<br />       dirname NAME<br />       dirname OPTION</p>
<p>DESCRIPTION<br />       Print  NAME  with  its trailing /component removed; if NAME contains no<br />       /&#8217;s, output `.&#8217; (meaning the current directory).</p>
<p>       &#8211;help display this help and exit</p>
<p>       &#8211;version<br />              output version information and exit</p>
<p>EXAMPLES<br />       dirname /usr/bin/sort<br />              Output &#8220;/usr/bin&#8221;.</p>
<p>       dirname stdio.h<br />              Output &#8220;.&#8221;.</p>
<p>AUTHOR<br />       Written by David MacKenzie and Jim Meyering.</p>
<p>REPORTING BUGS<br />       Report bugs to &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=bug-coreutils@gnu.org'); return false;" href="mailto:bug-coreutils@gnu.org">bug-coreutils@gnu.org</a>&gt;.</p>
<p>COPYRIGHT<br />       Copyright Â© 2008 Free Software Foundation, Inc.   License  GPLv3+:  GNU<br />       GPL version 3 or later &lt;<a target="_blank" href="http://gnu.org/licenses/gpl.html">http://gnu.org/licenses/gpl.html</a>&gt;<br />       This  is  free  software:  you  are free to change and redistribute it.<br />       There is NO WARRANTY, to the extent permitted by law.</p>
<p>SEE ALSO<br />       basename(1), readlink(1)</p>
<p>       The full documentation for dirname is maintained as a  Texinfo  manual.<br />       If  the  info and dirname programs are properly installed at your site,<br />       the command</p>
<p>              info coreutils &#8216;dirname invocation&#8217;</p>
<p>       should give you access to the complete manual.</p>
<p>GNU coreutils 6.12                 May 2008                         DIRNAME(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=5a7ef5af-5544-41ab-b120-acca6d44f43f" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/DIRNAME' rel='tag' target='_self'>DIRNAME</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkfs/" title="MKFS">MKFS</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mknod/" title="MKNOD">MKNOD</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/dirname/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HOSTNAME</title>
		<link>http://itechlog.com/linux-man-pages/2009/01/01/hostname/</link>
		<comments>http://itechlog.com/linux-man-pages/2009/01/01/hostname/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 17:20:00 +0000</pubDate>
		<dc:creator>Alex Costa</dc:creator>
				<category><![CDATA[Linux Man Pages]]></category>
		<category><![CDATA[HOSTNAME]]></category>

		<guid isPermaLink="false">http://itechlog.com/linux-man-pages/2009/01/01/hostname/</guid>
		<description><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/hostname/" title="HOSTNAME"></a>HOSTNAME(1) Linux Programmer&#8217;s Manual HOSTNAME(1) NAME hostname &#8211; show or set the system&#8217;s host name domainname &#8211; show or set the system&#8217;s NIS/YP domain name dnsdomainname &#8211; show the system&#8217;s DNS domain name nodename &#8211; show or set the system&#8217;s &#8230;<p class="read-more"><a href="http://itechlog.com/linux-man-pages/2009/01/01/hostname/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://itechlog.com/linux-man-pages/2009/01/01/hostname/" title="HOSTNAME"></a><p>HOSTNAME(1)                Linux Programmer&#8217;s Manual               HOSTNAME(1)</p>
<p>NAME<br />       hostname &#8211; show or set the system&#8217;s host name<br />       domainname &#8211; show or set the system&#8217;s NIS/YP domain name<br />       dnsdomainname &#8211; show the system&#8217;s DNS domain name<br />       nodename &#8211; show or set the system&#8217;s DECnet node name</p>
<p>SYNOPSIS<br />       hostname  [-v] [-a] [--alias] [-d] [--domain] [-f] [--fqdn] [-i] [--ip-<br />       address] [--long] [-s] [--short] [-y] [-n] [--node]</p>
<p>       hostname [-v] [-F filename] [--file filename] [hostname]</p>
<p>       domainname [-v] [-F filename] [--file filename] [name]</p>
<p>       nodename [-v] [-F filename] [--file filename] [name]</p>
<p>       hostname [-v] [-h] [--help] [-V] [--version]</p>
<p>       dnsdomainname [-v]</p>
<p>DESCRIPTION<br />       Hostname is the program that is used to either set or display the  cur-<br />       rent  host, domain or node name of the system.  These names are used by<br />       many of the networking programs to identify  the  machine.  The  domain<br />       name is also used by NIS/YP.</p>
<p>   GET NAME<br />       When  called  without  any  arguments, the program displays the current<br />       names:</p>
<p>       hostname will print the name of the system as returned by the  gethost-<br />       name(2) function.</p>
<p>       nodename  will  print the DECnet node name of the system as returned by<br />       the getnodename(2) function.</p>
<p>       dnsdomainname will print the domain part of the FQDN  (Fully  Qualified<br />       Domain Name). The complete FQDN of the system is returned with hostname<br />       &#8211;fqdn.</p>
<p>       The function gethostname(2) is used to get the hostname.  Only when the<br />       hostname  -s is called will gethostbyname(3) be called.  The difference<br />       in gethostname(2) and gethostbyname(3) is that gethostbyname(3) is net-<br />       work  aware,  so  it  consults /etc/nsswitch.conf and /etc/host.conf to<br />       decide  whether  to  read  information  in  /etc/sysconfig/network   or<br />       /etc/hosts  the  hostname  is  also  set  when the network interface is<br />       brought up.</p>
<p>   SET NAME<br />       When called with one argument or with the &#8211;file option,  the  commands<br />       set the host name, the NIS/YP domain name or the node name.</p>
<p>       Note, that only the super-user can change the names.</p>
<p>       It is not possible to set the FQDN or the DNS domain name with the dns-<br />       domainname command (see THE FQDN below).</p>
<p>       The  host  name  is   usually   set   once   at   system   startup   in<br />       /etc/rc.d/rc.inet1  or  /etc/init.d/boot  (normally by reading the con-<br />       tents of a file which contains the host name, e.g.  /etc/hostname).</p>
<p>   THE FQDN<br />       You can&#8217;t change the FQDN (as returned by hostname &#8211;fqdn) or  the  DNS<br />       domain  name (as returned by dnsdomainname) with this command. The FQDN<br />       of the system is the name that the resolver(3)  returns  for  the  host<br />       name.</p>
<p>       Technically: The FQDN is the name gethostbyname(2) returns for the host<br />       name returned by gethostname(2).  The DNS domain name is the part after<br />       the first dot.</p>
<p>       Therefore  it  depends on the configuration (usually in /etc/host.conf)<br />       how you can change it. Usually (if the hosts file is parsed before  DNS<br />       or NIS) you can change it in /etc/hosts.</p>
<p>OPTIONS<br />       -a, &#8211;alias<br />              Display the alias name of the host (if used).</p>
<p>       -d, &#8211;domain<br />              Display  the  name  of  the  DNS  domain.  Don&#8217;t use the command<br />              domainname to get the DNS domain name because it will  show  the<br />              NIS  domain  name and not the DNS domain name. Use dnsdomainname<br />              instead.</p>
<p>       -F, &#8211;file filename<br />              Read the host name from  the  specified  file.  Comments  (lines<br />              starting with a `#&#8217;) are ignored.</p>
<p>       -f, &#8211;fqdn, &#8211;long<br />              Display  the FQDN (Fully Qualified Domain Name). A FQDN consists<br />              of a short host name and the DNS domain  name.  Unless  you  are<br />              using  bind  or NIS for host lookups you can change the FQDN and<br />              the DNS  domain  name  (which  is  part  of  the  FQDN)  in  the<br />              /etc/hosts file.</p>
<p>       -h, &#8211;help<br />              Print a usage message and exit.</p>
<p>       -i, &#8211;ip-address<br />              Display the IP address(es) of the host.</p>
<p>       -n, &#8211;node<br />              Display the DECnet node name. If a parameter is given (or &#8211;file<br />              name ) the root can also set a new node name.</p>
<p>       -s, &#8211;short<br />              Display the short host name. This is the host name  cut  at  the<br />              first dot.</p>
<p>       -V, &#8211;version<br />              Print  version  information on standard output and exit success-<br />              fully.</p>
<p>       -v, &#8211;verbose<br />              Be verbose and tell what&#8217;s going on.</p>
<p>FILES<br />       /etc/hosts</p>
<p>AUTHOR<br />       Peter Tobias, &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=tobias@et-inf.fho-emden.de'); return false;" href="mailto:tobias@et-inf.fho-emden.de">tobias@et-inf.fho-emden.de</a>&gt;<br />       Bernd Eckenfels, &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=net-tools@lina.inka.de'); return false;" href="mailto:net-tools@lina.inka.de">net-tools@lina.inka.de</a>&gt; (NIS and manpage).<br />       Steve Whitehouse, &lt;<a target="_blank" onclick="top.Popup.composeWindow('pcompose.php?sendto=SteveW@ACM.org'); return false;" href="mailto:SteveW@ACM.org">SteveW@ACM.org</a>&gt; (DECnet support and manpage).</p>
<p>net-tools                         28 Jan 1996                      HOSTNAME(1)</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" src="http://img.zemanta.com/pixy.gif?x-id=580668ee-731d-40d7-aa7e-032e62bb7d44" /></div>

<!-- start wp-tags-to-technorati 1.02 -->

<p class='technorati-tags'>Technorati Tags: <a class='technorati-link' href='http://technorati.com/tag/HOSTNAME' rel='tag' target='_self'>HOSTNAME</a>, <a class='technorati-link' href='http://technorati.com/tag/Linux+Man+Pages' rel='tag' target='_self'>Linux Man Pages</a></p>

<!-- end wp-tags-to-technorati -->
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/hostname-2/" title="HOSTNAME">HOSTNAME</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/hostname-3/" title="HOSTNAME">HOSTNAME</a></li><li>January 4, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/04/sort/" title="SORT">SORT</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/mkdirhier/" title="MKDIRHIER">MKDIRHIER</a></li><li>January 1, 2009 -- <a href="http://itechlog.com/linux-man-pages/2009/01/01/modinfo/" title="MODINFO">MODINFO</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://itechlog.com/linux-man-pages/2009/01/01/hostname/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

