alexkarle.com

Source for alexkarle.com
git clone git://git.alexkarle.com/alexkarle.com.git
Log | Files | Refs | README | LICENSE

002-install.txt (1758B) [raw]


      1 # 002-install
      2 
      3 _Tues Sept 21, 2021_
      4 
      5 I'm a huge fan of OpenBSD. The simplicity of the system, the cohesive
      6 feel it has, the proactive stance on security... when we decided we'd
      7 set up a tilde, I knew I wanted it to be on OpenBSD.
      8 
      9 The only problem? My preferred registrar (Linode) doesn't support it!
     10 
     11 Fortunately there's a comprehensive post on the Linode forum of how to
     12 do it [here](https://www.linode.com/community/questions/10329/openbsd-on-linode).
     13 
     14 It took us ~45m, the longest OpenBSD install I've had since I first
     15 flashed it on an old thinkpad. 40m of that was waiting for the node to
     16 boot and reboot, etc (we kept messing up the configuration).
     17 
     18 1. Create a New Linode (any OS will do)
     19 2. Once booted, shut it down
     20 3. Under the "Storage" tab delete the ext4 partitions
     21 4. Create two new disks, both "Raw" format:
     22    1. One labeled "install", 1GB (could do less)
     23    2. One labeled "os", the rest of the space
     24 5. Boot in "Rescue" mode
     25 6. In the serial console, wget the minirootXX.img
     26    1. Check the sha256 against the SHA256 file
     27    2. Check the signature using signify (on a different machine that
     28       has signify)
     29 7. Find the install disk with `lsblk`
     30 8. Flash the img using: `dd if=minirootXX.img of=/dev/sdX bs=1M`
     31 9. In the Configurations tab, create a new one:
     32    1. Full Virtualization
     33    2. Select a Kernel > Direct Disk
     34    3. /dev/sda - os
     35    4. /dev/sdb - install
     36    5. boot from sdb
     37 10. Reboot into configuration, install OpenBSD from serial console
     38 11. Halt/shutdown, and change configuration to boot from sda
     39 12. Rejoice!
     40 
     41 In our case, our main problem was that we skipped the "Direct Disk"
     42 kernel step so we were booting a Linux kernel and trying to load the
     43 img... it panic'd every time! Took us a few boots to figure that out :)