Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
By 100101101 at 2014-10-19 13:06
Some people were wondering how to say goodbye to bash.
Personal reasons vary from security risks to bloat, or "Just because I can, and I want too."
Only if you are aware of the risks, have decided it is your OS/machine/time anyway, and are hellbent on this action should you continue.
Run$ dpkg-reconfigure dash
Edit: /etc/passwd - change any entries of "/bin/bash" to "/bin/dash".
Edit: /etc/shells - remove all but /bin/sh, and /bin/dash.
Use your package manager to "purge" the BASH package.
You will be asked to type "Yes, I am aware this is a very bad idea" twice.
From terminal: "executing only in the root directory will not succeed to fix scripts"
cd /bin
find . -type f -exec sed -i 's/bash/dash/g' {} +
cd /sbin
find . -type f -exec sed -i 's/bash/dash/g' {} +
cd /usr
find . -type f -exec sed -i 's/bash/dash/g' {} +
cd /etc
find . -type f -exec sed -i 's/bash/dash/g' {} +
Tip- Have some form of rescue disk as you never know when you will need to chroot/reinstall.
WARNING: some programs, packages, features, and who knows what else will be broken by this action.
Info: I operate as root, notice no "sudo", if you are uncomfortable with root, breaking your OS, or fixing "unsupported" quirks, then DO-NOT perform this action as I doubt you will find help or support.
Trouble: I haven't encountered any issues SO-FAR, but I will update this with Issues/Fixes.
The Be Operating System was build up from ground up without a shell. Linux can't seem and maybe doesn't really need to get along without a shell.
by dugan on Thu, 2015-02-26 18:47
I just read your howto, and it will probably last until the next time you install or upgrade anything with apt-get.
It's tremendously likely that it will leave a lot of stuff in a nonworking state too.
Quote:
Only if you are aware of the risks
How are you going to be aware of the risks if you don't even look at the list of files that you're changing?
Quote:
Originally Posted by jefro
The Be Operating System was build up from ground up without a shell. Linux can't seem and maybe doesn't really need to get along without a shell.
The howto is intended to replace bash with dash.
by veerain on Fri, 2015-02-27 00:45
Debian already has changed from bash to dash as much as possible.
Ubuntu follows debian.
I think it's a matter of distribution makers. Casual users must not attempt. Else there is chance of not functioning OS.
by dunne on Wed, 2015-03-04 14:52
I sym-linked /bin/sh to /bin/ksh (actually pdksh) years ago. The only thing that broke was ldd, which was easily fixed:
Code:
head -1 /usr/bin/ldd
#! /bin/bash
So it seems that Slackware (or slackware 11.0, at least) can live without bash -- ldd is useful but hardly essential. There are a few other scripts around which explicitly require bash i.e. they have a #!/bin/bash line, but nothing important.
by dugan on Wed, 2015-03-04 15:07
Quote:
Originally Posted by dunne
So it seems that Slackware (or slackware 11.0, at least) can live without bash -- ldd is useful but hardly essential. There are a few other scripts around which explicitly require bash i.e. they have a #!/bin/bash line, but nothing important.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
How to bork your system, click here!
How to remove all useful programs, ignore warnings and override safeties, click here!
They serve no purpose.
http://vignette1.wikia.nocookie.net/...ricityTest.jpg
The Be Operating System was build up from ground up without a shell. Linux can't seem and maybe doesn't really need to get along without a shell.
It's tremendously likely that it will leave a lot of stuff in a nonworking state too.
Ubuntu follows debian.
I think it's a matter of distribution makers. Casual users must not attempt. Else there is chance of not functioning OS.
I sym-linked /bin/sh to /bin/ksh (actually pdksh) years ago. The only thing that broke was ldd, which was easily fixed:
Bashism in /etc/rc.d/rc.S
but almost every "*.sh" script is pointing to "#!/bin/bash " or "#!/bin/sh "
have fun