[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#951709: /boot should get a bigger share of disk in default installation



On Tue, Mar 10, 2020 at 11:21:10PM +0100, Julien Cristau wrote:
>On Tue, Mar 10, 2020 at 09:50:07PM +0100, Holger Wansing wrote:
>> Hi,
>> 
>> Ben Hutchings <ben@decadent.org.uk> wrote:
>> > On Thu, 2020-02-20 at 18:50 +0530, Pirate Praveen wrote:
>> > > Package: debian-installer
>> > > Version: 20190702+deb10u3
>> > > Severity: important
>> > > 
>> > > With initrd around 60+ MBs, 236 MB /boot in a 300 GB hard disk can hold 
>> > > only 2 versions of the kernels at the same time. When installing a 3rd 
>> > > kernel /boot gets filled up. I think it should be able to store at 
>> > > least 3 kernels and ideally 4 or even more.
>> > >
>> > > The paritions were created automatically with just /home in a separate 
>> > > partition with lvm by debian buster installer.
>> > 
>> > I agree; the default size of /boot is now too small.  I think we should
>> > normally allocate at least 500 MB to it.
>> 
>> This has just been addressed; see
>> https://salsa.debian.org/installer-team/partman-auto/-/commit/cf6b2d152b08b6c78da6a6f7ca26a99bdadfdfce
>> 
>Not quite.  If Ben says we need at least 500M, then we'll have to
>adjust further, as that commit uses 512M as a maximum.  For comparison
>Ubuntu's partman-auto sets the min at 512M and max at 768M.  Do people
>feel that's where we should go?

I'm torn - that's a good plan for large systems, but people on smaller
platforms (e.g. small SD on rpi) that's a lot of space.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"War does not determine who is right - only who is left."
   -- Bertrand Russell


Reply to: