diff --git a/zh_TW.Big5/articles/Makefile b/zh_TW.Big5/articles/Makefile index d999776b7f..b9af7e008a 100644 --- a/zh_TW.Big5/articles/Makefile +++ b/zh_TW.Big5/articles/Makefile @@ -1,12 +1,13 @@ # $FreeBSD$ SUBDIR = SUBDIR+= contributing SUBDIR+= cvs-freebsd +SUBDIR+= freebsd-questions SUBDIR+= hubs SUBDIR+= mailing-list-faq SUBDIR+= pr-guidelines SUBDIR+= problem-reports DOC_PREFIX?= ${.CURDIR}/../.. .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/zh_TW.Big5/articles/freebsd-questions/Makefile b/zh_TW.Big5/articles/freebsd-questions/Makefile new file mode 100644 index 0000000000..3dfaecabc8 --- /dev/null +++ b/zh_TW.Big5/articles/freebsd-questions/Makefile @@ -0,0 +1,22 @@ +# +# $FreeBSD$ +# Original revision: 1.6 +# +# Article: How to get best results from the FreeBSD-questions mailing list + +MAINTAINER=chinsan.tw@gmail.com + +DOC?= article + +FORMATS?= html +WITH_ARTICLE_TOC?= YES + +INSTALL_COMPRESSED?= gz +INSTALL_ONLY_COMPRESSED?= + +SRCS= article.sgml + +URL_RELPREFIX?= ../../../.. +DOC_PREFIX?= ${.CURDIR}/../../.. + +.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/zh_TW.Big5/articles/freebsd-questions/article.sgml b/zh_TW.Big5/articles/freebsd-questions/article.sgml new file mode 100644 index 0000000000..fd50b7fb0e --- /dev/null +++ b/zh_TW.Big5/articles/freebsd-questions/article.sgml @@ -0,0 +1,627 @@ + +%articles.ent; +]> + + + +
+ + 如何在 FreeBSD-questions mailing list 上得到正解 + + + Greg + Lehey + + +
grog@FreeBSD.org
+ + + + $FreeBSD$ + + + &tm-attrib.freebsd; + &tm-attrib.microsoft; + &tm-attrib.netscape; + &tm-attrib.opengroup; + &tm-attrib.qualcomm; + &tm-attrib.general; + + + + 本文主要是給準備寫信到 FreeBSD-questions mailing list 的人提供一些參考。 + 我們會給你一些發問的技巧與建議，以便讓你的答案得到更有用的答覆。 + + 本文會定期發到 FreeBSD-questions mailing list 上。 + + + + + 簡介 + + FreeBSD-questions is a mailing list maintained by + the FreeBSD project to help people who have questions about the normal + use of FreeBSD. Another group, FreeBSD-hackers, + discusses more advanced questions such as future development + work. + + + The term hacker has nothing to do with breaking + into other people's computers. The correct term for the latter + activity is cracker, but the popular press has not found + out yet. The FreeBSD hackers disapprove strongly of cracking + security, and have nothing to do with it. For a longer description of + hackers, see Eric Raymond's How To Become + A Hacker + + + This is a regular posting aimed to help both those seeking advice + from FreeBSD-questions (the newcomers), and also those + who answer the questions (the hackers). + + Inevitably there is some friction, which stems from the different + viewpoints of the two groups. The newcomers accuse the hackers of being + arrogant, stuck-up, and unhelpful, while the hackers accuse the + newcomers of being stupid, unable to read plain English, and expecting + everything to be handed to them on a silver platter. Of course, there is + an element of truth in both these claims, but for the most part these + viewpoints come from a sense of frustration. + + In this document, I would like to do something to relieve this + frustration and help everybody get better results from + FreeBSD-questions. In the following section, I recommend how to submit + a question; after that, we will look at how to answer one. + + + + How to subscribe to FreeBSD-questions + + FreeBSD-questions is a mailing list, so you need mail access. Point + your WWW browser to the information page of the FreeBSD-questions mailing list. + In the section titled Subscribing to freebsd-questions fill + in the Your email address field; the other fields are optional. + + + + The password fields in the subscription form provide only mild + security, but should prevent others from messing with your + subscription. Do not use a valuable password as + it will occasionally be emailed back to you in cleartext. + + + You will receive a confirmation message from + mailman; follow the included instructions + to complete your subscription. + + Finally, when you get the Welcome message from + mailman telling you the details of the list + and subscription area password, please save it. + If you ever should want to leave the list, you will need the information + there. See the next section for more details. + + + + How to unsubscribe from FreeBSD-questions + + When you subscribed to FreeBSD-questions, you got a welcome message + from mailman. In this message, amongst + other things, it told you how to unsubscribe. Here is a typical + message: + + Welcome to the freebsd-questions@freebsd.org mailing list! + +To post to this list, send your email to: + + freebsd-questions@freebsd.org + +General information about the mailing list is at: + + http://lists.freebsd.org/mailman/listinfo/freebsd-questions + +If you ever want to unsubscribe or change your options (e.g., switch to +or from digest mode, change your password, etc.), visit your +subscription page at: + +http://lists.freebsd.org/mailman/options/freebsd-questions/grog%40lemsi.de + +You can also make such adjustments via email by sending a message to: + + freebsd-questions-request@freebsd.org + +with the word `help' in the subject or body (don't include the +quotes), and you will get back a message with instructions. + +You must know your password to change your options (including changing +the password, itself) or to unsubscribe. It is: + + 12345 + +Normally, Mailman will remind you of your freebsd.org mailing list +passwords once every month, although you can disable this if you +prefer. This reminder will also include instructions on how to +unsubscribe or change your account options. There is also a button on +your options page that will email your current password to you. + + From the URL specified in your Welcome message you + may visit the Account management page and enter a request + to Unsubscribe you from FreeBSD-questions mailing + list. + + A confirmation message will be sent to you from + mailman; follow the included instructions + to finish unsubscribing. + + If you have done this, and you still can not figure out what + is going on, send a message to + freebsd-questions-request@FreeBSD.org, and they will + sort things out for you. Do not send a message to + FreeBSD-questions: they can not help you. + + + + Should I ask <literal>-questions</literal> or + <literal>-hackers</literal>? + + Two mailing lists handle general questions about FreeBSD, + FreeBSD-questions and + FreeBSD-hackers. In some cases, it is not really + clear which group you should ask. The following criteria should help + for 99% of all questions, however: + + + + If the question is of a general nature, ask + FreeBSD-questions. Examples might be questions + about installing FreeBSD or the use of a particular &unix; + utility. + + + + If you think the question relates to a bug, but you are not sure, + or you do not know how to look for it, send the message to + FreeBSD-questions. + + + + If the question relates to a bug, and you are + sure that it is a bug (for example, you can + pinpoint the place in the code where it happens, and you maybe have + a fix), then send the message to + FreeBSD-hackers. + + + + If the question relates to enhancements to FreeBSD, and you + can make suggestions about how to implement them, then send the + message to FreeBSD-hackers. + + + + There are also a number of other specialized mailing lists, for + example FreeBSD-isp, which caters to the interests of + ISPs (Internet Service Providers) who run FreeBSD. If you happen to be + an ISP, this does not mean you should automatically send your questions + to FreeBSD-isp. The criteria above still apply, and + it is in your interest to stick to them, since you are more likely to get + good results that way. + + + + Before submitting a question + + You can (and should) do some things yourself before asking a question + on one of the mailing lists: + + + + Try solving the problem on your own. If you post a question which + shows that you have tried to solve the problem, your question will + generally attract more positive attention from people reading it. + Trying to solve the problem yourself will also enhance your understanding + of FreeBSD, and will eventually let you use your knowledge to help others + by answering questions posted to the mailing lists. + + + + + Read the manual pages, and the FreeBSD documentation (either + installed in /usr/doc or accessible via WWW at + ), especially the + handbook + and the FAQ. + + + + + Browse and/or search the archives for the mailing list, to see if your + question or a similar one has been asked (and possibly answered) on the + list. You can browse and/or search the mailing list archives + at + and + respectively. This can be done at other WWW sites as well, for example + at . + + + + + Use a search engine such as Google + or Yahoo to find answers to your question. + Google even has a BSD-specific search interface. + + + + + + + How to submit a question + + When submitting a question to FreeBSD-questions, consider the + following points: + + + + 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 is perfectly possible to send a + message to FreeBSD-questions and not get an answer even if you + follow these rules. It is much more possible to not get an answer if + you do not. In the rest of this document, we will look at how to get + the most out of your question to FreeBSD-questions. + + + + Not everybody who answers FreeBSD questions reads every message: + they look at the subject line and decide whether it interests them. + Clearly, it is in your interest to specify a subject. FreeBSD + problem or Help are not enough. If you provide no subject at + all, many people will not bother reading it. If your subject is not + specific enough, the people who can answer it may not read + it. + + + + Format your message so that it is legible, and + PLEASE DO NOT SHOUT!!!!!. We appreciate that a lot of people do not + speak English as their first language, and we try to make + allowances for that, but it is really painful to try to read a + message written full of typos or without any line breaks. + + Do not underestimate the effect that a poorly formatted mail + message has, not just on the FreeBSD-questions mailing list. + Your mail message is all people see of you, and if it is poorly + formatted, one line per paragraph, badly spelt, or full of + errors, it will give people a poor impression of you. + + 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: + + + + cc:Mail + + + + &eudora; + + + + exmh + + + + µsoft; Exchange + + + + µsoft; Internet Mail + + + + µsoft; &outlook; + + + + &netscape; + + + + 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 do not get on very well with + MIME. + + + + 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 does not come before the first answer, they + may assume they missed it and not bother to look. + + + + Do not include unrelated questions in the same message. Firstly, + a long message tends to scare people off, and secondly, it is more + difficult to get all the people who can answer all the questions to + read the message. + + + + Specify as much information as possible. This is a difficult + area, and we need to expand on what information you need to submit, + but here is a start: + + + + In nearly every case, it is important to know the version of + FreeBSD you are running. This is particularly the case for + FreeBSD-CURRENT, where you should also specify the date of the + sources, though of course you should not be sending questions + about -CURRENT to FreeBSD-questions. + + + With any problem which could be + hardware related, tell us about your hardware. In case of + doubt, assume it is possible that it is hardware. What kind of + CPU are you using? How fast? What motherboard? How much + memory? What peripherals? + + There is a judgement call here, of course, but the output of + the &man.dmesg.8; command can frequently be very useful, since it + tells not just what hardware you are running, but what version of + FreeBSD as well. + + + + If you get error messages, do not say I get error + messages, say (for example) I get the error + message 'No route to host'. + + + + If your system panics, do not say My system + panicked, say (for example) my system panicked + with the message 'free vnode isn't'. + + + + If you have difficulty installing FreeBSD, please tell us + what hardware you have. In particular, it is important to know + the IRQs and I/O addresses of the boards installed in your + machine. + + + + If 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? + + + + + + A lot of the information you need to supply is the output of + programs, such as &man.dmesg.8;, or console messages, which usually + appear in /var/log/messages. Do not try to copy + this information by typing it in again; it is a real pain, and you are + bound to make a mistake. To send log file contents, either make a + copy of the file and use an editor to trim the information to what + is relevant, or cut and paste into your message. For the output of + programs like &man.dmesg.8;, redirect the output to a file and + include that. For example, + + &prompt.user; dmesg > /tmp/dmesg.out + + This redirects the information to the file + /tmp/dmesg.out. + + + + If you do all this, and you still do not 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 do not get an answer after, say, a week, it + might help to re-send the message. If you do not get an answer to + your second message, though, you are probably not going to get one + from this forum. Resending the same message again and again will + only make you unpopular. + + + + To summarize, let's assume you know the answer to the following + question (yes, it is the same one in each case). + You choose which of these two questions you would be more prepared to + answer: + + + Message 1 + + Subject: HELP!!?!?? +I just can't get hits damn silly FereBSD system to +workd, and Im really good at this tsuff, but I have never seen +anythign sho difficult to install, it jst wont work whatever I try +so why don't you guys tell me what I doing wrong. + + + + Message 2 + + Subject: Problems installing FreeBSD + +I've just got the FreeBSD 2.1.5 CDROM from Walnut Creek, and I'm having a lot +of difficulty installing it. I have a 66 MHz 486 with 16 MB of +memory and an Adaptec 1540A SCSI board, a 1.2GB Quantum Fireball +disk and a Toshiba 3501XA CDROM drive. The installation works just +fine, but when I try to reboot the system, I get the message +Missing Operating System. + + + + + 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: + + + + You include the original message text, so people will know what + you are talking about. Do not forget to trim unnecessary text out, + though. + + + + The text in the subject line stays the same (you did remember to + put one in, did you not?). Many mailers will sort messages by + subject. This helps group messages together. + + + + 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. + + + + + + How to answer a question + + + Before you answer a question to FreeBSD-questions, consider: + + + + A lot of the points on submitting questions also apply to + answering questions. Read them. + + + + Has somebody already answered the question? The easiest way to + check this is to sort your incoming mail by subject: then + (hopefully) you will see the question followed by any answers, all + together. + + If somebody has already answered it, it does not automatically + mean that you should not send another answer. But it makes sense to + read all the other answers first. + + + + Do you have something to contribute beyond what has already been + said? In general, Yeah, me too answers do not help + much, although there are exceptions, like when somebody is + describing a problem he is having, and he does not know whether it is + his fault or whether there is something wrong with the hardware or + software. If you do send a me too answer, you should + also include any further relevant information. + + + + Are you sure you understand the question? Very frequently, the + person who asks the question is confused or does not express himself + very well. Even with the best understanding of the system, it is + easy to send a reply which does not answer the question. This + does not help: you will leave the person who submitted the question + more frustrated or confused than ever. If nobody else answers, and + you are not too sure either, you can always ask for more + information. + + + + Are you sure your answer is correct? + If not, wait a day or so. If nobody else comes up with a + better answer, you can still reply and say, for example, I + do not know if this is correct, but since nobody else has + replied, why don't you try replacing your ATAPI CDROM with + a frog?. + + + + Unless there is a good reason to do otherwise, reply to the + sender and to FreeBSD-questions. Many people on the + FreeBSD-questions are lurkers: they learn by reading + messages sent and replied to by others. If you take a message which + is of general interest off the list, you are depriving these people + of their information. Be careful with group replies; lots of people + send messages with hundreds of CCs. If this is the case, be sure to + trim the Cc: lines appropriately. + + + + Include relevant text from the original message. Trim it to the + minimum, but do not overdo it. It should still be possible for + somebody who did not read the original message to understand what + you are talking about. + + + + Use some technique to identify which text came from the original + message, and which text you add. I personally find that prepending + > to the original message + works best. Leaving white space after the + > and leave empty lines + between your text and the original text both make the result more + readable. + + + + Put your response in the correct place (after the text to which + it replies). It is very difficult to read a thread of responses + where each reply comes before the text to which it replies. + + + + Most mailers change the subject line on a reply by prepending a + text such as Re: . If your mailer does not do it + automatically, you should do it manually. + + + + If the submitter did not abide by format conventions (lines too + long, inappropriate subject line), please fix + it. In the case of an incorrect subject line (such as + HELP!!??), change the subject line to (say) + Re: Difficulties with sync PPP (was: HELP!!??). That + way other people trying to follow the thread will have less + difficulty following it. + + In such cases, it is appropriate to say what you did and why you + did it, but try not to be rude. If you find you can not answer + without being rude, do not answer. + + If you just want to reply to a message because of its bad + format, just reply to the submitter, not to the list. You can just + send him this message in reply, if you like. + + + +
+ + diff --git a/zh_TW.Big5/books/handbook/eresources/chapter.sgml b/zh_TW.Big5/books/handbook/eresources/chapter.sgml index f8b0b43aa8..2838fcd570 100644 --- a/zh_TW.Big5/books/handbook/eresources/chapter.sgml +++ b/zh_TW.Big5/books/handbook/eresources/chapter.sgml @@ -1,1747 +1,1711 @@ 網際網路上的資源 進展飛快的 FreeBSD 使得現有的印刷、平面媒體跟不上它的最新進度！ 反而數位版本的資源，也許有時並不是最好，但通常是唯一一個跟上最新進展的方式。 正由於 FreeBSD 是來自於許多志工的努力，所以廣大的使用者群也通常扮演著 IT技術支援部門 的角色。 只要善用電子郵件和 USENET 新聞群組就可以很快速地聯繫這些社群了。 以下簡介與 FreeBSD 社群搭上線的主要方式。 若你還知道其他這裡沒有列出的資源，請告知 &a.doc;，以便我們更新。 郵遞論壇(Mailing Lists) - Though many of the FreeBSD development members read USENET, we - cannot always guarantee that we will get to your questions in a timely - fashion (or at all) if you post them only to one of the - comp.unix.bsd.freebsd.* groups. By addressing your - questions to the appropriate mailing list you will reach both us and a - concentrated FreeBSD audience, invariably assuring a better (or at least - faster) response. - - The charters for the various lists are given at the bottom of this - document. Please read the charter before joining or sending - mail to any list. Most of our list subscribers now receive - many hundreds of FreeBSD related messages every day, and by setting down - charters and rules for proper use we are striving to keep the - signal-to-noise ratio of the lists high. To do less would see the - mailing lists ultimately fail as an effective communications medium for - the project. - - When in doubt about what list to post a question to, see How to get best results from - the FreeBSD-questions mailing list. - - Before posting to any list, please learn about how to best use - the mailing lists, such as how to help avoid frequently-repeated - discussions, by reading the - Mailing List Frequently Asked Questions (FAQ) document. - - Archives are kept for all of the mailing lists and can be searched - using the FreeBSD World - Wide Web server. The keyword searchable archive offers an - excellent way of finding answers to frequently asked questions and - should be consulted before posting a question. + 雖然，大部份的 FreeBSD 開發人員都有看 USENET 新聞群組， + 我們也不能保證我們永遠可以及時得知您的問題。 + 尤其是，若您只在 + comp.unix.bsd.freebsd.* 其中群組內發問的話。 + 建議您將問題發到適當的郵遞論壇(mailing list)上，不但可以同時讓 FreeBSD + 開發者和其他看倌們知道，通常也可以得到一個較好的(最起碼會比較快)的回應。 + + 本文後面介紹的是各式不同的郵遞論壇、討論規則(charter)。 + 在訂閱任何 list 之前，請先閱讀討論規則。 + 訂閱這些 list 的人們現在每天都會收到數百封 FreeBSD 相關信件。 + 而討論規則的制訂，則有助於提升彼此討論品質。 + 否則，這些討論 FreeBSD 的 list 終將陷入溝通不良，而失去其原本美意。 + + 對於該在哪個 list 發問覺得很疑惑的時候，就來看看 《如何在 FreeBSD-questions mailing list 上得到正解》 + 一文吧 + + 在發表問題、回覆到 list 之前，請先讀過 + + FreeBSD Mailing Lists 常見問答集(FAQ) 一文以學會如何善用 mailing list + ，才能避免像是經常重複的月經文、戰文之類的事情發生。 + + 全部的 mailing lists 討論記錄都可以在 + FreeBSD WWW主機 上找到。它提供了很棒的關鍵字搜尋功能，可讓您找到常用問答集(FAQ) + 。而在 mailing lists 上發問之前，也請先搜尋是否已有解答。 - List Summary + List 一覽表 - General lists: The following are general - lists which anyone is free (and encouraged) to join: + 一般論壇： 以下的 list 都是一般性質，而且大家可以自由地參與， + 我們也鼓勵大家訂閱： - List - Purpose + List 名稱 + 目的 &a.cvsall.name; - Changes made to the FreeBSD source tree + 所有的 FreeBSD 提交(commit)記錄 &a.advocacy.name; - FreeBSD Evangelism + FreeBSD 惡魔福音電台 &a.announce.name; - Important events and project milestones + 公布重要事件、計劃里程碑 &a.arch.name; - Architecture and design discussions + 架構研發討論 &a.bugbusters.name; - Discussions pertaining to the maintenance of the FreeBSD - problem report database and related tools + FreeBSD 問題回報(PR)資料庫的維護議題與工具 &a.bugs.name; - Bug reports + Bug 回報 &a.chat.name; - Non-technical items related to the FreeBSD - community + 非技術交流的 FreeBSD 社群聊天區 &a.current.name; - Discussion concerning the use of - &os.current; + 討論 &os.current; 版本的 FreeBSD &a.isp.name; - Issues for Internet Service Providers using - FreeBSD + FreeBSD 的 ISP 業者技術交流區 &a.jobs.name; - FreeBSD employment and consulting - opportunities + FreeBSD 人力銀行 &a.policy.name; - FreeBSD Core team policy decisions. Low volume, and - read-only + FreeBSD Core team 的 policy 方針討論區。這裡文章不多，且只限 core team 才可發言。 &a.questions.name; - User questions and technical support + 使用問題及技術支援 &a.security-notifications.name; - Security notifications + 安全漏洞通知 &a.stable.name; - Discussion concerning the use of - &os.stable; + 討論 &os.stable; 版本的 FreeBSD &a.test.name; - Where to send your test messages instead of one of - the actual lists + 論壇新手發表區，這裡可以讓你小試身手 - Technical lists: The following lists are for - technical discussion. You should read the charter for each list - carefully before joining or sending mail to one as there are firm - guidelines for their use and content. + 技術論壇： 以下 list 主是要以探討技術問題為主， + 在加入訂閱及討論之前，請務必仔細閱讀每個 list 的版規(charter)， + 因為它們的討論內容都有很嚴謹的限制。 - List - Purpose + List 名稱 + 目的 &a.acpi.name; - ACPI and power management development + ACPI 以及電力管理議題 &a.afs.name; - Porting AFS to FreeBSD + 移植 AFS 到 FreeBSD &a.aic7xxx.name; - Developing drivers for the &adaptec; AIC 7xxx + 研發 &adaptec; AIC 7xxx 的驅動程式 &a.alpha.name; - Porting FreeBSD to the Alpha + 移植 FreeBSD 到 Alpha 系統架構 &a.amd64.name; - Porting FreeBSD to AMD64 systems + 移植 FreeBSD 到 AMD64 系統架構 &a.apache.name; - Discussion about Apache related ports + 探討 Apache 相關的 ports 議題 &a.arm.name; - Porting FreeBSD to &arm; processors + 移植 FreeBSD 到 &arm; CPU 架構 &a.atm.name; - Using ATM networking with FreeBSD + 在 FreeBSD 上使用 ATM 網路 &a.audit.name; - Source code audit project + Source code 的稽核(audit)計劃 &a.binup.name; - Design and development of the binary update system + 研發 binary 的升級方式 &a.bluetooth.name; - Using &bluetooth; technology in FreeBSD + 在 FreeBSD 中使用藍芽(&bluetooth;)技術 &a.cluster.name; - Using FreeBSD in a clustered environment + 把 FreeBSD 在叢集架構環境(clustered environment)的運用 &a.cvsweb.name; - CVSweb maintenance + CVSweb 的維護 &a.database.name; - Discussing database use and development under - FreeBSD + 討論各式資料庫在 FreeBSD 的研發、運用 &a.doc.name; - Creating FreeBSD related documents + 撰寫 FreeBSD 相關文件 &a.drivers.name; - Writing device drivers for &os; + 撰寫 &os; 用的驅動程式 &a.eclipse.name; - FreeBSD users of Eclipse IDE, tools, rich client - applications and ports. + FreeBSD 的 Eclipse IDE 工具愛用者交流 &a.emulation.name; - Emulation of other systems such as - Linux/&ms-dos;/&windows; + 在 FreeBSD 上模擬其他系統，如：Linux、&ms-dos;、&windows; &a.firewire.name; - FreeBSD &firewire; (iLink, IEEE 1394) technical - discussion + FreeBSD 的 &firewire; (iLink, IEEE 1394) 方面技術交流 &a.fs.name; - File systems + 檔案系統的探討、研發 &a.geom.name; - GEOM-specific discussions and implementations + GEOM 議題的探討、研發 &a.gnome.name; - Porting GNOME and GNOME applications + 移植 GNOME 及 GNOME 相關應用軟體 &a.hackers.name; - General technical discussion + 一般技術議題的探討 &a.hardware.name; - General discussion of hardware for running - FreeBSD + FreeBSD 上的各式硬體問題交流 &a.i18n.name; - FreeBSD Internationalization + FreeBSD 的多語化(Internationalization) &a.ia32.name; - FreeBSD on the IA-32 (&intel; x86) platform + FreeBSD 在 IA-32 (&intel; x86) 平台上的使用探討 &a.ia64.name; - Porting FreeBSD to &intel;'s upcoming IA64 systems + 移植 FreeBSD 到 &intel; 的未來 IA64 平台架構 &a.ipfw.name; - Technical discussion concerning the redesign of the IP - firewall code + 對 ipfw(IP firewall) 的技術探討 &a.isdn.name; - ISDN developers + ISDN 研發 &a.java.name; - &java; developers and people porting &jdk;s to - FreeBSD + &java; 程式開發者以及移植 &jdk;s 到 FreeBSD 上 &a.kde.name; - Porting KDE and KDE applications + 移植 KDE 以及 KDE 相關應用程式 &a.lfs.name; - Porting LFS to FreeBSD + 移植 LFS 到 FreeBSD &a.libh.name; - The second generation installation and package - system + 新世代的安裝、打包套件機制 &a.mips.name; - Porting FreeBSD to &mips; + 移植 FreeBSD 到 &mips; &a.mobile.name; - Discussions about mobile computing + 關於各類 mobile computing(比如：筆記型電腦)的研討 &a.mozilla.name; - Porting Mozilla to FreeBSD + 把 Mozilla 軟體移植到 FreeBSD &a.multimedia.name; - Multimedia applications + 各式影音運用、軟體 &a.newbus.name; - Technical discussions about bus architecture + 各式 bus 架構的技術探討 &a.net.name; - Networking discussion and TCP/IP source code + 網路運用探討與 TCP/IP source code &a.openoffice.name; - Porting OpenOffice.org and - &staroffice; to FreeBSD + 移植 OpenOffice.org 及 + &staroffice; 到 FreeBSD &a.performance.name; - Performance tuning questions for high - performance/load installations + 在高效能/負荷環境下的效能調校(tuning)議題 &a.perl.name; - Maintenance of a number of - Perl-related ports + 探討 Perl 相關 ports 的維護 &a.pf.name; - Discussion and questions about the packet filter - firewall system + pf(packet filter) 防火牆機制的探討 &a.platforms.name; - Concerning ports to non &intel; architecture - platforms + 討論著重於移植 port 到非 &intel; 架構平台的議題 &a.ports.name; - Discussion of the Ports Collection + 關於 Ports Collection 的運用、探討 &a.ports-bugs.name; - Discussion of the ports bugs/PRs + ports 相關的 bugs/PRs &a.ppc.name; - Porting FreeBSD to the &powerpc; + 移植 FreeBSD 到 &powerpc; 系統架構 &a.proliant.name; - Technical discussion of FreeBSD on HP ProLiant server platforms + FreeBSD 在 HP ProLiant 主機平台的使用交流 &a.python.name; - FreeBSD-specific Python issues + Python 在 FreeBSD 上使用的各式議題。 &a.qa.name; - Discussion of Quality Assurance, usually pending a release + QA(Quality Assurance)討論，通常會決定是否已經到達可以 release 的程度 &a.rc.name; - Discussion related to the rc.d system and its development + rc.d 機制的討論、研發 &a.realtime.name; - Development of realtime extensions to FreeBSD + FreeBSD 上 realtime extensions 的研發 &a.scsi.name; - The SCSI subsystem + SCSI 方面議題 &a.security.name; - Security issues affecting FreeBSD + FreeBSD 安全漏洞議題 &a.small.name; - Using FreeBSD in embedded applications + 在嵌入式硬體環境的應用、探討 &a.smp.name; - Design discussions for [A]Symmetric - MultiProcessing + CPU 對稱多工處理(SMP, [A]Symmetric Multiprocessing)的應用、研討 &a.sparc.name; - Porting FreeBSD to &sparc; based systems + 移植 FreeBSD 到 &sparc; 平台架構 &a.standards.name; - FreeBSD's conformance to the C99 and the &posix; - standards + FreeBSD 與 C99 及 &posix標準的相容議題 &a.threads.name; - Threading in FreeBSD + FreeBSD 上的 Threading 運用、探討 &a.testing.name; - FreeBSD Performance and Stability Tests + FreeBSD 的效能與穩定性測試 &a.tokenring.name; - Support Token Ring in FreeBSD + FreeBSD 的 Token Ring 支援的應用、探討 &a.usb.name; - Discussing &os; support for USB + &os; 的 USB 支援的應用、探討 &a.vuxml.name; - Discussion on VuXML infrastructure + VuXML 漏洞通報架構的探討 &a.x11.name; - Maintenance and support of X11 on FreeBSD + X11 在 FreeBSD 的運用 - Limited lists: The following lists are for - more specialized (and demanding) audiences and are probably not of - interest to the general public. It is also a good idea to establish a - presence in the technical lists before joining one of these limited - lists so that you will understand the communications etiquette involved. + 有訂閱限制的論壇： 以下的 lists 是針對一些特定要求的讀者而設， + 而且並不適合當成是一般的公開討論區。 + 您最好先在某些技術討論區參與一段時間的討論後，再選擇訂閱這些有限制的論壇。 + 因為如此一來，您可以了解到在這些討論區發言所須的禮儀。 - List - Purpose + List 名稱 + 目的 &a.hubs.name; - People running mirror sites (infrastructural - support) + 映射站台(mirror)的交流討論區 &a.usergroups.name; - User group coordination + 社群間的協調 &a.vendors.name; Vendors pre-release coordination &a.www.name; - Maintainers of www.FreeBSD.org + www.FreeBSD.org 的管理維護 - Digest lists: All of the above lists - are available in a digest format. Once subscribed to a list, - you can change your digest options in your account options - section. + 論壇的摘要版： 上述的各 lists 都有摘要版(digest)， + 在訂閱 list 之後，就可以先以自己帳號登入，然後個人訂閱選項那邊改為摘要版即可。 - CVS lists: The following lists are for people - interested in seeing the log messages for changes to various areas of - the source tree. They are Read-Only lists and - should not have mail sent to them. + CVS lists: 以下的 lists 是提供給想要看各個 tree 的提交(commit)紀錄， + 請注意：他們是 唯讀(Read-Only) 性質的 list + ，而且不能寄信給這。 - List - Source area - Area Description (source for) + List 名稱 + Source 區域 + 本區簡介 (source for) &a.cvsall.name; /usr/(CVSROOT|doc|ports|projects|src) - All changes to any place in the tree (superset of other CVS commit lists) + 全部的變更記錄(包括各類 CVS commit) &a.cvs-doc.name; /usr/(doc|www) - All changes to the doc and www trees + doc 及 www trees 的所有變更紀錄 &a.cvs-ports.name; /usr/ports - All changes to the ports tree + ports tree 的所有變更紀錄 &a.cvs-projects.name; /usr/projects - All changes to the projects tree + projects tree 的所有變更紀錄 &a.cvs-src.name; /usr/src - All changes to the src tree + src tree 的所有變更紀錄 - How to Subscribe + 要如何訂閱 - To subscribe to a list, click on the list name above or - go to &a.mailman.lists.link; - and click on the list that you are interested in. The list - page should contain all of the necessary subscription - instructions. + 要訂閱 list 的話，請以滑鼠按下上述 list 名稱， + 或是到 &a.mailman.lists.link; 然後即可挑選有興趣的 list 來訂閱了， + 該網頁會指示你如何進行訂閱的步驟。 To actually post to a given list you simply send mail to listname@FreeBSD.org. It will then be redistributed to mailing list members world-wide. To unsubscribe yourself from a list, click on the URL found at the bottom of every email received from the list. It is also possible to send an email to listname-unsubscribe@FreeBSD.org to unsubscribe yourself. Again, we would like to request that you keep discussion in the technical mailing lists on a technical track. If you are only interested in important announcements then it is suggested that you join the &a.announce;, which is intended only for infrequent traffic. List Charters All FreeBSD mailing lists have certain basic rules which must be adhered to by anyone using them. Failure to comply with these guidelines will result in two (2) written warnings from the FreeBSD Postmaster postmaster@FreeBSD.org, after which, on a third offense, the poster will removed from all FreeBSD mailing lists and filtered from further posting to them. We regret that such rules and measures are necessary at all, but today's Internet is a pretty harsh environment, it would seem, and many fail to appreciate just how fragile some of its mechanisms are. Rules of the road: The topic of any posting should adhere to the basic charter of the list it is posted to, e.g. if the list is about technical issues then your posting should contain technical discussion. Ongoing irrelevant chatter or flaming only detracts from the value of the mailing list for everyone on it and will not be tolerated. For free-form discussion on no particular topic, the &a.chat; is freely available and should be used instead. No posting should be made to more than 2 mailing lists, and only to 2 when a clear and obvious need to post to both lists exists. For most lists, there is already a great deal of subscriber overlap and except for the most esoteric mixes (say -stable & -scsi), there really is no reason to post to more than one list at a time. If a message is sent to you in such a way that multiple mailing lists appear on the Cc line then the Cc line should also be trimmed before sending it out again. You are still responsible for your own cross-postings, no matter who the originator might have been. Personal attacks and profanity (in the context of an argument) are not allowed, and that includes users and developers alike. Gross breaches of netiquette, like excerpting or reposting private mail when permission to do so was not and would not be forthcoming, are frowned upon but not specifically enforced. However, there are also very few cases where such content would fit within the charter of a list and it would therefore probably rate a warning (or ban) on that basis alone. Advertising of non-FreeBSD related products or services is strictly prohibited and will result in an immediate ban if it is clear that the offender is advertising by spam. Individual list charters: &a.acpi.name; ACPI and power management development &a.afs.name; Andrew File System This list is for discussion on porting and using AFS from CMU/Transarc &a.announce.name; Important events / milestones This is the mailing list for people interested only in occasional announcements of significant FreeBSD events. This includes announcements about snapshots and other releases. It contains announcements of new FreeBSD capabilities. It may contain calls for volunteers etc. This is a low volume, strictly moderated mailing list. &a.arch.name; Architecture and design discussions This list is for discussion of the FreeBSD architecture. Messages will mostly be kept strictly technical in nature. Examples of suitable topics are: How to re-vamp the build system to have several customized builds running at the same time. What needs to be fixed with VFS to make Heidemann layers work. How do we change the device driver interface to be able to use the same drivers cleanly on many buses and architectures. How to write a network driver. &a.audit.name; Source code audit project This is the mailing list for the FreeBSD source code audit project. Although this was originally intended for security-related changes, its charter has been expanded to review any code changes. This list is very heavy on patches, and is probably of no interest to the average FreeBSD user. Security discussions not related to a particular code change are held on freebsd-security. Conversely, all developers are encouraged to send their patches here for review, especially if they touch a part of the system where a bug may adversely affect the integrity of the system. &a.binup.name; FreeBSD Binary Update Project This list exists to provide discussion for the binary update system, or binup. Design issues, implementation details, patches, bug reports, status reports, feature requests, commit logs, and all other things related to binup are fair game. &a.bluetooth.name; &bluetooth; in FreeBSD This is the forum where FreeBSD's &bluetooth; users congregate. Design issues, implementation details, patches, bug reports, status reports, feature requests, and all matters related to &bluetooth; are fair game. &a.bugbusters.name; Coordination of the Problem Report handling effort The purpose of this list is to serve as a coordination and discussion forum for the Bugmeister, his Bugbusters, and any other parties who have a genuine interest in the PR database. This list is not for discussions about specific bugs, patches or PRs. &a.bugs.name; Bug reports This is the mailing list for reporting bugs in FreeBSD. Whenever possible, bugs should be submitted using the &man.send-pr.1; command or the WEB interface to it. &a.chat.name; Non technical items related to the FreeBSD community This list contains the overflow from the other lists about non-technical, social information. It includes discussion about whether Jordan looks like a toon ferret or not, whether or not to type in capitals, who is drinking too much coffee, where the best beer is brewed, who is brewing beer in their basement, and so on. Occasional announcements of important events (such as upcoming parties, weddings, births, new jobs, etc) can be made to the technical lists, but the follow ups should be directed to this -chat list. &a.core.name; FreeBSD core team This is an internal mailing list for use by the core members. Messages can be sent to it when a serious FreeBSD-related matter requires arbitration or high-level scrutiny. &a.current.name; Discussions about the use of &os.current; This is the mailing list for users of &os.current;. It includes warnings about new features coming out in -CURRENT that will affect the users, and instructions on steps that must be taken to remain -CURRENT. Anyone running CURRENT must subscribe to this list. This is a technical mailing list for which strictly technical content is expected. &a.cvsweb.name; FreeBSD CVSweb Project Technical discussions about use, development and maintenance of FreeBSD-CVSweb. &a.doc.name; Documentation project This mailing list is for the discussion of issues and projects related to the creation of documentation for FreeBSD. The members of this mailing list are collectively referred to as The FreeBSD Documentation Project. It is an open list; feel free to join and contribute! &a.drivers.name; Writing device drivers for &os; This is a forum for technical discussions related to device drivers on &os;. It is primarily a place for device driver writers to ask questions about how to write device drivers using the APIs in the &os; kernel. &a.eclipse.name; &os; users of Eclipse IDE, tools, rich client applications and ports. The intention of this list is to provide mutual support for everything to do with choosing, installing, using, developing and maintaining the Eclipse IDE, tools, rich client applications on the &os; platform and assisting with the porting of Eclipse IDE and plugins to the &os; environment. The intention is also to facilitate exchange of information between the Eclipse community and the &os; community to the mutual benefit of both. Although this list is focused primarily on the needs of Eclipse users it will also provide a forum for those who would like to develop &os; specific applications using the Eclipse framework. &a.emulation.name; Emulation of other systems such as Linux/&ms-dos;/&windows; This is a forum for technical discussions related to running programs written for other operating systems on &os;. &a.firewire.name; &firewire; (iLink, IEEE 1394) This is a mailing list for discussion of the design and implementation of a &firewire; (aka IEEE 1394 aka iLink) subsystem for FreeBSD. Relevant topics specifically include the standards, bus devices and their protocols, adapter boards/cards/chips sets, and the architecture and implementation of code for their proper support. &a.fs.name; File systems Discussions concerning FreeBSD file systems. This is a technical mailing list for which strictly technical content is expected. &a.geom.name; GEOM Discussions specific to GEOM and related implementations. This is a technical mailing list for which strictly technical content is expected. &a.gnome.name; GNOME Discussions concerning The GNOME Desktop Environment for FreeBSD systems. This is a technical mailing list for which strictly technical content is expected. &a.ipfw.name; IP Firewall This is the forum for technical discussions concerning the redesign of the IP firewall code in FreeBSD. This is a technical mailing list for which strictly technical content is expected. &a.ia64.name; Porting FreeBSD to IA64 This is a technical mailing list for individuals actively working on porting FreeBSD to the IA-64 platform from &intel;, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. &a.isdn.name; ISDN Communications This is the mailing list for people discussing the development of ISDN support for FreeBSD. &a.java.name; &java; Development This is the mailing list for people discussing the development of significant &java; applications for FreeBSD and the porting and maintenance of &jdk;s. &a.jobs.name; Jobs offered and sought This is a forum for posting employment notices and resumes specifically related to &os;, e.g. if you are seeking &os;-related employment or have a job involving &os; to advertise then this is the right place. This is not a mailing list for general employment issues since adequate forums for that already exist elsewhere. Note that this list, like other FreeBSD.org mailing lists, is distributed worldwide. Thus, you need to be clear about location and the extent to which telecommuting or assistance with relocation is available. Email should use open formats only — preferably plain text, but basic Portable Document Format (PDF), HTML, and a few others are acceptable to many readers. Closed formats such as µsoft; Word (.doc) will be rejected by the mailing list server. &a.kde.name; KDE Discussions concerning KDE on FreeBSD systems. This is a technical mailing list for which strictly technical content is expected. &a.hackers.name; Technical discussions This is a forum for technical discussions related to FreeBSD. This is the primary technical mailing list. It is for individuals actively working on FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. This is a technical mailing list for which strictly technical content is expected. &a.hardware.name; General discussion of FreeBSD hardware General discussion about the types of hardware that FreeBSD runs on, various problems and suggestions concerning what to buy or avoid. &a.hubs.name; Mirror sites Announcements and discussion for people who run FreeBSD mirror sites. &a.isp.name; Issues for Internet Service Providers This mailing list is for discussing topics relevant to Internet Service Providers (ISPs) using FreeBSD. This is a technical mailing list for which strictly technical content is expected. &a.openoffice.name; OpenOffice.org Discussions concerning the porting and maintenance of OpenOffice.org and &staroffice;. &a.performance.name; Discussions about tuning or speeding up FreeBSD This mailing list exists to provide a place for hackers, administrators, and/or concerned parties to discuss performance related topics pertaining to FreeBSD. Acceptable topics includes talking about FreeBSD installations that are either under high load, are experiencing performance problems, or are pushing the limits of FreeBSD. Concerned parties that are willing to work toward improving the performance of FreeBSD are highly encouraged to subscribe to this list. This is a highly technical list ideally suited for experienced FreeBSD users, hackers, or administrators interested in keeping FreeBSD fast, robust, and scalable. This list is not a question-and-answer list that replaces reading through documentation, but it is a place to make contributions or inquire about unanswered performance related topics. &a.pf.name; Discussion and questions about the packet filter firewall system Discussion concerning the packet filter (pf) firewall system in terms of FreeBSD. Technical discussion and user questions are both welcome. This list is also a place to discuss the ALTQ QoS framework. &a.platforms.name; Porting to Non &intel; platforms Cross-platform FreeBSD issues, general discussion and proposals for non &intel; FreeBSD ports. This is a technical mailing list for which strictly technical content is expected. &a.policy.name; Core team policy decisions This is a low volume, read-only mailing list for FreeBSD Core Team Policy decisions. &a.ports.name; Discussion of ports Discussions concerning FreeBSD's ports collection (/usr/ports), ports infrastructure, and general ports coordination efforts. This is a technical mailing list for which strictly technical content is expected. &a.ports-bugs.name; Discussion of ports bugs Discussions concerning problem reports for FreeBSD's ports collection (/usr/ports), proposed ports, or modifications to ports. This is a technical mailing list for which strictly technical content is expected. &a.proliant.name; Technical discussion of FreeBSD on HP ProLiant server platforms This mailing list is to be used for the technical discussion of the usage of FreeBSD on HP ProLiant servers, including the discussion of ProLiant-specific drivers, management software, configuration tools, and BIOS updates. As such, this is the primary place to discuss the hpasmd, hpasmcli, and hpacucli modules. &a.python.name; Python on FreeBSD This is a list for discussions related to improving Python-support on FreeBSD. This is a technical mailing list. It is for individuals working on porting Python, its 3rd party modules and Zope stuff to FreeBSD. Individuals interested in following the technical discussion are also welcome. &a.questions.name; 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. &a.scsi.name; SCSI subsystem This is the mailing list for people working on the SCSI subsystem for FreeBSD. This is a technical mailing list for which strictly technical content is expected. &a.security.name; Security issues FreeBSD computer security issues (DES, Kerberos, known security holes and fixes, etc). This is a technical mailing list for which strictly technical discussion is expected. Note that this is not a question-and-answer list, but that contributions (BOTH question AND answer) to the FAQ are welcome. &a.security-notifications.name; Security Notifications Notifications of FreeBSD security problems and fixes. This is not a discussion list. The discussion list is FreeBSD-security. &a.small.name; Using FreeBSD in embedded applications This list discusses topics related to unusually small and embedded FreeBSD installations. This is a technical mailing list for which strictly technical content is expected. &a.stable.name; Discussions about the use of &os.stable; This is the mailing list for users of &os.stable;. It includes warnings about new features coming out in -STABLE that will affect the users, and instructions on steps that must be taken to remain -STABLE. Anyone running STABLE should subscribe to this list. This is a technical mailing list for which strictly technical content is expected. &a.standards.name; C99 & POSIX Conformance This is a forum for technical discussions related to FreeBSD Conformance to the C99 and the POSIX standards. &a.usb.name; Discussing &os; support for USB This is a mailing list for technical discussions related to &os; support for USB. &a.usergroups.name; User Group Coordination List This is the mailing list for the coordinators from each of the local area Users Groups to discuss matters with each other and a designated individual from the Core Team. This mail list should be limited to meeting synopsis and coordination of projects that span User Groups. &a.vendors.name; Vendors Coordination discussions between The FreeBSD Project and Vendors of software and hardware for FreeBSD. Filtering on the Mailing Lists The &os; mailing lists are filtered in multiple ways to avoid the distribution of spam, viruses, and other unwanted emails. The filtering actions described in this section do not include all those used to protect the mailing lists. Only certain types of attachments are allowed on the mailing lists. All attachments with a MIME content type not found in the list below will be stripped before an email is distributed on the mailing lists. application/octet-stream application/pdf application/pgp-signature application/x-pkcs7-signature message/rfc822 multipart/alternative multipart/related multipart/signed text/html text/plain text/x-diff text/x-patch Some of the mailing lists might allow attachments of other MIME content types, but the above list should be applicable for most of the mailing lists. If an email contains both an HTML and a plain text version, the HTML version will be removed. If an email contains only an HTML version, it will be converted to plain text. Usenet Newsgroups In addition to two FreeBSD specific newsgroups, there are many others in which FreeBSD is discussed or are otherwise relevant to FreeBSD users. Keyword searchable archives are available for some of these newsgroups from courtesy of Warren Toomey wkt@cs.adfa.edu.au. BSD Specific Newsgroups comp.unix.bsd.freebsd.announce comp.unix.bsd.freebsd.misc de.comp.os.unix.bsd (German) fr.comp.os.bsd (French) it.comp.os.freebsd (Italian) Other &unix; Newsgroups of Interest comp.unix comp.unix.questions comp.unix.admin comp.unix.programmer comp.unix.shell comp.unix.user-friendly comp.security.unix comp.sources.unix comp.unix.advocacy comp.unix.misc comp.bugs.4bsd comp.bugs.4bsd.ucb-fixes comp.unix.bsd X Window System comp.windows.x.i386unix comp.windows.x comp.windows.x.apps comp.windows.x.announce comp.windows.x.intrinsics comp.windows.x.motif comp.windows.x.pex comp.emulators.ms-windows.wine World Wide Web Servers &chap.eresources.www.inc; Email Addresses The following user groups provide FreeBSD related email addresses for their members. The listed administrator reserves the right to revoke the address if it is abused in any way. Domain Facilities User Group Administrator ukug.uk.FreeBSD.org Forwarding only freebsd-users@uk.FreeBSD.org Lee Johnston lee@uk.FreeBSD.org Shell Accounts The following user groups provide shell accounts for people who are actively supporting the FreeBSD project. The listed administrator reserves the right to cancel the account if it is abused in any way. Host Access Facilities Administrator dogma.freebsd-uk.eu.org Telnet/FTP/SSH Email, Web space, Anonymous FTP Lee Johnston lee@uk.FreeBSD.org diff --git a/zh_TW.Big5/books/handbook/install/chapter.sgml b/zh_TW.Big5/books/handbook/install/chapter.sgml index 7478898136..0d3165ec56 100644 --- a/zh_TW.Big5/books/handbook/install/chapter.sgml +++ b/zh_TW.Big5/books/handbook/install/chapter.sgml @@ -1,5208 +1,5196 @@ Jim Mock Restructured, reorganized, and parts rewritten by Randy Pratt The sysinstall walkthrough, screenshots, and general copy by 安裝 FreeBSD 概述 installation FreeBSD 提供一個簡單好用的文字介面安裝程式，叫做 sysinstall。 這是 FreeBSD 預設使用的安裝程式。協力廠商如果想，也可以改用自己的安裝程式。 本章將說明如何使用 sysinstall 來安裝 FreeBSD。 讀完這章，您將了解︰ 如何製作 FreeBSD 安裝片 FreeBSD 對硬碟的使用及配置。 如何啟動 sysinstall 程式。 在執行 sysinstall 時會問的相關問題有哪些、 這些問題的意思為何、以及該如何回答。 在開始閱讀這章之前，您需要︰ 閱讀要安裝的 FreeBSD 版本所附之硬體支援表，以確定您的硬體有沒有被支援。 一般來說，此安裝說明是針對 &i386; (相容的 PC 機種) 架構的電腦。 如果有其他架構(比如 Alpha)的安裝說明，我們會一併列出。 雖然本文件會常常更新，但有可能與您安裝版本上所附的說明文件有些許出入。 在此，我們建議您把本說明文章當作一般的安裝參考原則就好。 安裝前的準備工作 列出您電腦的硬體清單 在安裝 FreeBSD 之前，您應該試著將您電腦中的硬體清單列出來。 FreeBSD 安裝程式會將這些硬體(硬碟、網路卡、光碟機等等)以型號及製造廠商列出來。 FreeBSD 也會嘗試為這些硬體找出最適當的 IRQ 及 IO port 的設定。 但是因為 PC 的硬體種類實在太過複雜，這個步驟不一定保證絕對成功。 這時，您就可能需要手動更改有問題的設定值哩。 如果您已裝了其它的作業系統，如： &windows; 或 Linux，那麼可先由這些系統所提供的工具，來查看這些硬體設定值是怎麼設定的。 若真的沒辦法確定某些卡用什麼設定值，那麼可以檢查看看卡上面所標示的東西，說不定它的設定已有標示在卡上。 常用的 IRQ 號碼為 3、5 以及 7；而 IO 埠的值通常以 16 進位表示，例如 0x330。 建議您在安裝 FreeBSD 之前，把這些資料列印或抄錄下來，做成表格的樣子也許會較有用喔，例如： 硬體清單(舉例) 硬體名稱 IRQ IO port(s) 備註 第一顆 IDE 硬碟 N/A N/A 40 GB，Seagate 製造，first IDE master CDROM N/A N/A First IDE slave 第二顆硬碟 N/A N/A 20 GB，IBM 製造， second IDE master 第一個 IDE controller 14 0x1f0 網路卡 N/A N/A &intel; 10/100 數據機 N/A N/A &tm.3com; 56K faxmodem，接在 COM1 …
備份您的資料 如果要裝的電腦上面存有重要資料，那麼在安裝 FreeBSD 前， 請確定您已經將這些資料備份了，並且先測試過這些備份檔是否沒有問題。 FreeBSD 安裝程式在要寫入任何資料到您的硬碟前，都會先提醒您確認， 一旦您確定要寫入，那麼之後就再也沒有反悔的機會囉。 決定要將 FreeBSD 安裝到哪裡 如果您想讓 FreeBSD 直接使用整顆硬碟，那麼請直接跳到下一節。 然而，如果您想要 FreeBSD 跟既有的系統並存，那麼，您必須對硬碟的資料分佈方式有深入的了解， 以及其所造成的影響。 &i386; 架構的硬碟配置模式 PC 上的硬碟可以被細分為許多分散的區域。這些區域叫做 分割區(Partitions)。 因為設計的方式，每個硬碟最多可以有 4 個分割區，而這些分割叫做 主要分割區(Primary Partitions)。 為了突破這個限制，以便能使用更多的分割區，就有了新的分割區類型，叫作： 延伸分割區(Extended Partition)。 每個硬碟就只能有一個延伸分割區。然而，在延伸分割區裡面可以建立許多個特殊分割區，叫作 邏輯分割區(Logical Partitions)。 每種分割區都有其 分割區代號(Partition ID) 用以區別每種分割區的資料類型。而 FreeBSD 分割區代號是 165。 一般來講，每種作業系統都會有自己獨特的方式來區別分割區。舉例： DOS 及其之後的作業系統，比如 &windows; ，會分配給每個主要分割區及邏輯分割區 1 個 磁碟代號(drive letter)，從 C: 開始。 FreeBSD 必須安裝在主要分割區。FreeBSD 可以在這個分割區上面存放資料或是您建立的任何檔案。 然而，如果您有很多顆硬碟，也可以在這些(或部份)硬碟建立 FreeBSD 分割區。 安裝 FreeBSD 的時候，必須至少要有 1 個分割區給 FreeBSD 使用， 這個分割區可以是尚未使用的分割區，或是現存的分割區。(但上面的資料不打算繼續使用) 如果您已經用完了您磁碟上所有的分割區，那麼您必須使用其他作業系統所提供的工具 (像是 DOS or &windows; 上的 fdisk)來騰出一個分割區給 FreeBSD 用。 如果有多餘的分割區，也可以使用它。但使用前，您可能需要先整理一下這些分割區。 FreeBSD最小安裝需要約 100 MB 的空間，但是這只是『最小安裝』， 幾乎沒剩下多少空間來存放您自己的檔案。 較理想的(不含圖形介面)最小安裝是約 250 MB，或者是 350 MB 左右(包含圖形介面)。 還需要安裝其他的套件軟體，那麼將需要更多的硬碟空間。 您可以使用商業軟體，例如 &partitionmagic; 來重新調整分割區空間，來給 FreeBSD 用的空間。FreeBSD 光碟、FTP 上面的 tools 目錄包含兩個免費的工具，也可以達成這個工作，叫作： FIPS 及 PResizer。這些工具的說明文件可以在同個目錄內找到。 FIPS, PResizer 和 &partitionmagic; 可以重新調整在 &ms-dos; 到 &windows; ME 所使用的 FAT16 及 FAT32 分割區大小。另外， &partitionmagic; 則是上述軟體中唯一可以重新調整 NTFS 分割區大小。 不當的使用這些工具，可能會刪除所有硬碟上的資料。 在使用這些工具前，請確定您已有先備份好資料。 使用現有的分割區 假設您只有一個 4 GB 的硬碟，而且已經裝了 &windows; ，然後將這顆硬碟分成兩個磁碟代號：C: 及 D:，每個大小為 2 GB 。 C: 槽上放了 1 GB 的資料，而 D: 槽上放了 0.5 GB 的資料。 這表示硬碟上有兩個分割區，每個磁碟代號槽都是分割區。您可以把所有放在 D: 的資料，都移動到 C: ，這樣就空出了第二個分割區可以給 FreeBSD 使用。 縮減現有的分割區 假設您只有一個 4 GB 硬碟，而且已經裝了 &windows; 。在安裝 &windows; 時把 4 GB 都給 C: 槽，並且現在已經用了 1.5 GB 空間，而你想將剩下空間的 2 GB 給 FreeBSD 使用。 如此一來，為了裝 FreeBSD ，你必須在以下兩種方式二選一： 備份 &windows; 資料，然後重裝 &windows;，並在安裝 &windows; 時給 2 GB 的分割空間。 使用上述的工具，像是 &partitionmagic;，來重新調整 &windows; 所用的分割區大小。 Alpha 架構的磁碟配置模式 Alpha 在 Alpha 上，您必須使用一整顆硬碟給 FreeBSD ，沒有辦法在同顆硬碟上跟其他作業系統共存。根據不同型號的 Alpha 機器，您的硬碟可以是 SCSI 或 IDE 硬碟，只要您的機器可以從這些硬碟開機就可以。 按照 Digital / Compaq 使用手冊的編排風格，所有 SRM 輸入的部分都用大寫表示。 注意，SRM 大小寫有別。 要得知您磁碟的名稱以及型號，可以在 SRM console 提示下使用 SHOW DEVICE 命令： >>>SHOW DEVICE dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476 dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658 dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015 dva0.0.0.0.1 DVA0 ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01 pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27 pqa0.0.0.4.0 PQA0 PCI EIDE pqb0.0.1.4.0 PQB0 PCI EIDE 例子中機器為 Digital Personal Workstation 433au 並且顯示出此機器有連接三個磁碟機。第一個是 CDROM，叫做 DKA0 ；另外兩個是磁碟機， 分別叫做： DKC0 及 DKC100 。 磁碟機的名稱中有 DKx 字樣的是 SCSI 硬碟。例如： DKA100 表示是 SCSI 硬碟，其 SCSI ID 為 1， 位在第一個 SCSI 匯流排(A)； 而 DKC300 表示是 SCSI 硬碟，其 SCSI ID 為 3 ，位於第三個 SCSI 匯流排(C)。裝置名稱 PKx 表示 SCSI 控制卡。由上述 SHOW DEVICE 的結果看來， SCSI 光碟機也被視為是 SCSI 硬碟的一種。 若為 IDE 硬碟的話，名稱會有 DQx 字樣，而 PQx 則表示相對應的 IDE 磁碟控制器。 整理你的網路設定資料 如果想透過網路( FTP 站或 NFS)安裝 FreeBSD，那麼就必須知道您的網路組態。 在安裝 FreeBSD 的過程中將會提示您輸入這些資訊，以順利完成安裝過程。 使用乙太網路(Ethernet)或 Cable/DSL 數據機上網 若使用乙太網路，或是要透過 Cable/DSL 數據機上網，那麼您必須準備 下面的資訊： IP 位址 預設 Gateway(閘道) 的 IP 位址 Hostname(機器名稱) DNS 伺服器的 IP 位址 Subnet Mask 若不知道這些資訊，您可以詢問系統管理者或是您的 ISP 業者。 他們可能會說這些資訊會由 DHCP 自動指派；如果是這樣的話， 請記住這一點就可以了。 使用數據機上網 若由一般的數據機撥接上網，您仍然可以安裝 FreeBSD，只是會需要很長的時間。 您必須知道： 撥接到 ISP 的電話號碼。 您的數據機是連到哪個 COM 埠。 您撥接到 ISP 所用的帳號跟密碼。 查閱 FreeBSD 勘誤表(Errata) 雖然我們盡力使得每個 FreeBSD 發行版本都很穩定，但是過程中仍然不免有時會發生錯誤。 在很罕見的情形下，這些錯誤會影響到安裝的過程。當發現這些錯誤且修正後，會將它們列在 FreeBSD 勘誤表(Errata) 中。在您安裝 FreeBSD 前，應該先看看勘誤表中有沒有什麼問題會影響到您的安裝。 關於所有發行版本的資訊，包括勘誤表，可以在 FreeBSD 網站 的 發行情報(release information) 找到。 準備好 FreeBSD 安裝檔案 FreeBSD 可以透過下面任何一種安裝來源進行安裝︰ Local Media CDROM 或 DVD 現有的 DOS 分割區 SCSI 或 QIC 磁帶。 軟碟磁片 Network FTP 站、支援 Passvie 模式的 FTP 站(若您機器在 NAT 內)、甚至 HTTP proxy 都可以。 NFS 伺服器 專用(dedicated)的 parallel 或 serial 連線 若已經有 FreeBSD 的 CD 或 DVD，但機器不支援從光碟開機的話，那麼請直接進下一節 ()。 若沒有 FreeBSD 安裝片的話，那麼請先看 這裡會介紹如何準備所需要的安裝片，照該節步驟弄好後，就可以繼續下一步 。 準備好開機磁片 FreeBSD 安裝流程是要從電腦開機後，進入 FreeBSD 安裝畫面 —— 而不是在其他作業系統上執行程式。 一般來講，電腦都是用裝在硬碟上的作業系統來開機，也可以用開機磁片來開機； 此外，現在大多數電腦都可以從光碟開機。 如果您有 FreeBSD 的 CDROM 或 DVD(無論是用買的或是自己燒錄的)， 且您的電腦可支援由光碟開機， (通常在 BIOS 中會有 Boot Order 或類似選項)，那麼您就可以跳過此小節。因為 FreeBSD CDROM 或 DVD 都可以用來開機。 請按照下面步驟，以製作開機片： 取得開機片的映像檔(images) 開機磁片用的映像檔(images)通常會放在光碟片上的 floppies/ 目錄內，另外也可以從像是下面 FTP 站的 floppies 目錄下載： ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<arch>/<version>-RELEASE/floppies/ 。請將『arch』、『version』替換為打算安裝的電腦架構、OS 版本。例如：要裝的電腦屬 &i386 架構，而要裝的是 &os; &rel.current;-RELEASE ，那麼可以到 下載。 映像檔(images)的附檔名都是 .flp 。而 floppies/ 目錄內包含一些不同用途的映像檔(images)， 這取決於您要裝的 FreeBSD 版本、需求、硬體配備為何。 通常要 3 個映像檔，也就是： boot.flp、 kern1.flp、 kern2.flp。若有疑問的話，請翻閱同一目錄下的 README.TXT 文件檔，以瞭解相關最新注意事項。 安裝 &os; 5.3 之前的 5.X 系統時，有些硬體設備可能需要額外的驅動程式才能使用。 這些驅動程式都會放在 drivers.flp 這個映像檔內。 在使用 FTP 下載時，必須使用 binary 模式 進行傳輸。有些瀏覽器預設是以 text (或 ASCII) 模式來傳輸資料，所以這些錯誤傳輸模式下載的映像檔所做成的磁片，會無法使用。 準備開機磁片 每個映像檔都需要一張磁片，並且請避免使用到壞的磁片。最簡單的檢測方式就是自己先把這些磁片再重新格式化(format) 而不要相信所謂的已格式化的磁片，&windows; 內的 format 在格式化時，並不會告訴你是否有壞軌，而只會直接將它們標示壞軌而不使用壞軌部分而已。 此外，建議採用全新的磁片來製作安裝片比較保險。 若在安裝 FreeBSD 的過程中發生當機、畫面凍結或是其他怪異的現象，首先要懷疑的就是開機磁片是否壞掉。 請用其他的磁片製作映像檔再試試看。 將映像檔(images)寫入到磁片內 .flp 檔並非一般檔案，不能直接把它複製到磁片上。 事實上它是包含整張磁片所有內容的映像檔(image)。也就是說，不能純粹複製檔案到磁片上， 而必須使用特別的工具程式，來將映像檔直接寫到磁片上。 DOS 若要用 &ms-dos;/&windows; 來作安裝片的話，那麼可以用 fdimage 工具程式來將映像檔，寫到磁片上。 若您用的是 FreeBSD 光碟的話(假設光碟機代號為 E: ，那麼請執行類似下面的指令： E:\> tools\fdimage floppies\kern.flp A: 請針對每個需要用到的 .flp 映像檔，重複上述的指令(記得更改相關檔名)，每次的映像檔完成後， 都需要換另外一片來裝新的映像檔；請記得，在作好的磁片上註明是使用哪個映像檔作的。若 .flp 映像檔放在不同地方，請自行修改上述指令。若沒有 FreeBSD 光碟的話，可以到 FTP 上面的 tools 目錄 下載 fdimage 使用。 如果要用 &unix; 系統(比如其他台 FreeBSD 機器)來製作開機片的話，可以用 &man.dd.1; 指令來把映像檔直接寫入到磁片上。在 FreeBSD上的話，可以打類似下面的指令： &prompt.root; dd if=kern.flp of=/dev/fd0 在 FreeBSD 中，/dev/fd0 就是指第一台軟碟機(即一般 &ms-dos;/&windows; 上的 A: 磁碟機)；而 /dev/fd1 指 B: 磁碟機，其餘的依此類推。不過其他的 &unix; 系統可能會用不同的名稱，這時就要查閱該系統的說明文件了。 現在起，我們可以開始安裝 FreeBSD 囉！ 開始安裝 預設的情況下，安裝過程並不會改變您磁碟機中的任何資料，除非您看到下面的訊息： Last Chance: Are you SURE you want continue the installation? If you're running this on a disk with data you wish to save then WE STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding! We can take no responsibility for lost disk contents! 在看到這最後的警告訊息前，您都可以隨時離開安裝程式而不會變更您的硬碟。 如果您發現有任何設定錯誤，這時您可以直接將電源關掉而不會造成任何傷害。 開機啟動流程篇 &i386; 平台的開機流程 在一開始，電腦電源開關是關閉的。 打開電腦電源開關。剛開始的時候，它應該會顯示進入系統設定選單或 BIOS 要按哪個鍵，常見的有： F2, F10, Del 或 Alt S 。(按鍵請依據實際情況決定)不論是要按哪個鍵，請按它進入 BIOS 設定畫面。有時您的電腦可能會顯示一個圖形畫面，通常做法是按 Esc 鍵將離開這個圖形畫面，以使您能夠看到必要的設定訊息。 找出可以設定『開機順序(Boot Order)』的選項，通常該選項會列出一些設備讓您選擇，例如︰ Floppy, CDROM, First Hard Disk 等等。 如果要用軟碟安裝，請確定 floppy disk 要列為開機順序的第一個；若要用光碟安裝，記得 CDROM 要列為開機順序的第一個。為了避免疑惑，請參考機器、主機板說明手冊。 儲存設定並離開，系統應該會重新啟動。 若要用磁片安裝，請把在 一節中製作好的 kern.flp 那張安裝磁片放到第一台軟碟機中。 如果是從光碟安裝，那麼開機後請將 FreeBSD 光碟放入光碟機中。 如果，開機後如往常一樣而沒有從軟碟或光碟開機，請檢查︰ 是不是磁片或光碟太晚放入而錯失開機時間。如果是，請將它們放入，然後重新開機。 BIOS 設定不對或忘了儲存設定，請重新檢查 BIOS 的設定。 您的電腦 BIOS 不支援從光碟開機。 此時，FreeBSD 就開始啟動了。如果是從光碟開機，會見到類似下面的畫面(版本部分省略)：: Verifying DMI Pool Data ........ Boot from ATAPI CD-ROM : 1. FD 2.88MB System Type-(00) Uncompressing ... done BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive B: is disk1 BIOS drive C: is disk2 BIOS drive D: is disk3 BIOS 639kB/261120kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 /kernel text=0x277391 data=0x3268c+0x332a8 | | Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _ 如果您從軟碟開機，會看到類似下面的畫面(版本部分省略)： Verifying DMI Pool Data ........ BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/261120kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 /kernel text=0x277391 data=0x3268c+0x332a8 | Please insert MFS root floppy and press enter: 請根據提示將 kern.flp 磁片取出， 並放入 mfsroot.flp 這張磁片，然後按 Enter 鍵。若是 &os; 5.3 (含之後)的話，還有另外一張磁片(在前一節已經介紹過了)。 總之，您只需從第一張磁片啟動， 然後根據提示，再放入相關磁片即可。 無論從軟碟或光碟開機，您都會看到下面這段訊息： Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _ 您可以等待 10 秒，或是按 Enter 鍵。 Alpha 平台的開機流程 Alpha 在一開始，電腦電源開關是關閉的。 打開電腦電源開關，然後等開機畫面出現。 若要用磁片安裝，請把在 一節中製作好的 kern.flp 那張安裝磁片放到第一台軟碟機中。 然後，打下列指令來從磁片開機(請把下列軟碟機代號改為你電腦的軟碟機代號)： >>>BOOT DVA0 -FLAGS '' -FILE '' 若要用光碟安裝，請把做好的安裝片放入光碟機，然後打下列指令來從光碟開機(請把下列光碟機代號改為你電腦的光碟機代號)： >>>BOOT DKA0 -FLAGS '' -FILE '' 接著 FreeBSD 開機片就會開始了。若是由軟碟開機的話，這時會看到以下訊息： Please insert MFS root floppy and press enter: 請照指示，拿走 kern.flp 片，改放 mfsroot.flp 片，然後按 Enter。 無論從軟碟或光碟開機，您都會看到下面這段訊息： Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 9 seconds... _ 您可以等待 10 秒，或是按 Enter 鍵。接下來就會進入kernel configuration 選單。 那要怎麼去翻閱偵測硬體的結果呢？ 先前在螢幕上所顯示的最後幾百行字，會存在暫存區(buffer)以便您翻閱。 若要翻閱暫存區，請按 Scroll Lock 鍵，這會開啟捲動畫面功能。 然後就可以使用方向鍵，或是 PageUp、PageDown 鍵來上下翻閱。再按一次 Scroll Lock 鍵，就會停止畫面捲動。 - Do this now, to review the text that scrolled off the screen when - the kernel was carrying out the device probes. You will see text - similar to , although the precise - text will differ depending on the devices that you have in your - computer. + 現在就請試試看，翻閱一下偵測硬體的畫面吧， + 你應該會看到類似 的畫面，真正畫面會依你的電腦設備而有所不同。
偵測硬體的例子 avail memory = 253050880 (247120K bytes) Preloaded elf kernel "kernel" at 0xc0817000. Preloaded mfs_root "/mfsroot" at 0xc0817084. md0: Preloaded image </mfsroot> 4423680 bytes at 0xc03ddcd4 md1: Malloc disk Using $PIR table, 4 entries at 0xc00fde60 npx0: <math processor> on motherboard npx0: INT 16 interface pcib0: <Host to PCI bridge> on motherboard pci0: <PCI bus> on pcib0 pcib1:<VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 pci1: <Matrox MGA G200 AGP graphics accelerator> at 0.0 irq 11 isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0 isa0: <iSA bus> on isab0 atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0 <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 7.2 on pci 0 usb0: <VIA 83572 USB controller> on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr1 uhub0: 2 ports with 2 removable, self powered pci0: <unknown card> (vendor=0x1106, dev=0x3040) at 7.3 dc0: <ADMtek AN985 10/100BaseTX> port 0xe800-0xe8ff mem 0xdb000000-0xeb0003ff ir q 11 at device 8.0 on pci0 dc0: Ethernet address: 00:04:5a:74:6b:b5 miibus0: <MII bus> on dc0 ukphy0: <Generic IEEE 802.3u media interface> on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xec00-0xec1f irq 9 at device 10. 0 on pci0 ed0 address 52:54:05:de:73:1b, type NE2000 (16 bit) isa0: too many dependant configs (8) isa0: unexpected small tag 14 orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> flags 0x1 irq1 on atkbdc0 kbd0 at atkbd0 psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model Generic PS/@ mouse, device ID 0 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 pppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip0: <PLIP network interface> on ppbus0 ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master UDMA33 acd0: CD-RW <LITE-ON LTR-1210B> at ata1-slave PIO4 Mounting root from ufs:/dev/md0c /stand/sysinstall running as init on vty0
- Check the probe results carefully to make sure that FreeBSD found - all the devices you expected. If a device was not found, then it will - not be listed. If the device's driver required configuring - with the IRQ and port address then you should check that you entered - them correctly. + 請仔細檢查每項檢測結果，以確定 FreeBSD 有正確偵測到每項硬體。 + 若沒偵測到硬體的話，那畫面就不會列出來了。如果該硬體需要調 IRQ 及 + port address 的話，那麼請檢查是否設定正確。 - If you need to make changes to the UserConfig device probing, - it is easy to exit the sysinstall program - and start over again. It is also a good way to become more familiar - with the process. + 若想再改一些硬體的設定，那麼先退出 sysinstall 程式，再重頭來過即可。 + 這方式也有助你更熟悉這些流程。
離開 Sysinstall 程式
- Use the arrow keys to select - Exit Install from the Main - Install Screen menu. The following message will display: + 在主畫面選擇 Exit Install，接下來應該會出現以下訊息： User Confirmation Requested Are you sure you wish to exit? The system will reboot (be sure to remove any floppies from the drives). [ Yes ] No - The install program will start again if the CDROM is left - in the drive and &gui.yes; is selected. + 若按下 &gui.yes; 之後，卻忘了把光碟退出來的話，那麼等下重開機後又會再次啟動安裝程式了。 - If you are booting from floppies it will be necessary to remove - the mfsroot.flp floppy and replace it with - kern.flp before rebooting. + 若你是用磁片開機的話，那麼重開機之前，請記得退出開機片吧。 介紹 Sysinstall The sysinstall utility is the installation application provided by the FreeBSD Project. It is console based and is divided into a number of menus and screens that you can use to configure and control the installation process. The sysinstall menu system is controlled by the arrow keys, Enter, Space, and other keys. A detailed description of these keys and what they do is contained in sysinstall's usage information. To review this information, ensure that the Usage entry is highlighted and that the [Select] button is selected, as shown in , then press Enter. The instructions for using the menu system will be displayed. After reviewing them, press Enter to return to the Main Menu.
選擇 Sysinstall 主選單的『Usage(快速說明)』
選擇『 Documentation(說明文件)』選單 From the Main Menu, select Doc with the arrow keys and press Enter.
選擇『Documentation(說明文件)』選單
This will display the Documentation Menu.
Sysinstall 的說明文件(Documentation)選單
It is important to read the documents provided. To view a document, select it with the arrow keys and press Enter. When finished reading a document, pressing Enter will return to the Documentation Menu. To return to the Main Installation Menu, select Exit with the arrow keys and press Enter. 選擇『鍵盤對應』選單 To change the keyboard mapping, use the arrow keys to select Keymap from the menu and press Enter. This is only required if you are using a non-standard or non-US keyboard.
Sysinstall 主選單
A different keyboard mapping may be chosen by selecting the menu item using up/down arrow keys and pressing Space. Pressing Space again will unselect the item. When finished, choose the &gui.ok; using the arrow keys and press Enter. Only a partial list is shown in this screen representation. Selecting &gui.cancel; by pressing Tab will use the default keymap and return to the Main Install Menu.
Sysinstall 鍵盤對應選單
安裝選項的設定畫面 Select Options and press Enter.
Sysinstall 主選單
Sysinstall 選項設定
The default values are usually fine for most users and do not need to be changed. The release name will vary according to the version being installed. The description of the selected item will appear at the bottom of the screen highlighted in blue. Notice that one of the options is Use Defaults to reset all values to startup defaults. Press F1 to read the help screen about the various options. Pressing Q will return to the Main Install menu. 開始進行標準安裝 Standard(標準)安裝適用於那些初探 &unix; 或 FreeBSD 的使用者。用方向鍵選擇 Standard 然後按 Enter 即可開始進入標準安裝。
開始進行標準安裝
硬碟空間的分配 Your first task is to allocate disk space for FreeBSD, and label that space so that sysinstall can prepare it. In order to do this you need to know how FreeBSD expects to find information on the disk. BIOS 磁碟機編號 Before you install and configure FreeBSD on your system, there is an important subject that you should be aware of, especially if you have multiple hard drives. DOS Microsoft Windows In a PC running a BIOS-dependent operating system such as &ms-dos; or µsoft.windows;, the BIOS is able to abstract the normal disk drive order, and the operating system goes along with the change. This allows the user to boot from a disk drive other than the so-called primary master. This is especially convenient for some users who have found that the simplest and cheapest way to keep a system backup is to buy an identical second hard drive, and perform routine copies of the first drive to the second drive using Ghost or XCOPY . Then, if the first drive fails, or is attacked by a virus, or is scribbled upon by an operating system defect, he can easily recover by instructing the BIOS to logically swap the drives. It is like switching the cables on the drives, but without having to open the case. SCSI BIOS More expensive systems with SCSI controllers often include BIOS extensions which allow the SCSI drives to be re-ordered in a similar fashion for up to seven drives. A user who is accustomed to taking advantage of these features may become surprised when the results with FreeBSD are not as expected. FreeBSD does not use the BIOS, and does not know the logical BIOS drive mapping. This can lead to very perplexing situations, especially when drives are physically identical in geometry, and have also been made as data clones of one another. When using FreeBSD, always restore the BIOS to natural drive numbering before installing FreeBSD, and then leave it that way. If you need to switch drives around, then do so, but do it the hard way, and open the case and move the jumpers and cables. 範例：Bill 及 Fred 的安裝歷險 Bill breaks-down an older Wintel box to make another FreeBSD box for Fred. Bill installs a single SCSI drive as SCSI unit zero and installs FreeBSD on it. Fred begins using the system, but after several days notices that the older SCSI drive is reporting numerous soft errors and reports this fact to Bill. After several more days, Bill decides it is time to address the situation, so he grabs an identical SCSI drive from the disk drive archive in the back room. An initial surface scan indicates that this drive is functioning well, so Bill installs this drive as SCSI unit four and makes an image copy from drive zero to drive four. Now that the new drive is installed and functioning nicely, Bill decides that it is a good idea to start using it, so he uses features in the SCSI BIOS to re-order the disk drives so that the system boots from SCSI unit four. FreeBSD boots and runs just fine. Fred continues his work for several days, and soon Bill and Fred decide that it is time for a new adventure — time to upgrade to a newer version of FreeBSD. Bill removes SCSI unit zero because it was a bit flaky and replaces it with another identical disk drive from the archive. Bill then installs the new version of FreeBSD onto the new SCSI unit zero using Fred's magic Internet FTP floppies. The installation goes well. Fred uses the new version of FreeBSD for a few days, and certifies that it is good enough for use in the engineering department. It is time to copy all of his work from the old version. So Fred mounts SCSI unit four (the latest copy of the older FreeBSD version). Fred is dismayed to find that none of his precious work is present on SCSI unit four. Where did the data go? When Bill made an image copy of the original SCSI unit zero onto SCSI unit four, unit four became the new clone. When Bill re-ordered the SCSI BIOS so that he could boot from SCSI unit four, he was only fooling himself. FreeBSD was still running on SCSI unit zero. Making this kind of BIOS change will cause some or all of the Boot and Loader code to be fetched from the selected BIOS drive, but when the FreeBSD kernel drivers take-over, the BIOS drive numbering will be ignored, and FreeBSD will transition back to normal drive numbering. In the illustration at hand, the system continued to operate on the original SCSI unit zero, and all of Fred's data was there, not on SCSI unit four. The fact that the system appeared to be running on SCSI unit four was simply an artifact of human expectations. We are delighted to mention that no data bytes were killed or harmed in any way by our discovery of this phenomenon. The older SCSI unit zero was retrieved from the bone pile, and all of Fred's work was returned to him, (and now Bill knows that he can count as high as zero). Although SCSI drives were used in this illustration, the concepts apply equally to IDE drives. 以 FDisk 來建立分割磁區(Slices) No changes you make at this point will be written to the disk. If you think you have made a mistake and want to start again you can use the menus to exit sysinstall and try again or press U to use the Undo option. If you get confused and can not see how to exit you can always turn your computer off. After choosing to begin a standard installation in sysinstall you will be shown this message: Message In the next menu, you will need to set up a DOS-style ("fdisk") partitioning scheme for your hard disk. If you simply wish to devote all disk space to FreeBSD (overwriting anything else that might be on the disk(s) selected) then use the (A)ll command to select the default partitioning scheme followed by a (Q)uit. If you wish to allocate only free space to FreeBSD, move to a partition marked "unused" and use the (C)reate command. [ OK ] [ Press enter or space ] Press Enter as instructed. You will then be shown a list of all the hard drives that the kernel found when it carried out the device probes. shows an example from a system with two IDE disks. They have been called ad0 and ad2.
選擇 FDisk 要分割的硬碟
You might be wondering why ad1 is not listed here. Why has it been missed? Consider what would happen if you had two IDE hard disks, one as the master on the first IDE controller, and one as the master on the second IDE controller. If FreeBSD numbered these as it found them, as ad0 and ad1 then everything would work. But if you then added a third disk, as the slave device on the first IDE controller, it would now be ad1, and the previous ad1 would become ad2. Because device names (such as ad1s1a) are used to find filesystems, you may suddenly discover that some of your filesystems no longer appear correctly, and you would need to change your FreeBSD configuration. To work around this, the kernel can be configured to name IDE disks based on where they are, and not the order in which they were found. With this scheme the master disk on the second IDE controller will always be ad2, even if there are no ad0 or ad1 devices. This configuration is the default for the FreeBSD kernel, which is why this display shows ad0 and ad2. The machine on which this screenshot was taken had IDE disks on both master channels of the IDE controllers, and no disks on the slave channels. You should select the disk on which you want to install FreeBSD, and then press &gui.ok;. FDisk will start, with a display similar to that shown in . The FDisk display is broken into three sections. The first section, covering the first two lines of the display, shows details about the currently selected disk, including its FreeBSD name, the disk geometry, and the total size of the disk. The second section shows the slices that are currently on the disk, where they start and end, how large they are, the name FreeBSD gives them, and their description and sub-type. This example shows two small unused slices, which are artifacts of disk layout schemes on the PC. It also shows one large FAT slice, which almost certainly appears as C: in &ms-dos; / &windows;, and an extended slice, which may contain other drive letters for &ms-dos; / &windows;. The third section shows the commands that are available in FDisk.
(舉例)未編輯前的 Fdisk 分割區(Partition)
What you do now will depend on how you want to slice up your disk. If you want to use FreeBSD for the entire disk (which will delete all the other data on this disk when you confirm that you want sysinstall to continue later in the installation process) then you can press A, which corresponds to the Use Entire Disk option. The existing slices will be removed, and replaced with a small area flagged as unused (again, an artifact of PC disk layout), and then one large slice for FreeBSD. If you do this, then you should select the newly created FreeBSD slice using the arrow keys, and press S to mark the slice as being bootable. The screen will then look very similar to . Note the A in the Flags column, which indicates that this slice is active, and will be booted from. If you will be deleting an existing slice to make space for FreeBSD then you should select the slice using the arrow keys, and then press D. You can then press C, and be prompted for size of slice you want to create. Enter the appropriate figure and press Enter. The default value in this box represents the largest possible slice you can make, which could be the largest contiguous block of unallocated space or the size of the entire hard disk. If you have already made space for FreeBSD (perhaps by using a tool such as &partitionmagic;) then you can press C to create a new slice. Again, you will be prompted for the size of slice you would like to create.
Fdisk 採用整顆硬碟作分割區(Partition)
When finished, press Q. Your changes will be saved in sysinstall, but will not yet be written to disk. 安裝 Boot Manager You now have the option to install a boot manager. In general, you should choose to install the FreeBSD boot manager if: You have more than one drive, and have installed FreeBSD onto a drive other than the first one. You have installed FreeBSD alongside another operating system on the same disk, and you want to choose whether to start FreeBSD or the other operating system when you start the computer. If FreeBSD is going to be the only operating system on this machine, installed on the first hard disk, then the Standard boot manager will suffice. Choose None if you are using a third-party boot manager capable of booting FreeBSD. Make your choice and press Enter.
Sysinstall 的 Boot Manager 選單
The help screen, reached by pressing F1, discusses the problems that can be encountered when trying to share the hard disk between operating systems. 在其他硬碟上建立分割磁區(Slices) If there is more than one drive, it will return to the Select Drives screen after the boot manager selection. If you wish to install FreeBSD on to more than one disk, then you can select another disk here and repeat the slice process using FDisk. If you are installing FreeBSD on a drive other than your first, then the FreeBSD boot manager needs to be installed on both drives.
離開『選擇硬碟』畫面
The Tab key toggles between the last drive selected, &gui.ok;, and &gui.cancel;. Press the Tab once to toggle to the &gui.ok;, then press Enter to continue with the installation. 以 <application>Disklabel</application> 來建立分割區(Partitions) You must now create some partitions inside each slice that you have just created. Remember that each partition is lettered, from a through to h, and that partitions b, c, and d have conventional meanings that you should adhere to. Certain applications can benefit from particular partition schemes, especially if you are laying out partitions across more than one disk. However, for this, your first FreeBSD installation, you do not need to give too much thought to how you partition the disk. It is more important that you install FreeBSD and start learning how to use it. You can always re-install FreeBSD to change your partition scheme when you are more familiar with the operating system. This scheme features four partitions—one for swap space, and three for filesystems. 第一顆硬碟的分割區(Partition)配置 Partition Filesystem Size Description a / 100 MB This is the root filesystem. Every other filesystem will be mounted somewhere under this one. 100 MB is a reasonable size for this filesystem. You will not be storing too much data on it, as a regular FreeBSD install will put about 40 MB of data here. The remaining space is for temporary data, and also leaves expansion space if future versions of FreeBSD need more space in /. b N/A 2-3 x RAM The system's swap space is kept on this partition. Choosing the right amount of swap space can be a bit of an art. A good rule of thumb is that your swap space should be two or three times as much as the available physical memory (RAM). You should also have at least 64 MB of swap, so if you have less than 32 MB of RAM in your computer then set the swap amount to 64 MB. If you have more than one disk then you can put swap space on each disk. FreeBSD will then use each disk for swap, which effectively speeds up the act of swapping. In this case, calculate the total amount of swap you need (e.g., 128 MB), and then divide this by the number of disks you have (e.g., two disks) to give the amount of swap you should put on each disk, in this example, 64 MB of swap per disk. e /var 50 MB The /var directory contains files that are constantly varying; log files, and other administrative files. Many of these files are read-from or written-to extensively during FreeBSD's day-to-day running. Putting these files on another filesystem allows FreeBSD to optimize the access of these files without affecting other files in other directories that do not have the same access pattern. f /usr Rest of disk All your other files will typically be stored in /usr and its subdirectories.
If you will be installing FreeBSD on to more than one disk then you must also create partitions in the other slices that you configured. The easiest way to do this is to create two partitions on each disk, one for the swap space, and one for a filesystem. 其他硬碟的分割區(Partition)配置 Partition Filesystem Size Description b N/A See description As already discussed, you can split swap space across each disk. Even though the a partition is free, convention dictates that swap space stays on the b partition. e /diskn Rest of disk The rest of the disk is taken up with one big partition. This could easily be put on the a partition, instead of the e partition. However, convention says that the a partition on a slice is reserved for the filesystem that will be the root (/) filesystem. You do not have to follow this convention, but sysinstall does, so following it yourself makes the installation slightly cleaner. You can choose to mount this filesystem anywhere; this example suggests that you mount them as directories /diskn, where n is a number that changes for each disk. But you can use another scheme if you prefer.
Having chosen your partition layout you can now create it using sysinstall. You will see this message: Message Now, you need to create BSD partitions inside of the fdisk partition(s) just created. If you have a reasonable amount of disk space (200MB or more) and don't have any special requirements, simply use the (A)uto command to allocate space automatically. If you have more specific needs or just don't care for the layout chosen by (A)uto, press F1 for more information on manual layout. [ OK ] [ Press enter or space ] Press Enter to start the FreeBSD partition editor, called Disklabel. shows the display when you first start Disklabel. The display is divided in to three sections. The first few lines show the name of the disk you are currently working on, and the slice that contains the partitions you are creating (at this point Disklabel calls this the Partition name rather than slice name). This display also shows the amount of free space within the slice; that is, space that was set aside in the slice, but that has not yet been assigned to a partition. The middle of the display shows the partitions that have been created, the name of the filesystem that each partition contains, their size, and some options pertaining to the creation of the filesystem. The bottom third of the screen shows the keystrokes that are valid in Disklabel.
Sysinstall 的 Disklabel 編輯器
Disklabel can automatically create partitions for you and assign them default sizes. Try this now, by Pressing A. You will see a display similar to that shown in . Depending on the size of the disk you are using, the defaults may or may not be appropriate. This does not matter, as you do not have to accept the defaults. Beginning with FreeBSD 4.5, the default partitioning assigns the /tmp directory its own partition instead of being part of the / partition. This helps avoid filling the / partition with temporary files.
Sysinstall 的 Disklabel 編輯器 — 使用自動分配
If you choose to not use the default partitions and wish to replace them with your own, use the arrow keys to select the first partition, and press D to delete it. Repeat this to delete all the suggested partitions. To create the first partition (a, mounted as / — root), make sure the proper disk slice at the top of the screen is selected and press C. A dialog box will appear prompting you for the size of the new partition (as shown in ). You can enter the size as the number of disk blocks you want to use, or as a number followed by either M for megabytes, G for gigabytes, or C for cylinders. Beginning with FreeBSD 5.X, users can: select UFS2 (which is default on &os; 5.1 and above) using the Custom Newfs (Z) option, create labels with Auto Defaults and modify them with the Custom Newfs option or add during the regular creation period. Do not forget to add for SoftUpdates if you use the Custom Newfs option!
Free Space for Root Partition
The default size shown will create a partition that takes up the rest of the slice. If you are using the partition sizes described in the earlier example, then delete the existing figure using Backspace, and then type in 64M, as shown in . Then press &gui.ok;.
Edit Root Partition Size
Having chosen the partition's size you will then be asked whether this partition will contain a filesystem or swap space. The dialog box is shown in . This first partition will contain a filesystem, so check that FS is selected and press Enter.
Choose the Root Partition Type
Finally, because you are creating a filesystem, you must tell Disklabel where the filesystem is to be mounted. The dialog box is shown in . The root filesystem's mount point is /, so type /, and then press Enter.
Choose the Root Mount Point
The display will then update to show you the newly created partition. You should repeat this procedure for the other partitions. When you create the swap partition, you will not be prompted for the filesystem mount point, as swap partitions are never mounted. When you create the final partition, /usr, you can leave the suggested size as is, to use the rest of the slice. Your final FreeBSD DiskLabel Editor screen will appear similar to , although your values chosen may be different. Press Q to finish.
Sysinstall Disklabel Editor
選擇想要安裝的 選擇要安裝的套件集(Distribution Set) Deciding which distribution set to install will depend largely on the intended use of the system and the amount of disk space available. The predefined options range from installing the smallest possible configuration to everything. Those who are new to &unix; and/or FreeBSD should almost certainly select one of these canned options. Customizing a distribution set is typically for the more experienced user. Press F1 for more information on the distribution set options and what they contain. When finished reviewing the help, pressing Enter will return to the Select Distributions Menu. If a graphical user interface is desired then a distribution set that is preceded by an X should be chosen. The configuration of the X server and selection of a default desktop must be done after the installation of &os;. More information regarding the configuration of a X server can be found in . The default version of X11 that is installed depends on the version of FreeBSD that you are installing. For FreeBSD versions prior to 5.3, &xfree86; 4.X is installed. For &os; 5.3 and later, &xorg; is the default. If compiling a custom kernel is anticipated, select an option which includes the source code. For more information on why a custom kernel should be built or how to build a custom kernel, see . Obviously, the most versatile system is one that includes everything. If there is adequate disk space, select All as shown in by using the arrow keys and press Enter. If there is a concern about disk space consider using an option that is more suitable for the situation. Do not fret over the perfect choice, as other distributions can be added after installation.
選擇套件(Distributions)
安裝 Ports Collection After selecting the desired distribution, an opportunity to install the FreeBSD Ports Collection is presented. The ports collection is an easy and convenient way to install software. The Ports Collection does not contain the source code necessary to compile the software. Instead, it is a collection of files which automates the downloading, compiling and installation of third-party software packages. discusses how to use the ports collection. The installation program does not check to see if you have adequate space. Select this option only if you have adequate hard disk space. As of FreeBSD &rel.current;, the FreeBSD Ports Collection takes up about &ports.size; of disk space. You can safely assume a larger value for more recent versions of FreeBSD. User Confirmation Requested Would you like to install the FreeBSD ports collection? This will give you ready access to over &os.numports; ported software packages, at a cost of around &ports.size; of disk space when "clean" and possibly much more than that if a lot of the distribution tarballs are loaded (unless you have the extra CDs from a FreeBSD CD/DVD distribution available and can mount it on /cdrom, in which case this is far less of a problem). The Ports Collection is a very valuable resource and well worth having on your /usr partition, so it is advisable to say Yes to this option. For more information on the Ports Collection & the latest ports, visit: http://www.FreeBSD.org/ports [ Yes ] No Select &gui.yes; with the arrow keys to install the Ports Collection or &gui.no; to skip this option. Press Enter to continue. The Choose Distributions menu will redisplay.
Confirm Distributions
If satisfied with the options, select Exit with the arrow keys, ensure that &gui.ok; is highlighted, and pressing Enter to continue. 選擇安裝來源 若要從 CDROM 或 DVD 安裝，用方向鍵將游標移到 Install from a FreeBSD CD/DVD，並確定 選 &gui.ok; 後按下 Enter 就會開始裝了。 若是要用其他的方式安裝的話，請選擇適當的安裝來源，然後遵照螢幕指示進行安裝即可。 按 F1 可以顯示針對此部分(安裝來源)的線上說明。按一下 Enter 就會回到『選擇安裝來源』的畫面了。
選擇安裝來源
FTP 安裝模式 installation network FTP 使用 FTP 安裝的話，有分三種模式︰主動式(active)FTP、被動式(passive)FTP 或是透過 HTTP proxy server。 FTP Active: Install from an FTP server This option will make all FTP transfers use Active mode. This will not work through firewalls, but will often work with older FTP servers that do not support passive mode. If your connection hangs with passive mode (the default), try active! FTP Passive: Install from an FTP server through a firewall FTP passive mode This option instructs sysinstall to use Passive mode for all FTP operations. This allows the user to pass through firewalls that do not allow incoming connections on random TCP ports. FTP via a HTTP proxy: Install from an FTP server through a http proxy FTP via a HTTP proxy This option instructs sysinstall to use the HTTP protocol (like a web browser) to connect to a proxy for all FTP operations. The proxy will translate the requests and send them to the FTP server. This allows the user to pass through firewalls that do not allow FTP at all, but offer a HTTP proxy. In this case, you have to specify the proxy in addition to the FTP server. For a proxy FTP server, you should usually give the name of the server you really want as a part of the username, after an @ sign. The proxy server then fakes the real server. For example, assuming you want to install from ftp.FreeBSD.org, using the proxy FTP server foo.example.com, listening on port 1024. In this case, you go to the options menu, set the FTP username to ftp@ftp.FreeBSD.org, and the password to your email address. As your installation media, you specify FTP (or passive FTP, if the proxy supports it), and the URL ftp://foo.example.com:1234/pub/FreeBSD. Since /pub/FreeBSD from ftp.FreeBSD.org is proxied under foo.example.com, you are able to install from that machine (which will fetch the files from ftp.FreeBSD.org as your installation requests them). 開始進行安裝 到此為止，可以開始進行安裝了，這也是您避免更動到硬碟的最後機會。 User Confirmation Requested Last Chance! Are you SURE you want to continue the installation? If you're running this on a disk with data you wish to save then WE STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding! We can take no responsibility for lost disk contents! [ Yes ] No 選擇 &gui.yes; 並按下 Enter以確認真的要開始安裝 安裝所需時間會依據所選擇安裝的套件集(distribution) 、安裝來源以及電腦速度而有所不同。 在安裝的過程中，會有一些訊息顯示目前的安裝進度。 當您看到下面的訊息表示已經安裝完成了︰ Message Congratulations! You now have FreeBSD installed on your system. We will now move on to the final configuration questions. For any option you do not wish to configure, simply select No. If you wish to re-enter this utility after the system is up, you may do so by typing: /stand/sysinstall . [ OK ] [ Press enter to continue ] 請按 Enter 鍵來進行相關的後續設定。 如果剛選的是 &gui.no; 並按下 Enter 鍵，那麼會中斷安裝(就不會動到你的原有系統)。 接著，會出現以下訊息： Message Installation complete with some errors. You may wish to scroll through the debugging messages on VTY1 with the scroll-lock feature. You can also choose "No" at the next prompt and go back into the installation menus to retry whichever operations have failed. [ OK ] 這段訊息乃是因為都沒裝任何東西之故，請按 Enter 以跳回主畫面。 後續安裝 安裝系統成功之後，可以在新裝好的 FreeBSD 重開機之前，或者是事後再透過 sysinstall (&os; 5.2 之前版本則是 /stand/sysinstall) 然後選擇 Configure 選項以進行後續設定。 設定網路 如果您之前有設定用 PPP 連線透過 FTP 安裝，那麼這個畫面將不會出現； 正如上面剛所說的，您可以稍後再做更改。 有關 LAN 或把 FreeBSD 設定為 gateway 或 router 請參閱使用手冊中有關 網路進階運用 的章節。 User Confirmation Requested Would you like to configure any Ethernet or SLIP/PPP network devices? [ Yes ] No 如果要設定網路卡，請選擇 &gui.yes; 然後按 Enter。 否則請選 &gui.no; 以繼續。
選擇網路卡
用方向鍵選擇您要設定的網路卡，然後按 Enter。 User Confirmation Requested Do you want to try IPv6 configuration of the interface? Yes [ No ] In this private local area network, the current Internet type protocol (IPv4) was sufficient and &gui.no; was selected with the arrow keys and Enter pressed. If you are connected to an existing IPv6 network with an RA server, then choose &gui.yes; and press Enter. It will take several seconds to scan for RA servers. User Confirmation Requested Do you want to try DHCP configuration of the interface? Yes [ No ] If DHCP (Dynamic Host Configuration Protocol) is not required select &gui.no; with the arrow keys and press Enter. Selecting &gui.yes; will execute dhclient, and if successful, will fill in the network configuration information automatically. Refer to for more information. The following Network Configuration screen shows the configuration of the Ethernet device for a system that will act as the gateway for a Local Area Network.
Set Network Configuration for ed0
Use Tab to select the information fields and fill in appropriate information: Host The fully-qualified hostname, such as k6-2.example.com in this case. Domain The name of the domain that your machine is in, such as example.com for this case. IPv4 Gateway IP address of host forwarding packets to non-local destinations. You must fill this in if the machine is a node on the network. Leave this field blank if the machine is the gateway to the Internet for the network. The IPv4 Gateway is also known as the default gateway or default route. Name server IP address of your local DNS server. There is no local DNS server on this private local area network so the IP address of the provider's DNS server (208.163.10.2) was used. IPv4 address The IP address to be used for this interface was 192.168.0.1 Netmask The address block being used for this local area network is a Class C block (192.168.0.0 - 192.168.255.255). The default netmask is for a Class C network (255.255.255.0). Extra options to ifconfig Any interface-specific options to ifconfig you would like to add. There were none in this case. Use Tab to select &gui.ok; when finished and press Enter. User Confirmation Requested Would you like to Bring Up the ed0 interface right now? [ Yes ] No Choosing &gui.yes; and pressing Enter will bring the machine up on the network and be ready for use. However, this does not accomplish much during installation, since the machine still needs to be rebooted. Configure Gateway User Confirmation Requested Do you want this machine to function as a network gateway? [ Yes ] No If the machine will be acting as the gateway for a local area network and forwarding packets between other machines then select &gui.yes; and press Enter. If the machine is a node on a network then select &gui.no; and press Enter to continue. Configure Internet Services User Confirmation Requested Do you want to configure inetd and the network services that it provides? Yes [ No ] If &gui.no; is selected, various services such telnetd will not be enabled. This means that remote users will not be able to telnet into this machine. Local users will be still be able to access remote machines with telnet. These services can be enabled after installation by editing /etc/inetd.conf with your favorite text editor. See for more information. Select &gui.yes; if you wish to configure these services during install. An additional confirmation will display: User Confirmation Requested The Internet Super Server (inetd) allows a number of simple Internet services to be enabled, including finger, ftp and telnetd. Enabling these services may increase risk of security problems by increasing the exposure of your system. With this in mind, do you wish to enable inetd? [ Yes ] No Select &gui.yes; to continue. User Confirmation Requested inetd(8) relies on its configuration file, /etc/inetd.conf, to determine which of its Internet services will be available. The default FreeBSD inetd.conf(5) leaves all services disabled by default, so they must be specifically enabled in the configuration file before they will function, even once inetd(8) is enabled. Note that services for IPv6 must be separately enabled from IPv4 services. Select [Yes] now to invoke an editor on /etc/inetd.conf, or [No] to use the current settings. [ Yes ] No Selecting &gui.yes; will allow adding services by deleting the # at the beginning of a line.
Editing <filename>inetd.conf</filename>
After adding the desired services, pressing Esc will display a menu which will allow exiting and saving the changes. Anonymous FTP FTP anonymous User Confirmation Requested Do you want to have anonymous FTP access to this machine? Yes [ No ] Deny Anonymous FTP Selecting the default &gui.no; and pressing Enter will still allow users who have accounts with passwords to use FTP to access the machine. Allow Anonymous FTP Anyone can access your machine if you elect to allow anonymous FTP connections. The security implications should be considered before enabling this option. For more information about security see . To allow anonymous FTP, use the arrow keys to select &gui.yes; and press Enter. The following screen (or similar) will display:
Default Anonymous FTP Configuration
Pressing F1 will display the help: This screen allows you to configure the anonymous FTP user. The following configuration values are editable: UID: The user ID you wish to assign to the anonymous FTP user. All files uploaded will be owned by this ID. Group: Which group you wish the anonymous FTP user to be in. Comment: String describing this user in /etc/passwd FTP Root Directory: Where files available for anonymous FTP will be kept. Upload subdirectory: Where files uploaded by anonymous FTP users will go. The ftp root directory will be put in /var by default. If you do not have enough room there for the anticipated FTP needs, the /usr directory could be used by setting the FTP Root Directory to /usr/ftp. When you are satisfied with the values, press Enter to continue. User Confirmation Requested Create a welcome message file for anonymous FTP users? [ Yes ] No If you select &gui.yes; and press Enter, an editor will automatically start allowing you to edit the message.
Edit the FTP Welcome Message
This is a text editor called ee. Use the instructions to change the message or change the message later using a text editor of your choice. Note the file name/location at the bottom of the editor screen. Press Esc and a pop-up menu will default to a) leave editor. Press Enter to exit and continue. Press Enter again to save changes if you made any. Configure Network File System Network File System (NFS) allows sharing of files across a network. A machine can be configured as a server, a client, or both. Refer to for a more information. NFS Server User Confirmation Requested Do you want to configure this machine as an NFS server? Yes [ No ] If there is no need for a Network File System server, select &gui.no; and press Enter. If &gui.yes; is chosen, a message will pop-up indicating that the exports file must be created. Message Operating as an NFS server means that you must first configure an /etc/exports file to indicate which hosts are allowed certain kinds of access to your local filesystems. Press [Enter] now to invoke an editor on /etc/exports [ OK ] Press Enter to continue. A text editor will start allowing the exports file to be created and edited.
Editing <filename>exports</filename>
Use the instructions to add the actual exported filesystems now or later using a text editor of your choice. Note the file name/location at the bottom of the editor screen. Press Esc and a pop-up menu will default to a) leave editor. Press Enter to exit and continue. NFS Client The NFS client allows your machine to access NFS servers. User Confirmation Requested Do you want to configure this machine as an NFS client? Yes [ No ] With the arrow keys, select &gui.yes; or &gui.no; as appropriate and press Enter. Security Profile A security profile is a set of configuration options that attempts to achieve the desired ratio of security to convenience by enabling and disabling certain programs and other settings. The more severe the security profile, the fewer programs will be enabled by default. This is one of the basic principles of security: do not run anything except what you must. Please note that the security profile is just a default setting. All programs can be enabled and disabled after you have installed FreeBSD by editing or adding the appropriate line(s) to /etc/rc.conf. For more information, please see the &man.rc.conf.5; manual page. The following table describes what each of the security profiles does. The columns are the choices you have for a security profile, and the rows are the program or feature that the profile enables or disables. Possible Security Profiles Extreme Moderate &man.sendmail.8; NO YES &man.sshd.8; NO YES &man.portmap.8; NO MAYBE The portmapper is enabled if the machine has been configured as an NFS client or server earlier in the installation. NFS server NO YES &man.securelevel.8; YES If you choose a security profile that sets the securelevel to Extreme or High, you must be aware of the implications. Please read the &man.init.8; manual page and pay particular attention to the meanings of the security levels, or you may have significant trouble later! NO
User Confirmation Requested Do you want to select a default security profile for this host (select No for "medium" security)? [ Yes ] No Selecting &gui.no; and pressing Enter will set the security profile to medium. Selecting &gui.yes; and pressing Enter will allow selecting a different security profile.
Security Profile Options
Press F1 to display the help. Press Enter to return to selection menu. Use the arrow keys to choose Medium unless your are sure that another level is required for your needs. With &gui.ok; highlighted, press Enter. An appropriate confirmation message will display depending on which security setting was chosen. Message Moderate security settings have been selected. Sendmail and SSHd have been enabled, securelevels are disabled, and NFS server setting have been left intact. PLEASE NOTE that this still does not save you from having to properly secure your system in other ways or exercise due diligence in your administration, this simply picks a standard set of out-of-box defaults to start with. To change any of these settings later, edit /etc/rc.conf [OK] Message Extreme security settings have been selected. Sendmail, SSHd, and NFS services have been disabled, and securelevels have been enabled. PLEASE NOTE that this still does not save you from having to properly secure your system in other ways or exercise due diligence in your administration, this simply picks a more secure set of out-of-box defaults to start with. To change any of these settings later, edit /etc/rc.conf [OK] Press Enter to continue with the post-installation configuration. The security profile is not a silver bullet! Even if you use the extreme setting, you need to keep up with security issues by reading an appropriate mailing list (), using good passwords and passphrases, and generally adhering to good security practices. It simply sets up the desired security to convenience ratio out of the box. System Console Settings There are several options available to customize the system console. User Confirmation Requested Would you like to customize your system console settings? [ Yes ] No To view and configure the options, select &gui.yes; and press Enter.
System Console Configuration Options
A commonly used option is the screen saver. Use the arrow keys to select Saver and then press Enter.
Screen Saver Options
Select the desired screen saver using the arrow keys and then press Enter. The System Console Configuration menu will redisplay. The default time interval is 300 seconds. To change the time interval, select Saver again. At the Screen Saver Options menu, select Timeout using the arrow keys and press Enter. A pop-up menu will appear:
Screen Saver Timeout
The value can be changed, then select &gui.ok; and press Enter to return to the System Console Configuration menu.
System Console Configuration Exit
Selecting Exit and pressing Enter will continue with the post-installation configurations. Setting the Time Zone Setting the time zone for your machine will allow it to automatically correct for any regional time changes and perform other time zone related functions properly. The example shown is for a machine located in the Eastern time zone of the United States. Your selections will vary according to your geographical location. User Confirmation Requested Would you like to set this machine's time zone now? [ Yes ] No Select &gui.yes; and press Enter to set the time zone. User Confirmation Requested Is this machine's CMOS clock set to UTC? If it is set to local time or you don't know, please choose NO here! Yes [ No ] Select &gui.yes; or &gui.no; according to how the machine's clock is configured and press Enter.
Select Your Region
The appropriate region is selected using the arrow keys and then pressing Enter.
Select Your Country
Select the appropriate country using the arrow keys and press Enter.
Select Your Time Zone
The appropriate time zone is selected using the arrow keys and pressing Enter. Confirmation Does the abbreviation 'EDT' look reasonable? [ Yes ] No Confirm the abbreviation for the time zone is correct. If it looks okay, press Enter to continue with the post-installation configuration. Linux Compatibility User Confirmation Requested Would you like to enable Linux binary compatibility? [ Yes ] No Selecting &gui.yes; and pressing Enter will allow running Linux software on FreeBSD. The install will add the appropriate packages for Linux compatibility. If installing by FTP, the machine will need to be connected to the Internet. Sometimes a remote ftp site will not have all the distributions like the Linux binary compatibility. This can be installed later if necessary. Mouse Settings This option will allow you to cut and paste text in the console and user programs with a 3-button mouse. If using a 2-button mouse, refer to manual page, &man.moused.8;, after installation for details on emulating the 3-button style. This example depicts a non-USB mouse configuration (such as a PS/2 or COM port mouse): User Confirmation Requested Does this system have a non-USB mouse attached to it? [ Yes ] No Select &gui.yes; for a non-USB mouse or &gui.no; for a USB mouse and press Enter.
Select Mouse Protocol Type
Use the arrow keys to select Type and press Enter.
Set Mouse Protocol
The mouse used in this example is a PS/2 type, so the default Auto was appropriate. To change protocol, use the arrow keys to select another option. Ensure that &gui.ok; is highlighted and press Enter to exit this menu.
Configure Mouse Port
Use the arrow keys to select Port and press Enter.
Setting the Mouse Port
This system had a PS/2 mouse, so the default PS/2 was appropriate. To change the port, use the arrow keys and then press Enter.
Enable the Mouse Daemon
Last, use the arrow keys to select Enable, and press Enter to enable and test the mouse daemon.
Test the Mouse Daemon
Move the mouse around the screen and verify the cursor shown responds properly. If it does, select &gui.yes; and press Enter. If not, the mouse has not been configured correctly — select &gui.no; and try using different configuration options. Select Exit with the arrow keys and press Enter to return to continue with the post-installation configuration. Tom Rhodes Contributed by Configure Additional Network Services Configuring network services can be a daunting task for new users if they lack previous knowledge in this area. Networking, including the Internet, is critical to all modern operating systems including &os;; as a result, it is very useful to have some understanding &os;'s extensive networking capabilities. Doing this during the installation will ensure users have some understanding of the various services available to them. Network services are programs that accept input from anywhere on the network. Every effort is made to make sure these programs will not do anything harmful. Unfortunately, programmers are not perfect and through time there have been cases where bugs in network services have been exploited by attackers to do bad things. It is important that you only enable the network services you know that you need. If in doubt it is best if you do not enable a network service until you find out that you do need it. You can always enable it later by re-running sysinstall or by using the features provided by the /etc/rc.conf file. Selecting the Networking option will display a menu similar to the one below:
Network Configuration Upper-level
The first option, Interfaces, was previously covered during the , thus this option can safely be ignored. Selecting the AMD option adds support for the BSD automatic mount utility. This is usually used in conjunction with the NFS protocol (see below) for automatically mounting remote file systems. No special configuration is required here. Next in line is the AMD Flags option. When selected, a menu will pop up for you to enter specific AMD flags. The menu already contains a set of default options: -a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map The option sets the default mount location which is specified here as /.amd_mnt. The option specifies the default log file; however, when syslogd is used all log activity will be sent to the system log daemon. The /host directory is used to mount an exported file system from a remote host, while /net directory is used to mount an exported file system from an IP address. The /etc/amd.map file defines the default options for AMD exports. FTP anonymous The Anon FTP option permits anonymous FTP connections. Select this option to make this machine an anonymous FTP server. Be aware of the security risks involved with this option. Another menu will be displayed to explain the security risks and configuration in depth. The Gateway configuration menu will set the machine up to be a gateway as explained previously. This can be used to unset the Gateway option if you accidentally selected it during the installation process. The Inetd option can be used to configure or completely disable the &man.inetd.8; daemon as discussed above. The Mail option is used to configure the system's default MTA or Mail Transfer Agent. Selecting this option will bring up the following menu:
Select a default MTA
Here you are offered a choice as to which MTA to install and set as the default. An MTA is nothing more than a mail server which delivers email to users on the system or the Internet. Selecting Sendmail will install the popular sendmail server which is the &os; default. The Sendmail local option will set sendmail to be the default MTA, but disable its ability to receive incoming email from the Internet. The other options here, Postfix and Exim act similar to Sendmail. They both deliver email; however, some users prefer these alternatives to the sendmail MTA. After selecting an MTA, or choosing not to select an MTA, the network configuration menu will appear with the next option being NFS client. The NFS client option will configure the system to communicate with a server via NFS. An NFS server makes file systems available to other machines on the network via the NFS protocol. If this is a stand alone machine, this option can remain unselected. The system may require more configuration later; see for more information about client and server configuration. Below that option is the NFS server option, permitting you to set the system up as an NFS server. This adds the required information to start up the RPC remote procedure call services. RPC is used to coordinate connections between hosts and programs. Next in line is the Ntpdate option, which deals with time synchronization. When selected, a menu like the one below shows up:
Ntpdate Configuration
From this menu, select the server which is the closest to your location. Selecting a close one will make the time synchronization more accurate as a server further from your location may have more connection latency. The next option is the PCNFSD selection. This option will install the net/pcnfsd package from the Ports Collection. This is a useful utility which provides NFS authentication services for systems which are unable to provide their own, such as Microsoft's &ms-dos; operating system. Now you must scroll down a bit to see the other options:
Network Configuration Lower-level
The &man.rpcbind.8;, &man.rpc.statd.8;, and &man.rpc.lockd.8; utilities are all used for Remote Procedure Calls (RPC). The rpcbind utility manages communication between NFS servers and clients, and is required for NFS servers to operate correctly. The rpc.statd daemon interacts with the rpc.statd daemon on other hosts to provide status monitoring. The reported status is usually held in the /var/db/statd.status file. The next option listed here is the rpc.lockd option, which, when selected, will provide file locking services. This is usually used with rpc.statd to monitor what hosts are requesting locks and how frequently they request them. While these last two options are marvelous for debugging, they are not required for NFS servers and clients to operate correctly. As you progress down the list the next item here is Routed, which is the routing daemon. The &man.routed.8; utility manages network routing tables, discovers multicast routers, and supplies a copy of the routing tables to any physically connected host on the network upon request. This is mainly used for machines which act as a gateway for the local network. When selected, a menu will be presented requesting the default location of the utility. The default location is already defined for you and can be selected with the Enter key. You will then be presented with yet another menu, this time asking for the flags you wish to pass on to routed. The default is and it should already appear on the screen. Next in line is the Rwhod option which, when selected, will start the &man.rwhod.8; daemon during system initialization. The rwhod utility broadcasts system messages across the network periodically, or collects them when in consumer mode. More information can be found in the &man.ruptime.1; and &man.rwho.1; manual pages. The next to the last option in the list is for the &man.sshd.8; daemon. This is the secure shell server for OpenSSH and it is highly recommended over the standard telnet and FTP servers. The sshd server is used to create a secure connection from one host to another by using encrypted connections. Finally there is the TCP Extensions option. This enables the TCP Extensions defined in RFC 1323 and RFC 1644. While on many hosts this can speed up connections, it can also cause some connections to be dropped. It is not recommended for servers, but may be beneficial for stand alone machines. Now that you have configured the network services, you can scroll up to the very top item which is Exit and continue on to the next configuration section. Configure X Server As of &os; 5.3-RELEASE, the X server configuration facility has been removed from sysinstall, you have to install and configure the X server after the installation of &os;. More information regarding the installation and the configuration of a X server can be found in . You can skip this section if you are not installing a &os; version prior to 5.3-RELEASE. In order to use a graphical user interface such as KDE, GNOME, or others, the X server will need to be configured. In order to run &xfree86; as a non root user you will need to have x11/wrapper installed. This is installed by default beginning with FreeBSD 4.7. For earlier versions this can be added from the Package Selection menu. To see whether your video card is supported, check the &xfree86; web site. User Confirmation Requested Would you like to configure your X server at this time? [ Yes ] No It is necessary to know your monitor specifications and video card information. Equipment damage can occur if settings are incorrect. If you do not have this information, select &gui.no; and perform the configuration after installation when you have the information using sysinstall (/stand/sysinstall in &os; versions older than 5.2), selecting Configure and then XFree86. Improper configuration of the X server at this time can leave the machine in a frozen state. It is often advised to configure the X server once the installation has completed. If you have graphics card and monitor information, select &gui.yes; and press Enter to proceed with configuring the X server.
Select Configuration Method Menu
There are several ways to configure the X server. Use the arrow keys to select one of the methods and press Enter. Be sure to read all instructions carefully. The xf86cfg and xf86cfg -textmode methods may make the screen go dark and take a few seconds to start. Be patient. The following will illustrate the use of the xf86config configuration tool. The configuration choices you make will depend on the hardware in the system so your choices will probably be different than those shown: Message You have configured and been running the mouse daemon. Choose "/dev/sysmouse" as the mouse port and "SysMouse" or "MouseSystems" as the mouse protocol in the X configuration utility. [ OK ] [ Press enter to continue ] This indicates that the mouse daemon previously configured has been detected. Press Enter to continue. Starting xf86config will display a brief introduction: This program will create a basic XF86Config file, based on menu selections you make. The XF86Config file usually resides in /usr/X11R6/etc/X11 or /etc/X11. A sample XF86Config file is supplied with XFree86; it is configured for a standard VGA card and monitor with 640x480 resolution. This program will ask for a pathname when it is ready to write the file. You can either take the sample XF86Config as a base and edit it for your configuration, or let this program produce a base XF86Config file for your configuration and fine-tune it. Before continuing with this program, make sure you know what video card you have, and preferably also the chipset it uses and the amount of video memory on your video card. SuperProbe may be able to help with this. Press enter to continue, or ctrl-c to abort. Pressing Enter will start the mouse configuration. Be sure to follow the instructions and use Mouse Systems as the mouse protocol and /dev/sysmouse as the mouse port even if using a PS/2 mouse is shown as an illustration. First specify a mouse protocol type. Choose one from the following list: 1. Microsoft compatible (2-button protocol) 2. Mouse Systems (3-button protocol) & FreeBSD moused protocol 3. Bus Mouse 4. PS/2 Mouse 5. Logitech Mouse (serial, old type, Logitech protocol) 6. Logitech MouseMan (Microsoft compatible) 7. MM Series 8. MM HitTablet 9. Microsoft IntelliMouse If you have a two-button mouse, it is most likely of type 1, and if you have a three-button mouse, it can probably support both protocol 1 and 2. There are two main varieties of the latter type: mice with a switch to select the protocol, and mice that default to 1 and require a button to be held at boot-time to select protocol 2. Some mice can be convinced to do 2 by sending a special sequence to the serial port (see the ClearDTR/ClearRTS options). Enter a protocol number: 2 You have selected a Mouse Systems protocol mouse. If your mouse is normally in Microsoft-compatible mode, enabling the ClearDTR and ClearRTS options may cause it to switch to Mouse Systems mode when the server starts. Please answer the following question with either 'y' or 'n'. Do you want to enable ClearDTR and ClearRTS? n You have selected a three-button mouse protocol. It is recommended that you do not enable Emulate3Buttons, unless the third button doesn't work. Please answer the following question with either 'y' or 'n'. Do you want to enable Emulate3Buttons? y Now give the full device name that the mouse is connected to, for example /dev/tty00. Just pressing enter will use the default, /dev/mouse. On FreeBSD, the default is /dev/sysmouse. Mouse device: /dev/sysmouse The keyboard is the next item to be configured. A generic 101-key model is shown for illustration. Any name may be used for the variant or simply press Enter to accept the default value. Please select one of the following keyboard types that is the better description of your keyboard. If nothing really matches, choose 1 (Generic 101-key PC) 1 Generic 101-key PC 2 Generic 102-key (Intl) PC 3 Generic 104-key PC 4 Generic 105-key (Intl) PC 5 Dell 101-key PC 6 Everex STEPnote 7 Keytronic FlexPro 8 Microsoft Natural 9 Northgate OmniKey 101 10 Winbook Model XP5 11 Japanese 106-key 12 PC-98xx Series 13 Brazilian ABNT2 14 HP Internet 15 Logitech iTouch 16 Logitech Cordless Desktop Pro 17 Logitech Internet Keyboard 18 Logitech Internet Navigator Keyboard 19 Compaq Internet 20 Microsoft Natural Pro 21 Genius Comfy KB-16M 22 IBM Rapid Access 23 IBM Rapid Access II 24 Chicony Internet Keyboard 25 Dell Internet Keyboard Enter a number to choose the keyboard. 1 Please select the layout corresponding to your keyboard 1 U.S. English 2 U.S. English w/ ISO9995-3 3 U.S. English w/ deadkeys 4 Albanian 5 Arabic 6 Armenian 7 Azerbaidjani 8 Belarusian 9 Belgian 10 Bengali 11 Brazilian 12 Bulgarian 13 Burmese 14 Canadian 15 Croatian 16 Czech 17 Czech (qwerty) 18 Danish Enter a number to choose the country. Press enter for the next page 1 Please enter a variant name for 'us' layout. Or just press enter for default variant us Please answer the following question with either 'y' or 'n'. Do you want to select additional XKB options (group switcher, group indicator, etc.)? n Next, we proceed to the configuration for the monitor. Do not exceed the ratings of your monitor. Damage could occur. If you have any doubts, do the configuration after you have the information. Now we want to set the specifications of the monitor. The two critical parameters are the vertical refresh rate, which is the rate at which the whole screen is refreshed, and most importantly the horizontal sync rate, which is the rate at which scanlines are displayed. The valid range for horizontal sync and vertical sync should be documented in the manual of your monitor. If in doubt, check the monitor database /usr/X11R6/lib/X11/doc/Monitors to see if your monitor is there. Press enter to continue, or ctrl-c to abort. You must indicate the horizontal sync range of your monitor. You can either select one of the predefined ranges below that correspond to industry- standard monitor types, or give a specific range. It is VERY IMPORTANT that you do not specify a monitor type with a horizontal sync range that is beyond the capabilities of your monitor. If in doubt, choose a conservative setting. hsync in kHz; monitor type with characteristic modes 1 31.5; Standard VGA, 640x480 @ 60 Hz 2 31.5 - 35.1; Super VGA, 800x600 @ 56 Hz 3 31.5, 35.5; 8514 Compatible, 1024x768 @ 87 Hz interlaced (no 800x600) 4 31.5, 35.15, 35.5; Super VGA, 1024x768 @ 87 Hz interlaced, 800x600 @ 56 Hz 5 31.5 - 37.9; Extended Super VGA, 800x600 @ 60 Hz, 640x480 @ 72 Hz 6 31.5 - 48.5; Non-Interlaced SVGA, 1024x768 @ 60 Hz, 800x600 @ 72 Hz 7 31.5 - 57.0; High Frequency SVGA, 1024x768 @ 70 Hz 8 31.5 - 64.3; Monitor that can do 1280x1024 @ 60 Hz 9 31.5 - 79.0; Monitor that can do 1280x1024 @ 74 Hz 10 31.5 - 82.0; Monitor that can do 1280x1024 @ 76 Hz 11 Enter your own horizontal sync range Enter your choice (1-11): 6 You must indicate the vertical sync range of your monitor. You can either select one of the predefined ranges below that correspond to industry- standard monitor types, or give a specific range. For interlaced modes, the number that counts is the high one (e.g. 87 Hz rather than 43 Hz). 1 50-70 2 50-90 3 50-100 4 40-150 5 Enter your own vertical sync range Enter your choice: 2 You must now enter a few identification/description strings, namely an identifier, a vendor name, and a model name. Just pressing enter will fill in default names. The strings are free-form, spaces are allowed. Enter an identifier for your monitor definition: Hitachi The selection of a video card driver from a list is next. If you pass your card on the list, continue to press Enter and the list will repeat. Only an excerpt from the list is shown: Now we must configure video card specific settings. At this point you can choose to make a selection out of a database of video card definitions. Because there can be variation in Ramdacs and clock generators even between cards of the same model, it is not sensible to blindly copy the settings (e.g. a Device section). For this reason, after you make a selection, you will still be asked about the components of the card, with the settings from the chosen database entry presented as a strong hint. The database entries include information about the chipset, what driver to run, the Ramdac and ClockChip, and comments that will be included in the Device section. However, a lot of definitions only hint about what driver to run (based on the chipset the card uses) and are untested. If you can't find your card in the database, there's nothing to worry about. You should only choose a database entry that is exactly the same model as your card; choosing one that looks similar is just a bad idea (e.g. a GemStone Snail 64 may be as different from a GemStone Snail 64+ in terms of hardware as can be). Do you want to look at the card database? y 288 Matrox Millennium G200 8MB mgag200 289 Matrox Millennium G200 SD 16MB mgag200 290 Matrox Millennium G200 SD 4MB mgag200 291 Matrox Millennium G200 SD 8MB mgag200 292 Matrox Millennium G400 mgag400 293 Matrox Millennium II 16MB mga2164w 294 Matrox Millennium II 4MB mga2164w 295 Matrox Millennium II 8MB mga2164w 296 Matrox Mystique mga1064sg 297 Matrox Mystique G200 16MB mgag200 298 Matrox Mystique G200 4MB mgag200 299 Matrox Mystique G200 8MB mgag200 300 Matrox Productiva G100 4MB mgag100 301 Matrox Productiva G100 8MB mgag100 302 MediaGX mediagx 303 MediaVision Proaxcel 128 ET6000 304 Mirage Z-128 ET6000 305 Miro CRYSTAL VRX Verite 1000 Enter a number to choose the corresponding card definition. Press enter for the next page, q to continue configuration. 288 Your selected card definition: Identifier: Matrox Millennium G200 8MB Chipset: mgag200 Driver: mga Do NOT probe clocks or use any Clocks line. Press enter to continue, or ctrl-c to abort. Now you must give information about your video card. This will be used for the "Device" section of your video card in XF86Config. You must indicate how much video memory you have. It is probably a good idea to use the same approximate amount as that detected by the server you intend to use. If you encounter problems that are due to the used server not supporting the amount memory you have (e.g. ATI Mach64 is limited to 1024K with the SVGA server), specify the maximum amount supported by the server. How much video memory do you have on your video card: 1 256K 2 512K 3 1024K 4 2048K 5 4096K 6 Other Enter your choice: 6 Amount of video memory in Kbytes: 8192 You must now enter a few identification/description strings, namely an identifier, a vendor name, and a model name. Just pressing enter will fill in default names (possibly from a card definition). Your card definition is Matrox Millennium G200 8MB. The strings are free-form, spaces are allowed. Enter an identifier for your video card definition: Next, the video modes are set for the resolutions desired. Typically, useful ranges are 640x480, 800x600, and 1024x768 but those are a function of video card capability, monitor size, and eye comfort. When selecting a color depth, select the highest mode that your card will support. For each depth, a list of modes (resolutions) is defined. The default resolution that the server will start-up with will be the first listed mode that can be supported by the monitor and card. Currently it is set to: "640x480" "800x600" "1024x768" "1280x1024" for 8-bit "640x480" "800x600" "1024x768" "1280x1024" for 16-bit "640x480" "800x600" "1024x768" "1280x1024" for 24-bit Modes that cannot be supported due to monitor or clock constraints will be automatically skipped by the server. 1 Change the modes for 8-bit (256 colors) 2 Change the modes for 16-bit (32K/64K colors) 3 Change the modes for 24-bit (24-bit color) 4 The modes are OK, continue. Enter your choice: 2 Select modes from the following list: 1 "640x400" 2 "640x480" 3 "800x600" 4 "1024x768" 5 "1280x1024" 6 "320x200" 7 "320x240" 8 "400x300" 9 "1152x864" a "1600x1200" b "1800x1400" c "512x384" Please type the digits corresponding to the modes that you want to select. For example, 432 selects "1024x768" "800x600" "640x480", with a default mode of 1024x768. Which modes? 432 You can have a virtual screen (desktop), which is screen area that is larger than the physical screen and which is panned by moving the mouse to the edge of the screen. If you don't want virtual desktop at a certain resolution, you cannot have modes listed that are larger. Each color depth can have a differently-sized virtual screen Please answer the following question with either 'y' or 'n'. Do you want a virtual screen that is larger than the physical screen? n For each depth, a list of modes (resolutions) is defined. The default resolution that the server will start-up with will be the first listed mode that can be supported by the monitor and card. Currently it is set to: "640x480" "800x600" "1024x768" "1280x1024" for 8-bit "1024x768" "800x600" "640x480" for 16-bit "640x480" "800x600" "1024x768" "1280x1024" for 24-bit Modes that cannot be supported due to monitor or clock constraints will be automatically skipped by the server. 1 Change the modes for 8-bit (256 colors) 2 Change the modes for 16-bit (32K/64K colors) 3 Change the modes for 24-bit (24-bit color) 4 The modes are OK, continue. Enter your choice: 4 Please specify which color depth you want to use by default: 1 1 bit (monochrome) 2 4 bits (16 colors) 3 8 bits (256 colors) 4 16 bits (65536 colors) 5 24 bits (16 million colors) Enter a number to choose the default depth. 4 Finally, the configuration needs to be saved. Be sure to enter /etc/X11/XF86Config as the location for saving the configuration. I am going to write the XF86Config file now. Make sure you don't accidently overwrite a previously configured one. Shall I write it to /etc/X11/XF86Config? y If the configuration fails, you can try the configuration again by selecting &gui.yes; when the following message appears: User Confirmation Requested The XFree86 configuration process seems to have failed. Would you like to try again? [ Yes ] No If you have trouble configuring &xfree86;, select &gui.no; and press Enter and continue with the installation process. After installation you can use xf86cfg -textmode or xf86config to access the command line configuration utilities as root. There is an additional method for configuring &xfree86; described in . If you choose not to configure &xfree86; at this time the next menu will be for package selection. The default setting which allows the server to be killed is the hotkey sequence CtrlAlt Backspace. This can be executed if something is wrong with the server settings and prevent hardware damage. The default setting that allows video mode switching will permit changing of the mode while running X with the hotkey sequence CtrlAlt+ or CtrlAlt- . After you have &xfree86; running, the display can be adjusted for height, width, or centering by using xvidtune. There are warnings that improper settings can damage your equipment. Heed them. If in doubt, do not do it. Instead, use the monitor controls to adjust the display for X Window. There may be some display differences when switching back to text mode, but it is better than damaging equipment. Read the &man.xvidtune.1; manual page before making any adjustments. Following a successful &xfree86; configuration, it will proceed to the selection of a default desktop. Select Default X Desktop As of &os; 5.3-RELEASE, the X desktop selection facility has been removed from sysinstall, you have to configure the X desktop after the installation of &os;. More information regarding the installation and the configuration of a X desktop can be found in . You can skip this section if you are not installing a &os; version prior to 5.3-RELEASE. There are a variety of window managers available. They range from very basic environments to full desktop environments with a large suite of software. Some require only minimal disk space and low memory while others with more features require much more. The best way to determine which is most suitable for you is to try a few different ones. Those are available from the Ports Collection or as packages and can be added after installation. You can select one of the popular desktops to be installed and configured as the default desktop. This will allow you to start it right after installation.
Select Default Desktop
Use the arrow keys to select a desktop and press Enter. Installation of the selected desktop will proceed. Install Packages Packages are pre-compiled binaries and are a convenient way to install software. Installation of one package is shown for purposes of illustration. Additional packages can also be added at this time if desired. After installation sysinstall (/stand/sysinstall in &os; versions older than 5.2) can be used to add additional packages. User Confirmation Requested The FreeBSD package collection is a collection of hundreds of ready-to-run applications, from text editors to games to WEB servers and more. Would you like to browse the collection now? [ Yes ] No Selecting &gui.yes; and pressing Enter will be followed by the Package Selection screens:
Select Package Category
Only packages on the current installation media are available for installation at any given time. All packages available will be displayed if All is selected or you can select a particular category. Highlight your selection with the arrow keys and press Enter. A menu will display showing all the packages available for the selection made:
Select Packages
The bash shell is shown selected. Select as many as desired by highlighting the package and pressing the Space key. A short description of each package will appear in the lower left corner of the screen. Pressing the Tab key will toggle between the last selected package, &gui.ok;, and &gui.cancel;. When you have finished marking the packages for installation, press Tab once to toggle to the &gui.ok; and press Enter to return to the Package Selection menu. The left and right arrow keys will also toggle between &gui.ok; and &gui.cancel;. This method can also be used to select &gui.ok; and press Enter to return to the Package Selection menu.
Install Packages
Use the Tab and arrow keys to select [ Install ] and press Enter. You will then need to confirm that you want to install the packages:
Confirm Package Installation
Selecting &gui.ok; and pressing Enter will start the package installation. Installing messages will appear until completed. Make note if there are any error messages. The final configuration continues after packages are installed. If you end up not selecting any packages, and wish to return to the final configuration, select Install anyways. Add Users/Groups You should add at least one user during the installation so that you can use the system without being logged in as root. The root partition is generally small and running applications as root can quickly fill it. A bigger danger is noted below: User Confirmation Requested Would you like to add any initial user accounts to the system? Adding at least one account for yourself at this stage is suggested since working as the "root" user is dangerous (it is easy to do things which adversely affect the entire system). [ Yes ] No Select &gui.yes; and press Enter to continue with adding a user.
Select User
Select User with the arrow keys and press Enter.
Add User Information
The following descriptions will appear in the lower part of the screen as the items are selected with Tab to assist with entering the required information: Login ID The login name of the new user (mandatory). UID The numerical ID for this user (leave blank for automatic choice). Group The login group name for this user (leave blank for automatic choice). Password The password for this user (enter this field with care!). Full name The user's full name (comment). Member groups The groups this user belongs to (i.e. gets access rights for). Home directory The user's home directory (leave blank for default). Login shell The user's login shell (leave blank for default, e.g. /bin/sh). The login shell was changed from /bin/sh to /usr/local/bin/bash to use the bash shell that was previously installed as a package. Do not try to use a shell that does not exist or you will not be able to login. The most common shell used in the BSD-world is the C shell, which can be indicated as /bin/tcsh. The user was also added to the wheel group to be able to become a superuser with root privileges. When you are satisfied, press &gui.ok; and the User and Group Management menu will redisplay:
Exit User and Group Management
Groups can also be added at this time if specific needs are known. Otherwise, this may be accessed through using sysinstall (/stand/sysinstall in &os; versions older than 5.2) after installation is completed. When you are finished adding users, select Exit with the arrow keys and press Enter to continue the installation. Set the <username>root</username> Password Message Now you must set the system manager's password. This is the password you'll use to log in as "root". [ OK ] [ Press enter to continue ] Press Enter to set the root password. The password will need to be typed in twice correctly. Needless to say, make sure you have a way of finding the password if you forget. Notice that the password you type in is not echoed, nor are asterisks displayed. Changing local password for root. New password : Retype new password : The installation will continue after the password is successfully entered. Exiting Install If you need to configure additional network devices or any other configuration, you can do it at this point or after installation with sysinstall (/stand/sysinstall in &os; versions older than 5.2). User Confirmation Requested Visit the general configuration menu for a chance to set any last options? Yes [ No ] Select &gui.no; with the arrow keys and press Enter to return to the Main Installation Menu.
Exit Install
Select [X Exit Install] with the arrow keys and press Enter. You will be asked to confirm exiting the installation: User Confirmation Requested Are you sure you wish to exit? The system will reboot (be sure to remove any floppies from the drives). [ Yes ] No Select &gui.yes; and remove the floppy if booting from the floppy. The CDROM drive is locked until the machine starts to reboot. The CDROM drive is then unlocked and the disk can be removed from drive (quickly). The system will reboot so watch for any error messages that may appear. FreeBSD Bootup FreeBSD Bootup on the &i386; If everything went well, you will see messages scroll off the screen and you will arrive at a login prompt. You can view the content of the messages by pressing Scroll-Lock and using PgUp and PgDn. Pressing Scroll-Lock again will return to the prompt. The entire message may not display (buffer limitation) but it can be viewed from the command line after logging in by typing dmesg at the prompt. Login using the username/password you set during installation (rpratt, in this example). Avoid logging in as root except when necessary. Typical boot messages (version information omitted): Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> AMD Features=0x80000800<SYSCALL,3DNow!> real memory = 268435456 (262144K bytes) config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 256311296 (250304K bytes) Preloaded elf kernel "kernel" at 0xc0491000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. md0: Malloc disk Using $PIR table, 4 entries at 0xc00fde60 npx0: <math processor> on motherboard npx0: INT 16 interface pcib0: <Host to PCI bridge> on motherboard pci0: <PCI bus> on pcib0 pcib1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 pci1: <Matrox MGA G200 AGP graphics accelerator> at 0.0 irq 11 isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0 isa0: <ISA bus> on isab0 atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 7.2 on pci0 usb0: <VIA 83C572 USB controller> on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: <VIA 82C586B ACPI interface> at device 7.3 on pci0 ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xe800-0xe81f irq 9 at device 10.0 on pci0 ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit) isa0: too many dependant configs (8) isa0: unexpected small tag 14 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: <keyboard controller (i8042)> at port 0x60-0x64 on isa0 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: <System console> at flags 0x1 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: plip0: <PLIP network interface> on ppbus0 lpt0: <Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master using UDMA33 ad2: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata1-master using UDMA33 acd0: CDROM <DELTA OTC-H101/ST3 F/W by OIPD> at ata0-slave using PIO4 Mounting root from ufs:/dev/ad0s1a swapon: adding /dev/ad0s1b as swap device Automatic boot in progress... /dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 48752 free (552 frags, 6025 blocks, 0.9% fragmentation) /dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1f: clean, 128997 free (21 frags, 16122 blocks, 0.0% fragmentation) /dev/ad0s1g: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1g: clean, 3036299 free (43175 frags, 374073 blocks, 1.3% fragmentation) /dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS /dev/ad0s1e: clean, 128193 free (17 frags, 16022 blocks, 0.0% fragmentation) Doing initial network setup: hostname. ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 inet6 fe80::5054::5ff::fede:731b%ed0 prefixlen 64 tentative scopeid 0x1 ether 52:54:05:de:73:1b lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 Additional routing options: IP gateway=YES TCP keepalive=YES routing daemons:. additional daemons: syslogd. Doing additional network setup:. Starting final network daemons: creating ssh RSA host key Generating public/private rsa1 key pair. Your identification has been saved in /etc/ssh/ssh_host_key. Your public key has been saved in /etc/ssh/ssh_host_key.pub. The key fingerprint is: cd:76:89:16:69:0e:d0:6e:f8:66:d0:07:26:3c:7e:2d root@k6-2.example.com creating ssh DSA host key Generating public/private dsa key pair. Your identification has been saved in /etc/ssh/ssh_host_dsa_key. Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: f9:a1:a9:47:c4:ad:f9:8d:52:b8:b8:ff:8c:ad:2d:e6 root@k6-2.example.com. setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout starting standard daemons: inetd cron sshd usbd sendmail. Initial rc.i386 initialization:. rc.i386 configuring syscons: blank_time screensaver moused. Additional ABI support: linux. Local package initialization:. Additional TCP options:. FreeBSD/i386 (k6-2.example.com) (ttyv0) login: rpratt Password: Generating the RSA and DSA keys may take some time on slower machines. This happens only on the initial boot-up of a new installation. Subsequent boots will be faster. If the X server has been configured and a Default Desktop chosen, it can be started by typing startx at the command line. Bootup of FreeBSD on the Alpha Alpha Once the install procedure has finished, you will be able to start FreeBSD by typing something like this to the SRM prompt: >>>BOOT DKC0 This instructs the firmware to boot the specified disk. To make FreeBSD boot automatically in the future, use these commands: >>> SET BOOT_OSFLAGS A >>> SET BOOT_FILE '' >>> SET BOOTDEF_DEV DKC0 >>> SET AUTO_ACTION BOOT The boot messages will be similar (but not identical) to those produced by FreeBSD booting on the &i386;. FreeBSD Shutdown It is important to properly shutdown the operating system. Do not just turn off power. First, become a superuser by typing su at the command line and entering the root password. This will work only if the user is a member of the wheel group. Otherwise, login as root and use shutdown -h now. The operating system has halted. Please press any key to reboot. It is safe to turn off the power after the shutdown command has been issued and the message Please press any key to reboot appears. If any key is pressed instead of turning off the power switch, the system will reboot. You could also use the Ctrl Alt Del key combination to reboot the system, however this is not recommended during normal operation. 支援的硬體 hardware FreeBSD currently runs on a wide variety of ISA, VLB, EISA, and PCI bus-based PCs with Intel, AMD, Cyrix, or NexGen x86 processors, as well as a number of machines based on the Compaq Alpha processor. Support for generic IDE or ESDI drive configurations, various SCSI controllers, PCMCIA cards, USB devices, and network and serial cards is also provided. FreeBSD also supports IBM's microchannel (MCA) bus. A list of supported hardware is provided with each FreeBSD release in the FreeBSD Hardware Notes. This document can usually be found in a file named HARDWARE.TXT, in the top-level directory of a CDROM or FTP distribution or in sysinstall's documentation menu. It lists, for a given architecture, what hardware devices are known to be supported by each release of FreeBSD. Copies of the supported hardware list for various releases and architectures can also be found on the Release Information page of the FreeBSD Web site. 安裝的疑難雜症解決 installation troubleshooting The following section covers basic installation troubleshooting, such as common problems people have reported. There are also a few questions and answers for people wishing to dual-boot FreeBSD with &ms-dos;. What to Do If Something Goes Wrong Due to various limitations of the PC architecture, it is impossible for probing to be 100% reliable, however, there are a few things you can do if it fails. Check the Hardware Notes document for your version of FreeBSD to make sure your hardware is supported. If your hardware is supported and you still experience lock-ups or other problems, reset your computer, and when the visual kernel configuration option is given, choose it. This will allow you to go through your hardware and supply information to the system about it. The kernel on the boot disks is configured assuming that most hardware devices are in their factory default configuration in terms of IRQs, IO addresses, and DMA channels. If your hardware has been reconfigured, you will most likely need to use the configuration editor to tell FreeBSD where to find things. It is also possible that a probe for a device not present will cause a later probe for another device that is present to fail. In that case, the probes for the conflicting driver(s) should be disabled. Some installation problems can be avoided or alleviated by updating the firmware on various hardware components, most notably the motherboard. The motherboard firmware may also be referred to as BIOS and most of the motherboard or computer manufactures have a website where the upgrades and upgrade information may be located. Most manufacturers strongly advise against upgrading the motherboard BIOS unless there is a good reason for doing so, which could possibly be a critical update of sorts. The upgrade process can go wrong, causing permanent damage to the BIOS chip. Do not disable any drivers you will need during the installation, such as your screen (sc0). If the installation wedges or fails mysteriously after leaving the configuration editor, you have probably removed or changed something you should not have. Reboot and try again. In configuration mode, you can: List the device drivers installed in the kernel. Disable device drivers for hardware that is not present in your system. Change IRQs, DRQs, and IO port addresses used by a device driver. After adjusting the kernel to match your hardware configuration, type Q to boot with the new settings. Once the installation has completed, any changes you made in the configuration mode will be permanent so you do not have to reconfigure every time you boot. It is still highly likely that you will eventually want to build a custom kernel. Dealing with Existing &ms-dos; Partitions DOS Many users wish to install &os; on PCs inhabited by µsoft; based operating systems. For those instances, &os; has a utility known as FIPS. This utility can be found in the tools directory on the install CD-ROM, or downloaded from one of various &os; mirrors. The FIPS utility allows you to split an existing &ms-dos; partition into two pieces, preserving the original partition and allowing you to install onto the second free piece. You first need to defragment your &ms-dos; partition using the &windows; Disk Defragmenter utility (go into Explorer, right-click on the hard drive, and choose to defrag your hard drive), or use Norton Disk Tools. Now you can run the FIPS utility. It will prompt you for the rest of the information, just follow the on screen instructions. Afterwards, you can reboot and install &os; on the new free slice. See the Distributions menu for an estimate of how much free space you will need for the kind of installation you want. There is also a very useful product from PowerQuest (http://www.powerquest.com) called &partitionmagic;. This application has far more functionality than FIPS, and is highly recommended if you plan to add/remove operating systems often. It does cost money, so if you plan to install &os; and keep it installed, FIPS will probably be fine for you. Using &ms-dos; and &windows; File Systems At this time, &os; does not support file systems compressed with the Double Space™ application. Therefore the file system will need to be uncompressed before &os; can access the data. This can be done by running the Compression Agent located in the Start> Programs > System Tools menu. &os; can support &ms-dos; based file systems. This requires you use the &man.mount.msdos.8; command (in &os; 5.X, the command is &man.mount.msdosfs.8;) with the required parameters. The utilities most common usage is: &prompt.root; mount_msdos /dev/ad0s1 /mnt In this example, the &ms-dos; file system is located on the first partition of the primary hard disk. Your situation may be different, check the output from the dmesg, and mount commands. They should produce enough information to give an idea of the partition layout. Extended &ms-dos; file systems are usually mapped after the &os; partitions. In other words, the slice number may be higher than the ones &os; is using. For instance, the first &ms-dos; partition may be /dev/ad0s1, the &os; partition may be /dev/ad0s2, with the extended &ms-dos; partition being located on /dev/ad0s3. To some, this can be confusing at first. NTFS partitions can also be mounted in a similar manner using the &man.mount.ntfs.8; command. Alpha User's Questions and Answers Alpha This section answers some commonly asked questions about installing FreeBSD on Alpha systems. Can I boot from the ARC or Alpha BIOS Console? ARC Alpha BIOS SRM No. &os;, like Compaq Tru64 and VMS, will only boot from the SRM console. Help, I have no space! Do I need to delete everything first? Unfortunately, yes. Can I mount my Compaq Tru64 or VMS filesystems? No, not at this time. Valentino Vaschetto Contributed by 進階安裝指南 This section describes how to install FreeBSD in exceptional cases. Installing FreeBSD on a System without a Monitor or Keyboard installation headless (serial console) serial console This type of installation is called a headless install, because the machine that you are trying to install FreeBSD on either does not have a monitor attached to it, or does not even have a VGA output. How is this possible you ask? Using a serial console. A serial console is basically using another machine to act as the main display and keyboard for a system. To do this, just follow the steps to create installation floppies, explained in . To modify these floppies to boot into a serial console, follow these steps: Enabling the Boot Floppies to Boot into a Serial Console mount If you were to boot into the floppies that you just made, FreeBSD would boot into its normal install mode. We want FreeBSD to boot into a serial console for our install. To do this, you have to mount the kern.flp floppy onto your FreeBSD system using the &man.mount.8; command. &prompt.root; mount /dev/fd0 /mnt Now that you have the floppy mounted, you must change into the /mnt directory: &prompt.root; cd /mnt Here is where you must set the floppy to boot into a serial console. You have to make a file called boot.config containing /boot/loader -h. All this does is pass a flag to the bootloader to boot into a serial console. &prompt.root; echo "/boot/loader -h" > boot.config Now that you have your floppy configured correctly, you must unmount the floppy using the &man.umount.8; command: &prompt.root; cd / &prompt.root; umount /mnt Now you can remove the floppy from the floppy drive. Connecting Your Null-modem Cable null-modem cable You now need to connect a null-modem cable between the two machines. Just connect the cable to the serial ports of the 2 machines. A normal serial cable will not work here, you need a null-modem cable because it has some of the wires inside crossed over. Booting Up for the Install It is now time to go ahead and start the install. Put the kern.flp floppy in the floppy drive of the machine you are doing the headless install on, and power on the machine. Connecting to Your Headless Machine cu Now you have to connect to that machine with &man.cu.1;: &prompt.root; cu -l /dev/cuaa0 That's it! You should now be able to control the headless machine through your cu session. It will ask you to put in the mfsroot.flp, and then it will come up with a selection of what kind of terminal to use. Select the FreeBSD color console and proceed with your install! 製作安裝片 為避免重覆說明，在文中所提到的「FreeBSD 光碟」， 在這裡指的是您所購買或自行燒錄的 FreeBSD CDROM 或 DVD。 There may be some situations in which you need to create your own FreeBSD installation media and/or source. This might be physical media, such as a tape, or a source that sysinstall can use to retrieve the files, such as a local FTP site, or an &ms-dos; partition. For example: You have many machines connected to your local network, and one FreeBSD disc. You want to create a local FTP site using the contents of the FreeBSD disc, and then have your machines use this local FTP site instead of needing to connect to the Internet. You have a FreeBSD disc, and FreeBSD does not recognize your CD/DVD drive, but &ms-dos;/&windows; does. You want to copy the FreeBSD installation files to a DOS partition on the same computer, and then install FreeBSD using those files. The computer you want to install on does not have a CD/DVD drive or a network card, but you can connect a Laplink-style serial or parallel cable to a computer that does. You want to create a tape that can be used to install FreeBSD. Creating an Installation CDROM As part of each release, the FreeBSD project makes available two CDROM images (ISO images). These images can be written (burned) to CDs if you have a CD writer, and then used to install FreeBSD. If you have a CD writer, and bandwidth is cheap, then this is the easiest way to install FreeBSD. Download the Correct ISO Images The ISO images for each release can be downloaded from ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch/version or the closest mirror. Substitute arch and version as appropriate. That directory will normally contain the following images: FreeBSD 4.<replaceable>X</replaceable> ISO Image Names and Meanings Filename Contains version-RELEASE-arch-miniinst.iso Everything you need to install FreeBSD. version-RELEASE-arch-disc1.iso Everything you need to install FreeBSD, and as many additional third party packages as would fit on the disc. version-RELEASE-arch-disc2.iso A live filesystem, which is used in conjunction with the Repair facility in sysinstall. A copy of the FreeBSD CVS tree. As many additional third party packages as would fit on the disc.
FreeBSD 5.<replaceable>X</replaceable> ISO Image Names and Meanings Filename Contains version-RELEASE-arch-bootonly.iso Everything you need to boot into a FreeBSD kernel and start the installation interface. The installable files have to be pulled over FTP or some other supported source. version-RELEASE-arch-miniinst.iso Everything you need to install FreeBSD. version-RELEASE-arch-disc1.iso Everything you need to install &os; and a live filesystem, which is used in conjunction with the Repair facility in sysinstall. version-RELEASE-arch-disc2.iso &os; documentation and as many third party packages as would fit on the disc.
You must download one of either the miniinst ISO image, or the image of disc one. Do not download both of them, since the disc one image contains everything that the miniinst ISO image contains. The miniinst ISO image is only available for releases prior to 5.4-RELEASE. Use the miniinst ISO if Internet access is cheap for you. It will let you install FreeBSD, and you can then install third party packages by downloading them using the ports/packages system (see ) as necessary. Use the image of disc one if you want to install a &os; release and want a reasonable selection of third party packages on the disc as well. The additional disc images are useful, but not essential, especially if you have high-speed access to the Internet. Write the CDs You must then write the CD images to disc. If you will be doing this on another FreeBSD system then see for more information (in particular, and ). If you will be doing this on another platform then you will need to use whatever utilities exist to control your CD writer on that platform. The images provided are in the standard ISO format, which many CD writing applications support. If you are interested in building a customized release of FreeBSD, please see the Release Engineering Article. Creating a Local FTP Site with a FreeBSD Disc installation network FTP FreeBSD discs are laid out in the same way as the FTP site. This makes it very easy for you to create a local FTP site that can be used by other machines on your network when installing FreeBSD. On the FreeBSD computer that will host the FTP site, ensure that the CDROM is in the drive, and mounted on /cdrom. &prompt.root; mount /cdrom Create an account for anonymous FTP in /etc/passwd. Do this by editing /etc/passwd using &man.vipw.8; and adding this line: ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Ensure that the FTP service is enabled in /etc/inetd.conf. Anyone with network connectivity to your machine can now chose a media type of FTP and type in ftp://your machine after picking Other in the FTP sites menu during the install. If the boot media (floppy disks, usually) for your FTP clients is not precisely the same version as that provided by the local FTP site, then sysinstall will not let you complete the installation. If the versions are not similar and you want to override this, you must go into the Options menu and change distribution name to any. This approach is OK for a machine that is on your local network, and that is protected by your firewall. Offering up FTP services to other machines over the Internet (and not your local network) exposes your computer to the attention of crackers and other undesirables. We strongly recommend that you follow good security practices if you do this. Creating Installation Floppies installation floppies If you must install from floppy disk (which we suggest you do not do), either due to unsupported hardware or simply because you insist on doing things the hard way, you must first prepare some floppies for the installation. At a minimum, you will need as many 1.44 MB or 1.2 MB floppies as it takes to hold all the files in the bin (binary distribution) directory. If you are preparing the floppies from DOS, then they must be formatted using the &ms-dos; FORMAT command. If you are using &windows;, use Explorer to format the disks (right-click on the A: drive, and select Format). Do not trust factory pre-formatted floppies. Format them again yourself, just to be sure. Many problems reported by our users in the past have resulted from the use of improperly formatted media, which is why we are making a point of it now. If you are creating the floppies on another FreeBSD machine, a format is still not a bad idea, though you do not need to put a DOS filesystem on each floppy. You can use the disklabel and newfs commands to put a UFS filesystem on them instead, as the following sequence of commands (for a 3.5" 1.44 MB floppy) illustrates: &prompt.root; fdformat -f 1440 fd0.1440 &prompt.root; disklabel -w -r fd0.1440 floppy3 &prompt.root; newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0 Use fd0.1200 and floppy5 for 5.25" 1.2 MB disks. Then you can mount and write to them like any other filesystem. After you have formatted the floppies, you will need to copy the files to them. The distribution files are split into chunks conveniently sized so that five of them will fit on a conventional 1.44 MB floppy. Go through all your floppies, packing as many files as will fit on each one, until you have all of the distributions you want packed up in this fashion. Each distribution should go into a subdirectory on the floppy, e.g.: a:\bin\bin.aa, a:\bin\bin.ab, and so on. Once you come to the Media screen during the install process, select Floppy and you will be prompted for the rest. Installing from an &ms-dos; Partition installation from MS-DOS To prepare for an installation from an &ms-dos; partition, copy the files from the distribution into a directory called freebsd in the root directory of the partition. For example, c:\freebsd. The directory structure of the CDROM or FTP site must be partially reproduced within this directory, so we suggest using the DOS xcopy command if you are copying it from a CD. For example, to prepare for a minimal installation of FreeBSD: C:\> md c:\freebsd C:\> xcopy e:\bin c:\freebsd\bin\ /s C:\> xcopy e:\manpages c:\freebsd\manpages\ /s Assuming that C: is where you have free space and E: is where your CDROM is mounted. If you do not have a CDROM drive, you can download the distribution from ftp.FreeBSD.org. Each distribution is in its own directory; for example, the base distribution can be found in the &rel.current;/base/ directory. For as many distributions you wish to install from an &ms-dos; partition (and you have the free space for), install each one under c:\freebsd — the BIN distribution is the only one required for a minimum installation. Creating an Installation Tape installation from QIC/SCSI Tape Installing from tape is probably the easiest method, short of an online FTP install or CDROM install. The installation program expects the files to be simply tarred onto the tape. After getting all of the distribution files you are interested in, simply tar them onto the tape: &prompt.root; cd /freebsd/distdir &prompt.root; tar cvf /dev/rwt0 dist1 ... dist2 When you perform the installation, you should make sure that you leave enough room in some temporary directory (which you will be allowed to choose) to accommodate the full contents of the tape you have created. Due to the non-random access nature of tapes, this method of installation requires quite a bit of temporary storage. When starting the installation, the tape must be in the drive before booting from the boot floppy. The installation probe may otherwise fail to find it. Before Installing over a Network installation network serial (SLIP or PPP) installation network parallel (PLIP) installation network Ethernet There are three types of network installations available. Serial port (SLIP or PPP), Parallel port (PLIP (laplink cable)), or Ethernet (a standard Ethernet controller (includes some PCMCIA)). The SLIP support is rather primitive, and limited primarily to hard-wired links, such as a serial cable running between a laptop computer and another computer. The link should be hard-wired as the SLIP installation does not currently offer a dialing capability; that facility is provided with the PPP utility, which should be used in preference to SLIP whenever possible. If you are using a modem, then PPP is almost certainly your only choice. Make sure that you have your service provider's information handy as you will need to know it fairly early in the installation process. If you use PAP or CHAP to connect your ISP (in other words, if you can connect to the ISP in &windows; without using a script), then all you will need to do is type in dial at the ppp prompt. Otherwise, you will need to know how to dial your ISP using the AT commands specific to your modem, as the PPP dialer provides only a very simple terminal emulator. Please refer to the user-ppp handbook and FAQ entries for further information. If you have problems, logging can be directed to the screen using the command set log local .... If a hard-wired connection to another FreeBSD (2.0-R or later) machine is available, you might also consider installing over a laplink parallel port cable. The data rate over the parallel port is much higher than what is typically possible over a serial line (up to 50 kbytes/sec), thus resulting in a quicker installation. Finally, for the fastest possible network installation, an Ethernet adapter is always a good choice! FreeBSD supports most common PC Ethernet cards; a table of supported cards (and their required settings) is provided in the Hardware Notes for each release of FreeBSD. If you are using one of the supported PCMCIA Ethernet cards, also be sure that it is plugged in before the laptop is powered on! FreeBSD does not, unfortunately, currently support hot insertion of PCMCIA cards during installation. You will also need to know your IP address on the network, the netmask value for your address class, and the name of your machine. If you are installing over a PPP connection and do not have a static IP, fear not, the IP address can be dynamically assigned by your ISP. Your system administrator can tell you which values to use for your particular network setup. If you will be referring to other hosts by name rather than IP address, you will also need a name server and possibly the address of a gateway (if you are using PPP, it is your provider's IP address) to use in talking to it. If you want to install by FTP via a HTTP proxy, you will also need the proxy's address. If you do not know the answers to all or most of these questions, then you should really probably talk to your system administrator or ISP before trying this type of installation. Before Installing via NFS installation network NFS The NFS installation is fairly straight-forward. Simply copy the FreeBSD distribution files you want onto an NFS server and then point the NFS media selection at it. If this server supports only privileged port (as is generally the default for Sun workstations), you will need to set the option NFS Secure in the Options menu before installation can proceed. If you have a poor quality Ethernet card which suffers from very slow transfer rates, you may also wish to toggle the NFS Slow flag. In order for NFS installation to work, the server must support subdir mounts, for example, if your FreeBSD &rel.current; distribution directory lives on: ziggy:/usr/archive/stuff/FreeBSD, then ziggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff. In FreeBSD's /etc/exports file, this is controlled by the options. Other NFS servers may have different conventions. If you are getting permission denied messages from the server, then it is likely that you do not have this enabled properly. diff --git a/zh_TW.Big5/books/handbook/introduction/chapter.sgml b/zh_TW.Big5/books/handbook/introduction/chapter.sgml index 7ac1f7097f..cf47fce48e 100644 --- a/zh_TW.Big5/books/handbook/introduction/chapter.sgml +++ b/zh_TW.Big5/books/handbook/introduction/chapter.sgml @@ -1,794 +1,794 @@ Jim Mock Restructured, reorganized, and parts rewritten by 簡介 概述 非常感謝您對 FreeBSD 感興趣！以下章節涵蓋 FreeBSD 計劃的各方面：比如它的歷史、目標、開發模式等等。 讀完這章，您將了解︰ FreeBSD 與其他 OS 之間的關係； FreeBSD 計劃的歷史源流； FreeBSD 計劃的目標； FreeBSD open-source 開發模式的基礎概念； 當然囉，還有 FreeBSD 這名字的緣故。 Welcome to FreeBSD! 4.4BSD-Lite FreeBSD 是一個從 4.4BSD-Lite 衍生出而能在以 Intel (x86 and &itanium;), AMD64, Alpha, Sun &ultrasparc; 為基礎的電腦上執行的作業系統。同時，移植到其他平台的工作也在進行中。 對於本計劃歷史的介紹，請看 FreeBSD 歷史源流， 對於 FreeBSD 的最新版本介紹，請看 current release 。若打算對於 FreeBSD 計劃有所貢獻的話(像是程式碼硬體設備，資金)， 請看 如何對 FreeBSD 有貢獻。 FreeBSD 能做什麼？ FreeBSD 提供給你許多先進功能。這些功能包括： 先佔式多工(preemptive multitasking) 動態優先權調整的『先佔式多工』能夠確保，即使在系統負擔很重的情況下， 程式執行平順並且應用程式與使用者公平地共享資源。 支援多人共用 『多人共用(multi-user)』代表著許多人可以同時使用一個 FreeBSD 系統來處理各自的事務。 系統的硬體周邊(如印表機及磁帶機)也可以讓所有的使用者適當地分享。 也可以針對各別使用者或一群使用者的系統資源，予以設限， 以保護系統不致被過度使用。 TCP/IP 網路功能 好用的『TCP/IP 網路功能』可支援許多業界標準，比如：SLIP、PPP、NFS、DHCP 和 NIS 的支援，也就是說 FreeBSD 可以容易地跟其他作業系統透過網路共同運作， 或是當作企業的伺服器用途，例如提供遠端檔案共享(NFS)及電子郵件(email)等服務， 或是讓您的企業連上網際網路(Internet)並提供 WWW、FTP、路由(routing) 、及防火牆(firewall、security) 等必備服務。 記憶體保護 『記憶體保護(Memory protection)』能確保程式(或是使用者)不會互相干擾， 即使任何程式有不正常的運作，都不會影響其他程式的執行。 FreeBSD 是『32位元(32-bit)』的作業系統 (在 Alpha、&itanium;、 AMD64 及 &ultrasparc; 上則是『64位元(64-bit)』) — 打從一開始便是這樣設計的。 X Window System XFree86 業界標準的『X Window 系統』(X11R6)可以在常見的便宜 VGA 顯示卡/螢幕， 提供了圖形化的使用者介面(GUI)，並且包括了完整的原始程式碼。 binary compatibility Linux binary compatibility SCO binary compatibility SVR4 binary compatibility BSD/OS binary compatibility NetBSD 能『直接執行』許多其他作業系統(比如： Linux、SCO、SVR4、BSDI 和 NetBSD) 的可執行檔。 數以萬計的立即可以執行的應用程式，這些都可透過 FreeBSD 的『ports』及『packages』軟體管理機制來取得。 不再需要費心到網路上到處搜尋所需要的軟體。 此外，網路上尚有可非常容易移植的數以萬計應用程式。 FreeBSD 的原始程式碼與許多常見的商業版 &unix; 系統都相容， 所以大部分的程式都只需要很少的修改(或根本不用修改) ，就可以編譯執行。 virtual memory 需要時才置換(demand paged) virtual memory 及 merged VM/buffer cache 的設計， 這點在系統中有用去大量記憶體的程式執行時，仍然有不錯的效率表現。 Symmetric Multi-Processing (SMP) 支援 CPU 的對稱多工處理(SMP)：可以支援多 CPU 的電腦系統。 compilers C compilers C++ compilers FORTRAN 完全相容的 C、C++ 以及 Fortran 的環境和其他開發工具。 以及其他許多可供進階研發的程式語言也收集在 ports 和 packages。 source code 整個系統都有『原始程式碼』， 這讓你對作業環境擁有最完全的掌握度。 既然能擁有完全開放的系統，何苦被特定封閉軟體所約束，任廠商擺佈呢？ 廣泛且豐富的『線上文件』。 當然囉，還不止如此！ 4.4BSD-Lite Computer Systems Research Group (CSRG) U.C. Berkeley FreeBSD 系統乃是基於美國加州大學柏克萊分校的電腦系統研究群 (Computer Systems Research Group 也就是 CSRG) 所發行的 4.4BSD-Lite，以及基於 BSD 系統開發的優良傳統。 除了由 CSRG 所提供的高品質的成果， 為了提供可處理真正具負荷的工作， FreeBSD 計劃也投入了數千小時以上的細部調整， 以能獲得最好的執行效率以及系統的穩定度。 正當許多商業上的巨人正努力地希望能提供效能及穩定時， FreeBSD 已經具備這樣的特質 -- 就是現在！ FreeBSD 的運用範圍無限，其實完全限制在你的想像力上。 從軟體的開發到工廠自動化，或是人造衛星上面的天線的方位角度的遠端控制； 這些功能若可以用商用的 Unix 產品來達成， 那麼極有可能使用 FreeBSD 也能辦到！ FreeBSD 也受益於來自於全球各研究中心及大學所開發的數千個高品質的軟體 ，這些通常只需要花費很少的費用或根本就是免費的。 當然也有商業軟體，而且出現的數目是與日俱增。 由於每個人都可以取得 FreeBSD 的原始程式碼， 這個系統可以被調整而能執行任何原本完全無法想像的功能或計劃， 而對於從各廠商取得的作業系統通常沒有辦法這樣地被修改。 以下提供一些人們使用 FreeBSD 的例子： 網路服務： FreeBSD 內建強勁的網路功能使它成為網路服務(如下例)的理想平台： FTP servers 檔案伺服器(FTP servers) web servers 全球資訊網伺服器(WWW servers) (標準的或更安全的 SSL 連線) firewall IP masquerading 防火牆以及 NAT (IP masquerading) gateways。 electronic mail 電子郵件伺服器(Electronic Mail servers) USENET 網路新聞伺服器(USENET News) 或是電子佈告欄系統(BBS) 還有更多... 有了 FreeBSD，您可以容易地先用便宜的 386 PC， 再逐步升級您的機器到四個 CPU 的 Xeon 並使用磁碟陣列(RAID)來滿足您企業運用上的需求。 教育： 如果你是資訊或相關工程領域的學生，再也沒有比使用 FreeBSD 能學到更多作業系統、計算機結構、及網路的方法了。 另外如果你想利用電腦來處理一些其他的 工作，還有一些如 CAD、 數學運算以及圖形處理軟體等可以免費地取得使用。 研究：有了完整的原始程式碼，FreeBSD 是研究作業系統及電腦科學的極佳環境。 具有免費且自由取得特性的 FreeBSD 也使得一個分置兩地的合作計劃，不必擔心版權及系統開放性的問題， 而能自在的交流。 router DNS Server 網路： 你如果需要 router、Name Server (DNS) 或安全的防火牆(Firewall)， FreeBSD 可以輕易的將你沒有用到的 386 或 486 PC 變身成為絕佳的伺服器，甚至具有過濾封包(packet-filter) 的功能。 X Window System XFree86 X Window System Accelerated-X X 視窗工作站： FreeBSD 是 X 終端機的良策，你可以使用免費的 X11 Server 或是由 Xi Graphics 所提供的商業版 X Server。 FreeBSD 不但可以充當遠端 X 程式終端機， 也可以執行本地的 X 程式而減輕大型工作站的負荷。 如果有一台中央伺服器的話，FreeBSD 甚至可以經由網路開機 (不需硬碟，也就是diskless) ，而變成更便宜且易於管理的工作站。 GNU Compiler Collection 軟體開發： 基本安裝的 FreeBSD 就包含了完整的程式開發工具，如 GNU C/C++ 編譯器及除錯器。 你可以經由燒錄 CDROM、DVD 或是從 FTP 站上抓回 FreeBSD -- 包括立即可執行的系統以及系統的完整程式碼。 詳情請參閱 取得 FreeBSD。 誰在用 FreeBSD？ users large sites running FreeBSD 許多 Internet 上的大型網站都是以 FreeBSD 作為它的作業系統，例如： Yahoo! Yahoo! Apache Apache Blue Mountain Arts Blue Mountain Arts Pair Networks Pair Networks Sony Japan Sony Japan Netcraft Netcraft Weathernews Weathernews Supervalu Supervalu TELEHOUSE America TELEHOUSE America Sophos Anti-Virus Sophos Anti-Virus JMA Wired JMA Wired 以及許多其他的網站。 關於 FreeBSD 計劃 接下來講的是 FreeBSD 計劃的背景，包含歷史源流的簡介、計劃的目標，以及開發的模式。 Jordan Hubbard Contributed by FreeBSD 歷史源流的簡介 386BSD Patchkit Hubbard, Jordan Williams, Nate Grimes, Rod FreeBSD Project history FreeBSD 計畫的想法是在 1993 年初所形成的， 那是源自於維護一組 『非官方 386BSD 的 patchkit(修正工具)』計劃的三個協調維護人 Nate Williams，Rod Grimes 和我(Jordan Hubbard)。 386BSD 我們最初的目標是做出一份 386BSD 綜合修正的 snapshot 版，以便修正當時一堆 patchkit 都不容易解決的問題。有些人可能還記得早期的計劃名稱叫做 386BSD 0.5 或 386BSD Interim 就是這個原因。 Jolitz, Bill 386BSD 是 Bill Jolitz 的作業系統，在當時就已有約一年的分裂討論。 當該修正工具 (patchkit) 日漸龐雜得令人不舒服，我們無異議地同意要作一些事了， 並決定提供一份臨時性的 淨化版(cleanup) 來幫助 Bill。 然而，由於 Bill Jolitz 忽然決定取消其對該計劃的認可，且沒有明確指出未來的打算， 所以該計劃便突然面臨斷炊危機。 Greenman, David Walnut Creek CDROM 不久我們便決定在即使沒有 Bill 的支持下，讓該計劃仍然繼續下去， 最後我們採用 David Greenman 丟銅板決定的名字，也就是『FreeBSD』。 在詢問了當時的一些使用者意見之後，就開始決定了最初的目標， 當該計劃開始實施一切就要成真時，一切就變得更清楚了。 我跟 Walnut Creek CDROM 討論發行 CDROM 這樣子不便上網的人就可以用比較簡單的方式取得 FreeBSD。 Walnut Creek CDROM 不只贊成以 CDROM 來發行 FreeBSD 的想法，同時提供了一台機器以及快速的網際網路的頻寬。 如果不是 Walnut Creek CDROM 幾乎是空前的信任這個剛開始還是完全默默無聞的計劃， 那麼很可能 FreeBSD 不會如此快速的成長到今日這樣的規模。 4.3BSD-Lite Net/2 U.C. Berkeley 386BSD Free Software Foundation 第一張以 CDROM (及網路)發行的 FreeBSD 1.0 是在 1993 年十二月。 該版本是基於由 U.C. Berkeley 以磁帶方式發行的 4.3BSD-Lite (Net/2)以及許多來自於 386BSD 和自由軟體基金會的軟體。對於第一次發行而言還算成功， 我們又接著於 1994 年 5 月發行了相當成功的 FreeBSD 1.1。 Novell U.C. Berkeley Net/2 AT&T 然而此後不久，另一個意外的風暴在 Novell 和 U.C. Berkeley 關於 Berkeley Net/2 磁帶之法律地位的訴訟確定之後形成。 U.C. Berkeley 接受大部份的 Net/2 的程式碼都是『侵佔來的』且是屬於 Novell 的財產 -- 事實上是當時不久前從 AT&T 取得的。 Berkeley 得到的是 Novell 對於 4.4BSD-Lite 的『祝福』，最後當 4.4BSD-Lite 終於發行之後，便不再是侵佔行為。 而所有現有 Net/2 使用者都被強烈建議更換新版本，這包括了 FreeBSD。 於是，我們被要求於 1994 年 6 月底前停止散佈基於 Net/2 的產品。在此前提之下，本計劃被允許在期限以前作最後一次發行，也就是 FreeBSD 1.1.5.1。 FreeBSD 便開始了這宛如『重新發明輪子』的艱鉅工作 -- 從全新的且不完整的 4.4BSD-Lite 重新整合。 這個 Lite 版本是不完整的，因為 Berkeley 的 CSRG 已經刪除了大量在建立一個可以開機執行的系統所需要的程式碼 (基於若干法律上的要求)，且該版本在 Intel 平台的移植是非常不完整的。 直到 1994 年 11 月本計劃才完成了這個轉移， 同時在該年 12 月底以 CDROM 以及網路的形式發行了 FreeBSD 2.0。 雖然該份版本在當時有點匆促粗糙，但仍是富有意義的成功。 隨之於 1995 年 6 月又發行了更容易安裝，更好的 FreeBSD 2.0.5。 我們在 1996 年 8 月發行了 FreeBSD 2.1.5，在 ISP 和商業團體中非常流行。 隨後， 2.1-STABLE 分支的另一個版本應運而生，它就是在 1997 年 2 月發行 FreeBSD 2.1.7.1 ，同時也是 2.1-STABLE 分支的最後版。之後此分支便進入維護狀態， 僅僅提供安全性的加強和其他嚴重錯誤修補的維護(RELENG_2_1_0)。 1996 年 11 月 FreeBSD 2.2 從開發主軸分支 (-CURRENT) 出來成為 RELENG_2_2 分支。它的第一個完整版(2.2.1)於 1997 年 4 月發行。 2.2 分支的延續版本在 97 年夏秋之間發行的，其最後版是在 1998 年 11 月發行的 2.2.8 版。 第一個正式的 3.0 版本在 1998 年 10 月發行，亦即宣告 2.2 分支的落幕。 1999/01/20 日再度分支，這產生了 4.0-CURRENT 以及 3.X-STABLE 兩個分支。 3.X-STABLE 方面，3.1 發行於 1999/02/15，3.2 發行於1999/05/15，3.3 發行於 1999/09/16， 3.4 發行於 1999/12/20，3.5 發行於 2000/06/24 ，接下來幾天後發佈了一些的修補檔(對 Kerberos 安全性方面的修正)，就升級至 3.5.1 ，這是 3.X 分支最後一個發行版本。 在 2000/03/13 又有了一個新的分支， 也就是 4.X-STABLE 。這個分支之後發佈了許多的發行版本︰ 4.0-RELEASE 在 2000 年 3 月發行， 而最後的 4.11-RELEASE 則在 2005 年 1 月發行。4-STABLE 分支的支援會持續到 2007/01/31 ，但主要焦點在於安全方面的漏洞、臭蟲及其他嚴重問題的修補。 期待已久的 5.0-RELEASE 在 2003/01/19 正式發行。這是將近開發三年的巔峰之作，同時 也開始加強多顆CPU(SMPng)的支援、kernel thread(KSE) 的支援、檔案系統採用 UFS2 以及支援 snapshot 等， 並支援 &ultrasparc; 和 ia64 平台、支援藍芽、32 bit 的 PCMCIA 等。之後於 2003 年 6 月發行了 5.1。 而 -CURRENT 這個發展主軸分支的最後 5.X 版本是在 2004 年 2 月正式發行的 5.2.1-RELEASE，在 5.X 系列進入 -STABLE (RELENG_5分支)之後，-CURRENT 就轉移為 6.X 系列。 RELENG_5 分支於 2004 年 8 月正式開跑，之後是 5.3-RELEASE ，它是 5-STABLE 分支的第一個發行版本。&rel2.current;-RELEASE 的最新發表是在 &rel2.current.date; 發行的 &rel2.current;-RELEASE，照往例 RELENG_5 分支還將有後續的發行版。 RELENG_6 分支於 2005 年 7 月開跑，而 6.X 分支的第一個 release(6.0-RELEASE) 是在 2005 年 11 月出的。 最新的 &rel.current;-RELEASE 是在 &rel.current.date; 發行。當然囉，RELENG_6 分支還將有後續的發行版。 目前，長期的開發計畫繼續在 7.X-CURRENT (trunk) 分支中進行，而 7.X 的 CDROM (當然，也可以用網路抓) snapshot 版本可以在 FreeBSD snapshot server 取得。 Jordan Hubbard Contributed by FreeBSD 計劃的目標 FreeBSD Project goals FreeBSD 計劃的目標在於提供可作任意用途的軟體而不附帶任何限制條文。 我們之中許多人對程式碼 (以及計畫本身) 都有非常大的投入， 因此，當然不介意偶爾有一些資金上的補償，但我們並沒打算堅決地要求得到這類資助。 我們認為我們的首要『使命(mission)』是為任何人提供程式碼， 不管他們打算用這些程式碼做什麼， 因為這樣程式碼將能夠被更廣泛地使用，從而發揮其價值。 我認為這是自由軟體最基本的，同時也是我們所倡導的一個目標。 GNU General Public License (GPL) GNU Lesser General Public License (LGPL) BSD Copyright 我們程式碼樹中，有若干是以 GNU GPL 或者 LGPL 發佈的那些程式碼帶有少許的附加限制，還好只是強制性的要求開放程式碼而不是別的。 由於使用 GPL 的軟體在商業用途上會增加若干複雜性，因此，如果可以選擇的話， 我們會比較喜歡使用限制相對更寬鬆的 BSD 版權來發佈軟體。 Satoshi Asami Contributed by FreeBSD 的開發模式 FreeBSD Project development model FreeBSD 的開發是一個非常開放且具彈性的過程，就像從 貢獻者名單 所看到的，是由全世界上千上萬的貢獻者發展起來的。 FreeBSD 的開發基礎架構允許數以百計的開發者透過網際網路協同工作。 我們也經常關注著那些對我們的計畫感興趣的新開發者和新的創意， 那些有興趣更進一步參與計劃的人只需要在 &a.hackers; 連繫我們。 &a.announce; 對那些希望了解我們進度的人也是相當有用的。 無論是單獨開發者或者封閉式的團隊合作，多瞭解 FreeBSD 計劃和它的開發過程會是不錯的︰ The CVS repository CVS repository Concurrent Versions System CVS FreeBSD 的中央 source tree 是以 CVS (Concurrent Versions System) 來維護的，它是個自由軟體，可用來做為版本控制，一裝完 FreeBSD 內就有附了。 最主要的 CVS repository 是位於美國加州 Santa Clara 的某台機器上， 然後再 mirror 到世界上其他的許多機器上。CVS tree 內有兩個主分支：-CURRENT 以及 -STABLE ，這些都可輕鬆複製到自己機器上。 詳情請參閱 更新你的 source tree 一節。 The committers list committers 所謂的 committers 指的是對 CVS tree 有 write 權限， 並依不同授權部分，而有不同權限可修改 FreeBSD source。 (committer 這詞源自 &man.cvs.1; 中的 commit 指令，該指令是用來把新的修改提交給 CVS repository。) 而提交修改給 committer 們檢查的最好方式，就是用 &man.send-pr.1; 指令。 若提交 PR 的流程、系統上有壅塞現象的話，也可以改用寄信方式，寄信到 &a.committers; 即可。 The FreeBSD core team core team 如果把 FreeBSD 看成是一家公司的話，FreeBSD core team 就相當於『董事會(board of directors)』。 core team 的主要職責在於確保此計劃有良好的架構，以朝著正確的方向發展。 此外，邀請熱血且負責的軟體開發者加入 committers 行列，以在若干成員離去時得以補充新血。 目前的 core team 是在 2004 年 6 月 committers 候選人中選出來的，每兩年會舉辦一次選舉 有些 core team 成員還負責某些特定範圍，也就是說他們必須盡量確保一些子系統的穩定、效能。 關於 FreeBSD 開發者們以及各自責任範圍，請參閱 貢獻者名單。 core team 大部分成員加入 FreeBSD 開發都是志工性質而已，並未從本計劃中獲得任何薪酬， 所以不該把 commitment 誤解為 guaranteed support 才對。 剛前面所講的『董事會』可能是不恰當的類推，或許我們應該說： 他們是一群自願放棄原本的優渥生活、個人其他領域成就，而選擇投入 FreeBSD 開發的熱血有為者才對！ 其他的貢獻者 contributors 最後一點，但這點絕非最不重要的，最大的開發者團隊就是持續為我們提供回饋以及錯誤修正的使用者自己。 與 FreeBSD 非核心開發者互動的主要方式，便是透過訂閱 &a.hackers; 來進行溝通， 這方面可參考，請參閱 以瞭解各式不同的 FreeBSD 郵遞論壇(mailing lists)。 FreeBSD 貢獻者名單 相當長且不斷成長中，只要有貢獻就會被列入其中，要不要立即考慮貢獻 FreeBSD 一些回饋呢？ 然而，提供原始碼並非為這個計劃做貢獻的唯一方式； 還需要大家投入的完整工作列表、說明，請參閱 FreeBSD 官網。 簡單的說，我們的開發模式就像是一組沒有拘束的同心圓。 - 這種集中開發模式是以 給使用者方便， + 這種集中開發模式是以 給使用者方便 為主， 同時讓他們能很容易地共同維護軟體，而不會把潛在的貢獻者排除在外！ 我們的目標是提供含有大量一致性的 應用軟體(ports/packages) ，以便讓使用者輕鬆安裝、使用的作業系統 —— 而這開發模式相當符合此一目標。 我們對於那些想要加入 FreeBSD 開發者的期待是：請保持如同前人一樣的投入，以確保繼續成功！ 最新的 FreeBSD 發行版本 NetBSD OpenBSD 386BSD Free Software Foundation U.C. Berkeley Computer Systems Research Group (CSRG) FreeBSD 是免費使用且帶有完整原始程式碼的以 4.4BSD-Lite 為基礎的系統，可以在 Intel &i386;, &i486;, &pentium;, &pentium; Pro, &celeron;, &pentium; II, &pentium; III, &pentium; 4 (或者相容型號), &xeon;, DEC Alpha 和 Sun &ultrasparc; 為基礎的電腦上執行的作業系統。 它主要以加州大學巴爾克利分校 的 CSRG 研究小組的軟體為基礎，並加入了 NetBSD、OpenBSD、386BSD 以及自由軟體基金會的一些東西。 自從 1994 年末，我們發佈了 FreeBSD 2.0 之後，系統的執行效率、 功能、穩定性都有了令人注目的提升。 最大的改變就是我們將記憶體與檔案系統的 cache 機制結合在一起。 這不只使得系統的表現變得更好, 並且使得 FreeBSD 系統最少的記憶體需求減少到 5 MB。 其它的改進包括完整的 NIS cilent and server 功能支援， 支援 transaction TCP、PPP 撥接連線、整合的 DHCP 支援、 SCSI 子系統的改進、ISDN 的支援，ATM、FDDI 以及乙太網路 (Ethernet、包括 100 Mbit 和 Gigabit) 的支援，提升了最新的 Adaptec 控制卡驅動程式的改善，以及數以千計的 bug 修正。 除了最基本的系統軟體，FreeBSD 還提供了廣受歡迎的套件軟體管理機制： Ports Collection。 到本書付印時，已有超過 &os.numports; 個 ports，其中範疇包括從 http(WWW) 伺服器到遊戲、程式語言、編輯器以及您能想到的幾乎所有的東西。 完整的 Ports Collection 需要約 &ports.size; 的硬碟空間，除了 port 基本架構檔案外，都只儲存與該 port 軟體的原始碼有『須要變更』的部份。 如此一來，我們可以更容易更新這些 ports， 也大量的減少如舊的 1.0 版 Ports Collection 對於硬碟空間的需求。 要安裝一個 port 的話，只需要進入該 port 的目錄，輸入 make install ，這樣子系統就會幫你裝好了。您要編譯的每個程式的完整原始程式， 都可從 FTP 或 CDROM 中獲得，所以您只需準備足夠的硬碟空間來編譯你要的 port 軟體。 幾乎每一個 port 都有已事先編譯好的 package以方便安裝， 如果不想從編譯 port 的人，只要用個簡單指令(pkg_add)就可以安裝。 有關 packages 和 ports 的細節，可以參閱 。 FreeBSD 主機的 /usr/share/doc 目錄下找到許多有用的文件， 來幫助您安裝、使用 FreeBSD。也可以使用下面的網址，以瀏覽器來翻閱本機上安裝的手冊︰ FreeBSD 使用手冊 /usr/share/doc/handbook/index.html FreeBSD 常見問答集 /usr/share/doc/faq/index.html 此外，可在下列網址找到最新版 (也是更新最頻繁的版本)：。