root's shell (Was: Re: boot banner project)
From: Andre Guibert de Bruet (andy_at_siliconlandmark.com)
Date: Sun, 8 May 2005 04:17:04 -0400 (EDT) To: Wilko Bulte <firstname.lastname@example.org>
On Sun, 8 May 2005, Wilko Bulte wrote:
> On Sun, May 08, 2005 at 09:57:14AM +0200, Michael Nottebrock wrote..
>> On Sunday, 8. May 2005 09:34, Wilko Bulte wrote:
>>> On Sun, May 08, 2005 at 04:25:20AM +0200, Michael Nottebrock wrote..
>>>> On Thursday, 5. May 2005 04:16, Charles Swiger wrote:
>>>>> Data point: I've been running /bin/sh as root's shell on a bunch of
>>>>> machines with zero issues since 4.0.
>>>> You got lucky then, because there's some actual footshooting potential in
>>>> doing that. Use toor.
>>> Interesting, I have been running /bin/sh since 1.0R (yes..) for root
>>> and it never bit me. Where is that footshooting potential?
>> Sorry, I just scanned the thread before replying - there's probably no
>> footshooting potential in using /bin/sh for root.
>> I was thinking about using (/usr/local/bin/)bash for root, something a lot of
>> people try to do (until they notice a toe missing :).
I don't like the thought of root's login shell being anywhere but on the
root partition. You're absolutely correct though (Single user mode prompts
for the shell to use).
At this point, this thread would probably be more ontopic on the misc
mailing list. Additionally, I think that everyone's time would be better
invested testing 5.4-RC4, looking at PR's or driver locking.
/* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */
/* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */
/* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */
/* WWW: siliconlandmark.com * Tormenting bytes since 1980. */
email@example.com mailing list
To unsubscribe, send any mail to "firstname.lastname@example.org"