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

Bug#923091: base-installer: Allow installing w/o the broken merged-usr-via-symlinks



Hi,

Guillem Jover <guillem@debian.org> (2019-02-24):
> The current base-installer uses the default debootstrap settings
> which end up unconditionally installing systems with the
> merged-usr-via-symlinks deployment method which is broken by design,
> please see:
> 
>   <https://lists.debian.org/debian-devel/2019/02/msg00251.html>

I won't be commenting on the brokenness you claim in this bug report,
and in the mail you linked to, and in the subthread; that doesn't mean
I agree with your assessment.

Instead, I'll concentrate on the actual request for a change in
bootstrap-base below:

> I'm aware the original request to change the debootstrap default got
> unfortunately moved to the tech-ctte. :(
> 
> But regardless of that outcome I'd like to request to have a way to
> install using debootstrap's --no-merged-usr option, to not have to
> install from stretch and then upgrade to buster, or having to drop into
> a shell and do manual stuff from within the installer.

I'm not sure what costs (initial addition then maintenance) an
expert-only option would have, but I'm naively expect them to be rather
low? It seems to me that this would suit your needs and also make that
configurable through preseeding?

If that were to be implemented: the question must not be asked in a
normal installation, I think it shouldn't be translatable (at least at
first) so that it doesn't put more burden on l10n people (coordinator
and translators) for an expert-only option. Cc-ing Holger for input.

> In addition it would be also nice if that option was passed whenever
> /usr is not on its own partition, because then the properties from
> the merged-/usr concept are not relevant anymore, but we get all the
> downsides of the broken deployment method.

That shouldn't be tracked in this bug report as that seems quite
orthogonal (base-installer runs in d-i, not on installed systems)?

> If this was to be applied for buster, I'd be happy to provide patches.

Not promising anything, but I think I should be able to test/review such
patches once I'm done with updating the test suite.

> Otherwise I guess I might need to end up looking to generate
> alternative netinst somewhere else or something. :(

That won't be a factor regarding the inclusion of possible patches into
d-i, for buster or afterward.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature


Reply to: