-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Hannah Schroeter wrote:
Hi!
On Wed, May 10, 2006 at 04:17:11PM +0200, Marian Hettwer wrote:
Even if you use the bash-static package, bash gets installed into
/usr/local/bin (IIRC) and you may not have /usr while being in single
user
On Wed, May 10, 2006 at 12:40:28PM +0700, Tito Mari Francis Esca?o wrote:
| I got me a 3.8 box as gateway with bash as root's default shell. The
| pf logs filled up the /var partition and bash complained about not
| being able to load libiconv which I believe is a dependency of bash.
| With the
reboot in single mode (boot -s)
manually mount your partitions and delete unneeded trash :)
Tito Mari Francis Escaqo wrote:
I got me a 3.8 box as gateway with bash as root's default shell. The
pf logs filled up the /var partition and bash complained about not
being able to load libiconv which I
Paul de Weerd wrote:
Don't change root's shell.
It's set to a static shell (/bin/ksh these days) for a reason.
Changing the root shell doesn't hurt. But you have to install your shell
static. I use the bash-static from packages, and hadn't any problems. I
think that booting in single and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Giancarlo Razzolini wrote:
Paul de Weerd wrote:
Don't change root's shell.
It's set to a static shell (/bin/ksh these days) for a reason.
Changing the root shell doesn't hurt. But you have to install your shell
There is
Hi!
On Wed, May 10, 2006 at 04:17:11PM +0200, Marian Hettwer wrote:
[...]
Changing the root shell doesn't hurt. But you have to install your shell
There is absolutely no reason to change root's shell.
There is even no reason at all to work as root.
Use sudo, or even su -m, or execute bash after
On Wed, May 10, 2006 at 10:50:14AM -0300, Giancarlo Razzolini wrote:
Paul de Weerd wrote:
Don't change root's shell.
It's set to a static shell (/bin/ksh these days) for a reason.
Changing the root shell doesn't hurt. But you have to install your shell
static. I use the
On 5/10/06, Giancarlo Razzolini [EMAIL PROTECTED] wrote:
Paul de Weerd wrote:
Don't change root's shell.
It's set to a static shell (/bin/ksh these days) for a reason.
Changing the root shell doesn't hurt. But you have to install your shell
static. I use the bash-static from packages, and
Greg Thomas wrote:
On 5/10/06, Giancarlo Razzolini [EMAIL PROTECTED] wrote:
Paul de Weerd wrote:
Don't change root's shell.
It's set to a static shell (/bin/ksh these days) for a reason.
Changing the root shell doesn't hurt. But you have to install your shell
static. I use the
Daniel Ouellet wrote:
As good example to help understand this in practice is just like this.
You install your package bash-static, you think you are clever, fine.
Then time pass, you work with someone else, a new release come out, you
need to upgrade that box, but it happen to be remote. You
the shell, but might break. Further more, all my upgrades are done
locally. I do not have the luxury of having a remote serial console with
those nasty pci cards that can put even the BIOS to go through the
serial. I can live with it. Will not recommend people anymore to change
Who said you
Tobias Ulmer wrote:
On Wed, May 10, 2006 at 10:50:14AM -0300, Giancarlo Razzolini wrote:
Paul de Weerd wrote:
Don't change root's shell.
It's set to a static shell (/bin/ksh these days) for a reason.
Changing the root shell doesn't hurt. But you have to install your shell
static. I use
I got me a 3.8 box as gateway with bash as root's default shell. The
pf logs filled up the /var partition and bash complained about not
being able to load libiconv which I believe is a dependency of bash.
With the failure of loading libiconv, I can't login on the gateway box
and I can't login
13 matches
Mail list logo
