02-18-2020, 11:45 AM
(This post was last modified: 02-18-2020, 11:46 AM by ab1jx.
Edit Reason: subscribe
)
Alright, I'm thoroughly confused. I used OpenBSD for 15 years but only on x86. I'm looking at OpenBSD's INSTALL.arm64 and your post and wondering what goes where.
"/usr/mdec/pine64" where is that? Inside the miniroot? The OpenBSD directions talk about doing a dd of idbloader.img and u-boot.itb but is that after you dd the miniroot? Where does the real installation end up relative to this? Where do the files in the tarball's share/u-boot/pinebook go? They replace files in the miniroot?
I don't think I ever used a miniroot, there was a file that was an image of a floppy, I either wrote that to a real floppy or made a CD to boot from it. I'd put the install files in a partition of the drive I was installing onto, sometimes on the CD, or sometimes did an FTP or HTTP install from a local machine I'd set up for that. I'd assume in this case that the installer won't have a driver for the PBP's WiFi. So put them in a DOS partition on the SD card, shell out of the install and mount it?
"/usr/mdec/pine64" where is that? Inside the miniroot? The OpenBSD directions talk about doing a dd of idbloader.img and u-boot.itb but is that after you dd the miniroot? Where does the real installation end up relative to this? Where do the files in the tarball's share/u-boot/pinebook go? They replace files in the miniroot?
I don't think I ever used a miniroot, there was a file that was an image of a floppy, I either wrote that to a real floppy or made a CD to boot from it. I'd put the install files in a partition of the drive I was installing onto, sometimes on the CD, or sometimes did an FTP or HTTP install from a local machine I'd set up for that. I'd assume in this case that the installer won't have a driver for the PBP's WiFi. So put them in a DOS partition on the SD card, shell out of the install and mount it?