On Tue, Oct 31, 2000 at 08:58:19PM -0500, Brenda J. Butler wrote:
>
> Also, if you have split out your filesystem such that /usr/anything
> is mounted, then in the event of a system crash your /usr/lib dynamic
> libraries may not be available if those filesystems refuse to mount.
> This is a compe
On Tue, Oct 31, 2000 at 04:59:30PM -0600, Bud Rogers wrote:
> On Tue, 31 Oct 2000, Sean 'Shaleh' Perry wrote:
> > bin (whether bin or sbin) is more correctly name "executable". If you look
> > in /usr/bin or /usr/sbin you will find sh, perl, awk, python, etc scripts.
> >
> > If it is a system main
In article <[EMAIL PROTECTED]>,
William T Wilson <[EMAIL PROTECTED]> wrote:
>I also question the historical accuracy of 'sbin' as "static binary" -
>Unix has always had /sbin, but it hasn't always had dynamic linking.
How soon they forget. Not all Unices have always had /sbin. Not even Linux.
In
On Tue, 31 Oct 2000, Bud Rogers wrote:
> I think it could be argued that those changes are not necessarily good
> from the standpoint of system security.
In the modern world, sbin really does mean "system" binaries. The
division between "things you need to fix a crashed system" and "things for
o
On Tue, 31 Oct 2000, Sean 'Shaleh' Perry wrote:
> > Current practice seems to have strayed a bit from the concept of only
> > having statically linked binaries in the sbin directories. You may find
> > shell scripts, perl, python, all kinds of stuff. I think these days a
> > lot of people tend to
>
> Current practice seems to have strayed a bit from the concept of only having
> statically linked binaries in the sbin directories. You may find shell
> scripts, perl, python, all kinds of stuff. I think these days a lot of
> people tend to think the 's' stands for system or sysadmin or so
On Tue, 31 Oct 2000, Sean 'Shaleh' Perry wrote:
> On 31-Oct-2000 Krzys Majewski wrote:
> > I have a habit of writing many shell scripts for everything. Some of
> > them are very local to me, so I put them in ${HOME}/shell and stick
> > that in my PATH. Some of them may be generally useful, s
Krzys Majewski wrote:
>
> I have a habit of writing many shell scripts for everything. Some of
> them are very local to me, so I put them in ${HOME}/shell and stick
> that in my PATH.
Makes sense.
> Some of them may be generally useful, so although I
> don't have any users, I'm anal, a
On 31-Oct-2000 Krzys Majewski wrote:
> I have a habit of writing many shell scripts for everything. Some of
> them are very local to me, so I put them in ${HOME}/shell and stick
> that in my PATH. Some of them may be generally useful, so although I
> don't have any users, I'm anal, and I p
I have a habit of writing many shell scripts for everything. Some of
them are very local to me, so I put them in ${HOME}/shell and stick
that in my PATH. Some of them may be generally useful, so although I
don't have any users, I'm anal, and I put them in /usr/local/sbin/. I
don't know wha
10 matches
Mail list logo
