Re: Shipping /bin/sh [Re: Moving bash from essential/required to important?]
On 04/06/2011 01:55 AM, Carsten Hey wrote:
> * Luk Claes [2011-04-05 23:11 +0200]:
>> On 04/05/2011 11:05 PM, Jonathan Nieder wrote:
>>> Carsten Hey wrote:
>>>> * Steve Langasek [2011-04-04 19:37 -0700]:
>>>>> On Tue, Apr 05, 2011 at 02:00:36AM +0200, Carsten Hey wrote:
> Guaranteeing that /bin/sh exists and is functional during debootstrap,
> even before any maintainer script has been run, could be archived if
> every system shell would provide /bin/sh pointing to itself. To avoid
> file conflicts, all but the one whose preinst is run first (finding
> a clever way to detect this shouldn't be that hard) could divert their
> /bin/sh to /bin/sh.$SHELL. When update-shell (or whatever it's name
> would be) finally takes over managing /bin/sh, it could divert the
> remaining /bin/sh away and replace it with a symlink not known to the
> packaging system.
That unfortunately does not work as diversions are only meant to be used
when 2 packages provide the same file. One of the problems being what to
do when you remove one of the shells (for instance the one providing
/bin/sh)...
Cheers
Luk
Reply to: