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

Bug#838919: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#838919: debian-installer: please calculate swap parition according to max RAM supported by the motherboard)

2016-09-29 14:15 GMT+03:00 Ben Hutchings <ben@decadent.org.uk>:
> On Wed, 2016-09-28 at 16:20 +0300, Martin-Éric Racine wrote:
> [...]
>> The thing is, right now, the user has two choices:
>> 1) Trust d-i to make the right choices once, even though more RAM is
>> likely to be added later on, at which point there won't be enough swap
>> to save the suspend image;
> Why do you think it's likely?  Hibernation is mostly used on laptops
> and I don't believe they often get RAM upgrades; in fact increasingly
> they don't have even have sockets for RAM upgrades.

Because it's what everyone I know does: as soon as the price for the
type of RAM their computer needs drops, they max it out.

As for hibernate, it in fact is used a lot on office desktops as well.
It was the preferred way of leaving the office at my two previous

>> 2) Perform every tiny step of the partitioning and filesystem creation
>> manually in order to take into consideration the memory controller's
>> maximum supported RAM capacity.
>> The former is inadequate, the later is overkill and honestly beyond
>> the lay user's skills.
>> How about being able to tell the automated partitioning variant how
>> much swap we want, but let it calculate the size of the other
>> partitions by itself?
> How many 'lay users' that would be overwhelmed by the partitioner
> nevertheless understand how to upgrade RAM, what swap space is, and why
> they might need more than the default?  I think that's a very small
> group indeed.

Pretty much everyone I know knows how to download the upgrade
instructions from the manufacturer's website, remove a couple of
screws and insert a memory module.  By comparison, very few people I
know understand the intricacies of LVM partitioning.


Reply to: