Steps to install 32-bit GLFPE 512 to Virtualbox VM or to physical harddrive 13 Jan 2018 GLF --------------------------------------------------------------------------------------------- The following instructions have been tested under a Windows 10 installation of Oracle Virtualbox. GLF has only tested 32-bit VMs because his computer CPU, though a 64-bit CPU, does not support a key element necessary to run a 64-bit VM. It is presumed a higher level CPU would support 64 bit VMs, and the procedures below would be almost identical if applied to a 64 bit VM instead. Most of the instructions also alloly if instead of a VM, the OS is installed as the ONLY OS on a physical harddrive of a non-virtual computer. If Installing to Virtual Machine (Virtualbox VM): ------------------------------------------------- Start Virtualbox console window on the host computer. Prepare (or rename and reuse) a VM with 25Gb of virtual hard drive space suitable for 32 bit Debian Linux. Name the VM such that the version number of GLFPE is apparent. Example: 32TEST_GLFPE_512_Installer Set up the VM to boot from the current installer/live boot ISO. Click on named VM item to bring up configuration. Storage Right click on optical drive, then remove attachment from IDE Optical drive Right click on IDE, then add attachment optical drive Select choose disk identify the ISO file for current GLFPE version to test Make sure the network is connected (will look for some software online). Double Click on named VM item to launch -- should boot from ISO If desired, test boot from the ISO-- verify expected functionality, then reboot and restart the same VM. If installing to physical computer hard drive: ----------------------------------------------- Prepare the ISO image of GLFPE Linux to either a DVD or a bootable USB drive. Using a computer with a CPU compatible with the live boot disk of interest (either i386 or amd64), load the drive and boot the disk. The actual required CPU for the i386 specified target is actually at least a 686 cpu as of this writing. Many Debian libraries are no longer compiled for 386, 486, or 586 targets, since these systems are considered obsolete. Computers with AMD and most Intel 64-bit compatible CPUs should be able to boot either type. Debian 9 is not yet able to boot in Secure Boot mode. For the time being, only Legacy BIOS or UEFI WITHOUT Secure Boot support can boot the GLFPE Linux disks. It will be necessary for the user to manipulate the boot disk order, and perhaps the BIOS settings to allow booting from either the DVD or USB drive. Installation -- either VM or physical drive ------------------------------------------- If boot succeeds, you should see a text-based menu, with GLFPE splash screen background showing the version date and number. NOTE: For i386 builds, the menu for GLFPE Linux will show as "686". Because Debian support for generic i386 platform has evolved to only support 686 and higher platforms, the actual code built into libraries and the kernel will probably no longer actually run on a 586 class CPU, even if 586 is specified. Select Install from the boot menu (non-graphical). Sometimes graphical install is a better choice, if the non-graphical console does not work properly on a particular computer. The directions below assume non-graphical, but GUI directions are similar, although a mouse or trackpad will also be required A selection box for language will come up. Select English. Next box: select United States Next box: select American English (detect hardware, install components...) Next box: Configure the network Select hostname: glfpe512deb9 Next box: Select Domain name: home.org Next box: Set up users and passwords Select Root password: (empty -- hit ENTER only) blank password This sets up "sudo" access to root for first user. Reenter to verify: (empty again) Full name for new user: Gary Flispart User name for account: (will show "gary") ENTER to accept this. Choose password for new user: Type a GOOD password here, and keep track of it. It will get "sudo" (root) access later. Reenter password to verify: (same as above) Next box: Configure the clock Select Eastern (detect disks, install components...) Next box: Partition disks ASSUMING THIS IS A VM -- you are not really partitioning the computer's disk, just the VM disk. ASSUMING THIS IS A PHYSICAL DRIVE -- if you continue you will completely wipe all preexisting OS and other files from the actual hard drive. BE SURE YOU WANT TO DO THIS! If there will be only one partion and one OS ---------------------------------------------- Select Guided -- use entire disk At least one disk (One VM disk, one or more if physical) should show up, select the desired disk, ENTER. Select all files in one partition Finish partitioning and write changes to disk -- ENTER Write changes to disks? Tab to "Yes", ENTER (format partition...) POINT OF NO RETURN if installing to physical drive! If there will be another OS on the disk and its partition already exists ------------------------------------------------------------------------ Select Manual Use manual settings to select a partition, put an EXT4 filesytstem on it, mount root on it, make it bootable. Use manual settings to select a swap partition. Commit partitions and start installing data. (format partitions...) POINT OF NO RETURN if installing to physical drive! Continue with installation --------------------------- (Installing system, copying data to disk...) Next box: Configure packages Use a network mirror? Yes ENTER Package manager country: United States ENTER ftp.debian.us.org ENTER HTTP Proxy (blank for none): ENTER (configuring apt...) (installing GRUB...) Install GRUB to master boot record? Yes ENTER Device for boot loader installation: Arrow down to /dev/sda, ENTER (installing GRUB...) (finishing installation...) Installation complete. ENTER to continue (finishing installation...) (a few minutes...) Auto-reboots to installed OS. If installing to a physical hard drive, remember to remove the live boot installer disk (DVD or USB) before the boot proceeds to relaunch the live boot session. Testing the newly installed OS ------------------------------ When the newly installed OS reboots, watch for certain things: log in: user name is not displayed, type it in (gary) password: as set above Check the time after fully booted. Should be set correctly to local time (EDT). Click on time, brings up map and locations, Louisville. Click on the SET button. A password box pops up, enter password. (if "clock quits unexpectedly", press Reload) Should show Louisville time and temperature in degrees F. Now fully booted, give the system a few test runs to check out menus and key software functionality. Suggest: Skychart (verify location is IUS Observatory) Arduino IDE (verify version is 1.8.5) (verify tools include processors for Teensy models and ATtiny models) VIDE (verify it comes up -- testing compilation will require installing source) ... When done, shut down: System, Shut down, Shut down OS shuts down. If physical computer, should power off. If VM shuts down, reverts back to Virtualbox console screen. Reboot following a complete shutdown will show a normal GRUB boot screen with a short timeout for selection of OS (only one was installed), followed by continuation of the selected boot image. Getting external data on ond off the OS filesystem --------------------------------------------------- Whether physical or virtual, the installed OS should have access to the network, especially if (recommended for installation) a direct Ethernet connection is used. The host system passes to any VM the same hardware network access available to the host. If the installed (Debian) OS requires special software drivers to access an internal WiFi card, then without an Ethernet connection the network may be offline, which would impede installing and upgrading software from the repositories. If the installed OS is physical, then all normal peripherals such as USB, optical drives, ports, etc. should be available as usual. However if the OS is on a VM, access to external hardware is restricted. In general, VirtualBox will not provide USB ports directly, and if it does, it does at USB 1 specification (VERY SLOW). The practical way to exchange files with external sources is through a shared folder. Under VirtualBox, shared folders are easily specified in the console, but they are not recognized by the VM OS unless special software is installed on the VM OS. For Linux, the VirtualBox Guest Additions must be installed after the OS is successfully booted from VM before shared folders can be seen or used from the VM. This is not required for use of the VM, but except for network access (LAN, WAN, internet, file servers, etc.), no exchange of data is readily possible with the host computer. That limits use of the VM OS to such uses as browsing the internet and adhoc testing of OS functionality. If installed to VM, installing the VirtualBox Guest Additions -------------------------------------------------------------- For full practical use of the VM, it will be necessary to install Virtualbox Guest Additions, so that data can be passed back and forth (requires root access) between the VM and the host computer. Before installing the guest additions in the VM, set up the virtual connection to a physical hard drive folder in the Virtualbox console window: Select the VM of interest, Storage, click on "Shared Folders" in the tree on the left. Specify a physical hard drive folder, select autorun and full access. Installation under Debian VM of the Guest Additons can be initiated from the Virtualbox menu bar: Devices Insert Guest Additions CD Image A CD-ROM image is mounted and shows on desktop. The following looks right, but doesn't work: Select Autorun Select Run (ERROR) Instead, bring up a terminal window. sudo apt-get install module-assistant (enter password) sudo m-a prepare (takes a while...) Right-click the icon for the CD-ROM on the desktop, then select Open in Terminal (this brings up a second terminal window) ls (shows files) use linux built-in character copy-and-paste to assist the following type sudo sh ./ (no ENTER yet) move mouse to filename displayed after "ls": VBoxLinuxAdditions.run drag mouse while holding left button over complete filename move mouse to follow sudo sh ./ on command prompt line press scroll roller button (middle button) The following command should be pasted into the prompt: sudo sh ./VBoxLinuxAdditions.run (installation proceeds, takes a few minutes) Close all terminal windows. Reboot the VM (Shut down, then restart) The reboot will show a normal GRUB boot screen. On reboot, new functionality should be apparent: The window size should be reconfigurable from the System, Display menu There should be a shared folder icon on the desktop. To use the folder requires root access, which is available under the file manager (in GLFPE anyway) as a line item on right click, "Open as Administrator", which requires a password. This folder can be used to pass data back and forth to the host system, to allow saving work progress and/or loading supplemental data or programs. Remember that since root access is required to get to the shared folder, any files copied to the VM will be owned by root. You will need to chown them (or open a folder as Administrator under the file manager, the use Properties, Permissions) to change the owner and group to the login user for each file.