Comment 1 for bug 1842198
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
These are certainly interesting ideas! I would guess we'd be more likely to do something zfs based than btrfs based but I'm not completely sure.
For d, having to reboot after the install is more of a feature than a bug IMO. If the installer has screwed up the bootloader configuration somehow, it's much better to find out immediately than three weeks later after a power cut! (Also once the install media is more than about three weeks old, you'll usually be installing a newer kernel than the one running the live session).
Opportunistically coping the rootfs to RAM if there is a lot of it is certainly an interesting idea (although I installed my NVMe laptop with the server installer the other day and the entire curtin invocation only took about 80s of which the rsync only took 20s so there's not a whole heap of room for improvement here when the disks are this fast anyway).