From f2b9224840d245e7049ee14235f456f510017883 Mon Sep 17 00:00:00 2001 From: "mazocomp@125cb8d34e6d7cae380bf8564194dad8935888ba" Date: Mon, 8 Jan 2018 01:47:19 +0000 Subject: [PATCH] Fix UnixBasics --- docs/handbook/UnixBasics/index.mdwn | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/docs/handbook/UnixBasics/index.mdwn b/docs/handbook/UnixBasics/index.mdwn index 8f74bfc3..aff39499 100644 --- a/docs/handbook/UnixBasics/index.mdwn +++ b/docs/handbook/UnixBasics/index.mdwn @@ -41,22 +41,22 @@ DragonFly can be used in various ways. One of them is typing commands to a text If you have not configured DragonFly to automatically start a graphical environment during startup, the system will present you with a login prompt after it boots, right after the startup scripts finish running. You will see something similar to: - Additional ABI support:. + newaliases: no recipients Starting cron. Local package initialization:. Additional TCP options:. - Wed Feb 18 17:53:48 GMT 2009 + Mon Jan 8 03:02:40 EET 2018 - DragonFly/i386 (Amnesiac) (ttyv0) + DragonFly/x86_64 (mazocomp.pc) (ttyv0) login: The messages might be a bit different on your system, but you will see something similar. The last two lines are what we are interested in right now. The second last line reads: - DragonFly/i386 (Amnesiac) (ttyv0) + DragonFly/x86_64 (mazocomp.pc) (ttyv0) -This line contains some bits of information about the system you have just booted. You are looking at a ***DragonFlyBSD*** console, running on an Intel or compatible processor of the x86 architecture. The name of this machine (every UNIX machine has a name) is `Amnesiac`, and you are now looking at its system console--the `ttyv0` terminal. Finally, the last line is always: +This line contains some bits of information about the system you have just booted. You are looking at a ***DragonFlyBSD*** console, running on an AMD or compatible processor of the amd64 (aka x86_64) architecture. The name of this machine (every UNIX machine has a name) is `mazocomp.pc`, and you are now looking at its system console--the `ttyv0` terminal. Finally, the last line is always: login: @@ -249,7 +249,6 @@ A complete description of the file system hierarchy is available in [hier(7)](ht `/etc/` | System configuration files and scripts. `/etc/defaults/` | Default system configuration files; see [rc(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=rc§ion=8). `/etc/mail/` | Configuration files for mail transport agents such as [sendmail(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=sendmail§ion=8). - `/etc/namedb/` | `named` configuration files; see [named(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=named§ion=8). `/etc/periodic/` | Scripts that are run daily, weekly, and monthly, via [cron(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=cron§ion=8); see [periodic(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=periodic§ion=8). `/etc/ppp/` | `ppp` configuration files; see [ppp(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=ppp§ion=8). `/mnt/` | Empty directory commonly used by system administrators as a temporary mount point. @@ -260,6 +259,7 @@ A complete description of the file system hierarchy is available in [hier(7)](ht `/usr/` | The majority of user utilities and applications. `/usr/bin/` | Common utilities, programming tools, and applications. `/usr/dports/` | The dports tree for installing packages (optional). + `/usr/games/` | Useful and semi-frivolous programs. `/usr/include/` | Standard C include files. `/usr/lib/` | Archive libraries. `/usr/libdata/` | Miscellaneous utility data files. @@ -268,7 +268,7 @@ A complete description of the file system hierarchy is available in [hier(7)](ht `/usr/obj/` | Architecture-specific target tree produced by building the `/usr/src` tree. `/usr/sbin/` | System daemons & system utilities (executed by users). `/usr/share/` | Architecture-independent files. - `/usr/src/` | BSD and/or local source files. + `/usr/src/` | BSD, third-party, and/or local source files. `/var/` | Multi-purpose log, temporary, transient, and spool files. A memory-based file system is sometimes mounted at `/var`. This can be automated with an entry in `/etc/fstab`; see [mfs(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=mfs§ion=8). `/var/log/` | Miscellaneous system log files. `/var/mail/` | User mailbox files. @@ -286,9 +286,9 @@ Files are stored in directories. A directory may contain no files, or it may co Files and directories are referenced by giving the file or directory name, followed by a forward slash, `/`, followed by any other directory names that are necessary. If you have directory `foo`, which contains directory `bar`, which contains the file `readme.txt`, then the full name, or ***path*** to the file is `foo/bar/readme.txt`. -You might notice that all directories contain `.` and `..` directories. `.` is that directory itself, for example, `/usr/` is equivalent to `/usr/./` equivalent to `/usr/././` and so on. `..` is the parent directory, for example, `/` is equivalent to `/usr/../` equivalent to `/usr/../usr/..` and so on. So, the path to the file `foo/bar/readme.txt` could be written as `./foo/bar/../bar/./readme.txt`. `/`'s parent directory is `/`, so `/` is equivalent to `/../../../../../../` +You might notice that all directories contain `.` and `..` directories. `.` is that directory itself, for example, `/usr/` is equivalent to `/usr/./` equivalent to `/usr/././` and so on. `..` is the parent directory, for example, `/` is equivalent to `/usr/../` equivalent to `/usr/../usr/..` and so on. So, the path to the file `foo/bar/readme.txt` could be written as `./foo/bar/../bar/./readme.txt`. `/`'s parent directory is `/`, so `/` is equivalent to `/../../../../../../`. -Also there is a shortcut to user's home directory: `~`. So, if your user's home directory is `/home/john`, you may access it as `~`. For example, `/home/john/foo/bar/readme.txt` is equivalent to `~/foo/bar/readme.txt`. +Usually a [shell](#index11h2) has a shortcut to your user's home directory: `~`. If you're logged in as `john` and path to his home directory is `/home/john`, you may simply write `~` instead of that long path (i.e. `~/foo/bar/readme.txt` is equivalent to `/home/john/for/bar/readme.txt`). Directories and files are stored in a file system. Each file system contains exactly one directory at the very top level, called the ***root directory*** for that file system. This root directory can then contain other directories. @@ -740,6 +740,8 @@ The easiest and simplest editor to learn is an editor called **ee** , which sta DragonFly also comes with more powerful text editors such as **vi** as part of the base system, while other editors, like **emacs** and **vim** , are part of the dports tree. These editors offer much more functionality and power at the expense of being a little more complicated to learn. However if you plan on doing a lot of text editing, learning a more powerful editor such as **vim** or **emacs** will save you much more time in the long run. +**Note:** if you're not familiar with **vi** or can't (or don't want to) run **emacs**, you might want to install a small, fast, and portable editor called **mg**. It is compatible with **emacs** because there shouldn't be any reason to learn more editor types than **emacs** or **vi**. If you don't know how to use it, read `/usr/local/share/doc/mg/tutorial` first. + ## Devices and Device Nodes A device is a term used mostly for hardware-related activities in a system, including disks, printers, graphics cards, and keyboards. When DragonFly boots, the majority of what DragonFly displays are devices being detected. You can look through the boot messages again by viewing `/var/run/dmesg.boot`. -- 2.32.0