On Dec 05 10:57:49, re...@d-compu.dyndns.org wrote: > Joseph S. Testa II wrote: > > > On 12/04/2013 05:31 PM, Aaron wrote: > >> On Wed, Dec 4, 2013 at 3:20 PM, Joseph S. Testa II > >> <jte...@positronsecurity.com> wrote: > > > >>> scsibus0 at sdmmc0: 2 targets, initiator 0 > >>> sd0 at scsibus0 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed > >>> sd0: 7580MB, 512 bytes/sector, 15523840 sectors > >>> scsibus1 at sdmmc1: 2 targets, initiator 0 > >>> sd1 at scsibus1 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed > >>> sd1: 1832MB, 1024 bytes/sector, 1875968 sectors > >>> boot device: sd0 > > > > [...] > > > >>> Available disks are: sd0 sd1. > >>> Which disk is the root disk? ('?' for details) [sd0] sd1 > >> > >> I might be crazy, but I am pretty sure you need to install to sd0. > > > > In this case, sd0 is my external SD card with the boot image on it. sd1 > > is the internal memory (see above). > > > > - Joe > > AFAICT it's safe to choose sd0 (external SD card) as the target. (I know I > did !) This will leave your originally installed OS intact.
Yes, that's why also chose to install to the SD card, to keep the Angstrom distribution for the HDMI. Can someone please confirm that this is supposed to work? You can just install to the media you are booting the bsd.rd from and that's supposed to work, right? All of the installer/bsd.rd is already in memory, right? > $ disklabel -pm sd0 > # /dev/rsd0c: > type: SCSI > disk: SCSI disk > label: Drive #01 > duid: 58c67b6d799992e1 > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 1936 > total sectors: 31116288 # total bytes: 15193.5M > boundstart: 32832 > boundend: 31116288 > drivedata: 0 > > 16 partitions: > # size offset fstype [fsize bsize cpg] > a: 480.5M 32832 4.2BSD 2048 16384 1 # / > b: 768.0M 1016832 swap # none > c: 15193.5M 0 unused > d: 760.8M 2589696 4.2BSD 2048 16384 1 # /tmp > d: 760.8M 2589696 4.2BSD 2048 16384 1 # /tmp > e: 1121.2M 4147712 4.2BSD 2048 16384 1 # /var > f: 1300.5M 6443968 4.2BSD 2048 16384 1 # /usr > g: 752.3M 9107328 4.2BSD 2048 16384 1 # /usr/X11R6 > h: 2848.9M 10648000 4.2BSD 2048 16384 1 # /usr/local > i: 16.0M 64 MSDOS > j: 1184.2M 16482624 4.2BSD 2048 16384 1 # /usr/src > k: 1620.4M 18907840 4.2BSD 2048 16384 1 # /usr/obj > l: 4340.8M 22226368 4.2BSD 2048 16384 1 # /home > > I'm not sure the "i" partitions is a remnant of the install image used. > I think it's needed for running the boot loader off of it anyway. Yes it is. I made the mistake of zeroing the disklabel before creating my custom layout, and lost the 'i' to boot from.