In article <4f8f8d6d$0$16115$>,
Kevin McMurtrie <> wrote:
> In article <jollyroger->,
> Jolly Roger <> wrote:
>
> > In article <4f8ee410$0$16194$>,
> > Kevin McMurtrie <> wrote:
> >
> > > In article <jollyroger->,
> > > Jolly Roger <> wrote:
> > >
> > > > In article <2012041815001482727-info@stconinccom>,
> > > > Torsten Jørgensen <> wrote:
> > > >
> > > > > I did it with a Tiger, but Lion does not have NetInfo,
> > > > > so what then?
> > > > >
> > > > > Can you become root user on a Lion at all?
> > > > >
> > > > > /Torsten
> > > >
> > > > I have to ask: Why bother?
> > >
> > > I can think of a couple cases quickly.
> > >
> > > It can be useful for machines that have a simple task to perform and
> > > only one administrator. In such a case, the complexity of multiple user
> > > roles can be more of a risk than an asset. Unix ACLs are error prone
> > > and Apple's poorly supported ACL on top of that is an absolute nightmare
> > > to keep correct.
> > >
> > > Server consoles commonly have a root login for emergency maintenance
> > > without having to use single-user mode. (Remote root access can be
> > > disabled.)
> >
> > Explain how enabling the root user account would be preferable to using
> > the sudo facility which is already at your disposal.
>
> You wouldn't be at the console running emergency maintenance if sudo on
> a remote terminal worked. The biggest difference is that the root user
> has a small amount of spare resources reserved for it. A resource leak
> (files, memory, processes, sockets, etc.) will lock out an admin but not
> root.
I can't recall the last time I saw a unix system administrator permit
remote login to the root. Doing so provides no accountability.
Responsible administrators require an ordinary user login followed by
either a 'su' to switch to the root account or 'sudo' for one-time
privilege escalation.
--
PRAY, v. To ask that the laws of the universe be annulled in behalf
of a single petitioner confessedly unworthy. -- Ambrose Bierce
|