On Sat, Sep 27, 2014 at 04:33:28PM +0200, Axel Beckert wrote:
> Hi Troy,
>
> Troy Benjegerdes wrote:
> > I had an unusable system after removing bash because of dhclient.
>
> Bash is an "Essential" package. You're on yourself if you remove that
> (or any other "Essential") package.
>
> Being an "Essential" package means that this package is guaranteed to
> be installed and no package needing bash needs to declare a dependency
> explicitly.
>
> The current bash issue though raises the demand for making bash a
> non-essential package, so maybe making the bash package non-essential
> should become a release goal for Jessie+1.
So far my biggest problem removing bash is the dire warnings from dpkg/apt
about how essential bash is, and the reality is changing to /bin/sh solved
the one serious problem I had.
I would argue that unessentializing bash should be a release-critical bug
for Jessie, not Jessie+1.
If that's not possible, then at least make it a little easier to remove
and provide docs to sysadmins on what to expect and at least prevent bash
from being auto-reinstalled at the next apt-get upgrade.
Migrating users login shells from /bin/bash would be a slightly different
story. I'm thinking 'bash-noroot' that exits if started as root or any of
the common system accounts would be a reasonable compromise?
--
----------------------------------------------------------------------------
Troy Benjegerdes t...@7el.us
7 elements earth::water::air::fire::mind::spirit::soul grid.coop
Never pick a fight with someone who buys ink by the barrel,
nor try buy a hacker who makes money by the megahash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
