From owner-freebsd-doc Tue Jul 25 15:50:45 2000 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7431037BA90 for ; Tue, 25 Jul 2000 15:50:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA01406; Tue, 25 Jul 2000 15:50:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from mail.ruhr.de (in-ruhr2.ruhr.de [141.39.224.60]) by hub.freebsd.org (Postfix) with SMTP id 983EF37BA77 for ; Tue, 25 Jul 2000 15:40:23 -0700 (PDT) (envelope-from ue@nathan.ruhr.de) Received: (qmail 78888 invoked by alias); 25 Jul 2000 22:42:35 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.9.3/8.9.3) id AAA10740; Wed, 26 Jul 2000 00:35:19 +0200 (CEST) (envelope-from ue) Message-Id: <200007252235.AAA10740@nathan.ruhr.de> Date: Wed, 26 Jul 2000 00:35:19 +0200 (CEST) From: Udo Erdelhoff Reply-To: ue@nathan.ruhr.de To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/20183: [PATCHES] to replace s by something correct Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 20183 >Category: docs >Synopsis: Patches to replaces s by something correct >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 25 15:50:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Udo Erdelhoff >Release: FreeBSD 5.0-CURRENT i386 >Organization: >Environment: doc/en_US.ISO_8859-1/articles/fonts/article.sgml,v revision 1.8 doc/en_US.ISO_8859-1/articles/formatting-media/article.sgml,v revision 1.13 doc/en_US.ISO_8859-1/articles/mh/article.sgml,v revision 1.7 doc/en_US.ISO_8859-1/articles/multi-os/article.sgml,v revision 1.12 doc/en_US.ISO_8859-1/articles/new-users/article.sgml,v revision 1.13 doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v revision 1.11 (Should be the doc tree for 4.1-RELEASE) >Description: Several articles use as simple but annoying method to close the current entity. These patches fix these articles. The patches were generated with the help of an automatic script, verified by make in $DOC_PREFIX/en*/articles and two Mk one eyeballs. Additionally, one instance of \n >How-To-Repeat: find $DOC_PREFIX/en_US.ISO_8859-1 -name "*.sgml" -print | xargs grep '' >Fix: (use ^Number to jump from patch to patch) Number one: Index: article.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO_8859-1/articles/fonts/article.sgml,v retrieving revision 1.8 diff -u -r1.8 article.sgml --- article.sgml 2000/06/20 11:30:11 1.8 +++ article.sgml 2000/07/25 20:58:15 @@ -77,7 +77,7 @@ - .pfa, .pfb + .pfa, .pfb Postscript type 1 fonts. The @@ -89,7 +89,7 @@ - .afm + .afm The font metrics associated with a type 1 font. @@ -97,7 +97,7 @@ - .pfm + .pfm The printer font metrics associated with a type 1 @@ -106,7 +106,7 @@ - .ttf + .ttf A TrueType font @@ -114,7 +114,7 @@ - .fot + .fot An indirect reference to a TrueType font (not an @@ -123,7 +123,7 @@ - .fon, .fnt + .fon, .fnt Bitmapped screen fonts @@ -157,7 +157,7 @@ syscons - .fnt + .fnt @@ -271,7 +271,7 @@ is cross referenced to its X11 name by the contents of the fonts.dir file in each directory. - There is already a directory named Type1. The + There is already a directory named Type1. The most straight forward way to add a new font is to put it into this directory. A better way is to keep all new fonts in a separate directory and use a symbolic link to the additional @@ -364,7 +364,7 @@ Lets just name all the new fonts - type1. + type1. @@ -381,7 +381,7 @@ Normal, bold, medium, semibold, etc. From the - strings1 + strings1 output above, it appears that this font has a weight of medium. @@ -441,7 +441,7 @@ as the name, and then use - xfontsel1 to + xfontsel1 to examine it and adjust the name based on the appearance of the font. @@ -477,7 +477,7 @@ References: &man.xfontsel.1;, &man.xset.1;, The X - Windows System in a Nutshell, , O'Reilly & Associates. @@ -485,7 +485,7 @@ Using type 1 fonts with Ghostscript - Ghostscript references a font via its Fontmap + Ghostscript references a font via its Fontmap file. This must be modified in a similar way to the X11 fonts.dir file. Ghostscript can use either the .pfa or the .pfb @@ -541,7 +541,7 @@ /usr/share/groff_font/devps/SHOWBOAT. The file must be created using tools provided by groff. - The first tool is afmtodit. This is not + The first tool is afmtodit. This is not normally installed, so it must be retrieved from the source distribution. I found I had to change the first line of the file, so I did: @@ -582,10 +582,10 @@ printer in order for the font to be used (unless the printer happens to have the showboat font built in or on an accessible font disk.) The final step is to create a down loadable font. - The pfbtops tool is used to create the + The pfbtops tool is used to create the .pfa format of the font, and the - download file is modified to reference the new - font. The download file must reference the + download file is modified to reference the new + font. The download file must reference the internal name of the font. This can easily be determined from the groff font file as illustrated: @@ -686,7 +686,7 @@ - GS_TTF.PSGS_TTF.PS Number two: Index: article.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO_8859-1/articles/formatting-media/article.sgml,v retrieving revision 1.13 diff -u -r1.13 article.sgml --- article.sgml 1999/10/30 18:10:14 1.13 +++ article.sgml 2000/07/25 21:00:04 @@ -151,7 +151,7 @@ quite possible to destroy the contents of other disks in your system if the proper precautions are not taken. - Check your work carefully. It is very simple + Check your work carefully. It is very simple to destroy the incorrect disk when working with these commands. When in doubt consult the kernel boot output for the proper device. @@ -535,7 +535,7 @@ To create a new CCD, execute the following commands. This describes how to add three disks together; simply add or remove devices as necessary. Remember that the disks to be - striped must be identical. + striped must be identical. Before executing these commands, make sure you add the line Number three Index: article.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO_8859-1/articles/mh/article.sgml,v retrieving revision 1.7 diff -u -r1.7 article.sgml --- article.sgml 1999/10/10 20:20:38 1.7 +++ article.sgml 2000/07/25 21:14:48 @@ -35,7 +35,7 @@ initial philosophies behind MH were developed. MH isn't so much a monolithic email program but a philosophy about how best to develop tools for reading email. The MH developers have done a - great job adhering to the KISS principle: Keep It + great job adhering to the KISS principle: Keep It Simple Stupid. Rather than have one large program for reading, sending and handling email they have written specialized programs for each part of your email life. One might liken MH to @@ -64,9 +64,9 @@ - You will notice that it created a /usr/local/lib/mh + You will notice that it created a /usr/local/lib/mh directory for you as well as adding several binaries to the - /usr/local/bin directory. If you would prefer to + /usr/local/bin directory. If you would prefer to compile it yourself then you can anonymous ftp it from ftp.ics.uci.edu or louie.udel.edu. @@ -85,33 +85,33 @@ Reading Mail - This section covers how to use inc, - show, scan, next, - prev, rmm, rmf, and - msgchk. One of the best things about MH is the + This section covers how to use inc, + show, scan, next, + prev, rmm, rmf, and + msgchk. One of the best things about MH is the consistent interface between programs. A few things to keep in mind when using these commands is how to specify message lists. - In the case of inc this doesn't really make any - sense but with commands like show it is useful to + In the case of inc this doesn't really make any + sense but with commands like show it is useful to know. A message list can consist of something like 23 - 20 16 which will act on messages 23, 20 and 16. This is + 20 16 which will act on messages 23, 20 and 16. This is fairly simple but you can do more useful things like - 23-30 which will act on all the messages between + 23-30 which will act on all the messages between 23 and 30. You can also specify something like - cur:10 which will act on the current message and - the next 9 messages. The cur, last, - and first messages are special messages that refer + cur:10 which will act on the current message and + the next 9 messages. The cur, last, + and first messages are special messages that refer to the current, last or first message in the folder. - <command>inc</>, <command>msgchk</>—read in your + <title><command>inc</command>, <command>msgchk</command>—read in your new email or check it - If you just type in inc and hit - return you will be well on your way to getting - started with MH. The first time you run inc it + If you just type in inc and hit + return you will be well on your way to getting + started with MH. The first time you run inc it will setup your account to use all the MH defaults and ask you about creating a Mail directory. If you have mail waiting to be downloaded you will see something that looks like: @@ -126,45 +126,45 @@ This is the same thing you will see from a - scan (see ). If you just run - inc with no arguments it will look on your + scan (see ). If you just run + inc with no arguments it will look on your computer for email that is supposed to be coming to you. A lot of people like to use POP for grabbing their email. MH can do POP to grab your email. You will need to give - inc a few command line arguments. + inc a few command line arguments. &prompt.user; inc -host mail.pop.org -user username -norpop - That tells inc to go to - mail.pop.org to download your email, and that - your username on their system is username. The - option tells inc to use + That tells inc to go to + mail.pop.org to download your email, and that + your username on their system is username. The + option tells inc to use plain POP3 for downloading your email. MH has support for a few different dialects of POP. More than likely you will never ever need to use them though. While you can do more complex things with inc such as audit files and scan format files this will get you going. - The msgchk command is used to get information - on whether or not you have new email. msgchk takes + The msgchk command is used to get information + on whether or not you have new email. msgchk takes the same and - options that inc takes. + options that inc takes. - <command>show</>, <command>next</> and - <command>prev</>—displaying and moving through + <title><command>show</command>, <command>next</command> and + <command>prev</command>—displaying and moving through email - show is to show a letter in your current - folder. Like inc, show is a fairly - straightforward command. If you just type show - and hit return then it displays the current + show is to show a letter in your current + folder. Like inc, show is a fairly + straightforward command. If you just type show + and hit return then it displays the current message. You can also give specific message numbers to show: @@ -175,23 +175,23 @@ This would display message numbers 32, 45 and 56 right after each other. Unless you change the default behavior - show basically just does a more on the + show basically just does a more on the email message. - next is used to move onto the next message and - prev will go to the previous message. Both - commands have an implied show command so that when + next is used to move onto the next message and + prev will go to the previous message. Both + commands have an implied show command so that when you go to the next message it automatically displays it. - <command>scan</>—shows you a scan of your + <title><command>scan</command>—shows you a scan of your messages - scan will display a brief listing of the + scan will display a brief listing of the messages in your current folder. This is an example of what - the scan command will give you. + the scan command will give you. 30+ 01/16 "Jordan K. Hubbar Re: FBSD 2.1<<> Do you want a library instead of @@ -205,32 +205,32 @@ configurable. This is the typical default display. It gives you the message number, the date on the email, the sender, the subject line, and a sentence fragment from the very beginning - of the email if it can fit it. The + means that + of the email if it can fit it. The + means that message is the current message, so if you do a - show it will display that message. + show it will display that message. One useful option for scan is the option. This will list your messages with the highest message number first and lowest message - number last. Another useful option with scan is to + number last. Another useful option with scan is to have it read from a file. If you want to scan your incoming - mailbox on FreeBSD without having to inc it you + mailbox on FreeBSD without having to inc it you can do scan -file - /var/mail/username. This can be used - with any file that is in the mbox format. + /var/mail/username. This can be used + with any file that is in the mbox format. - <command>rmm</> and <command>rmf</>—remove the + <title><command>rmm</command> and <command>rmf</command>—remove the current message or folder - rmm is used to remove a mail message. The + rmm is used to remove a mail message. The default is typically to not actually remove the message but to rename the file to one that is ignored by the MH commands. You will need to through periodically and physically delete the - removed messages. + removed messages. - The rmf command is used to remove folders. + The rmf command is used to remove folders. This doesn't just rename the files but actually removes the from the hard drive so you should be careful when you use this command. @@ -240,8 +240,8 @@ A typical session of reading with MH The first thing that you will want to do is - inc your new mail. So at a shell prompt just type - in inc and hit return. + inc your new mail. So at a shell prompt just type + in inc and hit return. &prompt.user; inc @@ -255,7 +255,7 @@ This shows you the new email that has been added to your - mailbox. So the next thing to do is show the email + mailbox. So the next thing to do is show the email and move around. @@ -298,8 +298,8 @@ - The rmm removed the current message and the - next command moved me on to the next message. Now + The rmm removed the current message and the + next command moved me on to the next message. Now if I wanted to look at ten most recent messages so I could read one of them here is what I would do: @@ -320,7 +320,7 @@ Then if I wanted to read message number 27 I would do a - show 27 and it would be displayed. As you can + show 27 and it would be displayed. As you can probably tell from this sample session MH is pretty easy to use and looking through emails and displaying them is fairly intuitive and easy. @@ -337,19 +337,19 @@ the concept of folders. You have undoubtedly come across the folders concept using other email programs. MH has folders too. MH can even do sub-folders of a folder. One thing you should - keep in mind with MH is that when you ran inc for + keep in mind with MH is that when you ran inc for the first time and it asked you if it could create a - Mail directory it began storing everything in that + Mail directory it began storing everything in that directory. If you look at that directory you will find a - directory named inbox. The inbox + directory named inbox. The inbox directory houses all of your incoming mail that hasn't been thrown anywhere else. Whenever you create a new folder a new directory is going to - be created underneath your MH Mail directory, and + be created underneath your MH Mail directory, and messages in that folder are going to be stored in that directory. When new email comes in that new email is thrown - into your inbox directory with a file name that is + into your inbox directory with a file name that is equivalent to the message number. So even if you didn't have any of the MH tools to read your email you could still use standard UNIX commands to munge around in those directories and @@ -357,28 +357,28 @@ a lot of power with what you can do with your email. Just as you can use message lists like 23 16 - 42 with most MH commands there is a folder option you can + 42 with most MH commands there is a folder option you can specify with just about every MH command. If you do a - scan +freebsd it will scan your freebsd + scan +freebsd it will scan your freebsd folder, and your current folder will be changed to - freebsd. If you do a show +freebsd 23 16 - 42, show is going to switch to your - freebsd folder and display messages 23, 16 and 42. - So remember that + left it as inbox. - <command>pick</>—search email that matches certain + <title><command>pick</command>—search email that matches certain criteria - pick is one of the more complex commands in + pick is one of the more complex commands in the MH system. So you might want to read the - pick1 man + pick1 man page for a more thorough understanding. At its simplest level you can do something like @@ -392,12 +392,12 @@ - This will tell pick to look through every + This will tell pick to look through every single line in every message in your current folder and tell - you which message numbers it found the word pci - in. You can then show those messages and read them - if you wish or rmm them. You would have to specify - something like show 15 42 55-57 to display them + you which message numbers it found the word pci + in. You can then show those messages and read them + if you wish or rmm them. You would have to specify + something like show 15 42 55-57 to display them though. A slightly more useful thing to do is this: @@ -410,16 +410,16 @@ This will show you the same messages you just didn't have to work as hard to do it. The option is really an abbreviation of and - pick is just a sequence which contains the message + pick is just a sequence which contains the message numbers that matched. You can use sequences with just about - any MH command. So you could have done an rmm pick + any MH command. So you could have done an rmm pick and all those messages would be removed instead. You sequence can be named anything. If you run pick again it will overwrite the old sequence if you use the same name. Doing a pick -search can be a bit more time consuming than just searching for message from someone, - or to someone. So pick allows you to use the + or to someone. So pick allows you to use the following predefined search criteria: @@ -468,7 +468,7 @@ search for any other component in the header. (i.e. - to find all emails with a certain reply-to in the header) @@ -482,7 +482,7 @@ to get a list of all the email send to the FreeBSD hackers - mailing list. pick also allows you to group these + mailing list. pick also allows you to group these criteria in different ways using the following options: @@ -531,42 +531,42 @@ something called operator precedence. Remember in math how you evaluate from left to right and you do multiplication and division first and addition and subtraction second? MH has the - same type of rules for pick. It's fairly complex + same type of rules for pick. It's fairly complex so you might want to study the man page. This document is just to help you get acquainted with MH. - <command>folder</>, <command>folders</>, - <command>refile</>—three useful programs for folder + <title><command>folder</command>, <command>folders</command>, + <command>refile</command>—three useful programs for folder maintenance There are three programs which are primarily just for - manipulating your folders. The folder program is + manipulating your folders. The folder program is used to switch between folders, pack them, and list them. At its simplest level you can do a folder - +newfolder and you will be switched into - newfolder. From there on out all your MH - commands like comp, repl, - scan, and show will act on that - newfolder folder. + +newfolder and you will be switched into + newfolder. From there on out all your MH + commands like comp, repl, + scan, and show will act on that + newfolder folder. Sometimes when you are reading and deleting messages you - will develop holes in your folders. If you do a - scan you might just see messages 34, 35, 36, 43, + will develop holes in your folders. If you do a + scan you might just see messages 34, 35, 36, 43, 55, 56, 57, 80. If you do a folder -pack this will renumber all your messages so that there are no holes. It doesn't actually delete any messages though. So you may need to periodically go through and physically delete - rmm'd messages. + rmm'd messages. If you need statistics on your folders you can do a - folders or folder -all to list + folders or folder -all to list all your folders, how many messages they have, what the current message is in each one and so on. This line of stats it displays for all your folders is the same one you get when - you change to a folder with folder +foldername. A - folders command looks like this: + you change to a folder with folder +foldername. A + folders command looks like this: Folder # of messages ( range ); cur msg (other files) @@ -585,17 +585,17 @@ - The refile command is what you use to move + The refile command is what you use to move messages between folders. When you do something like - refile 23 +netfuture message number 23 is moved - into the netfuture folder. You could also do - something like refile 23 +netfuture/latest which + refile 23 +netfuture message number 23 is moved + into the netfuture folder. You could also do + something like refile 23 +netfuture/latest which would put message number 23 in a subfolder called - latest under the netfuture folder. + latest under the netfuture folder. If you want to keep a message in the current folder and link it you can do a refile -link 23 +netfuture - which would keep 23 in your current inbox but - also list in your netfuture folder. You are + which would keep 23 in your current inbox but + also list in your netfuture folder. You are probably beginning to realize some of the really powerful things you can do with MH. @@ -613,29 +613,29 @@ Subject: headers already in it. You are then sent into your editor where you fill in the header information and then type the body of your message below the dashed lines in the message. - Then to the whatnow program. When you are at the + Then to the whatnow program. When you are at the What now? prompt you can tell it to - send, list, edit, - edit, push, and quit. Most + send, list, edit, + edit, push, and quit. Most of these commands are self-explanatory. So the message sending process involves copying a component file, editing your email, - and then telling the whatnow program what to do with + and then telling the whatnow program what to do with your email. - <command>comp</>, <command>forw</>, - <command>reply</>—compose, forward or reply to a message + <title><command>comp</command>, <command>forw</command>, + <command>reply</command>—compose, forward or reply to a message to someone - The comp program has a few useful command line + The comp program has a few useful command line options. The most important one to know right now is the option. When MH is installed the default editor is usually a program called - prompter which comes with MH. It's not a very + prompter which comes with MH. It's not a very exciting editor and basically just gets the job done. So when you go to compose a message to someone you might want to use - comp -editor /usr/bin/vi/ or comp -editor - /usr/local/bin/pico/ instead. Once you have run + comp -editor /usr/bin/vi/ or comp -editor + /usr/local/bin/pico/ instead. Once you have run comp you are in your editor and you see something that looks like this: @@ -648,9 +648,9 @@ You need to put the person you are sending the mail to - after the To: line. It works the same way for the + after the To: line. It works the same way for the other headers also, so you would need to put your subject - after the Subject: line. Then you would just put + after the Subject: line. Then you would just put the body of your message after the dashed lines. It may seem a bit simplistic since a lot of email programs have special requesters that ask you for this information but there really @@ -667,55 +667,55 @@ You can now save this message and exit your editor. You - will see the What now? prompt and you can type in - send or s and hit - return. Then the FreeBSD core team will receive + will see the What now? prompt and you can type in + send or s and hit + return. Then the FreeBSD core team will receive their just rewards. As I mentioned earlier you can also use - other commands, for example quit if you don't want + other commands, for example quit if you don't want to send the message. - The forw command is stunningly similar. The + The forw command is stunningly similar. The big difference being that the message you are forwarding is automatically included in the outgoing message. When you run - forw it will forward your current message. You can + forw it will forward your current message. You can always tell it to forward something else by doing something - like forw 23 and then message number 23 will be + like forw 23 and then message number 23 will be put in your outgoing message instead of the current message. - Beyond those small differences forw functions - exactly the same as comp. You go through the exact + Beyond those small differences forw functions + exactly the same as comp. You go through the exact same message sending process. - The repl command will reply to whatever your + The repl command will reply to whatever your current message is, unless you give it a different message to - reply to. repl will do its best to go ahead and + reply to. repl will do its best to go ahead and fill in some of the email headers already. So you will notice - that the To: header already has the address of the - recipient in there. Also the Subject: line will + that the To: header already has the address of the + recipient in there. Also the Subject: line will already be filled in. You then go about the normal message composition process and you are done. One useful command line option to know here is the option. You - can use all, to, cc, - me after the option to have - repl automatically add the various addresses to + can use all, to, cc, + me after the option to have + repl automatically add the various addresses to the cc list in the message. You have probably noticed that the original message isn't included. This is because most MH setups are configured to do this from the start. - <filename>components</>, and - <filename>replcomps</>—components files for - <command>comp</> and <command>repl</> + <filename>components</filename>, and + <filename>replcomps</filename>—components files for + <command>comp</command> and <command>repl</command> - The components file is usually in + The components file is usually in /usr/local/lib/mh. You can copy that file into your MH Mail directory and edit to contain what you want it to contain. It is a fairly basic file. You have various email headers at the top, a dashed line and then nothing. The comp command just copies this - components file and then edits it. You can add + components file and then edits it. You can add any kind of valid RFC822 header you want. For instance you - could have something like this in your components + could have something like this in your components file: @@ -729,13 +729,13 @@ MH would then copy this components file and throw you into - your editor. The components file is fairly + your editor. The components file is fairly simple. If you wanted to have a signature on those messages you would just put your signature in that - components file. + components file. - The replcomps file is a bit more complex. The - default replcomps looks like this: + The replcomps file is a bit more complex. The + default replcomps looks like this: %(lit)%(formataddr %<{reply-to}%?{from}%?{sender}%?{return-path}%>)\ @@ -752,12 +752,12 @@ It's in the same basic format as the - components file but it contains quite a few extra - formatting codes. The %(lit) command makes room - for the address. The %(formataddr is a function + components file but it contains quite a few extra + formatting codes. The %(lit) command makes room + for the address. The %(formataddr is a function that returns a proper email address. The next part is %< which means if and the - {reply-to} means the reply-to field in the + {reply-to} means the reply-to field in the original message. So that might be translated this way: @@ -774,7 +774,7 @@ variables mean. All of the information on writing these format strings is in the MH-Format man page. The really nice thing is that once you have built your customized - replcomps file you won't need to touch it again. + replcomps file you won't need to touch it again. No other email program really gives you the power and flexibility that MH gives you. Number Four: Index: article.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO_8859-1/articles/multi-os/article.sgml,v retrieving revision 1.12 diff -u -r1.12 article.sgml --- article.sgml 2000/05/30 22:48:47 1.12 +++ article.sgml 2000/07/25 21:51:18 @@ -144,11 +144,11 @@ - /dev/wd0 (first physical hard disk) + /dev/wd0 (first physical hard disk) - /dev/wd1 (second hard disk) + /dev/wd1 (second hard disk) @@ -157,7 +157,7 @@ I boot from a MS-DOS or Windows 95 boot disk that - contains the FDISK.EXE utility and make a small + contains the FDISK.EXE utility and make a small 50 meg primary partition (35-40 for Windows 95, plus a little breathing room) on the first disk. Also create a larger partition on the second hard disk for my Windows @@ -166,7 +166,7 @@ I reboot and install Windows 95 (easier said than done) - on the C: partition. + on the C: partition. @@ -191,15 +191,15 @@ 1024th cylinder. (The 1024th cylinder is 528 megs into the disk with our hypothetical 720MB disks). I will use the rest of the hard drive (about 270 megs) for the - /usr and / slices if I wish. The + /usr and / slices if I wish. The rest of the second hard disk (size depends on the amount of my Windows application/data partition that I created in step - 1 can go to the /usr/src slice and swap + 1 can go to the /usr/src slice and swap space. - When viewed with the Windows 95 fdisk + When viewed with the Windows 95 fdisk utility, my hard drives should now look something like this: @@ -238,14 +238,14 @@ Install FreeBSD. I make sure to boot with my first hard - disk set at NORMAL in the BIOS. If it is not, + disk set at NORMAL in the BIOS. If it is not, I'll have the enter my true disk geometry at boot time (to get this, boot Windows 95 and consult Microsoft Diagnostics - (MSD.EXE), or check your BIOS) with the - parameter hd0=1416,16,63 where - 1416 is the number of cylinders on my hard - disk, 16 is the number of heads per track, - and 63 is the number of sectors per track on + (MSD.EXE), or check your BIOS) with the + parameter hd0=1416,16,63 where + 1416 is the number of cylinders on my hard + disk, 16 is the number of heads per track, + and 63 is the number of sectors per track on the drive. @@ -275,7 +275,7 @@ cylinder. If you install Windows 95 on an existing BSD system, it will - destroy the MBR, and you will have to reinstall your + destroy the MBR, and you will have to reinstall your previous boot manager. Boot Easy can be reinstalled by using the BOOTINST.EXE utility included in the \TOOLS directory on the CD-ROM, and via jayrich@sysc.com). FreeBSD+Win95: If you installed FreeBSD after Windows 95, - you should see DOS on the Boot Easy menu. This is + you should see DOS on the Boot Easy menu. This is Windows 95. If you installed Windows 95 after FreeBSD, read above. As long as your hard disk does not have 1024 cylinders you should not have a problem booting. If one of your partitions goes beyond the 1024th cylinder however, - and you get messages like invalid system disk + and you get messages like invalid system disk under DOS (Windows 95) and FreeBSD will not boot, try looking for a setting in your BIOS called > 1024 cylinder - support or NORMAL/LBA mode. DOS may need LBA + support or NORMAL/LBA mode. DOS may need LBA (Logical Block Addressing) in order to boot correctly. If the idea of switching BIOS settings every time you boot up doesn't appeal to you, you can boot FreeBSD through DOS via the - FBSDBOOT.EXE utility on the CD (It should find your + FBSDBOOT.EXE utility on the CD (It should find your FreeBSD partition and boot it.) FreeBSD+OS/2+Win95: Nothing new here. OS/2's boot manger @@ -399,7 +399,7 @@ (# of cylinders) × (# heads) × (63 - sectors/track) × (512 bytes/sect) + sectors/track) × (512 bytes/sect) For example, on my 1.6 Gig Western Digital AC31600 EIDE hard @@ -419,9 +419,9 @@ though: if you're using BIOS LBA (see ), you can't use just any program to get the physical geometry. This is because many programs (e.g. - MSD.EXE or FreeBSD fdisk) don't identify the + MSD.EXE or FreeBSD fdisk) don't identify the physical disk geometry; they instead report the - translated geometry (virtual numbers from using + translated geometry (virtual numbers from using LBA). Stay tuned for what that means. One other useful thing about these terms. Given 3 @@ -434,9 +434,9 @@ For those that are interested in more technical details, information on disk geometry, boot sectors, BIOSes, etc. can be found all over the net. Query Lycos, Yahoo, etc. for - boot sector or master boot record. + boot sector or master boot record. Among the useful info you'll find are Hale Landis's - How It Works document pack. See the How It Works document pack. See the section for a few pointers to this pack. @@ -449,21 +449,21 @@ On the first sector of your disk (Cyl 0, Head 0, Sector 1) lives the Master Boot Record (MBR). It contains a map of your - disk. It identifies up to 4 partitions, each of + disk. It identifies up to 4 partitions, each of which is a contiguous chunk of that disk. FreeBSD calls - partitions slices to avoid confusion with it's + partitions slices to avoid confusion with it's own partitions, but we won't do that here. Each partition can contain its own operating system. Each partition entry in the MBR has a Partition - ID, a Start Cylinder/Head/Sector, and an - End Cylinder/Head/Sector. The Partition ID + ID, a Start Cylinder/Head/Sector, and an + End Cylinder/Head/Sector. The Partition ID tells what type of partition it is (what OS) and the Start/End tells where it is. lists a smattering of some common Partition IDs. - Partition IDs</> + <title>Partition IDs @@ -515,7 +515,7 @@ Note that not all partitions are bootable (e.g. Extended DOS). Some are—some aren't. What makes a partition bootable is the configuration of the Partition Boot - Sector that exists at the beginning of each + Sector that exists at the beginning of each partition.When you configure your favorite boot manager, it looks up @@ -577,7 +577,7 @@ - 64 sectors/track, max (actually 63, 0 + 64 sectors/track, max (actually 63, 0 isn't available) Number Five: Index: article.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO_8859-1/articles/new-users/article.sgml,v retrieving revision 1.13 diff -u -r1.13 article.sgml --- article.sgml 2000/06/27 02:48:51 1.13 +++ article.sgml 2000/07/25 21:44:49 @@ -565,7 +565,7 @@ - CtrlL + CtrlL to redraw the screen @@ -573,36 +573,36 @@ - Ctrlb and - Ctrlf + Ctrlb and + Ctrlf go back and forward a screen, as they do with - more and view. + more and view. - Practice with vi in your home directory by - creating a new file with vi filename + Practice with vi in your home directory by + creating a new file with vi filename and adding and deleting text, saving the file, and calling it up - again. vi delivers some surprises because it's + again. vi delivers some surprises because it's really quite complex, and sometimes you'll inadvertently issue a command that will do something you don't expect. (Some people - actually like vi—it's more powerful than DOS - EDIT—find out about the :r command.) Use - Esc one or more times to be sure you're in command + actually like vi—it's more powerful than DOS + EDIT—find out about the :r command.) Use + Esc one or more times to be sure you're in command mode and proceed from there when it gives you trouble, save - often with :w, and use :q! to get out - and start over (from your last :w) when you need + often with :w, and use :q! to get out + and start over (from your last :w) when you need to. - Now you can cd to /etc, - su to root, use vi to edit the file + Now you can cd to /etc, + su to root, use vi to edit the file /etc/group, and add a user to wheel so the user has root privileges. Just add a comma and the user's login name to the end of the first line in the file, press - Esc, and use :wq to write the file to + Esc, and use :wq to write the file to disk and quit. Instantly effective. (You didn't put a space after the comma, did you?) @@ -625,7 +625,7 @@ will remove formatting codes and send the man page to the chmod.txt file instead of showing it on your screen. Now put a dos-formatted diskette in your floppy - drive a, su to root, and type + drive a, su to root, and type &prompt.root; /sbin/mount -t msdos /dev/fd0 /mnt @@ -636,7 +636,7 @@ /mnt.Now (you no longer need to be root, and you can type - exit to get back to being user jack) you can go to + exit to get back to being user jack) you can go to the directory where you created chmod.txt and copy the file to the floppy with: @@ -661,10 +661,10 @@ /sbin/dmesg is the boot log record, and it's useful to understand it because it shows what FreeBSD found when it booted up. If you ask questions on - freebsd-questions@FreeBSD.org or on a USENET + freebsd-questions@FreeBSD.org or on a USENET group—like FreeBSD isn't finding my tape drive, what do I do?—people will want to know what - dmesg has to say. + dmesg has to say. You can now dismount the floppy drive (as root) to get the disk out with @@ -679,7 +679,7 @@ Wordpad, or a word processor, make a minor change so the file has to be saved, and print as you normally would from DOS or Windows. Hope it works! man pages come out best if printed - with the dos print command. (Copying files from + with the dos print command. (Copying files from FreeBSD to a mounted dos partition is in some cases still a little risky.) @@ -687,15 +687,15 @@ an appropriate entry in /etc/printcap and creating a matching spool directory in /var/spool/output. If your printer is on - lpt0 (what dos calls LPT1), you may + lpt0 (what dos calls LPT1), you may only need to go to /var/spool/output and - (as root) create the directory lpd by typing: + (as root) create the directory lpd by typing: mkdir lpd, if it doesn't already exist. Then the printer should respond if it's turned on when the system is booted, and lp or lpr should send a file to the printer. Whether or not the file actually prints depends on configuring it, which is covered in the FreeBSD handbook. + URL="../../handbook/handbook.html">FreeBSD handbook. @@ -703,7 +703,7 @@ - df + df shows file space and mounted systems. @@ -711,27 +711,27 @@ - ps aux + ps aux - shows processes running. ps ax is a + shows processes running. ps ax is a narrower form. - rm filename + rm filename - remove filename. + remove filename. - rm -R dir + rm -R dir - removes a directory dir and all + removes a directory dir and all subdirectories—careful! @@ -750,7 +750,7 @@ - passwd + passwd to change user's password (or root's password) @@ -758,7 +758,7 @@ - man hier + man hier man page on the Unix file system @@ -766,7 +766,7 @@ - Use find to locate filename in + Use find to locate filename in /usr or any of its subdirectories with @@ -776,7 +776,7 @@ You can use * as a wildcard in - "filename" (which should be in + "filename" (which should be in quotes). If you tell find to search in / instead of /usr it will look for the file(s) on all mounted file systems, including the CDROM and the @@ -802,7 +802,7 @@ URL="http://www.cdrom.com/">Walnut Creek CDROM as well as the web site. The handbook tells you more about how to use them (get the package if it exists, with pkg_add - /cdrom/packages/All/packagename, where + /cdrom/packages/All/packagename, where packagename is the filename of the package). The cdrom has lists of the packages and ports with brief descriptions in cdrom/packages/index, @@ -813,10 +813,10 @@ programs and program names respectively. If you find the handbook too sophisticated (what with - lndir and all) on installing ports from the cdrom, + lndir and all) on installing ports from the cdrom, here's what usually works: - Find the port you want, say kermit. There will + Find the port you want, say kermit. There will be a directory for it on the cdrom. Copy the subdirectory to /usr/local (a good place for software you add that should be available to all users) with: @@ -833,16 +833,16 @@ Next, create the directory /usr/ports/distfiles if it doesn't already - exist using mkdir. Now check check + exist using mkdir. Now check check /cdrom/ports/distfiles for a file with a name that indicates it's the port you want. Copy that file to /usr/ports/distfiles; in recent versions you can skip this step, as FreeBSD will do it for you. In the - case of kermit, there is no distfile. + case of kermit, there is no distfile. - Then cd to the subdirectory of + Then cd to the subdirectory of /usr/local/kermit that has the file - Makefile. Type + Makefile. Type &prompt.root; make all install @@ -856,17 +856,17 @@ /cdrom/ports/distfiles, you will have to get the distfile using another machine and copy it to /usr/ports/distfiles from a floppy or your - dos partition. Read Makefile (with cat - or more or view) to find out where to go + dos partition. Read Makefile (with cat + or more or view) to find out where to go (the master distribution site) to get the file and what its name is. Its name will be truncated when downloaded to DOS, and after you get it into /usr/ports/distfiles - you'll have to rename it (with the mv command) to + you'll have to rename it (with the mv command) to its original name so it can be found. (Use binary file transfers!) Then go back to /usr/local/kermit, find the directory with - Makefile, and type make all - install. + Makefile, and type make all + install. The other thing that happens when installing ports or packages is that some other program is needed. If the @@ -874,10 +874,10 @@ unzip or whatever, you might need to install the package or port for unzip before you continue. - Once it's installed type rehash to make FreeBSD + Once it's installed type rehash to make FreeBSD reread the files in the path so it knows what's there. (If you - get a lot of path not found messages when you use - whereis or which, you might want to make additions + get a lot of path not found messages when you use + whereis or which, you might want to make additions to the list of directories in the path statement in .cshrc in your home directory. The path statement in Unix does the same kind of work it does in DOS, @@ -890,10 +890,10 @@ from their ftp site. (Netscape requires the X Window System.) There's now a FreeBSD version, so look around carefully. Just use gunzip - filename and tar xvf - filename on it, move the binary to + filename and tar xvf + filename on it, move the binary to /usr/local/bin or some other place binaries - are kept, rehash, and then put the following lines + are kept, rehash, and then put the following lines in .cshrc in each user's home directory or (easier) in /etc/csh.cshrc, the system-wide csh start-up file: @@ -901,11 +901,11 @@ setenv XKEYSYMDB /usr/X11R6/lib/X11/XKeysymDB setenv XNLSPATH /usr/X11R6/lib/X11/nls - + - This assumes that the file XKeysymDB and the - directory nls are in + This assumes that the file XKeysymDB and the + directory nls are in /usr/X11R6/lib/X11; if they're not, find them and put them there. @@ -977,7 +977,7 @@ you the tcsh as root, because the shell is part of the environment. You can make this permanent by adding it to your .tcshrc file as an alias with - alias su su -m. + alias su su -m. When tcsh starts up, it will read the @@ -1020,10 +1020,10 @@ Other As root, you can dismount the CDROM with - /sbin/umount /cdrom, take it out of the drive, + /sbin/umount /cdrom, take it out of the drive, insert another one, and mount it with - /sbin/mount_cd9660 /dev/cd0a /cdrom assuming - cd0a is the device name for your CDROM drive. The + /sbin/mount_cd9660 /dev/cd0a /cdrom assuming + cd0a is the device name for your CDROM drive. The most recent versions of FreeBSD let you mount the cdrom with just /sbin/mount /cdrom. @@ -1031,12 +1031,12 @@ CDROM disks—is useful if you've got limited space. What is on the live file system varies from release to release. You might try playing games from the cdrom. This involves using - lndir, which gets installed with the X Window + lndir, which gets installed with the X Window System, to tell the program(s) where to find the necessary files, because they're in the /cdrom file system instead of in /usr and its subdirectories, which is where they're expected to be. Read - man lndir. + man lndir. @@ -1049,6 +1049,6 @@ Fieber for helpful comments. Annelise Anderson, - andrsn@andrsn.stanford.edu + andrsn@andrsn.stanford.edu Number Six: Index: article.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO_8859-1/articles/programming-tools/article.sgml,v retrieving revision 1.11 diff -u -r1.11 article.sgml --- article.sgml 2000/06/14 13:18:43 1.11 +++ article.sgml 2000/07/25 21:48:27 @@ -44,10 +44,10 @@ FreeBSD offers an excellent development environment. Compilers for C, C++, and Fortran and an assembler come with the basic system, not to mention a Perl interpreter and classic Unix - tools such as sed and awk. If that is + tools such as sed and awk. If that is not enough, there are many more compilers and interpreters in the Ports collection. FreeBSD is very compatible with standards - such as POSIX and ANSI C, as well with + such as POSIX and ANSI C, as well with its own BSD heritage, so it is possible to write applications that will compile and run with little or no modification on a wide range of platforms. @@ -73,8 +73,8 @@ instruction. This section gives an overview of the two main ways in which you can give these instructions, or commands as they are usually called. One way - uses an interpreter, the other a - compiler. As human languages are too difficult for + uses an interpreter, the other a + compiler. As human languages are too difficult for a computer to understand in an unambiguous way, commands are usually written in one or other languages specially designed for the purpose. @@ -105,10 +105,10 @@ start if you have not done any programming before. This kind of environment is typically found with languages like Lisp, Smalltalk, Perl and Basic. It could also be argued that the - Unix shell (sh, csh) is itself an + Unix shell (sh, csh) is itself an interpreter, and many people do in fact write shell scripts to help with various - housekeeping tasks on their machine. Indeed, part + housekeeping tasks on their machine. Indeed, part of the original Unix philosophy was to provide lots of small utility programs that could be linked together in shell scripts to perform useful tasks. @@ -135,16 +135,16 @@ - BASIC + BASIC Short for Beginner's All-purpose Symbolic Instruction Code. Developed in the 1950s for teaching University students to program and provided with every self-respecting personal computer in the 1980s, - BASIC has been the first programming + BASIC has been the first programming language for many programmers. It's also the foundation - for Visual Basic. + for Visual Basic. The Bywater @@ -184,7 +184,7 @@ Very popular with system administrators for writing scripts; also often used on World Wide Web servers for - writing CGI scripts. + writing CGI scripts. The latest version (version 5) comes with FreeBSD. @@ -284,7 +284,7 @@ using separate programs, many commercial compiler makers have produced Integrated Development Environments (IDEs for short). FreeBSD does not have an - IDE as such; however it is possible to use Emacs + IDE as such; however it is possible to use Emacs for this purpose. This is discussed in . @@ -295,7 +295,7 @@ This section deals only with the GNU compiler for C and C++, since that comes with the base FreeBSD system. It can be - invoked by either cc or gcc. The + invoked by either cc or gcc. The details of producing a program with an interpreter vary considerably between interpreters, and are usually well covered in the documentation and on-line help for the @@ -324,9 +324,9 @@ understandable by humans. Allegedly. - To be strictly accurate, cc converts the + To be strictly accurate, cc converts the source code into its own, machine-independent - p-code instead of assembly language at + p-code instead of assembly language at this stage. @@ -361,20 +361,20 @@ - The word compiling is often used to refer to + The word compiling is often used to refer to just steps 1 to 4—the others are referred to as - linking. Sometimes step 1 is referred to as - pre-processing and steps 3-4 as - assembling. + linking. Sometimes step 1 is referred to as + pre-processing and steps 3-4 as + assembling. Fortunately, almost all this detail is hidden from you, as - cc is a front end that manages calling all these + cc is a front end that manages calling all these programs with the right arguments for you; simply typing &prompt.user; cc foobar.c - will cause foobar.c to be compiled by all the + will cause foobar.c to be compiled by all the steps above. If you have more than one file to compile, just do something like @@ -393,18 +393,18 @@ isn't. - There are lots and lots of options for cc, which + There are lots and lots of options for cc, which are all in the man page. Here are a few of the most important ones, with examples of how to use them. - + The output name of the file. If you do not use this - option, cc will produce an executable called - a.out. + option, cc will produce an executable called + a.out. The reasons for this are buried in the mists of @@ -432,7 +432,7 @@ - This will produce an object file (not an + This will produce an object file (not an executable) called foobar.o. This can be linked together with other object files into an executable. @@ -525,7 +525,7 @@ Turn off most, but not all, of the - non-ANSI C features provided by + non-ANSI C features provided by cc. Despite the name, it does not guarantee strictly that your code will comply to the standard. @@ -537,7 +537,7 @@ Turn off all - cc's non-ANSI C + cc's non-ANSI C features. @@ -1478,7 +1478,7 @@ listings of core files and sweat over machine code manuals, but now life is a bit easier. Incidentally, under FreeBSD and other 4.4BSD systems, a core file is called - progname.core instead of just + progname.core instead of just core, to make it clearer which program a core file belongs to. @@ -1771,7 +1771,7 @@ - Everything beginning with a ; is a comment + Everything beginning with a ; is a comment and is ignored by Emacs. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message