Re: [PATCH] sln: Install as a hard link to ldconfig

[Mike Frysinger <vapier at gentoo dot org>]

On 01 Aug 2016 15:37, Maciej W. Rozycki wrote:
> On Mon, 1 Aug 2016, Mike Frysinger wrote:
> > >  E.g. booting Linux with `rw init=/bin/bash.static' has always worked for 
> > > me, with the root filesystem mounted r/w and ready for any recovery 
> > > actions, such as fixing up DSO symlinks.  And I see no reason for it to 
> > > stop working even where an initial RAM disk is used, as an image of such a 
> > > RAM disk is always self-contained and not used beyond early (pre-init) 
> > > initialisation needed to pull the root and maybe console device drivers.
> > 
> > bash.static is just as much of a distro-specific convention.  i haven't
> > heard of this before, and Debian/Ubuntu/Gentoo don't have it.
> 
>  I find it a bit surprising for a general-purpose distribution not to 
> provide a static shell by default, but this is as you say a policy set by 
> individual distributions.  I would feel a bit nervous if I were a system 
> administrator and didn't have a static shell around on a system I was 
> taking care of.

i agree, but i don't think it's something we need to support.  having just
a static (bash) shell doesn't get you very far -- you've got a few bash
builtins and that's it.  trying to actually recover from things often need
far more commands.  sln only helps you with creating symlinks (e.g. like
resetting glibc links, assuming it's a glibc install error).  i think that
special casing this one scenario doesn't make sense nowadays.

in Gentoo, we ship a build of busybox with a lot of built-in commands.
you can recover form a wide range of issues, set up the network, fetch
files over the network, and decompress/unpack archives.
-mike

Attachment: signature.asc
Description: Digital signature