On 1/24/2012 12:38 PM, Ulrik Lunddahl wrote:
> Jim Wrote:
> 
>> Why not use a full install on a small disk? For VMware it would work much 
>> better and have none of the limitations
>> of the NanoBSD version.

It would actually use more disk space. Twice as much. You gain more from
snapshotting a VM than you do from the second OS slice.

> Why would it work better, if you were not going to use any of the features 
> not present on the nanobsd images ?

Because it's a full install meant to be run in that environment. The
tactics taken by the NanoBSD images are meant for embedded hardware.

The binaries are the same (except the default kernel), but NanoBSD
activates some different code paths in the software that react
differently, expecting the storage to be flash-based so limited writes
are done.

Certain packages are excluded on NanoBSD due to either size/complexity
or the fact that they aren't compatible with being run on a CF when
NanoBSD keeps it read only.

None of those are factors for a VM even with a small drive allocated.

>> There is no advantage to running an embedded version in a VM.
> 
> Probably not beside simplicity, one R/O image based on a trimmed freeBSD 
> booted to RAM and one configuration file, this itself is a very strong 
> argument when trying to put pfSense in where ordinary firewalls used to sit.

NanoBSD has two OS slices, plus a config slice. It is kept R/O unless
changes are being made, but even without that, changes aren't made
continually unless you have packages doing that.

The only other difference is the layout of /tmp and /var which on
NanoBSD are small in size and kept only in RAM, which is why some
package and other operations fail. On a full install, those are on the
HDD (except /var/run which is in RAM on both)

> Sorry, I'm a sales guy with technical skills... :-)

And a knack for overthinking things :-)

>> Probably not, that is intended for full installs, and NanoBSD is meant for 
>> embedded hardware.
> 
> The packages menu could/should warn about this then, as it is now, the 
> package installer just runs and brakes the box.

Usually packages are removed from the Embedded list if they are known to
be problematic. I'm not sure why that one is enabled for NanoBSD, it was
probably activated and since nobody ever tried it, nobody complained, so
there were no compelling reasons to change it. If it really doesn't
work, we can flag it as unsafe for embedded.

Also it's much easier to install from ISO to a VM than it is to monkey
around with converting disk images and either dealing with a serial pipe
(or using Nano+VGA)

Jim
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to