| Summary: | Live ISO booting updated kernel in encrypted +pick up mgalive-persist partition in LVM | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Morgan Leijström <fri> |
| Component: | Release (media or process) | Assignee: | Martin Whitaker <mageia> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | davidwhodgins, sysadmin-bugs |
| Version: | Cauldron | ||
| Target Milestone: | Mageia 9 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | Look at for Mageia 9 | ||
|
Description
Morgan Leijström
2020-12-08 22:30:48 CET
Morgan Leijström
2020-12-08 22:31:32 CET
Target Milestone:
--- =>
Mageia 8 See my previous answer in bug 25191, comment 2. Also note that there is a disadvantage to using an encrypted persistence partition (even in the simple case we support now). GRUB won't detect any newer kernels stored there, so you will always be using the original kernel. As I said in the previous bug, if you want/need a more complex setup, just use the classical installer to install directly onto your removable device. It may use more space, but it should be faster and more flexible. Oh, thanks for the heads up about the new kernel will not get used if using encryption! I will note that on the wiki. Trying to get to the bottom of what can be done - not mostly for me but for enthusiasts eventually reading the wiki. Yes a traditional install is more flexible. However, Live to me feels a bit more reliable. I have had some trouble before about where boot loader lands, and i believe an update screwed up main system (or a coincidence), but that was years ago. Did not report it, but something similar to Bug 27013 Not sure which is faster; compression also mean less data to read/write and transfer. Depends on how CPU intensive it is and CPU versus memory and connection speed. But OK we can compress on a normal install too. I will not experiment though - not now anyway... PS Today used mga8 live at a customer to replace a disk, writing diskimage. :) DS It's not straightforward to support this, so it's not going to happen for Mageia 8. GRUB2 does have some support for booting from encrypted filesystems, so that's something else to look at for Mageia 9. Target Milestone:
Mageia 8 =>
--- :) Status comment:
(none) =>
Look at for Mageia 9 Wondering: As an encrypted Live always boot original kernel, can that induce a problem with proprietary drivers rebuilding and use? Regardless of that, maybe kernel updates ought to be blacklisted if mgalive-persist is encrypted? Pinging for the question in comment 5 (for writing in wiki) (In reply to Morgan Leijström from comment #5) > Wondering: > As an encrypted Live always boot original kernel, can that induce a problem > with proprietary drivers rebuilding and use? It shouldn't since the running kernel will not be auto-orphaned. > Regardless of that, maybe kernel updates ought to be blacklisted if > mgalive-persist is encrypted? What about users installing updates in preparation for then installing to a different computer (that may need the new kernel)? CC:
(none) =>
davidwhodgins Thank you :)
Morgan Leijström
2021-03-15 09:01:42 CET
Severity:
normal =>
enhancement |