| Depan | Profil | Galeri | Artikel | Tutorial | Humor | Berita Terkini | Info Lowongan Kerja | Cara Cari Uang |
-----------------------------------------------------------------
"Tujuan yang besar memberikan hasil yang besar. Tidak ada tujuan tidak ada hasil apapun, atau menghasilkan tujuan orang lain" (Mark Victor Hansen)

Sep 2, 2008

1 - Overview of the OpenBSD installation procedure

OpenBSD has a robust and adaptable text-based installation procedure, and can be installed from a single floppy disk. Most platforms follow a similar installation procedure; however there are some differences in the details. In all cases, you are urged to read the platform-specific INSTALL document in the platform directory on the CD-ROM or FTP sites (for example, i386/INSTALL.i386, mac68k/INSTALL.mac68k or sparc/INSTALL.sparc).

The OpenBSD installation process uses a special kernel with a number of utilities and install scripts embedded in a preloaded RAM disk. After this kernel is booted, the operating system is extracted from a number of compressed tar(1) (.tgz) files from a source other than this preloaded RAM disk. There are several ways to boot this install kernel:

• Floppy disk: Floppy disk images are provided which can be used to create an install floppy on another Unix-like system, or on a DOS/Windows system. Typical file names are floppy41.fs, though several platforms have multiple floppy images available.

• CD-ROM: On several platforms a CD-ROM image (cd41.iso) is provided allowing creation of a bootable CD-ROM. This just contains the installation kernel - install files must still be retrieved via FTP or other source. You can, of course, build your own CD-ROM with whatever files and tools you desire.

• Existing partition: The RAM disk kernel can be booted off an already existing partition for an upgrade or reinstall.

• Network: Some platforms support booting over a network (for example using PXE or other network boot).

• Writing a file system image to disk: a filesystem image that can be written to an existing partition, and then can be booted.

• Bootable Tape: Some platforms support booting from tape. These tapes can be made following the INSTALL.platform instructions.

Not every platform supports all boot options:
• alpha: Floppy, CD-ROM, network, writing a floppy image to hard disk.
• amd64: Floppy, CD-ROM, network.
• cats: CD-ROM.
• hp300: CD-ROM, network.
• hppa: Network.
• i386: Floppy, CD-ROM, network.
• mac68k: Booted using utilities running on Mac OS. See INSTALL.mac68k for details.
• macppc: CD-ROM, network.
• mvme68k: Network, bootable tape.
• mvme88k: Network, bootable tape.
• sparc: Floppy, CD-ROM, network, writing image to existing swap partition, bootable tape.
• sparc64: Floppy (U1/U2 only), CD-ROM, network, writing image to existing partition.
• vax: Floppy, network.

All platforms can also use a bsd.rd to reinstall or upgrade.

Once the install kernel is booted, you have several options of where to get the install file sets. Again, not every platform supports every option.
• CD-ROM: Of course, we prefer you use the Official CD-ROM set, but for special needs, you can also make your own.
• FTP: Either one of the OpenBSD FTP mirror sites or your own local FTP server holding the file sets.
• HTTP: Either one of the OpenBSD HTTP mirror sites or your own local web server holding the file sets.
• Local disk partition: In many cases, you can install file sets from another partition on a local hard disk. For example, on i386, you can install from a FAT partition or a CD-ROM formatted in ISO9660, Rock Ridge or Joliet format. In some cases, you will have to manually mount the file system before using it.
• NFS: Some platforms support using NFS mounts for the file sets.
• Tape: File sets can also be read from a supported tape. Details on creating the tape are in the INSTALL.platform document.


No comments: