[Bug 262098] [nanobsd] builds with s2 for /cfg, and can't boot?
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262098] [nanobsd] builds with s2 for /cfg, and can't boot?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262098] [nanobsd] builds with s2 for /cfg, and can't boot?"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262098] [nanobsd] builds with s2 for /cfg, and can't boot?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 21 Feb 2022 16:34:26 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262098 Bug ID: 262098 Summary: [nanobsd] builds with s2 for /cfg, and can't boot? Product: Base System Version: 12.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: peter.larsen@larsendata.dk There seems to have been many changes from 12.2 to 12.3 in /usr/src/tools/tools/nanobsd for some reason I end up with a disk image with root on s1, /cfg on s2 and nothing on s3 this have not been a problem on 12.2, but I assume its a problem due to I have "NANO_IMAGES=1" in my .conf file expected behaviour: s1 for root, s2 preserved as a blank, and s3 used for /cfg actually getting: s1 for root, s2 used for /cfg, s3 blank result: Image can't boot... it expect /cfg on s3 -- You are receiving this mail because: You are the assignee for the bug.