Having some problems, seem minor so far, with my recent GhostBSD 15.0 installation.
Some bundled system utiliies are MIA, mount_nfs, mount_smbfs, perhaps(likely) others.
Rather than scrapping the whole thing and reinstalling, I'd like to simply extract these binaries from the install source.
I assume that all is contained within data/system.img on the installation ISO.
So, I tried:
# file system.img
Result:
system.img: ZFS snapshot (little-endian machine), version 2, type: NONE, destination GUID: 00 00 00 00 00 00 00 00, name: 'ghostbsd@clean'
# sudo mdconfig -a -t vnode -f system.img
Result:
md0
# ls -l /dev/md*
Result:
crw-r----- 1 root operator 0x91 Aug 1 06:14 /dev/md0
crw------- 1 root wheel 0xb Aug 1 03:56 /dev/mdctl
# sudo mount -r /dev/md0 /mnt
Result:
mount: /dev/md0: No such file or directory
# gpart show /dev/md0
Result:
gpart: No such geom: /dev/md0.
I guess that would have expected to see a partition/slice or 2.
And yes, same result whether mount -t is accompanied by ufs, zfs or does not appear at.
So, can somebody out there enlighten me as to what magic is required for to get into system.img ?
TIA
Some bundled system utiliies are MIA, mount_nfs, mount_smbfs, perhaps(likely) others.
Rather than scrapping the whole thing and reinstalling, I'd like to simply extract these binaries from the install source.
I assume that all is contained within data/system.img on the installation ISO.
So, I tried:
# file system.img
Result:
system.img: ZFS snapshot (little-endian machine), version 2, type: NONE, destination GUID: 00 00 00 00 00 00 00 00, name: 'ghostbsd@clean'
# sudo mdconfig -a -t vnode -f system.img
Result:
md0
# ls -l /dev/md*
Result:
crw-r----- 1 root operator 0x91 Aug 1 06:14 /dev/md0
crw------- 1 root wheel 0xb Aug 1 03:56 /dev/mdctl
# sudo mount -r /dev/md0 /mnt
Result:
mount: /dev/md0: No such file or directory
# gpart show /dev/md0
Result:
gpart: No such geom: /dev/md0.
I guess that would have expected to see a partition/slice or 2.
And yes, same result whether mount -t is accompanied by ufs, zfs or does not appear at.
So, can somebody out there enlighten me as to what magic is required for to get into system.img ?
TIA