"Quote from: franco on April 23, 2015, 07:15:36 PM
o I only want to provide 1 additional image per architecture, so the question is 1G, 2G or 4G? 1G might be just big enough to run, 2G is reasonable, and 4G might be too big for some folks. What do you think?
Why not providing the smallest image size, and let users growfs their partition once installed ?
Quote from: franco on April 23, 2015, 07:15:36 PM
o What should be different about this setup? I was thinking of making it dual serial/vga and enabling var and tmp MFS by default. Any other ideas?
On a dual serial/vga image, what kind of multi-boot loader (boot0) will you use ?
boot0 is used to display this message during boot:
Code Select
1 FreeBSD
2 FreeBSD
F6 PXE
Boot: 1
And this menu is very usefull on nanobsd using 2 system slices: If after an upgrade you didn't like the new version, you still can ask to boot the previous "version" (old slice).
But there are 2 versions of boot0:
- boot0, that use vga as default output: This message will not be display on a serial-only board
- boot0sio, that use serial as default output, this message will not be display on vga screen
Quote from: franco on April 23, 2015, 07:15:36 PM
o Upon further reflection a second slice doesn't hurt in case we decide to go down that road in the future. The bootstrapping is always kind of simple. It kills a bit of space, but even so it may make a few people happy in the progress (nanobsd can be operated on the command line as well).
Then if you aren't using 2 "system" slices today, I understand why you don't care of displaying boot0 message.
