From dd63eee42f6630f5de95b0e68a19dc9e94fe42c6 Mon Sep 17 00:00:00 2001 From: Dru Lavigne Date: Wed, 14 May 2014 15:19:14 +0000 Subject: More rewording around "you" usage. Remove question about shosts. Sponsored by: iXsystems --- en_US.ISO8859-1/books/faq/book.xml | 403 ++++++++++++++----------------------- 1 file changed, 147 insertions(+), 256 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index f9831ea55d..fce829e4f2 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -933,13 +933,12 @@ If the file is compressed, tar will automatically - detect the appropriate format and decompress it correctly. - You will be left with a collection of + detect the appropriate format and decompress it correctly, + resulting in a collection of .html files. The main one is called index.html, which will contain the table of contents, introductory material, and links to the - other parts of the document. You can then copy or move - these to their final location as necessary. + other parts of the document. @@ -950,7 +949,7 @@ - You can find full information in the Refer to the Handbook entry on mailing-lists and the Handbook @@ -986,7 +985,7 @@ questions. Other users can help with the basics, referring to the Handbook whenever possible and providing links for learning more about - the topic you need help with. This is primarily an + a particular topic. This is primarily an English speaking channel, though it does have users from all over the world. Non-native English speakers should try to ask the question in @@ -1208,18 +1207,18 @@ - Using the DOS copy command (or - equivalent GUI tool) to transfer the boot image to + Using the DOS copy command or + equivalent GUI tool to transfer the boot image to floppy. Programs like copy will not work as the boot image has been created to be booted into directly. The image has the complete content of the floppy, track for track, and is not meant to be - placed on the floppy as a regular file. You have to - transfer it to the floppy raw, using - the low-level tools (e.g., fdimage - or rawrite) described in the raw, using + fdimage + or rawrite as described in the installation guide to &os;. @@ -2195,7 +2194,7 @@ to /etc/mail/sendmail.cf. - After logging on to the remote machine, set your + After logging on to the remote machine, set the TERM shell variable to ansi or sco if the remote machine knows about these terminal @@ -2321,7 +2320,7 @@ to /etc/mail/sendmail.cf. - Your computer has two or more clocks, and &os; has + The computer has two or more clocks, and &os; has chosen to use the wrong one. Run &man.dmesg.8;, and check for lines that contain @@ -2334,7 +2333,7 @@ Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Timecounter "TSC" frequency 2998570050 Hz quality 800 Timecounters tick every 1.000 msec - You can confirm this by checking the + Confirm this by checking the kern.timecounter.hardware &man.sysctl.3;. @@ -2361,7 +2360,7 @@ kern.timecounter.hardware: ACPI-fast &prompt.root; sysctl kern.timecounter.hardware=i8254 kern.timecounter.hardware: TSC -> i8254 - Your computer should now start keeping more accurate + The computer should now start keeping more accurate time. To have this change automatically run at boot time, @@ -2624,8 +2623,8 @@ kern.timecounter.hardware: TSC -> i8254 &os; does not include a port upgrading tool, but it does have some tools to make the upgrade process somewhat - easier. You can also install additional tools to simplify - port handling, see the Upgrading Ports section in the &os; Handbook. @@ -2698,7 +2697,7 @@ kern.timecounter.hardware: TSC -> i8254 shells have. That is why other more featureful shells like bash, scsh, &man.tcsh.1;, and zsh are available. - You can compare the memory utilization of + Compare the memory utilization of these shells by looking at the VSZ and RSS columns in a ps -u listing. @@ -3059,9 +3058,8 @@ kern.sched.name: ULE &prompt.root; cd /mnt &prompt.root; dump 0af - / | restore rf - - You might prefer &man.cpio.1;, &man.pax.1;, - &man.tar.1; to &man.dump.8; for user data. At the time of - this writing, these are known to lose file flag + The &man.cpio.1; and &man.pax.1; utilities are also available + for moving user data. These are known to lose file flag information, so use them with caution. @@ -3232,26 +3230,28 @@ kern.sched.name: ULE - How do I boot &os; and &linux; using GRUB? + How do I boot &os; and &linux; using + GRUB? - Booting &os; using GRUB is very simple. Just add the - following to your configuration file - /boot/grub/menu.lst (or - /boot/grub/grub.conf in some systems, - e.g., Red Hat Linux and its derivatives). + To boot &os; using GRUB, add the + following to either + /boot/grub/menu.lst or + /boot/grub/grub.conf, depending upon + which is used by the &linux; distribution. - title &os; 6.1 + title &os; 9.1 root (hd0,a) kernel /boot/loader - Where hd0,a points to your - root partition on the first disk. If you need to specify - which slice number should be used, use something like this + Where hd0,a points to the + root partition on the first disk. To specify + the slice number, use something like this (hd0,2,a). By default, if the - slice number is omitted, GRUB searches the first slice - which has a partition. + slice number is omitted, GRUB + searches the first slice + which has the a partition. @@ -3267,11 +3267,9 @@ kern.sched.name: ULE then boot LILO from BootEasy. - If you are running &windows; and &linux; this is - recommended anyway, to make it simpler to get &linux; - booting again if you should need to reinstall &windows; - (which is a Jealous Operating System, and will bear no - other Operating Systems in the Master Boot Record). + This is recommended when running &windows; and &linux; as it + makes it simpler to get &linux; + booting again if &windows; is reinstalled. @@ -3283,29 +3281,29 @@ kern.sched.name: ULE - You can not do that with the standard boot manager + This can not be accomplished with the standard boot manager without rewriting it. There are a number of other boot - managers in the sysutils ports - category that provide this functionality. + managers in the sysutils category of the Ports + Collection. - I have a new removable drive, how do I use it? + How do I use a new removable drive? - If the drive already has a file system on it, you can + If the drive already has a file system on it, use a command like this: &prompt.root; mount -t msdosfs /dev/da0s1 /mnt - If the drive will only be used with &os; systems it is - better idea to stick a BSD file system on it, like UFS or - ZFS. You will get long filename support, at least a 2X - improvement in performance, and a lot more stability. If - the drive will be used by other operating systems a more + If the drive will only be used with &os; systems, + partition it with UFS or + ZFS. This will provide long filename support, + improvement in performance, and stability. If + the drive will be used by other operating systems, a more portable choice, such as msdosfs, is better. &prompt.root; dd if=/dev/zero of=/dev/da0 count=2 @@ -3332,15 +3330,13 @@ kern.sched.name: ULE Why do I get Incorrect super - block when mounting a CD-ROM? + block when mounting a CD? - You have to tell &man.mount.8; the type of the device - that you want to mount. This is described in the Handbook - section on optical media, specifically the - section The type of device + to mount must be specified. This is described in the Handbook + section on Using Data CDs. @@ -3349,12 +3345,12 @@ kern.sched.name: ULE Why do I get Device not - configured when mounting a CD-ROM? + configured when mounting a CD? - This generally means that there is no CD-ROM in the - CD-ROM drive, or the drive is not visible on the bus. + This generally means that there is no CD in the + drive, or the drive is not visible on the bus. Refer to the Using Data CDs section of the Handbook for a detailed @@ -3369,12 +3365,9 @@ kern.sched.name: ULE - Your CD-ROM probably uses the Joliet + The CD probably uses the Joliet extension for storing information about files and - directories. This is discussed in the Handbook chapter on - creating - and using CD-ROMs, specifically the section on + directories. This is discussed in the Handbook section on Using Data CD-ROMs. @@ -3383,17 +3376,14 @@ kern.sched.name: ULE - I burned a CD under &os; and now I can not read it + A CD burned under &os; can not be read under any other operating system. Why? - You most likely burned a raw file to your CD, rather + This means a raw file was burned to the CD, rather than creating an ISO 9660 file system. Take a look - at the Handbook - chapter on creating CD-ROMs, particularly the - section on Using Data CDs. @@ -3422,13 +3412,13 @@ kern.sched.name: ULE - If you try to mount an audio CD, you will get an error + Trying to mount an audio CD will produce an error like cd9660: /dev/acd0c: Invalid argument. This is because mount only works on file systems. Audio CDs do not have file systems; they just have data. - You need a program that reads audio CDs, such as the - audio/xmcd port. + Instead, use a program that reads audio CDs, such as the + audio/xmcd package or port. @@ -3440,8 +3430,8 @@ kern.sched.name: ULE By default, &man.mount.8; will attempt to mount the - last data track (session) of a CD. If you would like to - load an earlier session, you must use the + last data track (session) of a CD. To + load an earlier session, use the command line argument. Refer to &man.mount.cd9660.8; for specific examples. @@ -3495,7 +3485,7 @@ kern.sched.name: ULE The device name used in the previous examples must - be changed according to your configuration. + be changed according to the configuration. @@ -3508,8 +3498,7 @@ kern.sched.name: ULE - You need to understand what du and - df really do. du + This is due to how these commands actually work. du goes through the directory tree, measures how large each file is, and presents the totals. df just asks the file system how much space it has left. @@ -3517,26 +3506,23 @@ kern.sched.name: ULE directory entry will affect df but not du. - When a program is using a file, and you delete the - file, the file is not really removed from the file system + When a program is using a file, and the file is deleted, + the file is not really removed from the file system until the program stops using it. The file is immediately - deleted from the directory listing, however. You can see - this easily enough with a program such as - more. Assume you have a file large + deleted from the directory listing, however. As an example, + consider a file that is large enough that its presence affects the output of - du and df. (Since - disks can be so large today, this might be a - very large file!) If you delete this - file while using more on it, + du and df. If this file is deleted + while using more on it, more does not immediately choke and complain that it cannot view the file. The entry is removed from the directory so no other program or - user can access it. du shows that it - is gone — it has walked the directory tree and the + user can access it. However, du shows that it + is gone as it has walked the directory tree and the file is not listed. df shows that it is still there, as the file system knows that more is still using that space. Once - you end the more session, + the more session ends, du and df will agree. @@ -3550,8 +3536,8 @@ kern.sched.name: ULE this from happening, set up &man.newsyslog.8;. Note that Soft Updates can delay the freeing of disk - space; you might need to wait up to 30 seconds for the - change to be visible! + space and it can take up to 30 seconds for the + change to be visible. @@ -3561,12 +3547,9 @@ kern.sched.name: ULE - In the Configuration - and Tuning section of the Handbook, you will find - a section - describing how to do this. + This sectionof the Handbook + describes how to do this. @@ -3602,7 +3585,7 @@ kern.sched.name: ULE root user. &man.df.1; does not count that space when calculating the Capacity column, so it can exceed 100%. - Also, you will notice that the Blocks + Notice that the Blocks column is always greater than the sum of the Used and Avail columns, usually by a factor of 8%. @@ -3677,7 +3660,7 @@ kern.sched.name: ULE By default, ZFS stores the ZIL in the pool with all - the data. If your application has a heavy write load, + the data. If an application has a heavy write load, storing the ZIL in a separate device that has very fast synchronous, sequential write performance can improve overall system. For other workloads, a SSD is unlikely @@ -3741,7 +3724,7 @@ kern.sched.name: ULE This could happen because the pool is 100% full. ZFS requires space on the disk to write transaction metadata. To restore the pool to a usable state, - truncate a file you want to delete. + truncate the file to delete: &prompt.user; truncate -s 0 unimportant-file @@ -3798,19 +3781,18 @@ kern.sched.name: ULE The primary configuration file is - /etc/defaults/rc.conf (see - &man.rc.conf.5;). System startup scripts such as + /etc/defaults/rc.conf which is described in + &man.rc.conf.5;. System startup scripts such as /etc/rc and - /etc/rc.d (see &man.rc.8;) just + /etc/rc.d, which are described in &man.rc.8;, include this file. Do not edit this - file! Instead, if there is any entry in - /etc/defaults/rc.conf that you want - to change, you should copy the line into + file! Instead, to edit an entry in + /etc/defaults/rc.conf, copy the line into /etc/rc.conf and change it there. - For example, if you wish to start &man.named.8;, the - included DNS server, all you need to do is: + For example, if to start &man.named.8;, the + included DNS server: &prompt.root; echo 'named_enable="YES"' >> /etc/rc.conf @@ -3843,46 +3825,18 @@ kern.sched.name: ULE - This is normally caused by editing the system crontab - (/etc/crontab) and then using - &man.crontab.1; to install it: - - &prompt.root; crontab /etc/crontab - - This is not the correct way to do things. The system - crontab has a different format to the per-user crontabs - which &man.crontab.1; updates (the &man.crontab.5; manual - page explains the differences in more detail). + This is normally caused by editing the system crontab. + This is not the correct way to do things as the system + crontab has a different format to the per-user crontabs. + The system + crontab has an extra field, specifying which user to run + the command as. &man.cron.8; assumes this user is the + first word of the command to execute. Since no such + command exists, this error message is displayed. - If this is what you did, the extra crontab is a - copy of /etc/crontab in the wrong - format it. Delete it with the command: + To delete the extra, incorrect crontab: &prompt.root; crontab -r - - Next time, when you edit - /etc/crontab, you should not do - anything to inform &man.cron.8; of the changes, since it - will notice them automatically. - - If you want something to be run once per day, week, or - month, it is probably better to add shell scripts - /usr/local/etc/periodic, and let the - &man.periodic.8; command run from the system - cron schedule it with the other - periodic system tasks. - - The actual reason for the error is that the system - crontab has an extra field, specifying which user to run - the command as. In the default system crontab provided - with &os;, this is root for all entries. - When this crontab is used as the root user's crontab (which - is not the same as the system - crontab), &man.cron.8; assumes the string - root is the first word of the command - to execute, but no such command exists. @@ -3895,18 +3849,14 @@ kern.sched.name: ULE - This is a security feature. To su - to root (or any - other account with superuser privileges), you must be in + This is a security feature. In order to su + to root, or any + other account with superuser privileges, the user account must be a member of the wheel group. If this feature were not there, anybody with an account on a system who also found out root's password would be - able to gain superuser level access to the system. With - this feature, this is not strictly true; &man.su.1; will - prevent them from even trying to enter the password if - they are not in wheel. + able to gain superuser level access to the system. To allow someone to su to root, put @@ -3937,23 +3887,23 @@ kern.sched.name: ULE -urw / to re-mount the root file system in read/write mode. You may also need to run mount -a -t ufs to mount the file system where your - favorite editor is defined. If your favorite editor is on - a network file system, you will need to either configure - the network manually before you can mount network file + favorite editor is defined. If that editor is on + a network file system, either configure + the network manually before you mounting the network file systems, or use an editor which resides on a local file system, such as &man.ed.1;. - If you intend to use a full screen editor such as - &man.vi.1; or &man.emacs.1;, you may also need to run + In order to use a full screen editor such as + &man.vi.1; or &man.emacs.1;, run export TERM=xterm on &os; 9.0+, or export TERM=cons25 on &os; 8.X so that these editors can load the correct data from the &man.termcap.5; database. - Once you have performed these steps, you can edit - /etc/rc.conf as you usually would to + After performing these steps, edit + /etc/rc.conf to fix the syntax error. The error message displayed - immediately after the kernel boot messages should tell you + immediately after the kernel boot messages should indicate the number of the line in the file which is at fault. @@ -3967,16 +3917,7 @@ kern.sched.name: ULE See the Handbook - entry on printing. It should cover most of your - problem. - - Some printers require a host-based driver to do any - kind of printing. These so-called - WinPrinters are not natively supported by - &os;. If your printer does not work in DOS or &windows;, - it is probably a WinPrinter. Your only hope of getting - one of these to work is to check if the - print/pnm2ppa port supports it. + entry on printing for troubleshooting tips. @@ -4003,10 +3944,10 @@ kern.sched.name: ULE - It is possible that your kernel is not configured - to use quotas. If this is the case, you will need to - add the following line to your kernel configuration - file and recompile: + It is possible that the kernel is not configured + to use quotas. In this case, + add the following line to the kernel configuration + file and recompile the kernel: options QUOTA @@ -4074,13 +4015,13 @@ kern.sched.name: ULE sysvsem.ko and sysvmsg.ko kernel modules, or enabled in the custom kernel by adding the following lines - to your kernel config: + to the kernel configuration file: options SYSVSHM # enable shared memory options SYSVSEM # enable for semaphores options SYSVMSG # enable for messaging - Recompile and install your kernel. + Recompile and install the kernel. @@ -4094,25 +4035,13 @@ options SYSVMSG # enable for messaging The sendmail server is the default mail-server software for &os;, but - you can easily replace it with one of the other MTA (for - instance, an MTA installed from the ports). - - There are various alternative MTAs in the ports tree - already, with mail/exim, - mail/postfix, - mail/qmail, and - mail/zmailer being some of the most - popular choices. - - Diversity is nice, and the fact that you have many - different mail-servers to chose from is considered a good - thing; therefore try to avoid asking questions like - Is sendmail better than - qmail? in the mailing - lists. If you do feel like asking, first check the - mailing list archives. The advantages and disadvantages - of each and every one of the available MTAs have already - been discussed a few times. + it can be replaced with another + MTA installed from the Ports Collection. Available ports + include mail/exim, + mail/postfix, and + mail/qmail. Search the mailing lists + for discussions regarding the advantages and disadvantages + of the available MTAs. @@ -4128,9 +4057,9 @@ options SYSVMSG # enable for messaging boot -s at the Boot: prompt to enter single-user mode. At the question about the shell to use, hit - Enter. You will be dropped to a + Enter which will display a &prompt.root; prompt. Enter mount - -urw / to remount your root file system + -urw / to remount the root file system read/write, then run mount -a to remount all the file systems. Run passwd root to change the class="username">root password when entering the single-user mode, it means that the console has been marked as insecure in - /etc/ttys. In this case it will be + /etc/ttys. In this case, it will be required to boot from a &os; installation disk, choose the Live CD or Shell at the beginning of the install process and issue the commands mentioned above. - You will need to mount the specific partition in this + Mount the specific partition in this case and then chroot to it. For example, replace mount -urw / with mount /dev/ada0p1 /mnt; chroot /mnt for a system on @@ -4155,11 +4084,10 @@ options SYSVMSG # enable for messaging - If you cannot mount your root partition from + If the root partition can not be mounted from single-user mode, it is possible that the partitions are encrypted and it is impossible to mount them without the - access keys. Your chances depend on the chosen - implementation. For more information see the section + access keys. For more information see the section about encrypted disks in the &os; Handbook. @@ -4174,8 +4102,8 @@ options SYSVMSG # enable for messaging - If you are using &man.syscons.4; (the default console - driver) build and install a new kernel with the line in + When using &man.syscons.4;, the default console + driver, build and install a new kernel with this line in the configuration file: options SC_DISABLE_REBOOT @@ -4188,9 +4116,8 @@ options SYSVMSG # enable for messaging The above two methods are exclusive: The - &man.sysctl.8; does not exist if you compile your kernel - with the SC_DISABLE_REBOOT - option. + &man.sysctl.8; does not exist if the kernel is compiled + with SC_DISABLE_REBOOT. @@ -4211,8 +4138,7 @@ options SYSVMSG # enable for messaging with the original file stored with a .bak extension. - Alternatively you can use the &man.tr.1; - command: + Alternatively, use &man.tr.1;: &prompt.user; tr -d '\r' < dos-text-file > unix-file @@ -4319,17 +4245,17 @@ options SYSVMSG # enable for messaging - Short answer: You are probably at security level + Short answer: the security level is greater than 0. Reboot directly to single-user mode to install the kernel. Long answer: &os; disallows changing system flags at - security levels greater than 0. You can check your - security level with the command: + security levels greater than 0. To check the current + security level: &prompt.root; sysctl kern.securelevel - You cannot lower the security level; you have to boot + The security level can not be lowered in multi-user mode, so boot to single-user mode to install the kernel, or change the security level in /etc/rc.conf then reboot. See the &man.init.8; manual page for details on @@ -4347,19 +4273,19 @@ options SYSVMSG # enable for messaging - Short answer: You are probably at security level + Short answer: the system is at a security level greater than 1. Reboot directly to single-user mode to change the date. Long answer: &os; disallows changing the time by more - that one second at security levels greater than 1. You - can check your security level with the command: + that one second at security levels greater than 1. To + check the security level: &prompt.root; sysctl kern.securelevel - You cannot lower the security level; you have to boot - to single-user mode to change the date, or change the - security level in /etc/rc.conf then + The security level can not be lowered in multi-user mode. Either boot + to single-user mode to change the date or change the + security level in /etc/rc.conf and reboot. See the &man.init.8; manual page for details on securelevel, and see /etc/defaults/rc.conf and the @@ -4400,7 +4326,7 @@ options SYSVMSG # enable for messaging - You are running a securelevel greater than 0. + The system is running a securelevel greater than 0. Lower the securelevel and try again. For more information, see the FAQ entry on securelevel and the &man.init.8; manual @@ -4408,41 +4334,6 @@ options SYSVMSG # enable for messaging - - - Why does SSH authentication - through .shosts not work by default - in recent versions of &os;? - - - - The reason why .shosts - authentication does not work by default in more recent - versions of &os; is because &man.ssh.1; is not installed - suid root by - default. To fix this, you can do one of - the following: - - - - As a permanent fix, set - ENABLE_SUID_SSH to - true in - /etc/make.conf then rebuild and - reinstall &man.ssh.1;. - - - - As a temporary fix, change the mode on - /usr/bin/ssh to - 4555 by running chmod 4555 - /usr/bin/ssh as root. - - - - - What is vnlru? -- cgit v1.2.3