Index: head/zh_TW.UTF-8/books/handbook/install/chapter.xml =================================================================== --- head/zh_TW.UTF-8/books/handbook/install/chapter.xml (revision 46996) +++ head/zh_TW.UTF-8/books/handbook/install/chapter.xml (revision 46997) @@ -1,4569 +1,4569 @@ - 安裝 FreeBSD + 安裝 &os; 8.<replaceable>X</replaceable> JimMockRestructured, reorganized, and parts rewritten by RandyPrattThe sysinstall walkthrough, screenshots, and general copy by 概述 installation FreeBSD 提供一個簡單好用的文字介面安裝程式，叫做 sysinstall。 這是 FreeBSD 預設使用的安裝程式 。協力廠商若有意願的話，也可以改用自己的安裝程式。 本章將說明如何使用 sysinstall 來安裝 FreeBSD。 讀完這章，您將了解︰ 如何製作 FreeBSD 安裝片 FreeBSD 對硬碟的使用及配置。 如何啟動 sysinstall 程式。 在執行 sysinstall 時會問的相關問題有哪些、這些問題的意思為何、以及該如何回答。 在開始閱讀這章之前，您需要︰ 閱讀要安裝的 FreeBSD 版本所附之硬體支援表， 以確定您的硬體有沒有被支援。 一般來說，此安裝說明是針對 &i386; (相容的 PC 機種) 架構的電腦。 如果有其他架構(比如 Alpha)的安裝說明，我們會一併列出。 雖然本文件會常常更新，但有可能與您安裝版本上所附的說明文件有些許出入。 在此，我們建議您把本說明文章當作一般的安裝參考原則就好。 硬體需求 最低需求 安裝 &os; 的硬體方面最低需求，依各 &os; 版本與硬體架構差別而有所不同。 關於安裝所需的最低需求，可在 &os; 網站的 Release Information 找相關的 Installation Notes 說明。 接下來的章節會有相關說明整理。 根據安裝 &os; 的方式不同，可能會需要軟碟機或光碟機， 或某些情況則是要網路卡。 這些部份會在 有介紹。 &os;/&arch.i386; 及 &os;/&arch.pc98; 架構 &os;/&arch.i386; 及 &os;/&arch.pc98; 兩種版本均須 486 或更好的處理器， 以及至少 24 MB 的 RAM、至少 150 MB 的硬碟空間， 才能進行最小安裝。 對老舊硬體而言，在大部份情況裝更多的 RAM 與更大的硬碟空間，會比使用更快的 CPU 更有用。 &os;/&arch.alpha; 架構 若要裝 &os;/&arch.alpha;，則需確認該機型是否有支援 (請參閱 ) 且必須整顆硬碟皆給 &os; 使用。 目前無法同時與其他作業系統共存。 這硬碟須接到 SRM 韌體有支援的 SCSI controller 上，或者 IDE 硬碟 (該機型的 SRM 有支援可從 IDE 硬碟開機)。 此外，還需該機型的 SRM console firmware。 有些機型可以選擇 AlphaBIOS (or ARC) firmware 或 SRM 來用。 若沒有的話，則需從硬體廠商的網站去下載新的韌體。 從 &os; 7.0 就不再支援 Alpha。 &os; 6.X 系列則是此架構的最後支援 。 &os;/&arch.amd64; 架構 有兩種 CPU 能跑 &os;/&arch.amd64;。 第一種是包括 &amd.athlon;64 、&amd.athlon;64-FX、&amd.opteron; 或更好的 CPU。 第二種則是 &intel; EM64T 架構的 CPU，這些也可以用 &os;/&arch.amd64;。 這些 CPU 包括了 &intel; &core; 2 Duo 、Quad、Extreme 系列以及 &intel; &xeon; 3000、5000、7000 相關系列的 CPU。 若主機板晶片組為 nVidia nForce3 Pro-150，則 必須 調整 BIOS 設定，將 IO APIC 停用才行。 若找不到這選項，那可能就是找 ACPI 停用。 因為 Pro-150 晶片組有個 bug，目前我們尚無找到堪解之道。 &os;/&arch.sparc64; 架構 若要裝 &os;/&arch.sparc64;，則需確認該機型是否有支援 (請參閱 )。 &os;/&arch.sparc64; 必須使用整顆硬碟， 因為無法同時與其他作業系統共存。 有支援的硬體 &os; 每次 release 時都會有附上 &os; Hardware Notes 來說明有支援的硬體列表。 通常這份文件可在光碟或 FTP 的最上層目錄找到，也就是名為 HARDWARE.TXT 的檔案。 此外，在 sysinstall 的 documentation 選項內也可以看到。 每次 &os; release 時該列表會依各不同架構， 而列出相關已知有支援的硬體。 在 &os; 網站的 Release Information 頁可以找到各不同 release 版本與各架構上的硬體支援列表。 安裝前的準備工作 列出您電腦的硬體清單 在安裝 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 製造，接在第一條 IDE 排線的 master CDROM N/A N/A 接在第一條 IDE 排線的 slave 第二顆硬碟 N/A N/A 20 GB，IBM 製造，接在第二條 IDE 排線的 master 第一個 IDE controller 14 0x1f0 網路卡 N/A N/A &intel; 10/100 數據機 N/A N/A &tm.3com; 56K faxmodem，接在 COM1 …
硬體清單完成之後，就需針對你所要裝的 &os; 版本之硬體需求， 來檢查是否有支援。 備份您的資料 如果要裝的電腦上面存有重要資料，那麼在安裝 FreeBSD 前， 請確定您已經將這些資料備份了，並且先測試過這些備份檔是否沒有問題。 FreeBSD 安裝程式在要寫入任何資料到您的硬碟前，都會先提醒您確認， 一旦您確定要寫入，那麼之後就再也沒有反悔的機會囉。 決定要將 FreeBSD 安裝到哪裡 如果您想讓 FreeBSD 直接使用整顆硬碟，那麼請直接跳到下一節。 然而，如果您想要 FreeBSD 跟既有的系統並存，那麼， 您必須對硬碟的資料分佈方式有深入的了解，以及其所造成的影響。 &os;/&arch.i386; 架構的硬碟配置模式 PC 上的硬碟可以被細分為許多分散區(chunk)。這些區域叫做 分割區(Partitions)。 由於 &os; 內部也有 partition，名稱可能很容易造成混淆， 因此通常在 &os; 這邊會稱呼這些磁碟分散區為 disk slices 或簡稱 slices。 舉例來說，FreeBSD 的 fdisk 的對象是針對 PC 硬碟的 slice 而非 partition。 因為 PC 本身先天設計，每個硬碟最多可以有 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; 或免費自由工具像是 GParted 來重新調整分割區空間， 來給 FreeBSD 用的空間。FreeBSD 光碟、FTP 上面的 tools 目錄包含兩個免費的工具， 也可以達成這個工作，叫作：FIPS 及 PResizer。 這些工具的說明文件可以在同個目錄內找到。 FIPS、 PResizer 和 &partitionmagic; 可以重新調整在 &ms-dos; 到 &windows; ME 所使用的 FAT16 及 FAT32 分割區大小。 目前已知可更改 NTFS 分割區的有 &partitionmagic; 及 GParted 這兩種工具程式。 GParted在許多 Linux distributions 的 Live CD 都有提供，像是 SystemRescueCD。 目前已知 µsoft; Vista 分割區的重新調整大小會有問題。 在做上述類似動作時，請記得手邊要有 Vista 安裝光碟以免萬一。 此外，強烈建議先做磁碟維護，以及現有資料備份。 不當的使用這些工具，可能會刪除所有硬碟上的資料。 在使用這些工具前，請確定您已有先備份好資料。 使用現有的分割區 假設您只有一個 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; 所用的分割區大小。 整理你的網路設定資料 如果想透過網路( 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 安裝片的話，那麼請先看 這裡會介紹如何準備所需要的安裝片， 照該節步驟弄好後，就可以繼續下一步 。 Prepare the Boot Media The &os; installation process is started by booting the computer into the &os; installer. It is not a program that can be run within another operating system. The computer normally boots using the operating system installed on the hard disk, but it can also be configured to boot from a CDROM or from a USB disk. If installing from a CD/DVD to a computer whose BIOS supports booting from the CD/DVD, skip this section. The &os; CD/DVD images are bootable and can be used to install &os; without any other special preparation. To create a bootable memory stick, follow these steps: Acquire the Memory Stick Image Memory stick images for &os; 8.X can be downloaded from the ISO-IMAGES/ directory at ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/arch/ISO-IMAGES/version/&os;-version-RELEASE-arch-memstick.img. Replace arch and version with the architecture and the version number to install. For example, the memory stick images for &os;/&arch.i386; &rel2.current;-RELEASE are available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img. A different directory path is used for &os; 9.0-RELEASE and later versions. How to download and install &os; 9.X is covered in . The memory stick image has a .img extension. The ISO-IMAGES/ directory contains a number of different images and the one to use depends on the version of &os; and the type of media supported by the hardware being installed to. Before proceeding, back up the data on the USB stick, as this procedure will erase it. Write the Image File to the Memory Stick Using &os; to Write the Image The example below lists /dev/da0 as the target device where the image will be written. Be very careful that you have the correct device as the output target, or you may destroy your existing data. Writing the Image with &man.dd.1; The .img file is not a regular file that can just be copied to the memory stick. It is an image of the complete contents of the disk. This means that &man.dd.1; must be used to write the image directly to the disk: &prompt.root; dd if=&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k If an Operation not permitted error is displayed, make certain that the target device is not in use, mounted, or being automounted by another program. Then try again. Using &windows; to Write the Image Make sure to use the correct drive letter as the output target, as this command will overwrite and destroy any existing data on the specified device. Obtaining <application>Image Writer for Windows</application> Image Writer for Windows is a free application that can correctly write an image file to a memory stick. Download it from https://launchpad.net/win32-image-writer/ and extract it into a folder. Writing the Image with Image Writer Double-click the Win32DiskImager icon to start the program. Verify that the drive letter shown under Device is the drive with the memory stick. Click the folder icon and select the image to be written to the memory stick. Click Save to accept the image file name. Verify that everything is correct, and that no folders on the memory stick are open in other windows. Finally, click Write to write the image file to the drive. To create the boot floppy images for a &os;/&arch.pc98; installation, follow these steps: Acquire the Boot Floppy Images The &os;/&arch.pc98; boot disks can be downloaded from the floppies directory, ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/version-RELEASE/floppies/. Replace version with the version number to install. The floppy images have a .flp extension. floppies/ contains a number of different images. Download boot.flp as well as the number of files associated with the type of installation, such as kern.small* or kern*. The FTP program must use binary mode to download these disk images. Some web browsers use text or ASCII mode, which will be apparent if the disks are not bootable. 準備開機磁片 每個映像檔都需要一張磁片，並且請避免使用到壞的磁片。 最簡單的檢測方式就是自己先把這些磁片再重新格式化(format) 而不要相信所謂的已格式化的磁片，&windows; 內的 format 在格式化時，並不會告訴你是否有壞軌， 而只會直接將它們標示壞軌而不使用壞軌部分而已。 此外，建議採用全新的磁片來製作安裝片比較保險。 若在安裝 FreeBSD 的過程中發生當機、 畫面凍結或是其他怪異的現象，首先要懷疑的就是開機磁片是否壞掉。 請用其他的磁片製作映像檔再試試看。 將映像檔(images)寫入到磁片內 .flp 檔並非一般檔案， 不能直接把它複製到磁片上。 事實上它是包含整張磁片所有內容的映像檔(image)。 也就是說，不能純粹複製檔案到磁片上， 而必須使用特別的工具程式，來將映像檔直接寫到磁片上。 DOS 若要用 &ms-dos;/&windows; 來作安裝片的話，那麼可以用 fdimage 工具程式來將映像檔，寫到磁片上。 若您用的是 FreeBSD 光碟的話(假設光碟機代號為 E: ，那麼請執行類似下面的指令： E:\> tools\fdimage floppies\boot.flp A: 請針對每個需要用到的 .flp 映像檔， 重複上述的指令(記得更改相關檔名)，每次的映像檔完成後， 都需要換另外一片來裝新的映像檔； 請記得： 在作好的磁片上註明是使用哪個映像檔作的。 若 .flp 映像檔放在不同地方， 請自行修改上述指令。若沒有 FreeBSD 光碟的話， 可以到 FTP 上面的 tools 目錄 下載 fdimage 使用。 如果要用 &unix; 系統(比如其他台 FreeBSD 機器) 來製作開機片的話，可以用 &man.dd.1; 指令來把映像檔直接寫入到磁片上。 在 FreeBSD上的話，可以打類似下面的指令： &prompt.root; dd if=boot.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 要列為開機順序的第一個。 為了避免不必要的疑惑，請參考機器、主機板說明手冊。 儲存設定並離開，系統應該會重新啟動。 若要用磁片安裝，請把在 一節中製作好的 boot.flp 那張安裝磁片放到第一台軟碟機中。 如果是從光碟安裝，那麼開機後請將 FreeBSD 光碟放入光碟機中。 如果，開機後如往常一樣而沒有從軟碟或光碟開機，請檢查︰ 是不是磁片或光碟太晚放入而錯失開機時間。 如果是，請將它們放入，然後重新開機。 BIOS 設定不對或忘了儲存設定，請重新檢查 BIOS 的設定。 您的電腦 BIOS 不支援從光碟開機。 此時，FreeBSD 就開始啟動了。 如果是從光碟開機，會見到類似下面的畫面(版本部分省略)： Booting from CD-Rom... CD Loader 1.2 Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX loader BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS CD is cd0 BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 639kB/261120kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x64daa0 data=0xa4e80+0xa9e40 syms=[0x4+0x6cac0+0x4+0x88e9d] \ 如果您從軟碟開機，會看到類似下面的畫面(版本部分省略)： Booting from Floppy... Uncompressing ... done 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 1.1 Loading /boot/defaults/loader.conf /kernel text=0x277391 data=0x3268c+0x332a8 | Insert disk labelled "Kernel floppy 1" and press any key... 請根據提示將 boot.flp 磁片取出， 並放入 kern1.flp 這張磁片， 然後按 Enter 鍵。 總之，您只需從第一張磁片啟動，然後根據提示，再放入相關磁片即可。 無論從軟碟或光碟開機，接下來會進入 &os; boot loader 選單畫面：
&os; Boot Loader 選單
您可以等待 10 秒，或是按 Enter 鍵。 &sparc64; 平台的開機流程 大多數的 &sparc64; 機器預設會自動從硬碟開機。 因此要裝 &os; 的話，則需要進入 PROM(OpenFirmware) 設定由網路或光碟開機才可。 請先重開機，然後等待直到開機訊息出現。 這部分可能會隨機器型號不同 ，而有所差異，但大概會出現像下列這樣： Sun Blade 100 (UltraSPARC-IIe), Keyboard Present Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.2, 128 MB memory installed, Serial #51090132. Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. 若您機器此時會先由硬碟開機，那麼需要按 L1A 或 StopA 或者是透過 serial console (用法請參閱 &man.tip.1; 或 &man.cu.1; 內有關 ~# 的說明) 送出 BREAK 指令來進入 PROM prompt。 大概會像下面： ok ok {0} 這是適用於只有單一 CPU 的機器。 這是適用於 SMP 機器，數字部分是指目前在使用中的 CPU 編號。 此時請把安裝光碟放入光碟機內，然後在 PROM prompt 打 boot cdrom 即可。 那要怎麼去翻閱偵測硬體的結果呢？ 先前在螢幕上所顯示的最後幾百行字，會存在暫存區(buffer) 以便您翻閱。 若要翻閱暫存區，請按 Scroll Lock 鍵， 這會開啟捲動畫面功能。 然後就可以使用方向鍵，或是 PageUp、 PageDown 鍵來上下翻閱。 再按一次 Scroll Lock 鍵，就會停止畫面捲動。 現在就請試試看，翻閱一下偵測硬體的畫面吧， 你應該會看到類似 的畫面， 真正畫面會依你的電腦設備而有所不同。
偵測硬體的例子 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
請仔細檢查每項檢測結果，以確定 FreeBSD 有正確偵測到每項硬體。 若沒偵測到硬體的話，那畫面就不會列出來了。 自訂 kernel 可以讓您加上原本預設的 GENERIC kernel 所不支援的硬體，像是音效卡之類。 而 &os; 6.2 起的版本，在偵測硬體後會看到 ，請用方向鍵選擇你的國別、地區或群組。 然後按 Enter 鍵就會幫你設定相關國別、鍵盤對應。 此外，要離開、重啟 sysinstall 程式，也很簡單。
選擇國別
離開 Sysinstall 程式
在主畫面選擇 Exit Install， 接下來應該會出現以下訊息： User Confirmation Requested Are you sure you wish to exit? The system will reboot (be sure to remove any floppies/CDs/DVDs from the drives). [ Yes ] No 若按下 &gui.yes; 之後，卻忘了把光碟退出來的話， 那麼等下重開機後又會再次啟動安裝程式了。 若你是用磁片開機的話，那麼重開機之前，請記得先退出 boot.flp 片吧。 介紹 Sysinstall sysinstall 是 FreeBSD 計劃所提供的安裝程式。 它是以文字模式操作方式為主，分為幾層選單、畫面，以讓您進行安裝。 sysinstall 選單主要由方向鍵、 Enter、Tab、Space 以及其他按鍵來進行操作， 在 sysinstall 主畫面的 Usage 內有這些鍵盤操作上的說明。 要查閱這些說明，請將游標移到 Usage，然後選 [Select] ，這時你畫面應該會長像 ，接著請按 Enter 鍵。 接下來，會出現安裝的使用說明，閱讀完畢請按 Enter 以跳回主畫面。
選擇 Sysinstall 主畫面的『Usage(快速說明)』
選擇『 Documentation(說明文件)』選單 在主畫面用方向鍵選擇 Doc，然後按 Enter 鍵。
選擇『Documentation(說明文件)』選單
這時會出現說明文件的選單。
Sysinstall 的說明文件(Documentation)選單
閱讀這些說明文件很重要。 要閱讀文件的話，請用方向鍵選取要閱讀的文件然後按 Enter 鍵。讀完後，再按一次 Enter 鍵就會回到說明文件畫面了。 若要回到主畫面，用方向鍵選擇 Exit 然後按下 Enter 鍵即可。 選擇『鍵盤對應』選單 如果要改變鍵盤按鍵的對應模式，請在主選單選取 Keymap 然後按 Enter 鍵即可。 一般情況下是不用去改， 除非你用的鍵盤不是一般標準或非美式鍵盤。
Sysinstall 主選單
您可以使用上下鍵移動到您想使用的鍵盤對應方式，然後按下 Space 鍵以選取它；再按一下 Space 鍵可以取消選取。當您完成後，請選擇 &gui.ok; 然後按 Enter 鍵即可。 在這個畫面顯示的只是其中一小部分； 若只要用預設鍵盤對應方式就好的話，可以用 Tab 來選 &gui.cancel; 這樣就會返回主畫面。
Sysinstall 鍵盤對應選單
安裝選項的設定畫面 請選 Options 然後按 Enter 鍵。
Sysinstall 主選單
Sysinstall 選項設定
通常，使用者大多用預設值就可以了，而不用修改它們。 而 Release Name 的地方則依你所安裝的版本而有所不同。 而目前所選的的項目，會在畫面下方以藍底白字顯示說明。 注意：其中右邊最後的選項是 Use Defaults(使用預設值) ，您可以藉由此選項將所有的設定還原為預設值。 另外，可以按 F1 鍵來閱讀各選項的說明。 而按 Q 鍵則是可以回到主畫面。 開始進行標準安裝 Standard(標準)安裝適用於那些初探 &unix; 或 FreeBSD 的使用者。用方向鍵選擇 Standard 然後按 Enter 鍵即可開始進入標準安裝。
開始進行標準安裝
硬碟空間的分配 您的第一個任務就是要決定分配給 FreeBSD 用的磁碟空間、label， 以便 sysinstall 幫你做相關準備動作。 因此，你必須先對 FreeBSD 是如何確認磁碟的流程有個概念。 BIOS 磁碟機編號 在安裝、設定 FreeBSD 之前，有很重要的一點必須注意， 尤其當您有許多顆硬碟的時候。 DOS Microsoft Windows 在 PC 架構，當您跑像 &ms-dos; 或 µsoft.windows; 這種跟 BIOS 設定相關的作業系統， BIOS 那邊可以調整正常的磁碟機順序，然後這些作業系統會跟著 BIOS 做改變。 這讓使用者不一定非得要由所謂的 primary master 硬碟開機。 有人發現最簡單、便宜的備份系統方式，就是再去買一顆一模一樣的硬碟， 然後定期使用 Ghost 或 XCOPY 以將資料從第一顆硬碟複製到第二顆硬碟上面去。 所以，當第一顆硬碟掛了(可能是病毒或壞軌造成的)， 就可以輕鬆透過調整 BIOS 中的開機順序， 而直接用第二顆硬碟開機。 這跟將機殼拆開，把第二顆硬碟跟第一顆對調(要調 jumper)有同樣的效果， 差別就是：不用拆機殼。 SCSI BIOS 此外，若裝有比較貴的 SCSI 卡系統，通常本身也有 BIOS 的功能來讓 SCSI 設備(最多可到 7 個)達到類似改變順序的功能。 習慣上述方式的使用者很可能會感到驚訝，因為在 FreeBSD 中並非如此， FreeBSD 不會參考 BIOS 設定值，而且也不能偵測 logical BIOS drive mapping 設定。 這會讓人感覺很疑惑，明明就是一樣的硬碟， 而且資料也完全從另一顆複製過來，結果卻沒辦法像以前那樣用。 使用 FreeBSD 的時候，請將 BIOS 中的硬碟開機順序調回原本正常的順序， 並且以後不要再改這設定。如果您需要切換硬碟順序的話，那請用硬體方式， 直接打開機殼，調 jumper 及排線即可。 一段小故事：Bill 及 Fred 的安裝歷險 比爾(Bill)打算幫佛列德(Fred)把舊的 Wintel 機器灌 FreeBSD。 他在一顆 SCSI 硬碟(ID 是 0)裝上 FreeBSD。 於是佛列德開始用他新的 FreeBSD 系統；但是過了幾天，他發現這顆 SCSI 老硬碟發生許多小問題。 之後，他就跟比爾說起這件事。 此事經過幾天後，比爾決定是該解決問題的時候了， 所以他從後面房間的硬碟 收藏區 內拿出一個一模一樣的硬碟，並且經過初步 surface 掃瞄測試後， 顯示這顆硬碟還可堪用，因此，比爾將它的 ID 調成 4， 然後安裝到佛列德的機器， 並且將資料從磁碟 0 複製到磁碟 4。 現在新硬碟裝好了，而且看起來好像一切正常； 所以，比爾認為現在應該可以開始用它了。 於是到 SCSI BIOS 中設定 SCSI ID 4 為開機碟， 用磁碟 4 重新開機後，FreeBSD 一切跑得很順利。 佛列德繼續用了幾天後，比爾跟佛列德決定要來玩點新的： 試著升級 FreeBSD 看看。 比爾將 ID 0 的硬碟移除(因為有問題)並且又從 收藏區 中拿了一顆一樣的硬碟來。 然後他用佛列德的開機磁片透過 FTP 方式將在這顆硬碟上裝了新版的 FreeBSD，安裝過程都很順利。 佛列德用了這新版本幾天後，覺得它很適合用在工程部門... 是時候將以前放在舊系統的工作資料複製過來了。 因此，佛列德將 ID 4 的 SCSI 硬碟 (裡面有放從舊系統中複製過來的最新資料)先 mount 起來， 結果竟然發現在 ID 4 的硬碟上，他以前的所有資料都不見了！ 奇怪，資料到底是跑到哪裡去了呢？ 原來，當初比爾將 ID 0 硬碟的資料複製到 ID 4 硬碟的時候， ID 4 就變成 新的複製品(new clone)。 而當他調 SCSI BIOS 設定 ID 4 為開機碟，想讓系統從 ID 4 開機， 這步驟其實只是他自己搞混了， 因為大部分的作業系統可以藉由調 BIOS 設定以改變開機順序， 但是 FreeBSD 卻會把開機順序還原成正常的模式， 因此，佛列德的 FreeBSD 還是從最初的那顆 ID 0 硬碟開機的。 事實上，所有的資料都還在故事最初的那顆硬碟上， 而不是在他想像中的 ID 4 硬碟。 我們很高興在發現這件事時，那些資料都還在， 我們把資料從最初的那顆 ID 0 硬碟取出來並交還給佛列德 (而且比爾也從此瞭解了 0 的重要....)。 雖然我們這邊的例子是用 SCSI 硬碟， 但是相同的觀念也可以套用在 IDE 硬碟上。 以 FDisk 來建立分割磁區(Slices) 在這時候您所做的變更都還不會真正寫入硬碟中。 如果你發現弄錯了，想要重來一遍的話， 可以用選單來離開 sysinstall， 或是按 U 鍵來 Undo(回復) 所有設定。 如果你弄亂了而且不知道怎麼離開，你可以直接將電腦電源關掉再重來。 在 sysinstall 主畫面選擇使用標準安裝後， 應該會看到下面的訊息： 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 ] 這時請依畫面說明，按 Enter 鍵。 然後會看到一個列表，上面會列出所有在偵測硬體時所找到的硬碟。 範例顯示的是有找到兩個 IDE 磁碟機的情形，這兩個磁碟機分別為： ad0 與 ad2。
選擇 FDisk 要分割的硬碟
你可能會好奇，為何 ad1 沒列在這裡。 為什麼會不見了呢？ 試想，如果您有兩顆 IDE 硬碟，一個是 primary master，一個是 secondary master，這樣會發生什麼事呢？ 如果 FreeBSD 依照找到的順序來為他們命名， 比如首先是 ad0 再來是 ad1 那麼就不會出現困擾。 但是，現在問題來了。如果您現在想在 primary slave 加裝第三顆硬碟， 那麼這顆硬碟的名稱就會是 ad1，之前原本的 ad1 就會變成 ad2。 這樣會造成什麼問題呢？ 因為硬體設備的名稱(像是 ad1s1a)是用來尋找檔案系統的， 因此您可能會突然發現，有些檔案系統從此無法正常顯示， 必須修改 FreeBSD 設定(/etc/fstab)才可以正確顯示。 為了解決這個問題，在設定 kernel 時可以採用 IDE 硬碟所在的位置來命名，而非根據找到的順序。 使用這種方式的話， 在 secondary master 的 IDE 硬碟就永遠會是 ad2， 即使系統中並沒有 ad0 或 ad1 也不受影響。 由於此為 FreeBSD kernel 預設設定，也就是為何上述畫面只顯示 ad0 及 ad2 之故。 畫面上這台機器的兩顆硬碟是分別裝在 primary 以及 secondary 排線上的 master，這兩顆都沒有裝在 slave 上。 請選好想安裝 FreeBSD 的硬碟，然後按下 &gui.ok;。 接著就會開始 FDisk，然後會看到類似 的畫面。 FDisk 的顯示畫面分為三個部分。 第一部份是畫面最上方的前兩行，這裡會顯示目前所選的硬碟資訊， 包括它在 FreeBSD 的名稱、硬碟 geometry、硬碟總容量。 第二部分會顯示目前所選的硬碟上有哪些 slice 以及各 slice 的起末位置、 所佔容量、FreeBSD 名稱、描述說明、子類別(sub-type)。 例子中顯示出有 2 個小的並且尚未使用的 slice，這是受到 PC 的硬碟本身架構影響之故。 此外， 還有一個大的 FAT slice(通常是 &ms-dos; / &windows; 中的 C:)，以及一個延伸磁碟分割區 (在 &ms-dos; / &windows; 內的其他磁碟代號)。 第三部分則顯示 FDisk 可用的指令。
(舉例)未編輯前的 Fdisk 分割區(Partition)
接下來要做的事，跟您要怎麼分割硬碟有關。 若要讓 FreeBSD 使用整顆硬碟(稍後的安裝會再要您確認以 sysinstall 來繼續安裝， 就會清除該硬碟內上的資料)，那麼就可以按 A 鍵( Use Entire Disk)，以刪除所有既存的 slice， 取而代之的是一個小的並標示為 unused(同樣的，這也是 PC 硬碟架構所造成)的 slice，以及一個大的 FreeBSD slice。 之後， 請用方向鍵把光棒移至該 FreeBSD slice，然後按 S 鍵以便將此 slice 標為開機 slice。 此時的畫面應該類似 。 請注意： 在 Flags 欄位的 A 值表示該 slice 屬於 active，也會由此 slice 來開機。 若要刪除現有 slice 以挪出空間給 FreeBSD 使用，可以把光棒移到要刪除的 slice 後按 D 鍵，然後再按 C 鍵， 此時會出現對話框，請輸入要新增的 slice 大小為何，輸入合適大小之後按 Enter 鍵即可。 該預設值為可分配空間的最大值， 可以是最大的或尚未分配的整顆硬碟大小。 若已建立完畢給 FreeBSD 的空間(透過類似 &partitionmagic; 之類的工具)，那麼可以按 C 鍵以新增 slice。同樣也會有對話框出現，來問想要新增的 slice 大小為何。
Fdisk 採用整顆硬碟作分割區(Partition)
完畢後請按 Q 鍵。 這些更改會暫存給 sysinstall 使用，但還不會真正寫入到硬碟 。 安裝 Boot Manager 現在可以選擇是否要裝 boot manager。 一般而言， 遇到下列情況才會需要裝 boot manager： 有一個以上的硬碟，而 FreeBSD 並非裝在第一個硬碟上。 同一顆硬碟上除了有裝 FreeBSD 之外，還有裝其他作業系統， 所以需要在開機時選擇要進入哪個作業系統。 若只裝 FreeBSD，並且是裝在第一顆硬碟，那麼選 Standard 即可。 若已經有使用其他的 boot manager 可開機進入 FreeBSD 那麼請選 None 即可。 請依自身需求與情況做抉擇，然後按 Enter 鍵。
Sysinstall 的 Boot Manager 選單
按 F1 會有不同作業系統共存時， 有可能遇到的相關問題說明。 在其他硬碟上建立分割磁區(Slices) 若有一個以上的硬碟，那麼在選完 boot manager 之後會再回到選擇硬碟的畫面。 若要把 FreeBSD 裝在多個硬碟上， 那麼可以在此選擇其他硬碟，並重複使用 FDisk 來建立 slice 。 若第一顆硬碟不是裝 FreeBSD 的話，那麼每一顆就要都裝 FreeBSD boot manager 才可以。
離開『選擇硬碟』畫面
Tab 鍵可以在最後選擇的硬碟以及 &gui.ok;、 &gui.cancel; 之間進行切換。 先按一次 Tab 會先移到 &gui.ok;，然後再按 Enter 鍵以繼續安裝。 以 <application>Disklabel</application> 來建立分割區(Partitions) 現在必須在剛建立好的 slice 規劃一些分割區。 請注意： 每個分割區的代號是從 a 到 h， 此外 b、c、d 通常是特殊用途，不該隨意變動。 有些程式可以透過特殊的分割方式而達到更好的效果， 尤其是分割區是分散在不同硬碟上的時候。 但是，現在是您第一次裝 FreeBSD， 所以請不要去煩惱該如何分割硬碟才好。 最重要的是，裝好 FreeBSD 然後學習如何善用之。 當對 FreeBSD 有一定程度的熟悉之後，可以隨時重裝 FreeBSD，並改變分割的方式。 下面例子有四個分割區 — 其中一個是 swap 空間，i 其他三個是檔案系統。 第一顆硬碟的分割區(Partition)配置 分割區 檔案系統 大小 介紹 a / 128 MB 此為根目錄檔案系統(root filesystem)。 其他的檔案系統都會掛載在根目錄之下。 128 MB 對於此檔案系統來說是相當合理的大小， 因為通常這裡並不會放太多資料，而在 FreeBSD 裝完後會用到約 40 MB 的根目錄空間。 剩下的空間是放臨時資料用的， 此外也應該要預留一些空間，因為日後的 FreeBSD 版本可能會需要更多的 /(根目錄) 空間 。 b N/A RAM 的 2~3 倍 系統的 swap 空間是放在 b 分割區。 如何選擇適合的 swap 空間大小可是一門學問。 一般來說， swap 空間應該是記憶體(RAM)大小的 2 或 3 倍。 此外，swap 至少需要 64 MB，因此若 RAM 小於 32 MB 的話，請把 swap 大小設為 64 MB。 若有一個以上的硬碟，則可以在每個硬碟都配置 swap 空間。 FreeBSD 會善用每個硬碟上的 swap 空間，如此一來便能有效提高 swap 的性能。 若您屬這類情況，請先算出總共需要的 swap 總大小 (比如：128 MB)，然後除以全部的硬碟數量(比如：兩顆硬碟)， 這樣算出來的結果就是每個硬碟上所需配置的 swap 大小， 在這個例子中，則每個硬碟所需之 swap 空間為 64 MB 。 e /var 256 MB /var 目錄會放的檔案有很多種，像是 log 檔案以及其他的系統管理檔案。 這些檔案大部分都是 FreeBSD 每日運作所會讀、寫。 把這些檔案另外放到專門的檔案系統(即 /var) 則可以最佳化這些檔案的存取， 而不致於影響其他目錄的存取。 f /usr 剩餘的硬碟空間 所有其他檔案通常會存在 /usr 及其子目錄內。
若要把 FreeBSD 裝在多個硬碟上，那麼必須在您所配置的其他 slice 上新增分割區。 最簡單的方式，就是在每個硬碟上建立分割區，一個給 swap 空間，另一個則是檔案系統。 其他硬碟的分割區(Partition)配置 分割區 檔案系統 大小 介紹 b N/A 請參閱右側的介紹 前面有提過，swap 空間是可以跨各硬碟。 即使沒有使用 a 分割區，但習慣上還是會把 swap 空間設為 b 分割區。 e /diskn 剩餘的硬碟空間 剩下的空間是一個大的分割區，最簡單的做法是將之規劃為 a 分割區，而不是 e 分割區。 然而，習慣上 a 分割區是保留給 根目錄(/)所使用的。 當然， 您不一定要遵循此習慣，但 sysinstall 本身會，所以照它既有的方式會讓你安裝更加清爽、潔淨。 你可以把這些檔案系統掛載在任何地方，本範例是建議把它們掛載於 /diskn 目錄， 其中的 n 的數字， 則依各硬碟的順序而有所變化。 但若您高興， 也可以把它們掛載於其他地方。
完成分割區配置之後，就可以用 sysinstall 來建立之。 您會看到如下訊息： 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 ] 請按 Enter 鍵以進入 FreeBSD 分割區編輯器，叫做 Disklabel。 顯示第一次執行 Disklabel 的畫面， 這畫面可區分為三個區塊。 前幾行顯示的是正在編輯的硬碟，以及目前正在建立的 slice 位於哪個 分割區上。(在此處，Disklabel 是使用 Partition name(分割區名稱)，而非 slice 名稱)。 此畫面也會顯示目前 slice 還有多少空間可供使用， 換句話說就是尚未指定分割區的多餘空間。 在畫面中間，則顯示已建立的分割區、每個分割區的檔案系統名稱、 所佔大小，以及一些參數。 在畫面下方，則顯示 Disklabel 可用的按鍵。
Sysinstall 的 Disklabel 編輯器
Disklabel 可自動分配分割區， 並賦予預設值大小，按 A 即可自動完成。 您會看到類似 的畫面。 不過， 由於所用的硬碟大小不一，所以自動分配所設定的大小不一定合用，不要緊， 您不一定得使用預設大小才可以。 預設會給 /tmp 目錄作為獨立分割區， 而非附屬於 / 之下。 如此一來， 可避免 / 會被一堆臨時檔案塞爆。
Sysinstall 的 Disklabel 編輯器 — 使用自動分配
如果您不想用自動分配分割區而希望自行設定， 請用方向鍵選擇第一個分割區，並按下 D 刪除之。 重複此動作直到刪除所有分割區。 建立第一個分割區(a，掛載為 / — 根目錄)， 請在畫面最上方選擇正確的磁碟分割磁區(slice)並按下 C。 接下來將出現對話框， 會要求輸入新的分割區大小(如 所示) 。 這邊可以直接輸入以 block 為單位， 或者是以 M(MB)為單位、 或以 G(GB)為單位， 或者以 C(磁柱，cylinders) 為單位。 自 FreeBSD 5.X 起，則可使用 Custom Newfs 選項來用 UFS2 (從 &os; 5.1 起，此即為預設值)。 若是使用 Auto Defaults 自動預設的情況下，則可以再用 Custom Newfs 選項，或者在建立檔案系統時指定 參數亦可。 若用 Custom Newfs 選項的話，則別忘了要加上 來啟用 SoftUpdates 功能！
根目錄的空間分配
此處預設顯示的大小，會是整個 slice 的所有空間。 若要採用先前例子所介紹的劃分大小，則按 Backspace 鍵來消除這些數字，並輸入例子中的 128M，如 所示。 接著按下 &gui.ok;。
修改根目錄的空間分配
在輸入之後會問所要建立的是檔案系統(file system)或者是 swap 空間， 如 所示。 第一個選項為檔案系統，所以選擇 FS 後按下Enter。
選擇分割區的類型
最後，因為要新增的是檔案系統，所以必須告訴 Disklabel 要將其掛載至何處。 如 所示。 根目錄檔案系統 的掛載點為 /，所以請輸入 / ，然後按下 Enter。
選擇根目錄的掛載點
剛所建立的分割區會顯示在畫面上，可以用上述類似動作來建立其他分割區。 然而在建立 swap 分割區時，系統並不會問要掛載於哪邊，因為 swap 空間是不必額外掛載的。 此外在建立最後分割區 /usr 時，可以直接採用預設大小，也就是該 slice 剩餘的所有空間。 最後 FreeBSD 上的 DiskLabel 編輯器畫面會類似 ，實際數字則依安裝選擇而有所不同。 請按下 Q 即可完成分割區規劃。
Sysinstall Disklabel 編輯器
選擇想要安裝的 選擇要安裝的套件集(Distribution Set) 要裝哪些套件，主要取決於該系統的用途為何及磁碟空間而定。 預置的套件，從最小安裝到完整安裝都有。 若是 &unix; 或 FreeBSD 新手，通常直接選其中之一即可。 而自訂套件比較適合有經驗的人來用。 若要瞭解各套件的選項細節資訊，請按 F1 鍵。 看完之後按 Enter 即會回到剛才的套件選擇畫面。 若需要 GUI 介面，那必需加選 X 開頭的相關套件。 至於 X server 的設定及要用哪一類的桌面管理，必須在 &os; 裝好之後才能進行。 X server 設定細節部分請參閱 。 預設安裝的 X11 版本為 &xorg;。 若需要自訂 kernel，那麼需加選有含 source code 的選項。 至於為何需自訂 kernel 及相關細節，請參閱 。 很明顯地，全部都裝就不用困擾需要裝什麼了。 若硬碟夠大，請以方向鍵選 圖下的 All 選項，並按下 Enter 即可。 若硬碟空間不夠，請依自身需求選擇安裝。 當然在安裝完畢後， 還是可以依需求再加裝其他套件。
選擇要裝的套件集(Distributions)
安裝 Ports Collection 在裝完套件集之後，接著會問是否要裝 FreeBSD Ports 套件。 Ports 套件可以讓您輕鬆安裝各種常見的軟體，它本身並不含那些軟體的原始碼， 而是一個包含如何自動下載、編譯、安裝 third-party 軟體的檔案集合。 會介紹如何使用 ports。 安裝程式並不會檢查是否有足夠空間來放 ports tree， 所以請先確認有足夠空間。 目前 FreeBSD &rel.current; 的 FreeBSD Ports Collection 大約需要 &ports.size; 的空間。 因此， 可以推估更新版的 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 用方向鍵選 &gui.yes; 就會裝 Ports Collection，否則就選 &gui.no; 以略過。 選好後按 Enter 繼續， 然後會再次回到選擇套件集的畫面。
確認要安裝的套件集
若要勾選的項目都確認沒問題的話，就以方向鍵選 Exit 退出並確認 &gui.ok; 有選到，然後按I Enter 繼續。 選擇安裝來源 若要從 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：從 FTP server 安裝 該選項會透過 Active 模式作 FTP 傳輸動作。 這會無法穿過防火牆，但可用在那些較古早、不支援被動模式的 FTP 站。 若 FTP 連線會卡住(預設為被動模式)， 那請改換主動模式看看！ 被動式 FTP：透過防火牆，從 FTP server 安裝 FTP passive mode 該選項會讓 sysinstall 全程使用 Passive(被動式) 來進行 FTP 連線， 就可以穿過只允許使用固定 TCP port 連入的防火牆。 透過 HTTP proxy 的 FTP：透過 http proxy 來從 FTP 站安裝 FTP via a HTTP proxy 該選項會讓 sysinstall 的 FTP 連線， 先透過 HTTP 協定(就像網頁瀏覽器一樣)連到 proxy server，而 proxy server 會解譯送過來的的請求，然後轉送給 FTP server。 這可以穿透只允許 HTTP 連線但不允許 FTP 連線的防火牆。 但記得要用之時，必須指定 proxy server 的位址。 對 proxy FTP server 而言，通常要在登入用的帳號名稱後面， 加上 @ 符號再加上要登入的 server 名稱。 然後， proxy server 就會 fakes(偽裝) 為真的 server 樣子。 舉個例子，若要到 ftp.FreeBSD.org 來裝， 但中間透過 proxy FTP server 也就是 foo.example.com 並且使用 port 1234。 在此情況下，可以到 options 選單，將 FTP username 設為 ftp@ftp.FreeBSD.org，密碼則設為自己的 email 信箱。 安裝來源部分，則使用 FTP (或 proxy 有支援的話，就用 passive FTP)， 而 URL 則用 ftp://foo.example.com:1234/pub/FreeBSD。 因為 ftp.FreeBSD.org 的 /pub/FreeBSD 會被 porxy 到 foo.example.com，所以就可以從 foo.example.com 這台 機器(這台會從 ftp.FreeBSD.org 抓檔回來給您) 安裝。 開始進行安裝 到此為止，可以開始進行安裝了， 這也是您避免更動到硬碟的最後機會。 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: /usr/sbin/sysinstall. [ OK ] [ Press enter or space ] 請按 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 ] 在私人區域網路的情況，由於目前的 Internet 協定 (IPv4)還算夠用， 所以請選 &gui.no; 不設定 IPv6，然後按 Enter。 若是透過 RA server 連到既有的 IPv6 環境，那麼就選 &gui.yes; 並按 Enter，之後系統會花幾秒鐘去搜尋 RA server。 User Confirmation Requested Do you want to try DHCP configuration of the interface? Yes [ No ] 接下來，若不需要 DHCP (Dynamic Host Configuration Protocol)請選 &gui.no; 並按Enter。 選擇 &gui.yes; 的話，則會執行 dhclient，若成功要到 IP， 則其會自動填上相關的環境設定，細節請參閱 。 下面的網路設定圖顯示如何在區域網路(LAN)中， 將該機器設定為 gateway 的方式：
設定 ed0 這張網路卡的網路設定
可用 Tab 鍵在各欄位間作切換， 並填上適合的資料： Host(機器名稱) 完整的機器名稱，例如本例中的 k6-2.example.com。 Domain(網域) 機器所屬的網域名稱，例如本例中的 example.com。 IPv4 Gateway 這裡請輸入 Gateway 的 IP 位址，其可負責將封包轉遞到遠端網路。 只有在該 gateway 屬於該網路其中節點之一時，才要輸入。 若這機器本身要做為該區域網路的 gateway 的話， 請保持本欄為空白。 此外， 通常 IPv4 Gateway 也會被認為是 default gateway 或 default route。 Name server(Name server 或 DNS server) 該網路所用的 DNS server 之 IP。 本例假設該機器所在的網路沒有 DNS，故填上的是該 ISP 所提供的 DNS server (208.163.10.2)。 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.0.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 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. 啟用 SSH 登入 SSH sshd User Confirmation Requested Would you like to enable SSH login? Yes [ No ] 選擇 &gui.yes; 就會啟用 &man.sshd.8;，也就是 OpenSSH 的 daemon 程式。 這會允許該機器可從遠端安全登入。 關於 OpenSSH 請參閱 部分的說明。 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. 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 PS/2, serial, or bus mouse? [ Yes ] No Select &gui.yes; for a PS/2, serial, or bus 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. 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 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 <systemitem class="username">root</systemitem> 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 or space ] 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. 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/CDs/DVDs 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, see details. Configure Additional Network Services TomRhodesContributed by 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 X Exit and continue on to the next configuration item or simply exit sysinstall in selecting X Exit twice then [X Exit Install]. &os; 開機流程 &os;/&arch.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. &os;/&arch.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. 安裝的疑難雜症解決 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; or &windows;. 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 &os; to make sure your hardware is supported. 若硬體有在支援清單內，但使用 GENERIC kernel 仍有問題，那麼就可能需要 自訂 kernel，以加入有支援的硬體。 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 edit the kernel configuration and recompile to tell &os; 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. 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(FAT16 and FAT32). This requires you use the &man.mount.msdosfs.8; command with the required parameters. The utility most common usage is: &prompt.root; mount -t msdosfs /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. Troubleshooting Questions and Answers My system hangs while probing hardware during boot, or it behaves strangely during install, or the floppy drive isn't probed. &os; 5.0 and above makes extensive use of the system ACPI service on the i386, amd64 and ia64 platforms to aid in system configuration if it's detected during boot. Unfortunately, some bugs still exist in both the ACPI driver and within system motherboards and BIOS. The use of ACPI can be disabled by setting the hint.acpi.0.disabled hint in the third stage boot loader: set hint.acpi.0.disabled="1" This is reset each time the system is booted, so it is necessary to add hint.acpi.0.disabled="1" to the file /boot/loader.conf. More information about the boot loader can be found in . I go to boot from the hard disk for the first time after installing &os;, the kernel loads and probes my hardware, but stops with messages like: changing root device to ad1s1a panic: cannot mount root What is wrong? What can I do? What is this bios_drive:interface(unit,partition)kernel_name thing that is displayed with the boot help? There is a longstanding problem in the case where the boot disk is not the first disk in the system. The BIOS uses a different numbering scheme to &os;, and working out which numbers correspond to which is difficult to get right. In the case where the boot disk is not the first disk in the system, &os; can need some help finding it. There are two common situations here, and in both of these cases, you need to tell &os; where the root filesystem is. You do this by specifying the BIOS disk number, the disk type and the &os; disk number for that type. The first situation is where you have two IDE disks, each configured as the master on their respective IDE busses, and wish to boot &os; from the second disk. The BIOS sees these as disk 0 and disk 1, while &os; sees them as ad0 and ad2. &os; is on BIOS disk 1, of type ad and the &os; disk number is 2, so you would say: 1:ad(2,a)kernel Note that if you have a slave on the primary bus, the above is not necessary (and is effectively wrong). The second situation involves booting from a SCSI disk when you have one or more IDE disks in the system. In this case, the &os; disk number is lower than the BIOS disk number. If you have two IDE disks as well as the SCSI disk, the SCSI disk is BIOS disk 2, type da and &os; disk number 0, so you would say: 2:da(0,a)kernel To tell &os; that you want to boot from BIOS disk 2, which is the first SCSI disk in the system. If you only had one IDE disk, you would use '1:' instead. Once you have determined the correct values to use, you can put the command exactly as you would have typed it in the /boot.config file using a standard text editor. Unless instructed otherwise, &os; will use the contents of this file as the default response to the boot: prompt. I go to boot from the hard disk for the first time after installing &os;, but the Boot Manager prompt just prints F? at the boot menu each time but the boot won't go any further. The hard disk geometry was set incorrectly in the Partition editor when you installed &os;. Go back into the partition editor and specify the actual geometry of your hard disk. You must reinstall &os; again from the beginning with the correct geometry. If you are failing entirely in figuring out the correct geometry for your machine, here's a tip: Install a small DOS partition at the beginning of the disk and install &os; after that. The install program will see the DOS partition and try to infer the correct geometry from it, which usually works. The following tip is no longer recommended, but is left here for reference:
If you are setting up a truly dedicated &os; server or workstation where you don't care for (future) compatibility with DOS, Linux or another operating system, you've also got the option to use the entire disk (`A' in the partition editor), selecting the non-standard option where &os; occupies the entire disk from the very first to the very last sector. This will leave all geometry considerations aside, but is somewhat limiting unless you're never going to run anything other than &os; on a disk.
The system finds my &man.ed.4; network card, but I keep getting device timeout errors. Your card is probably on a different IRQ from what is specified in the /boot/device.hints file. The ed driver does not use the `soft' configuration by default (values entered using EZSETUP in DOS), but it will use the software configuration if you specify -1 in the hints for the interface. Either move the jumper on the card to a hard configuration setting (altering the kernel settings if necessary), or specify the IRQ as -1 by setting the hint hint.ed.0.irq="-1" This will tell the kernel to use the soft configuration. Another possibility is that your card is at IRQ 9, which is shared by IRQ 2 and frequently a cause of problems (especially when you have a VGA card using IRQ 2!). You should not use IRQ 2 or 9 if at all possible. 進階安裝指南 ValentinoVaschettoContributed 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 boot.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 boot.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/cuad0 在 &os; 5.X，請改用 /dev/cuaa0 而非 /dev/cuad0。 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 kern1.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 ISO As part of each release, the &os; Project provides ISO images for each supported architecture. These images can be written (burned) to CD or DVD media using a burning application, and then used to install &os;. If a CD/DVD writer is available, this is the easiest way to install &os;. 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. An image directory normally contains the following images: &os; ISO Image Names and Meanings Filename Contents &os;-version-RELEASE-arch-bootonly.iso This CD image starts the installation process by booting from a CD-ROM drive but it does not contain the support for installing &os; from the CD itself. Perform a network based install, such as from an FTP server, after booting from this CD. &os;-version-RELEASE-arch-dvd1.iso.gz This DVD image contains everything necessary to install the base &os; operating system, a collection of pre-built packages, and the documentation. It also supports booting into a livefs based rescue mode. &os;-version-RELEASE-arch-memstick.img This image can be written to a USB memory stick in order to install machines capable of booting from USB drives. It also supports booting into a livefs based rescue mode. The only included package is the documentation package. &os;-version-RELEASE-arch-disc1.iso This image can be written to a USB memory stick in order to install machines capable of booting from USB drives. Similar to the bootonly.iso image, it does not contain the distribution sets on the medium itself, but does support network-based installations (for example, via ftp). &os;-version-RELEASE-arch-disc1.iso This CD image contains the base &os; operating system and the documentation package but no other packages. &os;-version-RELEASE-arch-disc2.iso A CD image with as many third-party packages as would fit on the disc. This image is not available for &os; 9.X. &os;-version-RELEASE-arch-disc3.iso Another CD image with as many third-party packages as would fit on the disc. This image is not available for &os; 9.X. &os;-version-RELEASE-arch-livefs.iso This CD image contains support for booting into a livefs based rescue mode but does not support doing an install from the CD itself.
When performing a CD installation, download either the bootonly ISO image or disc1. Do not download both, since disc1 contains everything that the bootonly ISO image contains. Use the bootonly ISO to perform a network install over the Internet. Additional software can be installed as needed using the Ports Collection as described in . Use dvd1 to install &os; and a selection of third-party packages from the disc. Burn the Media Next, write the downloaded image(s) to disc. If using another &os; system, refer to for instructions. If using another platform, use any burning utility that exists for that platform. The images are in the standard ISO format which most CD writing applications support. To build a customized release of &os;, refer to 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. 建立安裝用的磁片 installation floppies 若您必須從磁片安裝(雖然我們不建議這樣做)， 不論是因為硬體不支援或是您堅持要用這麼刻苦的方式， 您都必須先準備一些磁片以供安裝。 磁片至少得是 1.44 MB At a minimum, you will need as many 1.44 MB floppies as it takes to hold all the files in the base (base 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; bsdlabel -w fd0.1440 floppy3 &prompt.root; newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0 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:\base\base.aa, a:\base\base.ab, and so on. The base.inf file also needs to go on the first floppy of the base set since it is read by the installation program in order to figure out how many additional pieces to look for when fetching and concatenating the distribution. Once you come to the Media screen during the install process, select Floppy and you will be prompted for the rest. 從 &ms-dos; 分割區安裝 installation from MS-DOS 若準備要從 &ms-dos; 分割區進行安裝， 請把所有安裝檔都複製到該分割區根目錄內的 freebsd 目錄。 比如：c:\freebsd。 此目錄結構必須與光碟或 FTP 內的目錄結構一致， 因此若是要從光碟複製檔案，建議使用 DOS 的 xcopy 指令。 例如，要複製 &os; 最小安裝所需的檔案： C:\> md c:\freebsd C:\> xcopy e:\bin c:\freebsd\bin\ /s C:\> xcopy e:\manpages c:\freebsd\manpages\ /s 假設 C: 槽有多餘空間，可以放 &os; 安裝檔；E:則是光碟機代號。 若沒有光碟機，可以到 ftp.FreeBSD.org 去下載安裝檔。 每個安裝套件都有其相對應的目錄；比如 base 是放在 &rel.current;/base/ 目錄內。 請將您要安裝的套件(當然空間要夠)放到 &ms-dos; 分割區的 c:\freebsd 裡 — 因為這個 BIN 安裝套件僅供最精簡安裝而已。 製作安裝用的磁帶 installation from QIC/SCSI Tape 從磁帶上安裝也許是最簡單的方式，比用 FTP 或光碟安裝還快。 安裝程式假設所有檔案都會壓縮放在磁帶上。 在取得所有要裝的安裝檔之後 ，可以用下列指令把它們壓縮放在磁帶上： &prompt.root; cd /freebsd/distdir &prompt.root; tar cvf /dev/rwt0 dist1 ... dist2 當要安裝時，必須先確認磁帶還有足夠空間， 以便讓安裝過程暫存空間(可以自行選擇要放在哪個目錄)， 可以容納磁帶安裝時的全部檔案。 由於磁帶本身並不能隨機存取，因此用磁帶安裝會需要很大的暫存空間。 在使用安裝磁片開機 之前， 磁帶一定要先放入磁帶機內，否則在偵測硬體時可能會無法偵測到磁帶機。 Before Installing over a Network installation network serial (SLIP or PPP) installation network parallel (PLIP) installation network Ethernet 有三種網路安裝方式： Ethernet (標準 Ethernet 晶片)、Serial port(SLIP 或 PPP)、 Parallel port (PLIP (laplink cable))。 透過網路安裝的最快方式，就是使用 Ethernet 網路卡！ &os; 支援大多數常見的 Ethernet 網路卡； 所有支援的網路卡(及其所需的設定)都有在各版本的 &os; 內的 Hardware Note 說明文件內列出。 若您所用的是有支援的 PCMCIA 網路卡， 請務必在開機之前，先把該網路卡插上。 因為 &os; 的安裝過程，目前並不支援 PCMCIA 卡的熱插拔。 此外，還需要知道該用的 IP 位址以及相對應的 netmask 為何， 以及機器名稱。 若所用的是 PPP 連線，而且沒有固定 IP，別擔心， 因為您的 ISP 會自動分配 IP 給您。 關於這些網路的細部設定， 可以洽詢您網路環境的系統管理者。 若要能以機器名稱就能連到相對應的機器，而非直接使用 IP位址去連， 那麼您還需要 DNS 以及 gateway 的位址(若用的是 PPP 連線， gateway 位址就是 ISP 所分配給你的 IP 位址)。 若想透過 HTTP proxy 來使用 FTP 安裝，那麼必須知道 proxy 的網址為何。 若您對上述所需資訊不甚了解，那麼請在安裝之前， 先詢問系統管理者或 ISP。 SLIP 的支援相當原始，並且主要受限於電腦之間的實體線路(hard-wired) ，比如筆記型電腦與其他電腦之間的 serial 線。 之所以得以電腦間以直接線路連結，乃是由於 SLIP 安裝目前並不支援撥接功能。 PPP 才有提供撥接功能， 所以請儘可能優先採用 PPP 而非 SLIP。 若要透過數據機(modem)來安裝，那 PPP 幾乎是您唯一選擇。 請先準備好 ISP 所提供的相關資料，因為在安裝之初就會用到。 若使用 PAP 或 CHAP 來連到 ISP(換句話說，若在 &windows; 可以不透過 script 就可以連線到 ISP)，那麼您僅需在 ppp 提示符號下輸入 dial 指令即可撥號。 否則，您必須知道如何以該數據機所採用的 AT 指令集來連到 ISP，因為 PPP 撥號程式僅提供非常陽春的 終端模擬器(terminal emulator)而起。 請參閱 Handbook 中 user-ppp 章節以及 FAQ 中的相關項目。 若有操作上的疑問，可以打 set log local ... 指令，以便在螢幕上顯示相關記錄。 若可直接以 hard-wired 方式連到另外的 &os;(2.0-R 及之後) 機器， 那麼可以考慮透過 laplink 平行電纜來安裝。 平行埠的傳輸速率比序列埠高很多(最高可達每秒 50 kbytes/sec)， 所以安裝速度會更快一些。 Before Installing via NFS installation network NFS NFS 安裝方式相當簡便，只需將 FreeBSD 安裝檔案都放到某台 NFS server 上，然後再指定使用這台 NFS 作為安裝來源即可。 若該 server 只允許 privileged port(通常這是 Sun 工作站的預設值)，那麼在安裝之前，必須先到 Options 選單去指定 NFS Secure 設定值。 若網路卡的連線品質不佳，那可能需要調整一下 NFS Slow 設定。 為了讓 NFS 安裝能順利完成，NFS 主機必須要可以支援子目錄的掛載 (mount)，例如：&os; &rel.current; 安裝目錄是在： ziggy:/usr/archive/stuff/FreeBSD，那麼 ziggy 必須允許直接掛載在 /usr/archive/stuff/FreeBSD，而非僅 /usr 或是 /usr/archive/stuff。 在 &os; 的 /etc/exports 檔，上述功能是由 選項所設定。 其他的 NFS server 可能會有不同的設定方式。 若看到 permission denied 錯誤訊息， 則表示可能由於沒有啟用這選項所造成的。