📄 0119-0121.html
字号:
<HTML>
<HEAD>
<TITLE>Linux Complete Command Reference:User Commands:EarthWeb Inc.-</TITLE>
</HEAD>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>
-->
<!-- ISBN=0672311046 //-->
<!-- TITLE=Linux Complete Command Reference//-->
<!-- AUTHOR=Red Hat//-->
<!-- PUBLISHER=Macmillan Computer Publishing//-->
<!-- IMPRINT=Sams//-->
<!-- CHAPTER=01 //-->
<!-- PAGES=0001-0736 //-->
<!-- UNASSIGNED1 //-->
<!-- UNASSIGNED2 //-->
<P><CENTER>
<a href="0116-0118.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0122-0123.html">Next</A></CENTER></P>
<A NAME="PAGENUM-119"><P>Page 119</P></A>
<P><B>
BUGS
</B></P>
<P>Queries of a class other than IN can have interesting results since ordinarily a nameserver only has a list of root
nameservers for class IN resource records.
</P>
<P>Query uses a call to inet_addr() to determine if the argument for the
-n option is a valid Internet address.
Unfortunately, inet_addr() seems to cause a segmentation fault with some (bad) addresses (for example,
1.2.3.4.5).
</P>
<P><B>
AUTHOR
</B></P>
<P>Bryan Beecher</P>
<P>
10 March 1990
</P>
<H3><A NAME="ch01_ 56">
domainname
</A></H3>
<P>domainname—Set or print domain of current host</P>
<P><B>
SYNOPSIS
</B></P>
<!-- CODE SNIP //-->
<PRE>
domainname [ name ]
</PRE>
<!-- END CODE SNIP //-->
<P><B>
DESCRIPTION
</B></P>
<P>domainname prints the domain name of the current host, from the
getdomainname(3) library call. If an argument is present
and the effective UID is 0, domainname changes the name of the host, with the
setdomainname(2) system call. This is usually done
at boot time in the /etc/rc.local script.
</P>
<P><B>
FILES
</B></P>
<!-- CODE SNIP //-->
<PRE>
/etc/rc.local
</PRE>
<!-- END CODE SNIP //-->
<P><B>
SEE ALSO
</B></P>
<P>
getdomainname(3), setdomainname(2), uname(1), uname(2)
</P>
<P><B>
AUTHOR
</B></P>
<P>Lars Wirzenius by substituting in hostname.c</P>
<P>
Linux 0.98, 26 December 1992
</P>
<H3><A NAME="ch01_ 57">
dsplit
</A></H3>
<P>dsplit—Split a large file into pieces</P>
<P><B>
SYNOPSIS
</B></P<!-- CODE SNIP //-->
<PRE>
dsplit [ _size nnn ][input_file [ output_base ]]
</PRE>
<!-- END CODE SNIP //-->
<P><B>
DESCRIPTION
</B></P>
<P>dsplit splits binary files into smaller chunks
so that they may be placed on floppy disks.
</P>
<B><P>
OPTIONS
</B></P>
<TABLE>
<TR><TD>
_size nnn
</TD><TD>
Specifies the size of each output file, in bytes. The default is
1457000, which is enough to will a 1.44MB floppy disk.
</TD></TR><TR><TD>
input_file
</TD><TD>
Specifies the name of the file to split up. A
_ indicates standard input. The default is
standard input.
</TD></TR></TABLE>
<A NAME="PAGENUM-120"><P>Page 120</P></A>
<TABLE>
<TR><TD>
output_base
</TD><TD>
Specifies the name of the output files to be written.
dsplit will append 000, 001, ..., to the
output_base. The default is dsplit.
</TD></TR></TABLE>
<P><B>
AUTHOR'S NOTES
</B></P>
<BLOCKQUOTE>
Submitted by: David Arnstein<BR>
(arnstein@netcom.com)<BR>
Posting number: Volume 40, Issue 51<BR>
Archive name: dsplit/part01<BR>
Environment: MS-DOS, UNIX<BR>
</BLOCKQUOTE>
<P>Here is a portable binary file splitting program. It reads a binary file and splits it into pieces. I use this program to put
large binary files on floppy disks. For this reason, the default size of the output files is 1,457,000 bytes, which just about fills up
a 1.44MB floppy disk.
</P>
<P>Unlike other binary split programs I have seen,
dsplit does not malloc a huge block of memory.
dsplit is suitable for use under MS-DOS and other primitive operating systems.
</P>
<P>(The program came from gatekeeper.dec.com:/pub/usenet/comp.sources.misc/volume40/dsplit
).
</P>
<P>
Linux 1.1, 5 July 1994
</P>
<H3><A NAME="ch01_ 58">
du
</A></H3>
<P>du—Summarize disk usage</P>
<P><B>
SYNOPSIS
</B></P>
<!-- CODE //-->
<PRE>
du [_abcklsxDLS] [—all] [—total] [—count-links] [—summarize] [—bytes]
[—kilobytes] [—one-file-system] [—separate-dirs] [—dereference]
[—dereference-args] [—help] [—-version] [filename...]
</PRE>
<!-- END CODE //-->
<P><B>
DESCRIPTION
</B></P>
<P>This manual page documents the GNU version of
du. du displays the amount of disk space used by each argument and
for each subdirectory of directory arguments. The space is measured in 1K blocks by default, unless the environment
variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used.
</P>
<P><B>
OPTIONS
</B></P>
<TABLE>
<TR><TD>
_a, —all
</TD><TD>
Display counts for all files, not just directories.
</TD></TR><TR><TD>
_b, —bytes
</TD><TD>
Print sizes in bytes.
</TD></TR><TR><TD>
_c, —total
</TD><TD>
Write a grand total of all of the arguments after all arguments have been processed. This
can be used to find out the disk usage of a directory, with some files excluded.
</TD></TR><TR><TD>
_k, —kilobytes
</TD><TD>
Print sizes in kilobytes. This overrides the environment variable
POSIXLY_CORRECT.
</TD></TR><TR><TD>
_l, —count-links
</TD><TD>
Count the size of all files, even if they have appeared already in another hard link.
</TD></TR><TR><TD>
_s, —summarize
</TD><TD>
Display only a total for each argument.
</TD></TR><TR><TD>
_x, —one-file-system
</TD><TD>
Skip directories that are on different filesystems from the one that the argument
being processed is on.
</TD></TR><TR><TD>
_D, —dereference-args
</TD><TD>
Dereference symbolic links that are command-line arguments. Does not affect
other symbolic links. This is helpful for finding out the disk usage of directories like
/usr/tmp where they are symbolic links.
</TD></TR><TR><TD>
_L, —dereference
</TD><TD>
Dereference symbolic links (show the disk space used by the file or directory that the
link points to instead of the space used by the link).
</TD></TR><TR><TD>
_S, —separate-dirs
</TD><TD>
Count the size of each directory separately, not including the sizes of subdirectories.
</TD></TR><TR><TD>
—help
</TD><TD>
Print a usage message on standard output and exit successfully.
</TD></TR><TR><TD>
—version
</TD><TD>
Print version information on standard output, then exit successfully.
</TD></TR></TABLE>
<A NAME="PAGENUM-121"><P>Page 121</P></A>
<P><B>
BUGS
</B></P>
<P>On BSD systems, du reports sizes that are half the correct values for files that are NFS-mounted from HP-UX systems.
On HP-UX systems, it reports sizes that are twice the correct values for files that are NFS-mounted from BSD systems. This
is due to a flaw in HP-UX; it also affects the HP-UX
du program.
</P>
<P>
GNU File Utilities
</P>
<H3><A NAME="ch01_ 59">
editres
</A></H3>
<P>editres—A dynamic resource editor for X Toolkit applications</P>
<P><B>
SYNTAX
</B></P>
<!-- CODE SNIP //-->
<PRE>
editres [ _toolkitoption ... ]
</PRE>
<!-- END CODE SNIP //-->
<P><B>
OPTIONS
</B></P>
<P>editres accepts all of the standard X Toolkit command-line options (see
X(1)). The order of the command-line options is
not important.
</P>
<P><B>
DESCRIPTION
</B></P>
<P>editres is a tool that allows users and application developers to view the full widget hierarchy of any X Toolkit
application that speaks the editres protocol. In addition,
editres will help the user construct resource specifications, allow the user
to apply the resource to the application and view the results dynamically. Once the user is happy with a resource
specification, editres will append the resource string to the user's X Resources file.
</P>
<P><B>
USING editres
</B></P>
<P>editres provides a window consisting of the following four areas:</P>
<TABLE>
<TR><TD>
Menu Bar
</TD><TD>
A set of pop-up menus that allow you full access to
editres's features.
</TD></TR><TR><TD>
Panner
</TD><TD>
The panner provides a more intuitive way to scroll the application tree display.
</TD></TR><TR><TD>
Message Area
</TD><TD>
Displays information to the user about the action that
editres expects.
</TD></TR><TR><TD>
Application Widget Tree
</TD><TD>
This area is used to display the selected application's widget tree.
</TD></TR></TABLE>
<P>To begin an editres session, select the Get Widget Tree menu item from the Command menu.
This will change the pointer cursor to crosshair. You should now select the application you wish look at by clicking on any of its windows. If
this application understands the editres protocol,
editres will display the application's widget tree in its tree window. If
the application does not understand the editres protocol,
editres will inform you of this fact in the message area after a
few seconds delay.
</P>
<P>After you have a widget tree, you may select any of the other menu options. The effect of each of these is described
in "Commands," next.
</P>
<P><B>
COMMANDS
</B></P>
<TABLE>
<TR><TD>
Get Widget Tree
</TD><TD>
Allows the user to click on any application that speaks the
editres protocol and receive its widget tree.
</TD></TR><TR><TD>
Refresh Current Widget Tree
</TD><TD>
editres only knows about the widgets that exist at the present time. Many
applications create and destroy widgets on the fly. Selecting this menu item will cause
editres to ask the application to resend its widget tree, thus updating its information to the new state of
the application.
</TD></TR><TR><TD>
</TD><TD>
For example, xman only creates the widgets for its topbox when it starts up. None of
the widgets for the manual page window are created until the user actually clicks on the
Manual Page button. If you retrieved xman's widget tree before the manual page is active, you
may wish to refresh the widget tree after the manual page has been displayed. This will allow
you to also edit the manual page's resources.
</TD></TR></TABLE>
<P><CENTER>
<a href="0116-0118.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0122-0123.html">Next</A></CENTER></P>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -