dman wrote: > I use bash as my shell. However the depends for initrd and/or > kernel-image want ash,...
Fine, but if they really need it they have to call it as 'ash' or they are buggy. > ...so /bin/sh is ash. You shouldn't need that: see above. While in theory /bin/sh -> ash should work since all maintainer scripts that use /bin/sh are supposed to be free of bashisms, in practice there may still be a few that aren't. Craig Dickson wrote: > I have ash installed also, but my /bin/sh --> bash. So I don't think that > the ash install script makes that association,... Of course not. ash does not conflict with bash. Why should it? It's just another shell, like tcsh and ksh. It just installs itself as /bin/ash and leaves /bin/sh alone. I can't find any kernel-image package that depends on ash, and initrd-tools wants it so that it can put it in the image (bash is too big). There is no need to make ash your system shell just because a few packages depend on it. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin
