Opened 15 months ago
Last modified 15 months ago
#18249 new enhancement
Implement "boot enviroments"
| Reported by: | nephele | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | System/Boot Loader | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
As a bit of context: FreeBSD has boot enviroments, which are similar to our state tracking. FreeBSD does it with the ZFS level which means all files are also in a version. Not so much for us.
What I would like is to have destinct "enviroments" where a new state is installed, that is I can have a r1beta4 branch installed to the exact same partition as a nightly, and the bootloader will prompt me which one to boot (or pick one per default). the current packagefs is already perfectly capable of handeling this, it would just be a big ui improvement over "installing beta4" for the next boot and then re-installing the nightly afterwards if i only need beta4 for some specific backwards compatibility testing.
This seems like it could end up quite confusing for regular users and only useful for us developers who are messing a lot with the system.
Personally I just have a separate partition that I use for such testing, so I don't ruin my main system?