Feature #4272
closedDepreciate Full install. Replace with Embedded, include gui to allow adding a mount / path to install packages to (and additional Full install features as packages)
0%
Description
Embedded looks like a great way to go, why continue supporting a full install?
I've had this idea for a while. It may not work out as well in a post pbi world
however, I think it would be great if a basic mount/folder chooser could be added
to embedded that would allow a user to have their SSD/CF/Flash/whatever and a HDD.
This gui could include remounting /var/log to a HDD; it would be be default spot for
pbi's, and data. Now having read that pbi's aren't likely to be sticking around I wonder
if since pkgng packages are STAGEd, if those packages could still be installed to a prefix
specified.
The benefit being, "Full installs" would have the nanobsd dual partition setup for reliability,
it would be one less branch that would need support and testing, and users could still install
whatever packages suits their needs. Additionally if done correctly it would allow a CF consumer
to say, install squid (on a HDD using the methods above) and setup a disk cache using the same
location.
I haven't recently compared the two installs to see what may be missing, but I assume it would
be relatively trivial to add missing components from the full install as additional packages.
tldr;
Kill off Full install support
Add gui to mount a slice/drive/destination for packages/logs/extra data
add missing full install features as packages (if there are any extras over Embedded these days)
reduce maintenance / testing / code paths
???
Profit?!?!
Updated by Jim Pingle almost 10 years ago
- Status changed from New to Rejected
Not likely to happen. If anything we may go the other way, deprecating NanoBSD and using full installs exclusively. Likely using ZFS with snapshots.