From: Tim Writer <Tim.Writer@ftlsol.com>
To: Marc Baudoin <Marc.Baudoin@solsoft.com>
Cc: Bruce Stephens <B.Stephens@isode.com>, zsh-users@math.gatech.edu
Subject: Re: zsh as root login
Date: 28 Aug 1997 22:17:24 -0400 [thread overview]
Message-ID: <m3afi1wx57.fsf@snoopy.ftlsol.com> (raw)
In-Reply-To: Marc Baudoin's message of Thu, 28 Aug 1997 09:15:34 +0200
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]
Marc Baudoin <Marc.Baudoin@solsoft.com> writes:
> Tim Writer <Tim.Writer@ftlsol.com> écrit :
> >
> > Agreed. But I'm curious as to why you (Marc Baudoin) even want zsh
> > statically linked.
>
> Just to be able to log in as root while my computer in booted
> single user, as only / is mounted and root's shell is zsh.
How often are you running single user? If the system is so badly hosed that
you can't get it to go multi-user, having zsh doesn't help much.
> > I prefer to keep root dead simple, using /bin/sh without evan a
> > .profile.
>
> Why? When you're logged as root, you also use ed instead of vi
> to keep it simple? :-)
ed? I use cat. :-)
But seriously, you didn't read what I said. I keep "root" simple for
emergencies. That is, to make sure I can login in an emergency. I have a
pretty fancy set of zsh startup scripts and I don't want a stupid mistake or
an oversite to shut me out of root. An alternate root account with a
different login name and zsh gives me the best of both worlds: safety and
functionality.
> As I manage a lot of machines remotely, I like to have a good
> shell for root (who still uses sh without beeing bothered?) and I
> don't want to have many uid 0 accounts. So root's shell is zsh
> and it needs to be static so I can log in where I'm in front of
> the computer and it's booted single user.
I manage a lot of machines remotely too and I also like having a good shell.
But, I don't mind an extra root account.
However, my main point was: you can have it exactly the way you want it with
a three line script. Trying to make configure be all things to all people
seems unwise.
Tim
--
Tim Writer Tim.Writer@ftlsol.com
FTL Solutions Inc.
Toronto, Ontario, CANADA
next prev parent reply other threads:[~1997-08-29 2:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-27 9:40 Marc Baudoin
1997-08-27 9:59 ` Andrew Main
1997-08-27 10:02 ` Marc Baudoin
1997-08-27 10:09 ` Andrew Main
1997-08-27 10:15 ` Marc Baudoin
1997-08-27 12:51 ` Juergen Christoffel
1997-08-27 12:55 ` Marc Baudoin
1997-08-27 12:58 ` Andrew Main
1997-08-27 10:44 ` Bruce Stephens
1997-08-27 23:20 ` Tim Writer
1997-08-28 1:58 ` Jason R Mastaler
1997-08-28 7:15 ` Marc Baudoin
1997-08-29 2:17 ` Tim Writer [this message]
1997-08-29 5:40 ` Duncan Sargeant
[not found] <5lu3gbh6vp.fsf@tequila.systemsz.cs.yale.edu>
1997-08-28 6:16 ` Geoff Wing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3afi1wx57.fsf@snoopy.ftlsol.com \
--to=tim.writer@ftlsol.com \
--cc=B.Stephens@isode.com \
--cc=Marc.Baudoin@solsoft.com \
--cc=zsh-users@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).