Use correct syntax markup for shell

Approved by:	carlavilla
This commit is contained in:
Li-Wen Hsu 2021-03-14 20:08:55 +08:00
parent 55c95407aa
commit a9a9e66105
No known key found for this signature in database
GPG key ID: 8D7BCC7D012FD37E
666 changed files with 17924 additions and 17924 deletions

View file

@ -33,7 +33,7 @@ Log in (when you see `login:`) as a user you created during installation or as `
To log out (and get a new `login:` prompt) type
[source,bash]
[source,shell]
....
# exit
....
@ -42,21 +42,21 @@ as often as necessary. Yes, press kbd:[enter] after commands, and remember that
To shut down the machine type
[source,bash]
[source,shell]
....
# /sbin/shutdown -h now
....
Or to reboot type
[source,bash]
[source,shell]
....
# /sbin/shutdown -r now
....
or
[source,bash]
[source,shell]
....
# /sbin/reboot
....
@ -68,7 +68,7 @@ You can also reboot with kbd:[Ctrl+Alt+Delete]. Give it a little time to do its
If you did not create any users when you installed the system and are thus logged in as `root`, you should probably create a user now with
[source,bash]
[source,shell]
....
# adduser
....
@ -77,7 +77,7 @@ The first time you use `adduser`, it might ask for some defaults to save. You mi
Suppose you create a user `jack` with full name _Jack Benimble_. Give `jack` a password if security (even kids around who might pound on the keyboard) is an issue. When it asks you if you want to invite `jack` into other groups, type `wheel`
[source,bash]
[source,shell]
....
Login group is "jack". Invite jack into other groups: wheel
....
@ -155,7 +155,7 @@ You might want to try using `whatis` on some common useful commands like `cat`,
Are some of these not working very well? Both man:locate[1] and man:whatis[1] depend on a database that is rebuilt weekly. If your machine is not going to be left on over the weekend (and running FreeBSD), you might want to run the commands for daily, weekly, and monthly maintenance now and then. Run them as `root` and, for now, give each one time to finish before you start the next one.
[source,bash]
[source,shell]
....
# periodic daily
output omitted
@ -176,14 +176,14 @@ To configure your system, you need to edit text files. Most of them will be in t
Before you edit a file, you should probably back it up. Suppose you want to edit [.filename]#/etc/rc.conf#. You could just use `cd /etc` to get to the [.filename]#/etc# directory and do:
[source,bash]
[source,shell]
....
# cp rc.conf rc.conf.orig
....
This would copy [.filename]#rc.conf# to [.filename]#rc.conf.orig#, and you could later copy [.filename]#rc.conf.orig# to [.filename]#rc.conf# to recover the original. But even better would be moving (renaming) and then copying back:
[source,bash]
[source,shell]
....
# mv rc.conf rc.conf.orig
# cp rc.conf.orig rc.conf
@ -191,7 +191,7 @@ This would copy [.filename]#rc.conf# to [.filename]#rc.conf.orig#, and you could
because `mv` preserves the original date and owner of the file. You can now edit [.filename]#rc.conf#. If you want the original back, you would then `mv rc.conf rc.conf.myedit` (assuming you want to preserve your edited version) and then
[source,bash]
[source,shell]
....
# mv rc.conf.orig rc.conf
....
@ -200,7 +200,7 @@ to put things back the way they were.
To edit a file, type
[source,bash]
[source,shell]
....
# vi filename
....
@ -275,7 +275,7 @@ manual page on the UNIX(R) filesystem
Use `find` to locate [.filename]#filename# in [.filename]#/usr# or any of its subdirectories with
[source,bash]
[source,shell]
....
% find /usr -name "filename"
....
@ -293,7 +293,7 @@ If you find the handbook too sophisticated (what with `lndir` and all) on instal
Find the port you want, say `kermit`. There will be a directory for it on the CDROM. Copy the subdirectory to [.filename]#/usr/local# (a good place for software you add that should be available to all users) with:
[source,bash]
[source,shell]
....
# cp -R /cdrom/ports/comm/kermit /usr/local
....
@ -304,7 +304,7 @@ Next, create the directory [.filename]#/usr/ports/distfiles# if it does not alre
Then `cd` to the subdirectory of [.filename]#/usr/local/kermit# that has the file [.filename]#Makefile#. Type
[source,bash]
[source,shell]
....
# make all install
....