Bug#1043226: debian-installer: Please consider moving root user setup to expert install, or change text

2023-08-08 Thread Luna Jernberg
I agree, this was talked on in two podcast this and last month,
Distrohoppers Digest from July and Linux Userspace from yesterday in
August

Den mån 7 aug. 2023 kl 18:27 skrev Jonathan Carter :
>
> Source: debian-installer
> Version: 20230607+deb12u1
> Severity: wishlist
>
> Dear Maintainer,
>
> When setting up users and passwords in debian-installer in a default install,
> it prompts a user to set up a root password. In d-i, this works very different
> than in other installers, which causes quite a bit of confusion for users.
>
> Firstly, the instructions start off with "You need to set a password for
> 'root'", followed by seemingly uninteresting text about what a good password
> should be, which makes it incredibly easy for users to miss the part that sudo
> won't be set up for the first user.
>
> So, many users, and especially newcomers to Debian, follow the instructions 
> in the
> first line and are then surprised when they can't use sudo from their user 
> from
> their newly installed system.
>
> Would it perhaps make more sense to move the root password setup to the expert
> install d-i preseed entirely? Since this is likely only something that expert
> users would require in the first place? Either that, or move the explanation
> of what happens upward so that it's more prominent and not so easy to miss. In
> the latter case, it might also be worth while changing the first line that 
> says
> "you need to..." so that user won't feel compelled to immediately start typing
> a root password and click on next.
>
> Thank you for considering,
>
> -Jonathan
>



Re: installation-guide: simplify RAM/disk space requirements

2023-08-08 Thread Holger Wansing
Hi,

Samuel Thibault  wrote (Tue, 8 Aug 2023 00:14:11 +0200):
> Hello,
> 
> This looks reasonable, thanks!

Now pushed to git.

thanks



> Samuel
> 
> Holger Wansing, le mar. 08 août 2023 00:06:14 +0200, a ecrit:
> > Hi again,
> > 
> > Samuel Thibault  wrote (Sun, 6 Aug 2023 14:32:22 
> > +0200):
> > > Holger Wansing, le sam. 05 août 2023 20:46:27 +0200, a ecrit:
> > > > Now looking in the doc source, I see that the "780MB" value from above 
> > > > is 
> > > > architecture-dependent too.
> > > 
> > > Ah, yes, that's part of the lowmem testing.
> > > 
> > > > While 780MB seems realistic for amd64 to me, I wonder if the other 
> > > > values can
> > > > be up-to-date:
> > > > 
> > > > amd64:minimum_memory=780
> > > > arm64:minimum_memory=260
> > > > armel:minimum_memory=80
> > > > armhf:minimum_memory=190
> > > > i386:minimum_memory=485
> > > > mips:minimum_memory=85
> > > > mips64el:minimum_memory=345
> > > > mipsel:minimum_memory=170
> > > > ppc64el:minimum_memory=64
> > > > s390x:minimum_memory=44
> > > > 
> > > > In the most eye-catching case of s390x, my proposal would mean, to 
> > > > change
> > > > the value in the guide from 44 to 512MB !
> > > > That leads to the question, if the new situation after my changing 
> > > > would be 
> > > > wrong, or if the doc was wrong in the past?
> > > 
> > > The doc probably just ended up wrong by just not getting updated,
> > > because we don't have people who both care about updating them, and have
> > > access to the hardware or know the qemu tricks to test all archs.
> > > 
> > > I see that in the lowmem package,
> > > bbb4ed4c4da20d585cf30ceba9f0987173d3ac70 raised the default levels from
> > > 32MB/64MB to 120MB/155MB, that being the minimum numbers that were
> > > actually seen to work on at least some arch.
> > 
> > Ok, I have now included those changes into my patch, to get the numbers
> > up-to-date for all archs. 
> > 
> > That is:
> > 
> > amd64:minimum_memory_strict=350
> > amd64:minimum_memory=780
> > 
> > arm64:minimum_memory_strict=245
> > arm64:minimum_memory=260
> > 
> > armel:minimum_memory_strict=140
> > armel:minimum_memory=190
> > 
> > armhf:minimum_memory_strict=140
> > armhf:minimum_memory=190
> > 
> > i386:minimum_memory_strict=285
> > i386:minimum_memory=485
> > 
> > mips64el:minimum_memory_strict=200
> > mips64el:minimum_memory=345
> > 
> > mipsel:minimum_memory_strict=160
> > mipsel:minimum_memory=170
> > 
> > ppc64el:minimum_memory_strict=256
> > ppc64el:minimum_memory=500
> > 
> > s390x:minimum_memory_strict=120
> > s390x:minimum_memory=155
> > 
> > See patch.
> > 
> > 
> > > > And, if a generic value for all archs is realistic and makes sense at 
> > > > all?
> > > 
> > > Probably not, as seen in the values in the lowmem package.
> > 
> > I think I found a reasonable solution.
> > 
> > Current situation is:
> > 
> > We have two sorts of numbers for RAM size:
> > 
> > a) some kind of rough values, identical for all archs. These are just 
> >subjective values, rounded up to the next bigger RAM modules you can buy
> >(current values can be found in
> >"Table 3.2. Recommended Minimum System Requirements" at
> >https://d-i.debian.org/manual/en.amd64/ch03s04.html )
> >These are only rough recommendations, as in "we **recommend** X MB".
> >And this chapter 3.4 also mentions, that these recommendations can well 
> > be 
> >underrun by the second sort of values:
> > b) these are values based on meassurements during lowmem testing. They are 
> >different over the archs, and in the current text they are considered as 
> >some kind of strict requirement, as in "you **need** at least X MB" 
> > values.
> >--> Compare this to the "we **recommend** X MB" values from a) !
> > 
> > 
> > 
> > 
> > Taking all this as a basis, I would like to propose the following:
> > 
> > 
> > 1. in chapter 2 
> > (https://people.debian.org/~holgerw/installation-guide___improve-ram-size-values/amd64/ch02s05.html)
> >which is about hardware requirements, just mention the minimal rough 
> >recommended values from a) which says something like "512MB" or "1GB",
> >corresponding to RAM modules available from your favorite hardware store.
> > 
> > 2. People who want to try to go with lower values, are guided to
> >chapter 3 
> > (https://people.debian.org/~holgerw/installation-guide___improve-ram-size-values/amd64/ch03s04.html),
> >where they find the values from b) based on lowmem tests, which contain
> >the "absolute minimum values", drawing the baseline that cannot be 
> > underrun.
> >Note, that this page is different, depending on arch!
> > 
> > 3. Move all the constraints / advanced infos like
> >  - installer should automatically do memory-saving tricks on low-memory 
> > systems"
> >  - warning, when lowmem levels are untested for some archs
> >  - note, that graphical installer images need more RAM
> >   from chapter 2 to 3, where they fit better: That's not hardware (which 
> > woul