From owner-freebsd-doc Wed Oct 11 00:53:26 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA26939 for doc-outgoing; Wed, 11 Oct 1995 00:53:26 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA26932 ; Wed, 11 Oct 1995 00:52:56 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id AAA11971; Wed, 11 Oct 1995 00:52:36 -0700 To: doc@freefall.FreeBSD.org cc: faq@freefall.FreeBSD.org Subject: Darryl Okahata: Re: I do not see that this ever made it in to the FAQ?? Date: Wed, 11 Oct 1995 00:52:35 -0700 Message-ID: <11969.813397955@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-doc@FreeBSD.org Precedence: bulk Did you guys get these changes? I think they should certainly be folded in, if not! Jordan ------- Forwarded Message Return-Path: darrylo@hpnmhjw.sr.hp.com Received: from freefall.cdrom.com (freefall.cdrom.com [192.216.222.4]) by time.cdrom.com (8.6.11/8.6.9) with ESMTP id PAA09413 for ; Fri, 28 Jul 1995 15:59:48 -0700 Received: from violet.berkeley.edu (violet.Berkeley.EDU [128.32.155.22]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id QAA13485 for ; Fri, 28 Jul 1995 16:00:34 -0700 Received: from relay.hp.com by violet.berkeley.edu (8.6.10/1.33r) id QAA07173; Fri, 28 Jul 1995 16:00:32 -0700 Received: from srmail.sr.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA037452431; Fri, 28 Jul 1995 16:00:31 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA114042430; Fri, 28 Jul 1995 16:00:30 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA232812429; Fri, 28 Jul 1995 16:00:29 -0700 Message-Id: <199507282300.AA232812429@hpnmhjw.sr.hp.com> To: jkh@violet.berkeley.edu (Jordan K. Hubbard) Subject: Re: I do not see that this ever made it in to the FAQ?? In-Reply-To: Your message of "Fri, 28 Jul 1995 14:52:43 PDT." <199507282152.OAA00397@violet.berkeley.edu> Date: Fri, 28 Jul 1995 16:00:28 -0700 From: Darryl Okahata > Here's a fragment of some things that I submitted for addition to > the FAQ (ignore the strange question numbering). Check out the last > question. > > [ Hmm. Looking at these answers, some of them are a bit incomplete. > Not all possibilities are given. ] OK, I'll just send you what I sent to the FAQ folks (ignore my previous message to you). The following consists of diffs relative to the ASCII version, as that is what the FAQ folks requested. Also, I noticed that some of the answers are a bit incomplete. Would you like me to fix them and send you the changes? -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion or policy of Hewlett-Packard or of the little green men that have been following him all day. =============================================================================== Date: Wed, 19 Jul 1995 01:34:43 PDT To: roberto@blaise.ibp.fr (Ollivier Robert) cc: gclarkii@freebsd.org, freebsd-doc@freebsd.org From: Darryl Okahata Subject: Re: Who's working on the FAQ? >From owner-freebsd-doc@freefall.cdrom.com Wed Jul 19 01: 44:16 1995 Sender: doc-owner@freebsd.org Precedence: bulk [ This is being cc'd to freebsd-doc to get any feedback. ] > > Has the FAQ been fixed up to handle the following? > > > > If not, I'd be willing to submit some entries for these. > > Go and send your changes. I'm a little bit short on time for the moment. Hi, Here are some changes. In addition to adding some common questions, I also changed the introduction slightly. The idea is that someone new to FreeBSD would ask questions like the following: 1. What is FreeBSD? 2. What do I need to run FreeBSD? 3. Where do I get it? I placed these close to the beginning because they are probably among the most-asked questions, and burying them in the bowels of the document would probably frustrate people and make them use Linux. ;-) Anyway, keep what you think is useful and throw out the rest. I added a question on "FreeBSD books/documents". I've mentioned some good books, but I don't know what the FreeBSD policy is regarding commercial products. Anyway, I've got no connections to any of the mentioned books/CDROMs, aside from being a customer. I didn't add/change anything regarding the serial port devices (e.g., lack of /dev/tty00, etc.), as I haven't had the time. I'm not sure what changes other people have been making, and so I didn't make a large amount of changes. If you'd like me to continue fiddling with the FAQ, just ask. Areas marked with need to be verified/corrected. Also, the section/question numbering may seem odd. They just need to be renumbered. I just chose some numbers to make the questions sequential, and I'm not trying to create some weird question hierarchy. The patches are relative to rev 1.5 of /usr/share/FAQ/Text/FreeBSD.FAQ. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion or policy of Hewlett-Packard or of the little green men that have been following him all day. =============================================================================== *** FreeBSD.FAQ.orig Tue Jul 11 23:23:56 1995 - --- FreeBSD.FAQ Wed Jul 19 00:43:28 1995 *************** *** 33,38 **** - --- 33,42 ---- Welcome to the FreeBSD 2.0 FAQ! This document tries to answer some of the most frequently asked questions about FreeBSD 2.0. + + The latest released version is FreeBSD 2.0.5R. (What about + current snapshots?) + If there's something you're having trouble with and you do not see it here, please send email to: *************** *** 40,49 **** Some of the instructions here will also refer to auxiliary utilities ! in the /usr/src/share/FAQ directory. CDROM purchasers and net folks ! who've grabbed the FreeBSD 2.0 `srcdist' will have these files. If ! you don't have the source distribution, then you can either grab the ! whole thing from: ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current - --- 44,56 ---- Some of the instructions here will also refer to auxiliary utilities ! in the /usr/share/FAQ directory and below. If you do not have this ! directory, or if it does not contain the file that you want, you are ! probably using a version of FreeBSD prior to 2.0.5R. In this case, ! install the FreeBSD sources and look in /usr/src/share/FAQ (instead of ! /usr/share/FAQ). CDROM purchasers and net folks who've grabbed the ! FreeBSD 2.0 `srcdist' will have these files. If you don't have the ! source distribution, then you can either grab the whole thing from: ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current *************** *** 78,83 **** - --- 85,115 ---- Sync PPP Improved SCSI support + 0.1.1: What do I need to run FreeBSD? + + See section 2, "Hardware compatibility", of this FAQ. + + 0.1.2: Where can I get FreeBSD? + + The distribution is available via anonymous ftp from: + + ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ + + For the current release, 2.0.5R, look in: + + ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.0.5-RELEASE/ + + FreeBSD is also available via CDROM, from the following place(s): + + Walnut Creek CDROM + 4041 Pike Lane, Suite D-386 + Concord, CA 94520 USA + Orders: (800)-786-9907 + Questions: (510)-674-0783 + FAX: (510)-674-0821 + email: orders@cdrom.com + WWW: http://www.cdrom.com/ + 0.2: What are the FreeBSD mailing lists, and how can I get on them? *************** *** 123,132 **** - --- 155,272 ---- (probably only for a short time longer). + 0.4: Books on FreeBSD + + There currently aren't any books written specifically for FreeBSD, although + some people are supposedly working on some. + + However, as FreeBSD 2.0 is based upon Berkeley 4.4BSD-Lite, most of the + 4.4BSD manuals are applicable to FreeBSD 2.0. O'Reilly and Associates + publishes these manuals: + + 4.4BSD System Manager's Manual + By Computer Systems Research Group, UC Berkeley + 1st Edition June 1994, 804 pages + ISBN: 1-56592-080-5 + + 4.4BSD User's Reference Manual + By Computer Systems Research Group, UC Berkeley + 1st Edition June 1994, 905 pages + ISBN: 1-56592-075-9 + + 4.4BSD User's Supplementary Documents + By Computer Systems Research Group, UC Berkeley + 1st Edition July 1994, 712 pages + ISBN: 1-56592-076-7 + + 4.4BSD Programmer's Reference Manual + By Computer Systems Research Group, UC Berkeley + 1st Edition June 1994, 886 pages + ISBN: 1-56592-078-3 + + 4.4BSD Programmer's Supplementary Documents + By Computer Systems Research Group, UC Berkeley + 1st Edition July 1994, 596 pages + ISBN: 1-56592-079-1 + + A description of these can be found via WWW as: + + http://gnn.com/gnn/bus/ora/category/bsd.html + + A good book on system administration is: + + Evi Nemeth, Garth Snyder, Scott Seebass, & Trent R. Hein, + "Unix System Administraion Handbook", Prentice-Hall, 1995, + ISBN: 0-13-151051-7 + [ Note: make sure you get the second edition, with a red cover, + instead of the first edition. ] + + This book covers the basics, as well as TCP/IP, DNS, NFS, SLIP/PPP, + sendmail, INN/NNTP, printing, etc.. It's expensive (~US$45-$55), but worth + it. It also includes a CDROM with the sources for various tools; most of + these, however, are also on the FreeBSD 2.0.5R CDROM (and the FreeBSD CDROM + often has newer versions). + + + 0.5: Other sources of information. + + One good source of additional information is the "[comp.unix.bsd] NetBSD, + FreeBSD, and 386BSD (0.1) FAQ". Much of the information is relevant to + FreeBSD, and this FAQ is posted around twice a month to the following + newsgroups: + + comp.unix.bsd.netbsd.announce + comp.unix.bsd.freebsd.announce + comp.answers + news.answers + + ( is this FAQ still being maintained/posted???) + + If you have WWW access, the FreeBSD home page is at: + + http://www.freebsd.org/ + + A FreeBSD "handbook" is being created, and can be found as: + + http://www.freebsd.org/How/handbook/ + + Note that this is a work in progress, and so parts may be incomplete. + 1 Installation -------------- + 1.0: How do I install FreeBSD? + + [ IMPORTANT NOTE: if you are installing 2.0.5R from tape, see the question + titled, "Help! I can't install from tape! The install fails with a + `record too big' error!" ] + + Installation instructions can be found as: + + ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.0.5-RELEASE/INSTALL + + Release notes are also available as: + + ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.0.5-RELEASE/RELNOTES + + On the CDROM, the following files are in the top-most directory: + + INSTALL -- Installation instructions + README.TXT -- Basic README file + RELNOTES -- Release notes + + + 1.0.1: Help! I can't install from tape! The install fails with a + "record too big" error! + + If you are installing 2.0.5R from tape, you must create the tape using a tar + blocksize of 10 (5120 bytes). The default tar blocksize is 20 (10240 + bytes), and tapes created using this default size cannot be used to install + 2.0.5R; with these tapes, you will get an error that complains about the + record size being too big. + + 1.1: I want to install FreeBSD onto a SCSI disk that has more than 1024 cylinders. How do I do it? *************** *** 179,184 **** - --- 319,334 ---- No. FreeBSD 2.0 comes with bounce buffers which allows your bus mastering controller access to greater than 16MB. + 1.5.1: My network card keeps getting errors like, "ed1: timeout". What's + going on? + + This is usually caused by an interrupt conflict (e.g., two boards using + the same IRQ). FreeBSD prior to 2.0.5R used to be tolerant of + this, and the network driver would still function in the presence of IRQ + conflicts. However, with 2.0.5R and later, IRQ conflicts are no + longer tolerated. See the file, "", for more details. + + 1.6: Do I need to install the complete sources? In general, no. However, we would strongly recommend that you *************** *** 565,570 **** - --- 715,867 ---- 5 Miscellaneous Questions ---------------- + + + 5.0.1: Hey! Chmod doesn't change the file permissions of symlinked files! + What's going on? + + You have to use either "-H" or "-L" together with the "-R" option to make + this work. See the chmod(1) and symlink(7) man pages for more info. + + WARNING: the "-R" option does a *RECURSIVE* chmod. Be careful about + specifying directories or symlinks to directories to chmod. If you want to + change the permissions of a directory referenced by a symlink, use chmod(1) + without any options and follow the symlink with a trailing slash ("/"). For + example, if "foo" is a symlink to directory "bar", and you want to change + the permissions of "foo" (actually "bar"), you would do something like: + + chmod 555 foo/ + + With the trailing slash, chmod will follow the symlink, "foo", to change the + permissions of the directory, "bar". + + + 5.0.2: How do I mount a CDROM? I've tried using mount(8), but it keeps on + giving me an error like, "/dev/cd0a on /mnt: Incorrect super block." + + You have to tell mount(8) the type of the device that you want to mount. By + default, mount(8) will assume the filesystem is of type "ufs". You want to + mount a CDROM filesystem, and you do this by specifying the "-t cd9660" + option to mount(8). This does, of course, assume that the CDROM contains an + ISO 9660 filesystem, which is what most CDROMs have. As of 2.0.5R, FreeBSD + also understands the Rock Ridge (long filename) extensions. + + As an example, if you want to mount the CDROM device, "/dev/cd0c", under + /mnt, you would execute: + + mount -t cd9660 /dev/cd0c /mnt + + Note that your device name ("/dev/cd0c" in this example) could be different, + depending on the CDROM interface. Note that the "-t cd9660" option just + causes the "mount_cd9660" command to be executed, and so the above example + could be shortened to: + + mount_cd9660 /dev/cd0c /mnt + + + 5.0.3: When I try to mount a CDROM, I get a "Device not configured" error. + What's going on? + + This generally means that there is no CDROM in the CDROM drive. Feed the + drive something. + + + 5.0.4: My programs occasionally die with "Signal 11" errors. What's + going on? + + This can be caused by bad hardware (memory, motherboard, etc.). Try running + a memory-testing program on your PC. Note that, even though every memory + testing program you try will report your memory as being fine, it's possible + for slightly marginal memory to pass all memory tests, yet fail under + operating conditions (such as during busmastering DMA from a SCSI + controller like the Adaptec 1542). + + + 5.0.5: Help, some of my X Window menus and dialog boxes don't work right! I + can't select them. + + Try turning off the Num Lock key. + + + 5.0.6: How do I access the virtual consoles? + + If the console is not currently displaying X Windows, just press Alt-F1 to + Alt-F12. NOTE: the default FreeBSD installation has only three (3) virtual + consoles enabled, and so only Alt-F1, Alt-F2, and Alt-F3 will work to switch + between three virtual consoles. If you want to increase this number, see + the next question. + + If the console is currently displaying X Windows, you can use Ctrl-Alt-F1, + etc. to switch to a virtual console. Note, however, that once you've + switched away from X Windows to a virtual terminal, you use only the Alt- + function key to switch to another virtual terminal or back to X Windows. + You do not also press the Ctrl key; the Ctrl-Alt-function key combination is + used only when switching from X Windows to a virtual terminal. + + + 5.0.7: How do I increase the number of virtual consoles? + + Edit /etc/ttys and add entries for "ttyv4" to "ttyvc" after the comment on + "Virtual terminals" (delete the leading whitespace in the following + example): + + # Edit the existing entry for ttyv3 in /etc/ttys and change + # "off" to "on". + ttyv3 "/usr/libexec/getty Pc" cons25 on secure + ttyv4 "/usr/libexec/getty Pc" cons25 on secure + ttyv5 "/usr/libexec/getty Pc" cons25 on secure + ttyv6 "/usr/libexec/getty Pc" cons25 on secure + ttyv7 "/usr/libexec/getty Pc" cons25 on secure + ttyv8 "/usr/libexec/getty Pc" cons25 on secure + ttyv9 "/usr/libexec/getty Pc" cons25 on secure + ttyva "/usr/libexec/getty Pc" cons25 on secure + ttyvb "/usr/libexec/getty Pc" cons25 on secure + + Use as many or as few as you want. The more virtual terminals you have, the + more resources that are used; this can be important if you have 8MB RAM or + less. You may also want to change the "secure" to "insecure". + + IMPORTANT NOTE: if you want to run X Windows, you *MUST* leave a virtual + terminal unused (or turned off). For example, if you want to attach a + virtual terminal to all of your twelve Alt-function keys, you can only + attach virtual terminals to eleven of them. The last must be left unused, + because X Windows will use it, and you will use the last Alt-function key to + switch back to X Windows (after you have switched from X Windows to a + virtual console via a Ctrl-Alt-function key). The easiest way to do this is + to disable a console by turning it off. For example, if you have a keyboard + with twelve function keys, you would change settings for virtual terminal 12 + from: + + ttyvb "/usr/libexec/getty Pc" cons25 on secure + + to: + + ttyvb "/usr/libexec/getty Pc" cons25 off secure + + If your keyboard has only ten function keys, you would end up with: + + ttyv9 "/usr/libexec/getty Pc" cons25 off secure + ttyva "/usr/libexec/getty Pc" cons25 off secure + ttyvb "/usr/libexec/getty Pc" cons25 off secure + + (You could also just delete these lines.) + + Once you have edited /etc/ttys, the next step is to make sure that you have + enough virtual terminal devices. The easiest way to do this is: + + cd /dev + ./MAKEDEV vty12 # For 12 devices + + Next, the easiest (and cleanest) way to activate the virtual consoles is to + reboot. However, if you really don't want to reboot, you can just shut down + X Windows and execute (as root): + + kill -HUP 1 + + It's imperative that you completely shut down X Windows if it is running, + before running this command. If you don't, your system will probably appear + to hang/lock up after executing the kill command. + 5.1: I've heard of something called FreeBSD-current. How do I run it, and where can I get more information? ------- End of Forwarded Message