--- introduction.mm 2003/04/02 06:36:16 4.22 +++ introduction.mm 2003/06/30 06:47:54 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: introduction.mm,v 4.22 2003/04/02 06:36:16 grog Exp $ +.\" $Id: introduction.mm,v 4.26 2003/06/30 06:47:54 grog Exp $ .Chapter \*[nchintro] "Introduction" FreeBSD is a free operating system derived from AT&T's \fIUNIX\fP\/ operating system.\*F @@ -249,8 +249,9 @@ .LI FreeBSD is secure. Its track record is borne out by the reports of the \fICERT\fP, the leading organization dealing with computer security. See -\fIhttp://www.cert.org/\fP\/ for more information. The FreeBSD project has a -team of security officers concerned with maintaining this lead. +.URI http://www.cert.org +for more information. The FreeBSD project has a team of security officers +concerned with maintaining this lead. .LI FreeBSD is reliable. It is used by ISPs around the world. FreeBSD systems regularly go several years without rebooting. FreeBSD can fail, of course, but @@ -550,12 +551,13 @@ identical to FreeBSD. The main differences are that NetBSD concentrates on hardware independence, whereas FreeBSD concentrates on performance. FreeBSD also tries harder to be easy to understand for a beginner. You can find more -information about NetBSD at \fIhttp://www.NetBSD.org\fP. +information about NetBSD at +.URI http://www.NetBSD.org . .LI .X "OpenBSD" \fIOpenBSD\fP\/ is a spin-off of NetBSD that focuses on security. It's also very similar to FreeBSD. You can find more information at -\fIhttp://www.OpenBSD.org\fP. +.URI http://www.OpenBSD.org . .LI .X "Mac OS X" Apple computer introduced Version 10 (X) of its \fIMac OS\fP\/ in early 2001. @@ -599,7 +601,7 @@ T{ FreeBSD is a complete operating system, maintained by a central group of software developers under the Concurrent Versions System which maintains a -complete history of the project developemnt. There is only one distribution of +complete history of the project development. There is only one distribution of FreeBSD. T}#T{ Linux is a kernel, personally maintained by Linus Torvalds and a few trusted @@ -894,7 +896,8 @@ option, or by starting the program .Command apropos \/: .Dx -$ \f(CBman -k mail \fP $ \f(CBapropos mail \fP +$ \f(CBman -k mail \fP +$ \f(CBapropos mail \fP .De Both of these commands do the same thing: they show the names of the man pages that have the keyword \fImail\fP\/ in their descriptions. @@ -970,7 +973,7 @@ .De In .Command -n Emacs , -enter \fBCTRL-h i\fP or \fBALT-X\fP \f(CWinfo\fP. Whichever way you start +enter \fBCTRL-h i\fP or \fBALT-x\fP \f(CWinfo\fP. Whichever way you start .Command info , you can get brief introduction by typing \f(CBh\fP, and a quick command reference by typing \f(CB?\fP. @@ -1061,12 +1064,15 @@ liability. If you're on the Internet, you're not alone, however. Liability is one thing, but there are plenty of people prepared to help you, most for free, some for fee. A good place to start is with the mailing lists. There are a -number of mailing lists that you can join: +number of mailing lists that you can join. Some of the more interesting ones +are: .Ls B .LI \f(CWFreeBSD-questions@FreeBSD.org\fP is the list to which you may send general -questions, in particular on how to use FreeBSD. Use this one if you're not sure -which is the most appropriate. +questions, in particular on how to use FreeBSD. If you have difficulty +understanding anything in this book, for example, this is the right place to +ask. It's also the list to use if you're not sure which is the most +appropriate. .LI \f(CWFreeBSD-newbies@FreeBSD.org\fP is a list for newcomers to FreeBSD. It's intended for people who feel a little daunted by the system and need a bit of @@ -1075,114 +1081,177 @@ \f(CWFreeBSD-hackers@FreeBSD.org\fP is a technical discussion list. .LI \f(CWFreeBSD-current@FreeBSD.org\fP is an obligatory list for people who run the -development version of FreeBSD, called \f(CWFreeBSD-CURRENT\fP. We'll talk -about \f(CW-CURRENT\fP, as it is usually called, on pages -.Sref "\*[release-tags]" \& -and -.Sref "\*[current]" . +development version of FreeBSD, called \f(CWFreeBSD-CURRENT\fP. +.LI +\f(CWFreeBSD-stable@FreeBSD.org\fP is a similar list for people who run the more +recent stable version of FreeBSD, called \f(CWFreeBSD-STABLE\fP. We'll talk +about these versions on page +.Sref \*[release-names] . +Unlike the case for \f(CWFreeBSD-CURRENT\fP users, it's not obligatory for +\f(CWFreeBSD-STABLE\fP users to subscribe to \f(CWFreeBSD-stable\fP. .Le -You can find a complete list on the web site. +You can find a complete list of FreeBSD mailing lists on the web site, currently +at +.URI http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/eresources.html . +This address is part of the online handbook and may change when the handbook is +modified; follow the link \fIMailing Lists\fP\/ from +.URI http://www.FreeBSD.org/ +if it is no longer valid, or if you can't be bothered typing in the URI. +.P +The mailing lists are run by +.Command mailman +(in the Ports Collection). Join them via the web interface mentioned above. +You will receive a mail message from \fImailman\fP\/ asking you to confirm your +subscription by replying to the message. You don't need to put anything in the +reply: the reply address is used once only, and you're the only person who will +ever see it, so the system knows that it's you by the fact that you replied at +all. You also have the option of confirming via a web interface with a +specially generated URI. Similar considerations apply in this case. +.P +FreeBSD mailing lists can have a very high volume of traffic. The +FreeBSD-questions mailing list, for example, has thousands of subscribers, and +many of them are themselves mailing lists. It receives over a hundred messages +every day. That's about a million messages a day in total for just one mailing +list, so when you sign up for a mailing list, be sure to read the charter. You +can find the URI from the \fImailman\fP\/ confirmation message. It's also a +good idea to ``lurk'' (listen, but not say anything) on the mailing list a while +before posting anything: each list has its own traditions. .P -To join a list, send a mail message to \f(CWmajordomo@FreeBSD.org\fP with the -names of the lists you want to join: -.Dx -subscribe FreeBSD-newbies -subscribe FreeBSD-questions -.De -If the mail ID that you want to add to the list is different from the ID you're -sending from, put the ID at the end of the line. This requires manual -intervention to confirm that the user really wants to be on the list, so it can -take longer. It's always better to send the mail from the ID at which you want -to receive the mail. -.P -You don't need a subject line; if you include one, it will be ignored. You'll -get a reply back saying that the request must be authenticated: it'll look -something like this: -.Dx -Please be sure to read the charters before subscribing or sending -mail to any FreeBSD mailing list for an explanation of which topics -are relevant for a given list and what types of postings are and -are not allowed. They may be found at: - - http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL - -Someone (possibly you) has requested that your email address be added -to or deleted from the mailing list "freebsd-questions@FreeBSD.ORG". - -If you really want this action to be taken, please send the following -commands (exactly as shown) back to "Majordomo@FreeBSD.ORG": - - auth b2c64f95 subscribe freebsd-questions grog@example.org - -If you do not want this action to be taken, simply ignore this message -and the request will be disregarded. - -If your mailer will not allow you to send the entire command as a single -line, you may split it using backslashes, like so: - - auth b2c64f95 subscribe freebsd-questions \e - grog@example.org - -If you have any questions about the policy of the list owner, please -contact "postmaster@FreeBSD.ORG". - -Thanks! - -Majordomo@FreeBSD.ORG -.De -Just reply to that message, removing all the text except the \f(CWauth\fP line: -.Dx - auth b2c64f95 subscribe freebsd-questions grog@example.org -.De -Send this message to \f(CWmajordomo@FreeBSD.org\fP (which is what you do if you -just reply), not to the list itself. You'll get another reply back: -.Dx -Welcome to the freebsd-questions mailing list! - -Please save this message for future reference. Thank you. - -If you ever want to remove yourself from this mailing list, -you can send mail to with the following -command in the body of your email message: - - unsubscribe freebsd-questions - -or from another account, besides grog@example.org: - - unsubscribe freebsd-questions grog@example.org - -If you ever need to get in contact with the owner of the list, -(if you have trouble unsubscribing, or have questions about the -list itself) send email to . -This is the general rule for most mailing lists when you need -to contact a human. - - Here's the general information for the list you've subscribed to, - in case you don't already have it: - -FREEBSD-QUESTIONS User questions -This is the mailing list for questions about FreeBSD. You should not -send "how to" questions to the technical lists unless you consider the -question to be pretty technical. -.De -When submitting questions to \f(CW-questions\fP, remember that people are under -no obligation to answer them. Make them want to answer it: submit the question -in a clear, understandable manner. For more details, see -\fIhttp://www.lemis.com/questions.html\fP. You may also like to check out the -FreeBSD World Wide Web (WWW) site at \fIhttp://www.FreeBSD.org\fP, in particular -the support page at \fIhttp://www.FreeBSD.org/support.html\fP. +.ne 2v +When submitting a question to \f(CWFreeBSD-questions\fP, consider the following +points: +.Ls +.LI +Remember that nobody gets paid for answering a FreeBSD question. They do it of +their own free will. You can influence this free will positively by submitting +a well-formulated question supplying as much relevant information as possible. +You can influence this free will negatively by submitting an incomplete, +illegible, or rude question. It's perfectly possible to send a message to +FreeBSD-questions and not get an answer even if you follow these rules. It's +much more possible to not get an answer if you don't. +.LI +Not everybody who answers FreeBSD questions reads every message: they look at +the subject line and decide whether it interests them. Clearly, it's in your +interest to specify a subject. ``FreeBSD problem'' or ``Help'' aren't enough. +If you provide no subject at all, many people won't bother reading it. If your +subject isn't specific enough, the people who can answer it may not read it. +.LI +When sending a new message, well, send a new message. Don't just reply to some +other message, erase the old content and change the subject line. That leaves +an \f(CWIn-Reply-To:\fP header which many mail readers use to thread messages, +so your message shows up as a reply to some other message. People often delete +messages a whole thread at a time, so apart from irritating people, you also run +a chance of having the message deleted unread. +.LI +Format your message so that it is legible, and PLEASE DON'T SHOUT!!!!!. It's +really painful to try to read a message written full of typos or without any +line breaks. A lot of badly formatted messages come from bad mailers or badly +configured mailers. The following mailers are known to send out badly formatted +messages without you finding out about them: +.P +.nf +Eudora +exmh +Microsoft Exchange +Microsoft Internet Mail +Microsoft Outlook +Netscape +.fi +.P +.ne 2v +As you can see, the mailers in the Microsoft world are frequent offenders. If +at all possible, use a UNIX mailer. If you must use a mailer under Microsoft +environments, make sure it is set up correctly. Try not to use MIME: a lot of +people use mailers which don't get on very well with MIME. +.P +For further information on this subject, check out +.URI http://www.lemis.com/email.html . +.LI +Make sure your time and time zone are set correctly. This may seem a little +silly, since your message still gets there, but many of the people you are +trying to reach get several hundred messages a day. They frequently sort the +incoming messages by subject and by date, and if your message doesn't come +before the first answer, they may assume they missed it and not bother to look. +.LI +Don't include unrelated questions in the same message. Firstly, a long message +tends to scare people off, and secondly, it's more difficult to get all the +people who can answer all the questions to read the message. +.LI +Specify as much information as possible. This is a difficult area: the +information you need to submit depends on the problem. Here's a start: +.Ls B +.LI +If you get error messages, don't say ``I get error messages'', say (for example) +``I get the error message \fINo route to host\fP''. +.LI +If your system panics, don't say ``My system panicked'', say (for example) ``my +system panicked with the message \fIfree vnode isn't\fP''. +.LI +If you have difficulty installing FreeBSD, please tell us what hardware you +have, particularly if you have something unusual. +.LI +If, for example, you have difficulty getting PPP to run, describe the +configuration. Which version of PPP do you use? What kind of authentication do +you have? Do you have a static or dynamic IP address? What kind of messages do +you get in the log file? See +.Sref "\*[chppp]" , +for more details in this particular case. +.Le +.LI +If you don't get an answer immediately, or if you don't even see your own +message appear on the list immediately, don't resend the message. Wait at least +24 hours. The FreeBSD mailer offloads messages to a number of subordinate +mailers around the world. Usually the messages come through in a matter of +seconds, but sometimes it can take several hours for the mail to get through. +.LI +If you do all this, and you still don't get an answer, there could be other +reasons. For example, the problem is so complicated that nobody knows the +answer, or the person who does know the answer was offline. If you don't get an +answer after, say, a week, it might help to re-send the message. If you don't +get an answer to your second message, though, you're probably not going to get +one from this forum. Resending the same message again and again will only make +you unpopular. +.Le +.H3 "How to follow up to a question" +Often you will want to send in additional information to a question you have +already sent. The best way to do this is to reply to your original message. +This has three advantages: +.Ls +.LI +You include the original message text, so people will know what you're talking +about. Don't forget to trim unnecessary text, though. +.LI +The text in the subject line stays the same (you did remember to put one in, +didn't you?). Many mailers will sort messages by subject. This helps group +messages together. +.LI +The message reference numbers in the header will refer to the previous message. +Some mailers, such as mutt, can thread messages, showing the exact relationships +between the messages. +.Le +There are more suggestions, in particular for answering questions, at +.URI http://www.lemis.com/questions.html . +See also +.Sref "\*[chmua]" \& +for more information about sending mail messages. You may also like to check +out the FreeBSD web site at +.URI http://www.FreeBSD.org/ +and the support page at +.URI http://www.FreeBSD.org/support.html . .P In addition, a number of companies offer support for FreeBSD. See the web page -\fIhttp://www.freebsd.org/commercial/consulting_bycat.html\fP\/ for some -possibilities. +.URI http://www.FreeBSD.org/commercial/consulting_bycat.html +for some possibilities. .H3 "Unsubscribing from the mailing lists" There's a lot of traffic on the mailing lists, particularly on -\f(CW-questions\fP. You may find you can't take it and want to get out again. -Again, send mail to \f(CWmajordomo@FreeBSD.org\fP, \f(BInot\fP\/ to the list. -Each message you get from the mailing lists finishes with the following text: +\f(CWFreeBSD-questions\fP. You may find you can't take it and want to get out +again. Again, you unsubscribe from the list either via the web or via a special +mail address, \f(BInot\fP\/ by sending mail to the the list. Each message you +get from the mailing lists finishes with the following text: .Dx -To Unsubscribe: send mail to majordomo@FreeBSD.org -with "unsubscribe freebsd-questions" in the body of the message +freebsd-questions@freebsd.org mailing list +http://lists.freebsd.org/mailman/listinfo/freebsd-questions +To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" .De Don't be one of those people who send the unsubscribe request to the mailing list instead. @@ -1190,15 +1259,19 @@ .X "user, groups" But how about meeting FreeBSD users face to face? There are a number of user groups around the world. If you live in a big city, chances are that there's -one near you. Check \fIhttp://www.freebsd.org/support.html#user\fP\/ for a -list. If you don't find one, consider taking the initiative and starting one. +one near you. Check +.URI http://www.FreeBSD.org/support.html#user +for a list. If you don't find one, consider taking the initiative and starting +one. .P .X "BSDCon" In addition, USENIX holds an annual conference, the \fIBSDCon\fP, which deals with technical aspects of the BSD operating systems. It's also a great opportunity to get to know other users from around the world. If you're in Europe, there is also a BSDCon Europe, which at the time of writing was not run -by USENIX. See \fIhttp://www.eurobsdcon.org/\fP\/ for more details. +by USENIX. See +.URI http://www.eurobsdcon.org +for more details. .H3 "Reporting bugs" .X "reporting bugs" .X "bugs, reporting" --- install.mm 2003/04/02 06:39:30 4.21 +++ install.mm 2003/06/29 04:34:08 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: install.mm,v 4.21 2003/04/02 06:39:30 grog Exp $ +.\" $Id: install.mm,v 4.22 2003/06/29 04:34:08 grog Exp $ .\" .\" This file contains conditional code for the following sizes: .\" complete (The Complete FreeBSD) @@ -1138,7 +1138,7 @@ only knows the BIOS names, so you'd normally be looking for the first partition on drive .Directory C: . -After booting, install the correct bootstrap with \f(CWdisklabel -B\fP\/ or +After booting, install the correct bootstrap with \f(CWbsdlabel -B\fP\/ or .Command boot0cfg , and you should be able to boot from hard disk again. .H3 "Geometry problems" @@ -1680,7 +1680,7 @@ file systems on the floppies instead: .Dx # \f(CBfdformat -f 1440 fd0.1440\fP -# \f(CBdisklabel -w -r fd0.1440 floppy3\fP +# \f(CBbsdlabel -w fd0.1440 floppy3\fP # \f(CBnewfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0\fP .De Next, copy the files to the floppies. The distribution files are split into --- postinstall.mm 2003/04/02 06:40:31 4.12 +++ postinstall.mm 2003/06/29 04:30:44 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: postinstall.mm,v 4.12 2003/04/02 06:40:31 grog Exp $ +.\" $Id: postinstall.mm,v 4.13 2003/06/29 04:30:44 grog Exp $ .\" .Chapter \*[nchpostinstall] "Post-installation configuration" In the last chapter we looked at the installation of the basic system, up to the @@ -180,7 +180,7 @@ window manager to .X "desktop, kde" .X "kde, desktop" -.Command -k kde , +.Command -n kde , or the .Command pine or --- disks.mm 2003/04/02 06:44:17 4.17 +++ disks.mm 2003/06/29 03:06:37 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: disks.mm,v 4.17 2003/04/02 06:44:17 grog Exp $ +.\" $Id: disks.mm,v 4.19 2003/06/29 02:54:00 grog Exp $ .\" .\" XXX Add section on snapshots .Chapter \*[nchdisks] "Disks" @@ -314,7 +314,7 @@ that can recover from some data problems. In most cases, though, it's sufficient to write zeros to the entire disk: .Dx -# \f(CBdd if=/dev/zero of=/dev/ad1s2 bs=128k\fP +# \f(CBdd if=/dev/zero of=/dev/ad1 bs=128k\fP .De If this doesn't work, you may find formatting programs on the manufacturer's web site. You'll probably need to run them under a Microsoft platform. @@ -800,10 +800,10 @@ .Le The only information we need to input is the kind, size and locations of the partitions. In this case, we have decided to create a file system on partition -\f(CWh\fP ( -.Device da1s2h \/) +\f(CWh\fP +.File -n ( /dev/da1s2h \/) and swap space on partition \f(CWb\fP -.Device -n ( da1s1b ). +.File -n ( /dev/da1s1b ). The swap space will be 512 MB, and the file system will take up the rest of the slice. This is mainly tradition: traditionally data disks use the \f(CWh\fP partition and not the \f(CWa\fP partition, so we'll stick to that tradition, @@ -824,98 +824,92 @@ .PE .Figure-heading "FreeBSD slice on second disk" .Fn second-disk-freebsd-slice -.H3 "Disklabel" +.H3 "bsdlabel" .Pn disklabel -The program that writes the disk label is called (wait for it) +The program that writes the disk label used to be called .Command disklabel . -It's not as warty as +As FreeBSD migrated to multiple platforms, this proved to be too generic: many +hardware platforms have their own disk label formats. For example, FreeBSD on +SPARC64 uses the Sun standard labels. On platforms which use the old BSD +labels, such as the PC, the name was changed to +.Command bsdlabel . +On SPARC64 it is called +.Command sunlabel . +On each platform, the appropriate file is linked to the name +.Command disklabel , +but some of the options have changed. In addition, the output format now +normally ignores a number of historical relics. It's not as warty as .Command fdisk , -but it can still give you a run for your money. Nowadays you can ignore most of +but it can still give you a run for your money. You can usually ignore most of the complexity, though. You can normally create a disk label with the single command: .Dx -# \f(CBdisklabel -w -r /dev/da1s2 auto\fP +# \f(CBbsdlabel -w /dev/da1s2 auto\fP .De This creates the label with a single partition, \f(CWc\fP. You can look at the label with -.Command disklabel +.Command bsdlabel without options: .Dx -# \f(CBdisklabel /dev/da1s2\fP +# \f(CBbsdlabel /dev/da1s2\fP # /dev/da0s2: -type: SCSI -disk: SEAGATE -label: -flags: -bytes/sector: 512 -sectors/track: 47 -tracks/cylinder: 13 -sectors/cylinder: 611 -cylinders: 10303 -sectors/unit: 6295133 -rpm: 3600 -interleave: 1 -trackskew: 0 -cylinderskew: 0 -headswitch: 0 # milliseconds -track-to-track seek: 0 # milliseconds -drivedata: 0 - 8 partitions: # size offset fstype [fsize bsize bps/cpg] - c: 6295133 0 unused 0 0 # (Cyl. 0 - 10302) + c: 6295133 0 unused 0 0 # "raw" part, don't edit .De -Only the last three lines are of interest. The rest is historical information -that is irrelevant and that may be just plain wrong, like the \f(CWrpm\fP -value 3600, a typical value 20 years ago. Nowadays even the cheapest disks run -at 5400 rpm. -.P At this point, the only partition you have is the ``whole disk'' partition -\f(CWc\fP. You still need to partitions \f(CWb\fP and \f(CWh\fP and specify -their location and size. Do this with \fIdisklabel -e\fP, which starts an -editor with the output you see above. Simply add additional partitions: +\f(CWc\fP. You still need to create partitions \f(CWb\fP and \f(CWh\fP and +specify their location and size. Do this with \fIbsdlabel -e\fP, which starts +an editor with the output you see above. Simply add additional partitions: .Dx 8 partitions: # size offset fstype [fsize bsize bps/cpg] - c: 6295133 0 unused 0 0 # (Cyl. 0 - 10302) + c: 6295133 0 unused 0 0 # "raw" part, don't edit .ft CB - b: 1048576 0 swap 0 0 # (Cyl. 0 - 10302) - h: 5246557 1048576 unused 0 0 # (Cyl. 0 - 10302) + b: 1048576 0 swap 0 0 + h: 5246557 1048576 unused 0 0 .ft .De You don't need to maintain any particular order, and you don't need to specify that partition \f(CWh\fP will be a file system. In the next step, .Command newfs -will do that for you automatically. +does that for you automatically. .\" Because of the list at the beginning of the section .br .ne 12v -.H3 "Problems running disklabel" -Sometimes this doesn't quite work. Here are some of the errors you might -encounter: +.H3 "Problems running bsdlabel" +Using the old +.Command disklabel +program used to be like walking through a minefield. Things have got a lot +better, but it's possible that some problems are still hiding. Here are some of +the problems that have been encountered in the past, along with some suggestions +about what to do if you experience them: .Ls B .LI -You may find: +When writing a label (the \f(CW-w\fP option), you may find: .Dx -# \f(CBdisklabel -w -r da1s2 auto\fP -disklabel: /dev/da1s2c: Undefined error: 0 +# \f(CBbsdlabel -w da1s2\fP +bsdlabel: /dev/da1s2c: Undefined error: 0 .De This message may be the result of the kernel having out-of-date information about the slice in memory. If this is the case, a reboot may help. .LI \f(CWNo disk label on disk\fP is straightforward enough. You tried to use -.Command disklabel +.Command bsdlabel to look at the label before you had a label to look at. .LI \f(CWLabel magic number or checksum is wrong!\fP tells you that -.Command disklabel +.Command bsdlabel thinks it has a label, but it's invalid. This could be the result of an incorrect previous attempt to label the disk. It can be difficult to get rid of an incorrect label. The best thing to do is to repartition the disk with the label in a different position, and then copy .Device zero -to where the label used to be. Then you can repartition again the way you want -to have it. +to where the label used to be: +.Dx +# \f(CBdd if=/dev/zero of=/dev/da1 bs=128k count=1\fP +.De +Then you can repartition again the way you want to have it. .LI \f(CWOpen partition would move or shrink\fP probably means that you have specified incorrect values in your slice definitions. Check particularly that @@ -932,34 +926,6 @@ fixlabel: raw partitions offset != slice offset .De The meanings of these messages should be obvious. -.LI -You may get this message: -.Dx -# \f(CBdisklabel -w -r /dev/da1s2 auto\fP -disklabel: "auto" requires the usage of a canonical disk name -.De -This is -.Command disklabel 's -inimitable way of telling you that it wants you to type \f(CWda1s2\fP, not -\f(CW/dev/da1s2\fP. -.LI -.Pn disktab -In old times, -.Command disklabel -sometimes failed to create a file system with the \f(CWauto\fP keyword. -In such a case, you needed to describe the disk geometry in the file -.File /etc/disktab . -This problem hasn't occurred for a long time. If it happens to you, you might -get around it by defining the disk in -.File /etc/disktab -(see the man page \fIdisktab(5)\fP\/ for details) and then referencing the -definition in the invocation of -.Command disklabel \/: -.Dx -# \f(CBdisklabel -w -r da1s2 definition\fP -.De -where \f(CWdefinition\fP is the name of the entry in -.File /etc/disktab . .Le .SPUP .H2 "Creating file systems" @@ -971,18 +937,19 @@ Mercifully, this is easier: .Dx # \f(CBnewfs -U /dev/da1s2h\fP -Warning: Block size and bytes per inode restrict cylinders per group to 89. -Warning: 420 sector(s) in last cylinder unallocated -/dev/da1s2h: 5246556 sectors in 1281 cylinders of 1 tracks, 4096 sectors - 2561.8MB in 15 cyl groups (89 c/g, 178.00MB/g, 21632 i/g) +/dev/vinum/da1s2h: 2561.8MB (5246556 sectors) block size 16384, fragment size 2048 + using 14 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. + with soft updates super-block backups (for fsck -b #) at: - 32, 364576, 729120, 1093664, 1458208, 1822752, 2187296, 2551840, 2916384, -3280928, 3645472, 4010016, 4374560, 4739104, 5103648 + 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, + 3763680, 4140032, 4516384, 4892736 .De The \f(CW-U\fP flag tells .Command newfs to enable soft updates, which we looked at on page .Sref \*[soft-updates] . +.br +.ne 10v .H3 "Mounting the file systems" .X "mounting, file systems" .X "file system, mounting" @@ -1003,7 +970,7 @@ presto:/usr 912271 824927 41730 95% /presto/usr presto:/home 1905583 1193721 521303 70% /presto/home presto:/S 4065286 3339635 563039 86% /S -/dev/da1s2h 2582220 2 2375642 0% /newhome +/dev/da1s2h 2540316 2 2337090 0% /newhome # \f(CBpstat -s\fP \fIshow swap usage\fP\/ Device 1K-blocks Used Avail Capacity Type /dev/ad0s4b 524160 0 524160 0% Interleaved @@ -1049,6 +1016,7 @@ \f(BICheck /var/tmp/tarerrors and make sure that the files really made it to the right place!\fP\/ .LI +.ne 3v Remove the old files: .Dx # \f(CBrm -rf /usr/home\fP --- vinum.mm 2003/04/09 19:56:42 4.19 +++ vinum.mm 2003/06/29 04:33:42 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: vinum.mm,v 4.19 2003/04/09 19:56:42 grog Exp $ +.\" $Id: vinum.mm,v 4.20 2003/06/29 04:33:42 grog Exp $ .\" .Chapter \*[nchvinum] "The Vinum Volume Manager" .X "vinum" @@ -1317,23 +1317,23 @@ file system to take up the rest. It's important to create the swap partition at the beginning of the disk, so you create that first. After installation, the output of -.Command disklabel +.Command bsdlabel looks like this: .Dx 8 partitions: # size offset fstype [fsize bsize bps/cpg] - a: 524288 532480 4.2BSD 2048 16384 94 # (Cyl. 871*- 1729*) - b: 532215 265 swap # (Cyl. 0*- 871*) - c: 8386733 0 unused 0 0 # (Cyl. 0 - 13726*) - e: 4194304 1056768 4.2BSD 2048 16384 89 # (Cyl. 1729*- 8594*) - f: 3135661 5251072 4.2BSD 2048 16384 89 # (Cyl. 8594*- 13726*) + a: 524288 532480 4.2BSD 2048 16384 94 + b: 532215 265 swap + c: 8386733 0 unused 0 0 # "raw" part, don't edit + e: 4194304 1056768 4.2BSD 2048 16384 89 + f: 3135661 5251072 4.2BSD 2048 16384 89 .De To convert to Vinum, use -.Command disklabel +.Command bsdlabel with the \f(CW-e\fP (edit label) option to create a volume of type \fIvinum\fP\/ that maps the \fIc\fP\/ partition: .Dx - h: 8386733 0 vinum # (Cyl. 0 - 13726*) + h: 8386733 0 vinum .De .ne 10v After this, you have the following situation: @@ -1363,7 +1363,7 @@ swap partition to start after the Vinum configuration information and to be 265 sectors shorter. The file systems are relatively trivial to recreate: take the size and offset values from the -.Command disklabel +.Command bsdlabel output above and use them in a Vinum configuration file: .Dx drive rootdev device /dev/da0s2h @@ -1387,7 +1387,7 @@ .X "create, vinum command" .X "vinum, create command" The comments are the corresponding lines from the -.Command disklabel +.Command bsdlabel output. They show the corresponding values for size and offset. Run \fIvinum create\fP\/ against this file, and confirm that you have the volumes .Directory / , --- tapes.mm 2003/04/02 06:47:36 4.10 +++ tapes.mm 2003/06/29 03:06:33 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: tapes.mm,v 4.10 2003/04/02 06:47:36 grog Exp $ +.\" $Id: tapes.mm,v 4.12 2003/06/29 03:06:33 grog Exp $ .\" .Chapter \*[nchtapes] "Tapes, backups and floppy disks" .P @@ -184,12 +184,11 @@ invokes it for you automatically with the \f(CW-z\fP option. The size of the resultant archives depends strongly on the data you put in them. JPEG images, for example, hardly compress at all, while text compresses quite well and can be -as high as 90% smaller than the constituent files. +as much as 90% smaller than the original file. .H4 "Creating a tar archive" .X "creating a tar archive" .X "tar, creating an archive" Create an archive with the \f(CWc\fP option. Unlike most UNIX programs, - .Command tar does not require a hyphen (\f(CW-\fP) in front of the options. For example, to save your complete kernel source tree, you could write: @@ -423,8 +422,8 @@ Processing ---------------------------------------- .De Each hyphen character (\f(CW-\fP) represents two tracks. As the format -proceeds, the hyphens change individually to an \f(CBF\fP (Format) and then to -\f(CBV\fP (Verify) in turn, so at the end the line reads +proceeds, the hyphens change to an \f(CBF\fP (Format) and then to \f(CBV\fP +(Verify) in turn, so at the end the line reads .Dx Processing VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV done. .De @@ -441,72 +440,31 @@ the space available on the disk. Here's an example of creating a file system, mounting it on the directory .Directory /A , -and listing the remaining space available -on an empty 3\(12\f(CW"\fP floppy. We use the -.Command disktab -approach to labelling the disk, as we saw on page -.Sref \*[disktab] . -.File /etc/disktab -does have labels for floppy disks: use \f(CWfd1440\fP for a 3\(12\f(CW"\fP 1.44 -MB floppy, and \f(CWfd1200\fP for a 5\(14\f(CW"\fP 1.2 MB floppy: -.Dx -# \f(CBdisklabel -w -r /dev/fd0 fd1440\fP \fIlabel the floppy\fP\/ -# \f(CBdisklabel -r /dev/fd0\fP \fIand list the information\fP\/ -# /dev/fd0: -type: unknown -disk: fd1440 -label: -flags: -bytes/sector: 512 -sectors/track: 18 -tracks/cylinder: 2 -sectors/cylinder: 36 -cylinders: 80 -sectors/unit: 2880 -rpm: 300 -interleave: 1 -trackskew: 0 -cylinderskew: 0 -headswitch: 0 # milliseconds -track-to-track seek: 0 # milliseconds -drivedata: 0 - -3 partitions: -# size offset fstype [fsize bsize bps/cpg] - a: 2880 0 unused 512 4096 # (Cyl. 0 - 79) - b: 2880 0 unused 512 4096 # (Cyl. 0 - 79) - c: 2880 0 unused 512 4096 # (Cyl. 0 - 79) -# \f(CBnewfs /dev/fd0\fP \fIcreate a new file system\fP\/ -Warning: Block size restricts cylinders per group to 6. -Warning: 1216 sector(s) in last cylinder unallocated -/dev/fd0.1440: 2880 sectors in 1 cylinders of 1 tracks, 4096 sectors - 1.4MB in 1 cyl groups (6 c/g, 12.00MB/g, 736 i/g) +and listing the remaining space available on an empty 3\(12\f(CW"\fP floppy. +Since release 5, FreeBSD no longer requires a partition table on a floppy, so +you don't need to run +.Command bsdlabel +(the replacement for the older +.Command disklabel +program). +.Dx +# \f(CBnewfs -O1 /dev/fd0\fP \fIcreate a new file system\fP\/ +/dev/fd0: 1.4MB (2880 sectors) block size 16384, fragment size 2048 + using 2 cylinder groups of 1.00MB, 64 blks, 128 inodes. super-block backups (for fsck -b #) at: - 32, + 32, 2080 # \f(CBmount /dev/fd0 /A\fP \fImount the floppy on /A\fP\/ -# \f(CBdf /A\fP \fIdisplay the space available\fP\/ +# \f(CBdf -k /A\fP \fIdisplay the space available\fP\/ Filesystem 1024-blocks Used Avail Capacity Mounted on -/dev/fd0 1319 0 1213 0% /mnt +/dev/fd0 1326 2 1218 0% /A .De Let's look at this in a little more detail: .Ls B .LI -.X "UFS" -The first invocation of -.Command disklabel , -with the \f(CW-w\fP option, writes a disk label to the floppy, which supplies -enough information for -.Command newfs -to create a \fIUFS\fP\/ file system on it. -.LI -The second invocation of -.Command disklabel , -just with the \f(CW-r\fP option, lists the information written by the first -invocation. This isn't necessary for creating the file system, but it helps to -check that the disk is labelled correctly. -.LI .Command newfs -creates the \fIUFS\fP\/ file system on the floppy. +creates the \fIUFS\fP\/ file system on the floppy. We use the \f(CW-O1\fP flag +to force the older UFS1 format, which leaves more usable space than the default +UFS2. .LI We have already seen .Command mount @@ -520,18 +478,19 @@ program shows the maximum and available space on a file system. By default, .Command df -displays usage in blocks of 512 bytes, an inconvenient size. In this example, -the environment variable \f(CWBLOCKSIZE\fP was set to 1024 to display the usage -in 1 kB (1024 byte) blocks. See page +displays usage in blocks of 512 bytes, an inconvenient size. In this example we +use the \f(CW-k\fP option to display it in kilobytes. You can set a default +block size via the environment variable \f(CWBLOCKSIZE\fP. If it had been set +to 1024, we would see the same output without the \f(CW-k\fP option. See page .Sref \*[environment-variables] \& for more details of environment variables. .Le The output of .Command df -looks terrible! Our floppy only has 1213 kB left for normal user data, even +looks terrible! Our floppy only has 1218 kB left for normal user data, even though there is nothing on it and even .Command df -claims that it can really store 1319 kB. This is because \fIUFS\fP\/ keeps a +claims that it can really store 1326 kB. This is because \fIUFS\fP\/ keeps a default of 8% of the space free for performance reasons. You can change this, however, with .Command tunefs , @@ -546,10 +505,12 @@ # \f(CBtunefs -m 0 /dev/fd0\fP \fIand change the minimum free to 0\fP\/ tunefs: minimum percentage of free space changes from 8% to 0% tunefs: should optimize for space with minfree < 8% +# \f(CBtunefs -o space /dev/fd0\fP \fIchange the optimization\fP\/ +tunefs: optimization preference changes from time to space # \f(CBmount /dev/fd0 /A\fP \fImount the file system again\fP\/ # \f(CBdf /A\fP \fIand take another look\fP\/ Filesystem 1024-blocks Used Avail Capacity Mounted on -/dev/fd0 1319 0 1319 0% /A +/dev/fd0 1326 2 1324 0% /A .De Still, this is a far cry from the claimed data storage of a Microsoft disk. In fact, Microsoft disks can't store the full 1.4 MB either: they also need space @@ -558,7 +519,7 @@ .H3 "Microsoft file systems" .X "Microsoft file systems" .Pn DOS-fs -To create an MS-DOS file system, use the +To create a Microsoft FAT12, FAT16 or FAT32 file system, use the .Command newfs_msdos command: .Dx @@ -578,7 +539,7 @@ tracks and 18 sectors (a standard 3\(12\f(CW"\fP 1.44 MB floppy), you could enter: .Dx -$ mformat -t 80 -s 18 A: +$ \f(CBmformat -t 80 -s 18 A:\fP .De .Command mformat is one of the --- netsetup.mm 2003/04/03 08:56:41 4.17 +++ netsetup.mm 2003/06/29 09:05:45 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: netsetup.mm,v 4.17 2003/04/03 08:56:41 grog Exp $ +.\" $Id: netsetup.mm,v 4.21 2003/06/29 09:05:45 grog Exp $ .\" .Chapter \*[nchnetsetup] "Configuring the local network" .X "PPP" @@ -788,23 +788,22 @@ .X "adding routes, automatically" .X "routed, daemon" .X "daemon, routed" -.X "gated, daemon" -.X "daemon, gated" FreeBSD comes with all the currently available routing software, primarily the -daemons -.Daemon routed -and -.Daemon gated . -.Daemon routed -is in the base system, and the newer +daemon +.Daemon routed . +The newer .Daemon gated -is in the Ports Collection. +used to be included as well, but it is no longer available for free. It is +available from +.URI http://www.nexthop.com/products/howto_order.shtml . +An alternative in the Ports Collection is +.Daemon zebra . .P -Both daemons have one thing in common: you don't need them. At any rate, you -don't need them until you have at least two different connections to the +All these daemons have one thing in common: you don't need them. At any rate, +you don't need them until you have at least two different connections to the Internet, and even then it's not sure. As a result, we won't discuss them here. -If you do need to run routing daemons, read all about them in \fITCP/IP -Network Administration\fP, by Craig Hunt. +If you do need to run routing daemons, read all about them in \fITCP/IP Network +Administration\fP, by Craig Hunt. .P From our point of view, however, the routing protocols have one particular significance: the system expects the routing table to be updated automatically. --- netclient.mm 2003/04/03 02:17:18 4.14 +++ netclient.mm 2003/06/30 06:12:58 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: netclient.mm,v 4.14 2003/04/03 02:17:18 grog Exp $ +.\" $Id: netclient.mm,v 4.18 2003/06/30 06:12:58 grog Exp $ .\" .Chapter \*[nchclient] "Basic network access: clients" Finally we have set up the network connections, and everything is working. What @@ -477,7 +477,7 @@ .File .profile file: .Dx -if tty > /dev/null +if tty > /dev/null; then ssh-add -l > /dev/null if [ $? -ne 0 ]; then eval `ssh-agent` @@ -586,7 +586,7 @@ "\f(CW\s880\s0\fP" at LB.c+(0,-.1) .PE The \fIssh\fP\/ connection is shown in \f(CIfixed italic\fP font. It looks just -like any other \fIssh\fP\/ connection. The difference are the local connections +like any other \fIssh\fP\/ connection. The differences are the local connections at each end: instead of talking to presto port 80 (\f(CWhttp\fP), you talk to port 4096 on your local machine. Why 4096? It's your choice; you can use any port above 1024. If you're on \fIandante\fP, you can set up this tunnel with @@ -612,20 +612,22 @@ .De In addition to setting up the tunnel, .Command ssh -creates a normal interactive session. If you don't want this, you can use the -\f(CW-f\fP option tell +can create a normal interactive session. If you don't want this, use the +\f(CW-f\fP option to tell .Command ssh -to go into the background after authentication. You also need a command to -execute; in case of doubt, use -.Command sleep , -which simply delays for a specified time. If this is what you want to do, you -could enter a command like: +to go into the background after authentication. You can also specify a command +to execute, but this is no longer necessary for protocol version 2. If you +don't want to execute a command, use the \f(CW-N\fP option: +.Dx +$ \f(CBssh -L 4096:presto.example.org:80 presto.example.org -f -N\fP +.De +If you're running protocol version 1, you can use +.Command sleep +with an appropriately long timeout, in this example 1 hour: .Dx $ \f(CBssh -L 4096:presto.example.org:80 presto.example.org -f sleep 3600\fP .De -The command \f(CWsleep 3600\fP suspends execution for an hour (3600 seconds) and -then exits. At this point, your tunnel also shuts down, so you should choose -the time to be long enough. +.SPUP .H3 "Tunneling X" Running X clients on the remote machine is special enough that .Command ssh @@ -854,6 +856,7 @@ In summary, then, you can expect the following files in your .Directory ~/.ssh \/: .Dx +drwx------ 2 grog grog 512 Jan 18 21:04 . \fIdirectory\fP\/ -rw-r--r-- 1 grog grog 1705 Oct 26 1999 authorized_keys \fIkeys\f(CW -rw-r--r-- 1 grog grog 844 Jan 27 22:18 authorized_keys2 \fIkeys, Version 2 only\f(CW -rw-r--r-- 1 grog grog 25 Oct 20 01:35 environment \fIenvironment for sshd\f(CW @@ -866,10 +869,11 @@ -rw------- 1 grog grog 1000 Jul 25 1999 known_hosts \fIlist of known hosts\f(CW -rw------- 1 grog grog 512 Jul 25 1999 random_seed \fIfor key generation\f(CW .De -Note particularly the permissions and the ownership of the files. If they are -wrong, +Note particularly the permissions and the ownership of the files and the +directory itself. If they are wrong, .Command ssh -won't work, and it won't tell you why not. +won't work, and it won't tell you why not. In particular, the directory must +not be group writeable. .H2 "Troubleshooting ssh connections" A surprising number of things can go wrong with setting up .Command ssh @@ -903,11 +907,11 @@ Could not open a connection to your authentication agent. .De .ne 4v -This means that you haven't run +This message means that you haven't run .Command ssh-agent . Do it like this: .Dx -$ eval `ssh-agent` +$ \f(CBeval `ssh-agent`\fP Agent pid 95180 $ \f(CBssh-add -l\fP The agent has no identities. @@ -921,9 +925,10 @@ 1024 95:d5:01:ca:90:04:7d:84:f6:00:32:7a:ea:a6:57:2d /home/grog/.ssh/id_rsa (RSA) 1024 53:53:af:22:87:07:10:e4:5a:2c:21:31:ec:29:1c:5f /home/grog/.ssh/id_dsa (DSA) .De -This shows that all three keys are set correctly. If you have, say, only an -RSA1 (protocol Version 1) key, and the other end doesn't support protocol -Version 1, you'll get this kind of message. +In this case, all three keys are set correctly. If you have, say, only an RSA1 +(protocol Version 1) key, and the other end doesn't support protocol Version 1, +.Command ssh +will ask for a password. .br .ne 5v .LI @@ -960,8 +965,7 @@ .Dx StrictHostKeyChecking no .De -This won't remove the warning, but at least you don't have to attend to it -immediately. +It doesn't remove the warning, but it allows you to connect anyway. .Le .Le .Command ssh @@ -1019,7 +1023,7 @@ .X "pseudo-tty" .X "pty" .X "pity" -Once you get this far, you are connected to the machine in almost identical +Once you get this far, you are connected to the machine in an almost identical manner as if you were directly connected. This is particularly true if you are running X. As the output of the .Command tty @@ -1523,9 +1527,9 @@ files, this can be relatively inefficient. You can perform this task more efficiently with .Command rsync , -which is designed to keep identical copies of files on and to optimize network -bandwidth while doing so. It's in the Ports Collection. Install in the normal -manner: +which is designed to keep identical copies of files on two different systems and +to optimize network bandwidth while doing so. It's in the Ports Collection. +Install in the normal manner: .Dx # \f(CBcd /usr/ports/net/rsync\fP # \f(CBmake install\fP @@ -2078,10 +2082,10 @@ Depending on which device it is, this could create some subtle problems that could go undetected for quite a while. .LI -If a driver for the for the specified major number exists on your local system, -and the devices are different on the two systems, you will still access the -local device with the same major and minor numbers, if such a device exists. -The results could be very confusing. +If a driver for the specified major number exists on your local system, and the +devices are different on the two systems, you will still access the local device +with the same major and minor numbers, if such a device exists. The results +could be very confusing. .LI If no driver for the specified major number exists on your local system, the request will fail. This can still cause considerable confusion. --- xtheory.mm 2003/04/03 03:13:24 4.13 +++ xtheory.mm 2003/05/18 02:19:19 @@ -1,6 +1,6 @@ \" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: xtheory.mm,v 4.13 2003/04/03 03:13:24 grog Exp $ +.\" $Id: xtheory.mm,v 4.14 2003/05/18 02:19:19 grog Exp $ .\" ..if article .ce 2 @@ -1383,8 +1383,8 @@ number of PCI boards. But PCI boards are difficult to find nowadays, and they're slower and have less memory. .P -If you have a number machines physically next to each other, you have the -alternative of running X on each of them and controlling everything from one +If you have a number of machines located physically next to each other, you have +the alternative of running X on each of them and controlling everything from one keyboard and mouse. You do this with the .Daemon x11/x2x port. For example: \fIfreebie\fP, \fIpresto\fP\/ and \fIbumble\fP\/ have --- starting.mm 2003/04/03 02:35:05 4.21 +++ starting.mm 2003/06/29 03:13:08 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: starting.mm,v 4.21 2003/04/03 02:35:05 grog Exp $ +.\" $Id: starting.mm,v 4.23 2003/06/29 03:13:08 grog Exp $ .\" .Chapter \*[nchstarting] "Starting and stopping the system" Before you can run FreeBSD, you need to start it up. That's normally pretty @@ -1361,9 +1361,9 @@ Dec 11 14:18:46 bumble savecore: 192.109.197.82:/src/nodisk/swap/bumble: No such file or directory .De -This, too, will -change; in the meantime, it \fIis\fP\/ possible to mount swap on files, even if -they are NFS mounted. This means that the first of the following entries in +This, too, will change; in the meantime, it \fIis\fP\/ possible to mount swap on +files, even if they are NFS mounted, but not on the NFS file system itself. +This means that the first of the following entries in .File /etc/fstab will not work, but the second will: .Dx @@ -1426,8 +1426,7 @@ .Directory /usr/obj directories as long as all systems maintain the same release of FreeBSD. You can even have different kernels: each kernel build directory carries the name of -the of the configuration file, which by convention matches the name of the -system. +the configuration file, which by convention matches the name of the system. .Le .Le The big problem is --- configfiles.mm 2003/04/03 02:42:08 4.18 +++ configfiles.mm 2003/06/29 04:32:34 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: configfiles.mm,v 4.18 2003/04/03 02:42:08 grog Exp $ +.\" $Id: configfiles.mm,v 4.19 2003/06/29 04:32:34 grog Exp $ .\" .Chapter \*[nchconfigfiles] "FreeBSD configuration files" .Pn configfiles @@ -1330,8 +1330,7 @@ contains descriptions of disk geometries for .Command disklabel . This is almost -obsolete. We looked at it briefly on page -.Sref \*[disktab] . +obsolete. .H3 "/etc/ftpusers" .File /etc/ftpusers is a list of users who are \fInot\fP\/ allowed to connect to this system using --- current.mm 2003/04/09 19:28:00 4.17 +++ current.mm 2003/06/29 04:29:20 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: current.mm,v 4.17 2003/04/09 19:28:00 grog Exp $ +.\" $Id: current.mm,v 4.18 2003/06/29 04:29:20 grog Exp $ .\" .Chapter \*[nchcurrent] "Keeping up to date" FreeBSD is constantly changing. The average time that elapses between changes @@ -101,6 +101,7 @@ If you're a serious developer, there are a number of advantages to keeping a copy of the repository. If you're a casual user, it's probably overkill. .H2 "FreeBSD releases" +.Pn release-names There are four main versions of FreeBSD, each intended for use by different people: .H3 "FreeBSD-RELEASE" --- upgrading.mm 2003/04/03 01:51:34 4.6 +++ upgrading.mm 2003/06/30 06:13:43 @@ -3,7 +3,7 @@ .\" .\" To do: add info about disabled devices .\" -.\" $Id: upgrading.mm,v 4.6 2003/04/03 01:51:34 grog Exp $ +.\" $Id: upgrading.mm,v 4.12 2003/06/30 06:13:43 grog Exp $ .Chapter \*[nchupgrading] "Updating the system software" .Pn make-world .X "make world" @@ -291,6 +291,7 @@ change, or that you won't be using any, you can skip building them by specifying the \f(CW-DNO_MODULES\fP flag. T} +.sp .4v installkernel#T{ Install a kernel you have built with \f(CWbuildkernel\fP. T} @@ -419,12 +420,32 @@ .H2 "Upgrading the boot files" At the time of writing, it's still necessary to install the files in .Directory /boot -separately. Do this with: -.Dx -# \f(CBcd /usr/src/sys\fP -# \f(CBmake install\fP -.De -It's possible that this requirement will go away in the future. +separately. It's possible that this requirement will go away in the future. +There are two steps: first you build and install the boot files in the +.Directory /boot +directory, then you install them on your boot disk. Assuming your system disk +is the SCSI disk +.Device da0 , +you would perform some of the following steps. +.Dx +# \f(CBcd /usr/src/sys\fP \fIbuild directory\fP\/ +# \f(CBmake install\fP \fIbuild and install the bootstraps\fP\/ +# \f(CBbsdlabel -B da0\fP \f(BIEither\fI, for a dedicated disk\f(CW +# \f(CBbsdlabel -B da0s1\fP \f(BIOr\fI, for a PC disk slice\f(CW +# \f(CBboot0cfg -B da0\fP \f(BIOr\fI, booteasy for a dedicated PC disk\f(CW +.De +If you have a dedicated disk, which is normal on a non-Intel platform, use the +first +.Command bsdlabel +invocation to install the bootstrap +.Command -n ( boot1 ) +at the beginning of the disk. Otherwise, install +.Command -n boot1 +at the beginning of your FreeBSD slice and use +.Command boot0cfg +to install the +.Command -n boot0 +boot manager at the beginning of the disk. .H2 "Upgrading the configuration files" Currently, the system build procedure does not install the configuration files in --- biblio.mm 2003/04/02 04:56:03 4.7 +++ biblio.mm 2003/06/29 06:27:59 @@ -1,6 +1,6 @@ .\" This file is in -*- nroff-fill -*- mode .\" STATUS: 4th edition -.\" $Id: biblio.mm,v 4.7 2003/04/02 04:56:03 grog Exp $ +.\" $Id: biblio.mm,v 4.8 2003/06/29 06:27:59 grog Exp $ .\" .Appendix \*[nbiblio] "Bibliography" While the manual pages provide the definitive reference for individual pieces of @@ -35,6 +35,10 @@ Addison-Wesley, 2001. An introduction to FreeBSD for Microsoft system administrators. .P +.X "Smith, Roderick W." +\fIFreeBSD: The Complete Reference\fP, by Roderick W. Smith. +McGraw-Hill/Osborne, 2003. +.P .X "Stokely, Murray" .X "Clayton, Nik" \fIThe FreeBSD Handbook\fP, edited by Murray Stokely and Nik Clayton. Wind @@ -79,7 +83,7 @@ .X "Cheswick, William R." .X "Bellovin, Steven M." \fIFirewalls and Internet Security: Repelling the Wily Hacker\fP, by William -R. Cheswick and Steven M. Bellovin. Addison-Wesley, 1994. +R. Cheswick and Steven M. Bellovin. Second edition, Addison-Wesley, 2003. .P .X "Frisch, \(AEleen" \fIEssential System Administration\fP, by \(AEleen Frisch. Third edition, @@ -124,7 +128,7 @@ .P .X "Jolitz, William F." \fI``Porting UNIX to the 386''\fP in \fIDr. Dobb's Journal\fP, William Jolitz. -January 1991-July 1992. +January 1991\(enJuly 1992. .P .X "Lehey, Greg" \fIPorting UNIX Software\fP, by Greg Lehey. O'Reilly & Associates, 1995. --- evolution.mm 2003/04/02 04:59:47 4.13 +++ evolution.mm 2003/06/24 05:24:32 @@ -630,4 +630,15 @@ \fIVinum\fP\/ now supports the root file system. See Chapter .Sref \*[nchvinum] \& for details. +.LI +.Command disklabel , +the program which creates disk labels, has been split into multiple programs +depending on the platform: on PCs it is now called +.Command bsdlabel , +and on SPARC64 it is called +.Command sunlabel . +Some options have changed. In particular, the \f(CW-r\fP option no longer +exists. See page +.Sref \*[disklabel] \& +for further details. .Le