recovering a system

[Will Senn]

Hi Matt,

On 1/10/23 6:06 PM, Matthew Dillon wrote:
> Note that there are two partitions, 'a' and 'd'. 'a' has /boot and 'd' 
> has root.   You can display the disklabel installed in the GPT slice 
> with 'disklabel'
>
> disklabel da0s1
>
> If you want to mount both from the USB stick, mount root first, and 
> boot on top of it in /boot:
>
> mount /dev/da0s1d /mnt
> mount /dev/da0s1a /mnt/boot
>
> like that.  Its also easy to get confused when editing files and 
> accidentally edit files on the USB stick instead of on the drive.
>
> There is also a third partition... the EFI boot slice is da0s0 with 
> the msdos filesystem that the EFI boot program is stored on.  You 
> usually do not have to mount that one though, and we generally don't 
> mount it on running systems.  Its only used by the BIOS as the stage 1 
> boot loader.

Thanks for the details, I just had just written:

TODO: Learn more about disks, slices, and hammer stuff in DragonFly

into my notes.

> On it not finding avalon...
Ah this is a bug, prolly:

Pristine 6.4 install - log in as root and...

# backup df-latest.conf which is hosed by pkg upgrade
cp /usr/local/etc/pkg/repos/df-latest.conf 
/usr/local/etc/pkg/repos/df-latest.conf.bak

pkg update
... all goes swell

pkg upgrade
Updating Avalon repository catalogue...
Avalon repository is up to date.
All repositories are up to date.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
     pkg: 1.14.4 -> 1.18.4 [Avalon]

Number of packages to be upgraded: 1

3 MiB to be downloaded.

Proceed with this action? [y/N]: Y
[1/1] Fetching pkg-1.18.4.pkg: 100%    3 MiB 790.6kB/s    00:04
Checking integrity... done (0 conflicting)
[1/1] Upgrading pkg from 1.14.4 to 1.18.4...
[1/1] Extracting pkg-1.18.4: 100%
pkg: Failed to execute lua script: [string "-- args: 
etc/pkg.conf.sample..."]:12: attempt to call a nil value (field 'stat')
pkg: lua script failed
No active remote repositories configured.

# and it appears that pkg upgrade blows away the df-latest.conf

# restore the backed up version? or the sample? I chose the backed up 
version this time, last time I picked the sample
# either way, pkg upgrade works fine now
cp /usr/local/etc/pkg/repos/df-latest.conf.bak 
/usr/local/etc/pkg/repos/df-latest.conf
redo pkg upgrade

Where/how should I report it?

Thanks,

Will