From 1322cedd111954d66e282c436e0dd619ef586a4b Mon Sep 17 00:00:00 2001 From: P. J. McDermott Date: Wed, 08 Jul 2015 17:36:28 -0400 Subject: doc/install/pc: Update installation instructions --- diff --git a/doc/install/pc.mdwn b/doc/install/pc.mdwn index e52aedb..619ab60 100644 --- a/doc/install/pc.mdwn +++ b/doc/install/pc.mdwn @@ -4,8 +4,7 @@ **NOTE:** These instructions use a feature in an unreleased version of the ProteanOS Development Kit. You'll need to have built prokit from its Git -repository to use the PC installer. The installer interface is also subject to -change. +repository to use the PC installer. This guide explains how to use the interactive installer program distributed with prokit, the ProteanOS Development Kit, to install ProteanOS on a PC @@ -39,188 +38,23 @@ can only boot from an internal PATA drive. Pick a storage device on which you want to install ProteanOS and connect it to the computer on which you plan to run the installer. You can either connect the -device to a different computer (easiest in the case of a USB flash drive) or run -a live GNU/Linux system on the computer on which you plan to install ProteanOS. +device to a different computer (easiest in the case of a USB flash drive, while +an HDD or SSD would require a SATA/PATA-to-USB adapter) or run a live GNU/Linux +system on the computer on which you plan to install ProteanOS. Installation ============ -From your prokit build directory, run the `installers/pc` script as the -superuser to begin the installation. - -Answer the installer's questions ("Select a platform:" and "Select a block -device:") and it will install and configure ProteanOS and a boot loader for you. - -Sample Installation -------------------- - -Following is an installation of ProteanOS for the Dell Dimension 2400 to a hard -disk drive connected to a laptop by a SATA/PATA to USB adapter: - - $ sudo installers/pc - - Select a platorm - ================ - - Select a platform: - 1) Acer Aspire One AO751h - 2) Dell Dimension 2400 - 3) Lenovo ThinkPad X60/X60s/X60t - #? 2 - - Select a block device - ===================== - - Select a block device: - 1) ATA WDC WD3200BEKT-6 (sda) - 320.07 GB (298.09 GiB) - 2) ST316021 5ACE (sdb) - 160.04 GB (149.05 GiB) - #? 2 - - Making partition table and file system - ====================================== - - 1+0 records in - 1+0 records out - 512 bytes (512 B) copied, 0.00334818 s, 153 kB/s - Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel - Building a new DOS disklabel with disk identifier 0x51011a81. - Changes will remain in memory only, until you decide to write them. - After that, of course, the previous content won't be recoverable. - - Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) - - Command (m for help): Partition type: - p primary (0 primary, 0 extended, 4 free) - e extended - Select (default p): Partition number (1-4, default 1): First sector (2048-312581807, default 2048): Using default value 2048 - Last sector, +sectors or +size{K,M,G} (2048-312581807, default 312581807): Using default value 312581807 - - Command (m for help): Selected partition 1 - Hex code (type L to list codes): - Command (m for help): Partition number (1-4): - Command (m for help): The partition table has been altered! - - Calling ioctl() to re-read partition table. - Syncing disks. - mke2fs 1.42.9 (28-Dec-2013) - Filesystem label= - OS type: Linux - Block size=4096 (log=2) - Fragment size=4096 (log=2) - Stride=0 blocks, Stripe width=0 blocks - 9773056 inodes, 39072470 blocks - 1953623 blocks (5.00%) reserved for the super user - First data block=0 - Maximum filesystem blocks=4294967296 - 1193 block groups - 32768 blocks per group, 32768 fragments per group - 8192 inodes per group - Superblock backups stored on blocks: - 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, - 4096000, 7962624, 11239424, 20480000, 23887872 - - Allocating group tables: done - Writing inode tables: done - Creating journal (32768 blocks): done - Writing superblocks and filesystem accounting information: done - - - Installing base system - ====================== - - prokit: Using architecture i686-linux-glibc - prokit: Using platform dimension2400 - prokit: Using mirror http://us.mirror.gnu.dk/pub/proteanos - prokit: Setting up root... - prokit: Configuring opkg and retrieving Packages files... - prokit: Downloading base-files... - prokit: Unpacking base-files... - prokit: Downloading busybox... - prokit: Unpacking busybox... - prokit: Downloading config-base... - prokit: Unpacking config-base... - prokit: Downloading config-dimension2400-common... - prokit: Unpacking config-dimension2400-common... - prokit: Downloading libc.6... - prokit: Unpacking libc.6... - prokit: Downloading libopkg.1... - prokit: Unpacking libopkg.1... - prokit: Downloading linux-common... - prokit: Unpacking linux-common... - prokit: Downloading linux-image... - prokit: Unpacking linux-image... - prokit: Downloading opkg... - prokit: Unpacking opkg... - prokit: Downloading proteanos-branding... - prokit: Unpacking proteanos-branding... - prokit: Configuring packages... - Package base-files (1.0.3) installed in root is up to date. - Package busybox (1.21.1-12) installed in root is up to date. - Package config-base (1.5) installed in root is up to date. - Package config-dimension2400-common (1.5) installed in root is up to date. - Package libc.6 (2.19~r25243+sip1-3) installed in root is up to date. - Package libopkg.1 (0.2.2-1) installed in root is up to date. - Package linux-common (3.10.55~gnu-1) installed in root is up to date. - Package linux-image (3.10.55~gnu-1) installed in root is up to date. - Package opkg (0.2.2-1) installed in root is up to date. - Package proteanos-branding (0.2) installed in root is up to date. - Configuring linux-common. - Configuring libopkg.1. - Configuring opkg. - Configuring libc.6. - Configuring busybox. - update-alternatives: Linking //usr/bin/awk to /usr/bin/awk.busybox - update-alternatives: Linking //usr/bin/dc to /usr/bin/dc.busybox - update-alternatives: Linking //usr/bin/bzip2 to /usr/bin/bzip2.busybox - update-alternatives: Linking //usr/bin/bunzip2 to /usr/bin/bunzip2.busybox - update-alternatives: Linking //usr/bin/bzcat to /usr/bin/bzcat.busybox - update-alternatives: Linking //usr/bin/xz to /usr/bin/xz.busybox - update-alternatives: Linking //usr/bin/unxz to /usr/bin/unxz.busybox - update-alternatives: Linking //usr/bin/xzcat to /usr/bin/xzcat.busybox - update-alternatives: Linking //usr/bin/lzma to /usr/bin/lzma.busybox - update-alternatives: Linking //usr/bin/unlzma to /usr/bin/unlzma.busybox - update-alternatives: Linking //usr/bin/lzcat to /usr/bin/lzcat.busybox - update-alternatives: Linking //usr/bin/ar to /usr/bin/ar.busybox - update-alternatives: Linking //usr/bin/strings to /usr/bin/strings.busybox - update-alternatives: Linking //usr/bin/clear to /usr/bin/clear.busybox - update-alternatives: Linking //usr/bin/reset to /usr/bin/reset.busybox - update-alternatives: Linking //usr/bin/mkpasswd to /usr/bin/mkpasswd.busybox - update-alternatives: Linking //usr/bin/patch to /usr/bin/patch.busybox - Configuring base-files. - Configuring config-dimension2400-common. - Configuring proteanos-branding. - Configuring config-base. - Configuring linux-image. - - Installing boot loader - ====================== - - Installing lilo (24.0-2) on root. - Downloading http://us.mirror.gnu.dk/pub/proteanos/feeds/dev/trunk/i686-linux-glibc/all/base/../../../../../../pool/l/lilo/lilo_24.0-2_i686-linux-glibc_all.opk. - Installing config-lilo (1.5) on root. - Downloading http://us.mirror.gnu.dk/pub/proteanos/feeds/dev/trunk/all/dimension2400/base/../../../../../../pool/c/config-dimension2400/config-lilo_1.5_all_dimension2400.opk. - Configuring config-lilo. - Configuring lilo. - Reading boot sector from /dev/sdb - Warning: /dev/sdb is not on the first disk - Warning: Unable to determine video adapter in use in the present system. - Using BITMAP secondary loader - Calling map_insert_data - Mapping bitmap file /boot/tuxlogo.bmp - Warning: Video adapter does not support VESA BIOS extensions needed for - display of 256 colors. Boot loader will fall back to TEXT only operation. - Calling map_insert_file - - Boot image: /boot/vmlinuz - Added ProteanOS_1.0 * - - Boot image: /boot/vmlinuz.old - Added ProteanOS_1.0_~ - - Boot image: /boot/vmlinuz - Added ProteanOS_1.0_+ - - Writing boot sector. - Backup copy of boot sector in /boot/boot.0810 - 3 warnings were issued. +If you installed prokit to your system, run: + + $ sudo prokit installer-pc -a $arch -p $plat dev/trunk $device + +Otherwise, from your prokit build directory, run: + + $ sudo src/prokit installer-pc -a $arch -p $plat dev/trunk $device + +Replace `$arch` with the architecture (e.g. `i686-linux-glibc`), `$plat` with +the platform (e.g. `x60`), and `$device` with the device file name (e.g. +`/dev/sdb`). Make sure you've selected the right device; prokit will erase the +partition table and write a new file system on the device you specify! -- cgit v0.9.1