I second this as we are at the point where this size increase won't affect most folks. Pop!_OS uses a 512MB /boot (/boot/efi) partition which works well for dual boot setups as well. <br><br><br>Sent from ProtonMail mobile<br><br><br><br>-------- Original Message --------<br>On Feb 14, 2022, 03:45, Michael Mikowski < mmikowski@kfocus.org> wrote:<blockquote class="protonmail_quote"><br><html>
<head>
<style>/* for HTML 5 */
article,
aside,
datalist,
details,
dialog,
figure,
footer,
header,
main,
menu,
nav,
section {
display: block;
}
audio,
canvas,
progress,
video {
display: inline-block;
}
abbr,
mark,
meter,
time,
output {
display: inline;
}
html {
box-sizing: border-box;
}
*,
*::before,
*::after {
box-sizing: inherit;
}
html,
body,
blockquote,
ul,
ol,
form,
button,
figure {
margin: 0;
padding: 0;
}
button,
progress {
border: 0;
}
p,
ul,
ol,
dl,
blockquote,
pre,
menu,
td,
th {
font-size: 1em;
line-height: 1.5;
margin: 1.5em 0;
}
input,
select,
textarea,
optgroup,
button {
font: inherit;
}
img,
iframe {
vertical-align: middle;
}
ul,
ol,
menu {
padding-left: 2em;
}
dd {
margin-left: 2em;
}
b,
strong {
font-weight: bold;
}
pre,
code,
kbd,
samp {
font-family: SFMono-Regular, Consolas, "Liberation Mono", "Menlo", monospace,
monospace;
font-size: 1em;
}
pre {
white-space: pre-wrap;
word-wrap: break-word;
}
mark {
background-color: var(--bgcolor-mark, #ff0);
color: var(--color-mark, currentColor);
font-weight: bold;
}
small {
font-size: 80%;
}
a:link img,
a:visited img,
img {
border-style: none;
}
audio:not([controls]) {
display: none;
height: 0;
}
abbr[title] {
border-bottom: dotted 1px;
cursor: help;
text-decoration: none;
}
code,
pre,
samp {
white-space: pre-wrap;
}
code {
line-height: 1;
}
dfn {
font-style: italic;
}
h1,
.h1 {
display: block;
font-size: 2em;
line-height: 1.5;
margin: 0.75em 0;
font-weight: normal;
}
h2,
.h2 {
display: block;
font-size: 1.5em;
line-height: 1;
margin: 0.5em 0;
font-weight: normal;
}
h3,
.h3 {
display: block;
font-size: 1.1875em;
line-height: 1.2631578947;
margin: 1.2631578947em 0;
font-weight: normal;
}
h4,
.h4 {
display: block;
font-size: 1em;
line-height: 1.5;
margin: 1.5em 0;
font-weight: normal;
}
h5,
.h5 {
display: block;
font-size: 0.8125em;
line-height: 1.8461538462;
margin: 1.8461538462em 0;
font-weight: normal;
}
h6,
.h6 {
display: block;
font-size: 0.75em;
line-height: 2;
margin: 2em 0;
font-weight: normal;
}
:root {
--background-norm: white;
--text-norm: #262a33;
}
body {
font-size: 100%;
width: 100%;
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto,
Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;
padding: 1rem;
line-height: 1.5;
background: var(--background-norm);
color: var(--text-norm);
}
q {
quotes: none;
}
q::after,
q::before {
content: none;
}
a:focus {
outline: dotted thin;
}
a:active,
a:hover {
outline: 0;
}
img {
border: 0;
max-width: 100%;
}
table img {
max-width: none;
}
blockquote {
padding: 0.2em 1.2em !important;
margin: 0 !important;
border: 3px solid #657ee4 !important;
border-width: 0 0 0 3px !important;
}
blockquote blockquote blockquote blockquote blockquote {
padding: 0 !important;
border: none !important;
}
[hidden] {
display: none;
}
/* for HTML 5 */
:root {
--background-norm: #17181C;
--text-norm: white;
}</style>
<meta name="viewport" content="width=411, maximum-scale=2">
</head>
<body>
<div id="pm-body" class="inbox-body">
<div dir="ltr">
Hi Everyone:
<div>
<p>Members of the ubuntu-meeting asked me to clarify the issue with /boot. You can see the bugs filed at <a href="https://launchpad.net/bugs/1959971">https://launchpad.net/bugs/1959971</a> and <a href="https://launchpad.net/bugs/1960089">https://launchpad.net/bugs/1960089</a>.</p>
</div>
<div> <b>Personal Background:</b>
</div>
<div>
I currently lead the <a href="https://kfocus.org">Kubuntu Focus</a> engineering efforts, and have been a professional product engineer specializing in mission-critical HP/HA/HV systems for decades. You can see a overview of my experience at <a href="https://michaelmikowski.com">https://michaelmikowski.com</a>.
</div>
<div>
<br>
</div>
<div> <b>My Assessments:</b>
</div>
<div> <b><br></b>
</div>
<div> <b>0. This is a low-cost, high-return proposal.</b> People have pushed back against increasing the /boot partition, but I find most of the reasoning does not consider the true impact of a small /boot partition to the complete product.
</div>
<div>
<br>
</div>
<div>
<div> <b>1. The cost to provide the space needed is minimal for almost all FDE systems. </b>So why not just do it? Of course, there is more work to be done for the rest of the product (guide users on kernel selection; improve the kernel cleaning logic), but this is an important component that is required in any complete solution. It would provide substantial relief to many users immediately.
</div>
<div>
<br>
</div>
</div>
<div> <b>2. An overfull /boot partition is catastrophic for many users.</b> Many cannot recover their system because they don't have a rescue disk or knowledge of ext4, chroot, LUKS, lvm, cryptesetup, package management, and more. These people either reload the OS or give up.
<br>
</div>
<div>
<br>
</div>
<div> <b>3. This happens frequently, even when everything works as designed</b>, and even when just using a single kernel flavor. While on IRC yesterday discussing this, 3 unsolicited individuals stepped in to comment about how this is needed. And those are advanced developers who know better. Search for 'ubuntu full /boot partition' and check out how frequently this continues to occur.
<br>
</div>
<div>
<br>
</div>
<div> <b>4. There are many use cases where multiple kernel flavors will occur</b>, such as when the users switches from HWE to OEM to address hardware issues, or they install lowlatency for studio work. When this happens, the current size boot partition is highly likely to fill. This can corrupt the system and require a rescue disk for recovery.
</div>
<div>
<br>
</div>
<div>
Check out the DFMEA which is used to assess the severity of a failure mode: <a href="https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1959971/comments/7">https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1959971/comments/7</a>
</div>
<div>
<br>
</div>
<div>
Finally, I assure you the calculations for kernel boot-file-set sizes (180M with Nvidia GPU) are correct for 20.04, and will be correct for 22.04 unless the compression technique has been changed. It seems perfectly reasonable to expect this size to grow to 200M or more over the next 2 years. Also, the headroom + safety factor specified (10 kernel file-sets total) is reasonable when you consider that systems that reboot less frequently will accumulate kernels and that a single upgrade can install multiple additional kernel images.
</div>
<div>
<br>
</div>
<div>
Sincerely, Mike
</div>
<div>
<br>
</div>
</div>
</div>
</body>
</html></div>