LQWiki - User contributions [en]

Dd

2007-06-19T10:08:02Z

HadroLepton: revert

The '''<tt>dd</tt>''' command copies data from one place to another. Sometimes [[cat]] can do the same thing (with [[redirection]]), but dd has options to translate data, selectively copy only part of a data stream, and buffer its reads and writes.

<tt>dd</tt> can [[Making_an_ISO_from_CDROM|copy a CD to an ISO file]], copy one partition to another, or restore an image file to a disk. Using the <tt>seek</tt> and <tt>count</tt> options, an individual sector of a disk can be extracted without having to wait for the entire rest of the disk to be read.

<tt>dd</tt> may also be used to extract data from or insert data into arbitrary positions in a file. This can be useful as a way of working with binary files from the command line.

==Examples==

The main options to be concerned about are if= (input file) and of= (output file). By default, <tt>dd</tt> reads from [[stdin]] and writes to [[stdout]]. Here are some examples of how dd may be used:

===Creating a hard drive backup directly to another hard drive ===

# dd if=/dev/hda of=/dev/sda conv=noerror,sync bs=4k

This command is used often to create a backup of a drive (/dev/hda) directly to another hard drive (/dev/sda). (The device name /dev/hda is typical of an IDE hard drive, the device /dev/sda is typical of a USB disk.) This works only if the hard drive has enough storage to accommodate the source drive's filesystem. The advantage of this is that you do not have to mount the hard drive to make a backup and the only reference to hda is in /dev and in the command which is usually in a script in cron.

The option "bs=4k" is used to specify the block size used in the copy. The default for the dd command is 512 bytes: use of this small block size can result in significantly slower copying. However, the tradeoff with larger block sizes is that when an error is encountered, the remainder of the block is filled with zero-bytes. So if you increase your block size when copying a failing device, you'll lose more data but also spend less time trying to read broken sectors. Tools like [[dd_rescue]] and [[dd_rhelp]] can provide a more flexible solution in such cases, combining the speed of a large block size for the regions without errors with finer-grained block-copies for regions with errors.

===Creating a hard drive backup image===

# dd if=/dev/hda | gzip > /mnt/hdb1/system_drive_backup.img.gz

Here <tt>dd</tt> is making an image of the first harddrive, and piping it through the [[gzip]] compression program. The compressed image is then placed in a file on a seperate drive. To reverse the process:

# gzip -dc /mnt/hdb1/system_drive_backup.img.gz | dd of=/dev/hda

Here, gzip is decompressing (the -d switch) the file, sending the results to stdout (the -c switch), which are piped to dd, and then written to /dev/hda.

===Copy floppy===
# dd if=/dev/fd0 of=/tmp/floppy.img bs=10240

That will copy the contents of the floppy to a file. Then, to put the image onto a new floppy, swap "if" and "of" params.

# dd if=/tmp/floppy.img of=/dev/fd0 bs=10240

===Backing up your Master Boot Record ([[MBR]]).===
You should do this before you edit your partition table so that you can put it back if you mess things up.

# dd if=/dev/hda of=/root/hda.boot.mbr bs=512 count=1

If things mess up, you can boot with [[Knoppix]], mount the partition containing /root (hda1 in this example) and put back the MBR with the command:

# dd if=/mnt/hda1/root/hda.boot.mbr of=/dev/hda bs=512 count=1

Obviously, if you have a [[GPT]] system (like the intel mac for instance) this will need some adjustment.

see: http://forum.onmac.net/showthread.php?t=136

You can backup only the MBR and exclude the partition table with the command:

# dd if=/dev/hda of=/root/hda.mbr.noparttab bs=446 count=1

===Getting around file size limitations using split===
When making images, it's quite easy to run up against various file size limitations. One way to work around a given file size limitation is to use the [[split]] command.

# dd if=/dev/hda1 | gzip -c | split -b 2000m - /mnt/hdc1/backup.img.gz.

# This example is using dd to take an image of the first partition on the first harddrive.
# The results are passed through to [[gzip]] for compression
#* The -c option switch is used to output the result to [[stdout]].
# The compressed image is then piped to the [[split]] tool
#* The -b 2000m switch tells split how big to make the individual files. You can use k and m to tell switch kilobytes and megabytes (this option uses bytes by default).
#* The - option tells split to read from [[stdin]]. Otherwise, split would interpret the /mnt/hdc1... as the file to be split.
#* The /mnt/hdc1... is the prefix for the created files. Split will create files named backup.img.gz.aa, backup.img.gz.ab, etc.

To restore the multi-file backup, do the following:

# cat /mnt/hdc1/backup.img.gz.* | gzip -dc | dd of=/dev/hda1

#Cat recombines contents of the compressed and split image files to [[stdout]], in order.
#Results are piped through gzip for decompression.
#And are then written to the first partition of the hard drive with dd.

===Creating empty disk images===

To create an empty disk image, to be used as the disk for an emulator for example, one can get data from /dev/zero. To create a 10mb image:

$ dd if=/dev/zero of=myimage bs=1024 count=10240

A clever alternative is:

$ dd of=myimage bs=1024 count=0 seek=10240

Here we don't write anything, not even zeroes, we just seek 10mb into the file and close it. The result is a sparse file that is implicitly full of 10mb of zeroes, but that takes no disk space. <tt>[[ls]] -l</tt> will report 10mb, while <tt>[[du]]</tt> and <tt>[[df]]</tt> will report 0. When the file is written to, either as an emulator disk or a loopback device, Linux will allocate disk space for the data. <tt>ls</tt> will still show 10mb, while <tt>du</tt> will gradually approach 10mb.

For swap images, where it's more important to reserve the data than to save disk space, a non-sparse file is better.

==Jargon File Entry==
This is what the [[Jargon File]] has to say about dd:

:''[Unix: from IBM JCL] Equivalent to [[cat]] or BLT. Originally the name of a Unix copy command with special options suitable for [[block device|block-oriented devices]]; it was often used in heavy-handed system maintenance, as in "Let's dd the [[root]] partition onto a tape, then use the boot PROM to load it back on to a new disk". The Unix dd(1)was designed with a weird, distinctly non-Unixy keyword option syntax reminiscent of IBM System/360 JCL (which had an elaborate DD "Dataset Definition" specification for I/O devices); though the command filled a need, the interface design was clearly a prank. The jargon usage is now very rare outside Unix sites and now nearly obsolete even there, as dd(1) has been [[deprecated]] for a long time (though it has no exact replacement). The term has been displaced by BLT or simple English "copy".''

Although deprecated, <tt>dd</tt> is still widely in use on many systems.

==See also==
* [[image]]
* [[Blanking a hard drive]]
* [[rawrite]]
* [[dd_rescue]] recover media with errors on it.
* [[Cloning]]

==External links==
* [http://man.linuxquestions.org/index.php?query=dd&section=0&type=2 dd man page] (''man.linuxquestions.org'')
* [http://www.debianhelp.co.uk/ddcommand.htm Taking Backup With dd Command] (''www.debianhelp.co.uk'')

* [http://www.linuxquestions.org/linux/answers/Applications_GUI_Multimedia/How_To_Do_Eveything_With_DD How To Do Eveything With DD] (''www.linuxquestions.org'')

* [http://www.linuxquestions.org/questions/showthread.php?s=&postid=1848006 LQ Thread] (''www.linuxquestions.org'')
This is the most comprehensive documentation and example sheet for one of the most useful, and least understood linux commands, called "dd". This command has been part of UNIX since the 1970's. It is a bitstream duplicator for copying data, but can use input or output pipes to another command.

:{{Jargon File/Attribution}}

Dos2Unix

2004-11-08T02:15:38Z

HadroLepton: redirect redirect

#REDIRECT [[Unix2dos]]

Unix2dos

2004-11-08T02:14:20Z

HadroLepton: wiki linked line seperator

Unix2dos and its partner, [[Dos2unix]] are two text processor applications which convert [[Line separator|line endings]] of plaintext files.

Unix2dos converts standard UNIX line endings (\n) to DOS/Mac line endings (\n\r). Dos2unix is the reverse of this operation.

These utilities are fairly standard in most GNU-based distributions, but they do not appear to have their own home page.

Dos2unix

2004-11-08T02:11:40Z

HadroLepton: redirect

#REDIRECT [[Unix2dos]]

Dos2Unix

2004-11-08T02:10:38Z

HadroLepton: redirect

#REDIRECT [[Dos2unix]]

Unix2Dos

2004-11-08T02:09:50Z

HadroLepton: redirect

#REDIRECT [[Unix2dos]]

File extension

2004-06-05T23:25:15Z

HadroLepton: wiki linked shebang

A '''file extension''' is a more or less arbitrary component of a filename, used to identify the type. Due to DOS and Windows' widespread and fairly consistent use of them, they have become widely known and there is wide consensus on them, with subtle variations. A failing of file extensions is that any extension can be applied to any file, so the extension is no guarantee of contents. The extension takes the form of a 'dot' and various letters, usually three, appended to the filename. For a list of commonly used file extensions, see [[List of file extensions]].

==DOS==

DOS filenames supported a maximum of eight characters and, optionally, an extension up to three letters separated by a dot. The most familiar example would probably be 'AUTOEXEC.BAT' (DOS was all uppercase.) This extension had the rare feature of being meaningful to the operating system. Since DOS did not have an executable permission bit, this was the how the system knew to execute a non-binary executable. Rename foo.bat to foo.baz and it would not run. Most extensions were made up by the user (MYLETTER.LTR) or generated by the application on a per-application basis (MYDATA.DBF). Since DOS was a command line system, the extension didn't matter for many things but, with text interface shells (file managers), extensions could be 'associated' with applications, such that hitting 'enter' on a .TXT file would open that file in EDIT, for instance.

==Windows==

With the introducton of DOS7/Windows4 (Windows 95) the 8.3 restriction was removed and filenames like 'ReallyLongFilename.html' were possible. If a DOS user downloaded a set of webpages full of links to 'html' pages while his system could only save them as .HTM, the links would be broken. However, as the file format is actually called 'HyperText Markup Language' and HML somehow escaped people, '.html' has become the dominant extension. The same applies to .JPG --> .jpeg, except that .jpg seems to have remained standard.

==Linux==

Given Unix's "Everything Is A File" philosophy, file extensions are a late comer to the Unix/Linux world. Restricting a file to only be used with only a certain program (or type of program), or even suggesting that a file be used with a certain program, would go against that philosophy. However, over time file extensions, or at least file [[naming conventions]], have been introduced without quite elaborating it into a logical, consistent, and useful semi-standard. Examples include:

* Many configuration files such as 'bashrc' end in 'rc' without a dot and many configuration files don't.

* ~ - Not strictly an extension, as it's appended to a file with or without an extension (letter~, letter.txt~) usually indicates a backup file.

* Gcc expects a C source file to end in dot-C (mysource.c).

* The shell has the capacity to execute a shell script whatever its name, due to its executable bit, but some text editors implement syntax highlighting on a simplistic check for a '.sh' extension, rather than looking to the [[shebang]] magic number (the characteristic sequence of #!). So some shell scripts may have the .sh extension and some may not.

* Many non-Microsoft formats such as X pixmaps have long been known by the '.xpm' extension.

Overall, Unix/Linux file extension development has been fairly random.

Since extensions are so useful and indicative, and as Unix/Linux has become increasingly graphically oriented (thus needing to execute applications and load files indirectly), extensions have become more prevalent and naturalized.

==See also==
* [[file prefixes]]

* [[MIME]]

Bash

2004-04-18T22:20:45Z

HadroLepton: added external link: prompt magic

'''bash''' (the '''b'''ourne-'''a'''gain '''sh'''ell) - is the default [[shell]] for Linux users. It is compatible with the traditional Bourne shell ([[sh]]) in that Bourne shell scripts will work in bash, though there are some bash-specific features that will not work on older Bourne shells.

== Shell initialization ==

The place to put [[alias]]es and simple [[environment variable]] settings that you want every time you open a shell is in <tt>.bashrc</tt> in your home directory. Example <tt>.bashrc</tt> file:
if [ -f /etc/bashrc ]; then . /etc/bashrc ; fi # Load system-wide bashrc
export PAGER=less
alias md='mkdir'
alias rd='rmdir'

Appending text to environment variables like your [[PATH]] should not be done in the <tt>.bashrc</tt>, because it gets run often when subshells are started. Place lines like this in your <tt>~/.bash_profile</tt>:
PATH=$HOME/bin:$PATH # Adds to path, only in .bash_profile

When started as a login shell, bash first reads <tt>/etc/profile</tt>, then the first of <tt>~/.bash_profile</tt>, <tt>~/.bash_login</tt>, or <tt>~/.profile</tt> that it finds. It doesn't automatically read the <tt>~/.bashrc</tt> file in login shells. For consistency, the following line shold probably be in your <tt>.bash_profile</tt>:
if [ -f ~/.bashrc ]; then . ~/.bashrc ; fi

== Bash-specific features ==

=== User features ===

* Tab filename completion - Type the beginning of a [[commands|command]], variable, or file, press TAB, and bash will attempt to fill in the rest.

* Typing <Esc>. repeats the last argument of the previous command.

* Typing <Esc><BackSpace> backspaces a whole "word" at a time.

* Readline - a [[GNU]]-created [[library]] for line-by-line text input. It allows a searchable command history and easy editing of the current command line, among other things.

*<ctrl> + <r> invokes reverse-i-search for the [[command buffer]] (history of what you've typed). Then just type a part, any part, not necessarily from the begining, of a command you've typed in before and it'll give you the chronologically closest match

=== Language features ===

* The use of <tt>$( command )</tt> for command substitution (backquotes are traditional)

* Numerical for loops
for (( i=0; i<10; i++ )) ; do echo $i ; done

* Substitution in variable expansions (not [[regex]])
TEXT="I like dogs."
echo ${TEXT/dogs/bats} # Prints: I like bats.

Be sure to check out the [http://www.tldp.org/LDP/abs/html Advanced Bash Scripting Guide], which has (most of) the info you need to start with bash scripting.

=== Custom Prompt ===

The PS1 variable stores the command-line prompt that <tt>bash</tt> prints. For a colorful bash prompt that looks like:
username@hostname/pwd $
use the following:
export PS1='\[\e[32m\]\u@\h/\[\e[1;31m\]\w\[\e[1;34m\]\$\[\e[0m\] '

For one without colors:
username@hostname:pwd$

export PS1='\u@\h:\w\$ ' # Single quotes with single backslashes

Some PS1 options:

*\d Displays the [[date]] in "Weekday Month Date".
*\e [[ASCII]] escape (See the [http://man.linuxquestions.org/index.php?query=console_codes&section=0&type=2 console_codes man page] for what you can do).
*\h Displays the [[hostname]] (up to the first '.').
*\t Displays current time in 24-hour HH:MM:SS format.
*\u Displays the name of your [[user]].
*\w Displays the name of the [[cwd|current directory]].
*\W Displays only the [[basename]] of the current directory.
*\$ Displays '$' if you're not [[root]], '#' if you are.
*\[ and \] Surround non-printing characters

In addition, the PROMPT_COMMAND variable is run every time the shell prompt is printed. Many use this to change the [[xterm]] title bar:

export PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME%%.*}:${PWD/$HOME/~}\007"'

==External links ==

* [http://man.linuxquestions.org/index.php?query=bash&section=0&type=2 bash man page]
* [http://www.linuxcommand.org/ LinuxCommand tutorials]
* [http://www.tldp.org/LDP/abs/html Advanced Bash Scripting Guide]
* [http://www-106.ibm.com/developerworks/linux/library/l-tip-prompt/ Prompt magic]

''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]] !''

Talk:Etc files

2004-04-14T13:58:10Z

HadroLepton: suggestion to reduce ambiguity

shouldn't this page be called 'Etc_files'?

----

Yeah, I think so.

BTW, please sign your name to talks (not to articles) with three/four tildes. :)

[[User:Digiot|Digiot]] 17:21, Mar 16, 2004 (EST)

----

I just reverted the page. I think the overall look and the introductory paragraph was definitely better. And we need to think about linking these things. Including slashes in link names kinda gunks up the works but *not* doing will lead to ambiguity, like with 'hosts', I'd imagine. And how would subdirectories be treated? In a way, it seems better not to link the files, themselves, but provide side links to relevant commands. Like

<nowiki>lilo.conf (See [[LILO]])</nowiki>

Thoughts, ideas, opinions, wild flights of fancy?

[[User:Digiot|Digiot]] 17:31, Mar 16, 2004 (EST)

----

how about '''file:hosts''' as page name. like this [[file:hosts|/etc/hosts]]. that would keep the files in the etc folder separate from the more general topics with same name.

i think a dedicated page for each of the files is warranted. because it is often required to edit these files by hand and then it would be nice if there is a reference for the syntax and keywords required for the file.

[[User:HadroLepton|HadroLepton]] 09:58, Apr 14, 2004 (EDT)

Line separator

2004-04-13T21:03:48Z

HadroLepton: made some corrections, added mac carriage return

Linux, like Unix, uses a single line feed character (LF, \n, [[ASCII]] 0x0A) to indicate End of Line.

[[DOS]] and [[Windows]] uses a carriage return followed by a line feed (CRLF, \r\n, 0x0D 0x0A), which is generally accepted as the standard (with no lobbying on Microsoft's part).

[[Mac]] uses only a carriage return (CR, \r, 0x0D) for an end of line.

Conversion between the different formats are handled transparently in most editors, and can be done manually using the [[Unix2Dos]] and [[Dos2Unix]] utilities.

Technically, carriage return is an [[ASCII]] code to make the carriage (a [[dot-matrix]] printer's head) return to the beginning of the line, while line feed tells it to scroll one step down to the next line.

User:HadroLepton

2004-04-11T01:07:34Z

HadroLepton: me the linux n00b

i am still linux n00b but i am learning

Shadow file

2004-04-08T23:50:58Z

HadroLepton: redirect to shadow

#REDIRECT [[Shadow]]

Shadow

2004-04-08T23:49:58Z

HadroLepton: ported from shadow file

The '''shadow''' file (/etc/shadow) stores passwords and expiry dates in encrypted form in a colon-delimited text file akin to /etc/passwd - which formerly held unencrypted passwords and now contains all kinds of information about users ''except'' the password.

== Tips ==
This should '''not''' be readable by a regular user. If a user can see this file, they can copy your password hashes, and attempt a [[brute force crack]]. Permissions should be something like:

-rw-r----- 1 root shadow size date /etc/shadow

or

-rw------- 1 root root size date /etc/shadow

==See also==
* [[Security]]
* [[User Commands]]

''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]]!''

Etc files

2004-04-08T23:49:05Z

HadroLepton: added shadow, minor restructuring

The <tt>/etc</tt> directory is the location on a UNIX system where system-wide configuration files and scripts are stored. Some common files in the <tt>/etc</tt> directory are:

==/etc==

; [[fstab|/etc/fstab]] : Contains filesystem configuration information.

; [[hosts|/etc/hosts]] : Configures names and aliases of IP-addresses. Fields should be separated with Tab or white space. The functionality of this file has been almost entirely replaced by the [[DNS]] protocol so a hosts file is rarely used.

; [[inittab|/etc/inittab]] : Controls process dispatching. Basically ''the'' key system initialization file, since it's used by process 1, init.

; [[lilo.conf|/etc/lilo.conf]] : Is the configuration file used by the Linux Loader while booting.

; [[modules.conf|/etc/modules.conf]] : Loads modules specific options at startup.

; [[nologin|/etc/nologin]] : Is a text file that, if it exists in /etc/, will prevent non-root users from logging in. If a user attempts to login, it will be shown the contents of the file, and then be disconnected.

; [[nsswitch.conf|/etc/nsswitch.conf]] : Specifies how the lookup for different databases are performed and in what order. Lookups are done left to right.

; [[printcap|/etc/printcap]] : Describes printers and allows dynamic addition and deletion of printers by the spooling system.

; [[resolv.conf|/etc/resolv.conf]] : Configures DNS name servers to use for hostname lookups.

; [[xinetd.conf|/etc/xinetd.conf]] : Contains the configuration for the extended internet services started by the xinetd command.

; [[shadow|/etc/shadow]] : stores passwords and expiry dates in encrypted form.

==/etc/sysconfig==

; /etc/sysconfig/network : Configures the system's network. Specifies hostname and gateway.

''Descriptions of all of these files are in Chapter 9 of the Universal Command Guide for Operating Systems but are not found in all [[Distributions|distributions]].''

Talk:Shebang

2004-04-06T02:21:19Z

HadroLepton: what is shebang?

the page is titled shebang but the text doesn't really explain what a shebang is. i asume the whole #!... thing is the shebang, true? [[User:HadroLepton|HadroLepton]] 22:21, Apr 5, 2004 (EDT)

Ext2

2004-04-05T09:41:13Z

HadroLepton: minor restructuring

'''Ext2''', also called '''ext2fs''', standing for '''Second Extended Filesystem''', is a [[filesystem]] widely used as a default option by many Linux distributions. It provides standard Unix file semantics such as [[File permissions|file permissions]] and [[symbolic link|symbolic links]].

'''[[Ext3]]''' is an enhancement to the ext2 filesystem that adds [[journalling]] support to avoid having to perform a filesystem check after a power failure or system crash.

=Details=
*Max filename length is 255 characters. Extendable to 1012 if needed.
*Percentage of disk reserved for root to prevent users filling drive.
*Large partition support.
*Filesystem checks can be forced by administrator on boot, plus after a set number of boots.
*Advanced disk check monitoring so known when there may be problems with disk.

=Pros=

=Cons=

Mount

2004-04-02T11:34:53Z

HadroLepton: made some terms to wiki links

mount - Attach a volume to the filesystem

You can call mount directly from the command line, using the following general syntax:

mount [options] [device] [dir]

For example, you might use this command to mount a CD-ROM disc:

mount -t iso9660 /dev/cdrom /mnt/cdrom

The -t iso9660 option tells the system that you are mounting an iso9660 format CD-ROM. Type man fs in a shell for more information on the various [[filesystem|filesystems]].

During the installation process, most linux distributions create a file called [[fstab|/etc/fstab]]. This file contains mount settings for the [[volume|volumes]] installed in your system. This can make mounting drives easier. For example, you could add a line in your /etc/fstab file for your cdrom drive:

/dev/cdrom /cdrom iso9660 ro,user,noauto 0 0

Then, when you want to mount a new CD, you would just type mount cdrom.

By default, many linux distributions will require you to [[go root]] to mount and unmount volumes.

For more information on the mount command, type man mount at any shell prompt.

=== Mounting an ISO image ===

Sometimes it is useful to mount an ISO image that you made or have downloaded to be able to access or check the contents. This is possible with the following invocation:

mount -t iso9660 -o ro,loop=/dev/loop0 NameOfISOFile MountPoint

The MountPoint has to be a directory, as described above. You can also [[Making_an_ISO_from_CDROM|make an ISO of an existing CDROM]].

Etc files

2004-03-30T20:49:38Z

HadroLepton: made filenames to wiki links

The <tt>/etc</tt> directory is the location on a UNIX system where system-wide configuration files and scripts are stored. Some common files in the <tt>/etc</tt> directory are:

; [[fstab|/etc/fstab]] : Contains filesystem configuration information.

; [[hosts|/etc/hosts]] : Configures names and aliases of IP-addresses. Fields should be separated with Tab or white space.

; [[inittab|/etc/inittab]] : Controls process dispatching. Basically ''the'' key system initialization file, since it's used by process 1, init.

; [[lilo.conf|/etc/lilo.conf]] : Is the configuration file used by the Linux Loader while booting.

; [[modules.conf|/etc/modules.conf]] : Loads modules specific options at startup.

; [[nologin|/etc/nologin]] : Is a text file that, if it exists in /etc/, will prevent non-root users from logging in. If a user attempts to login, it will be shown the contents of the file, and then be disconnected.

; [[nsswitch.conf|/etc/nsswitch.conf]] : Specifies how the lookup for different databases are performed and in what order. Lookups are done left to right.

; [[printcap|/etc/printcap]] : Describes printers and allows dynamic addition and deletion of printers by the spooling system.

; [[resolv.conf|/etc/resolv.conf]] : Configures DNS name servers to use for hostname lookups.

; /etc/sysconfig/network : Configures the system's network. Specifies hostname and gateway.

; [[xinetd.conf|/etc/xinetd.conf]] : Contains the configuration for the extended internet services started by the xinetd command.

''Descriptions of all of these files are in Chapter 9 of the Universal Command Guide for Operating Systems but are not found in all [[Distributions|distributions]].''

Cfdisk

2004-03-30T19:16:01Z

HadroLepton: made CLI to wiki link

'''cfdisk''' is an [[ncurses]]-based disk partitioning tool similar to the [[CLI]] [[fdisk]] program. It offers a slightly more user-friendly interface than the former. Actions are perfomed by arrowing through menu options rather than typing command letters at a prompt.