According to Bjoern Groenvall:
> While you are moving things around you might as well move
> /usr/sbin/sshd to /usr/libexec/sshd where it should have
> resided in the first place.
I disagree. sshd is like named or moused, a daemon running standalone and
not under inetd's control. Most of /usr/lib
> No, that would be contrary to the conventions documented in hier(4).
> /usr/libexec is for things that are executed by other programs.
> Normal persistent daemons such as sshd belong in /usr/sbin. Take a
> look at the current contents of those two directories and you'll see
> the distinction.
In article <[EMAIL PROTECTED]>, Bjoern Groenvall <[EMAIL PROTECTED]> wrote:
>
> While you are moving things around you might as well move
> /usr/sbin/sshd to /usr/libexec/sshd where it should have
> resided in the first place.
No, that would be contrary to the conventions documented in hier(4).
Kris Kennaway <[EMAIL PROTECTED]> writes:
> On Fri, 25 Feb 2000, Ollivier Robert wrote:
>
> > I just saw that openssh (thanks Mark!) is using /etc/ for its configuration
> > file. As the author of the "--with-etcdir" option of SSH (back in '96) and
> > for the sake of consistency, I'd like to cr
Crypto/ is just a storage location for the for files. They are
committed there just like files are in contrib. Buildworld never
explicitly goes into either of these directories; the files stored there
are referenced by makefiles in other parts of the tree. For example,
look at the directory src
According to Kris Kennaway:
> crypto/ is the analogue of contrib/ for crypto code. You're not supposed
> to build there..look under secure/.
I was confused :)
"buildworld" is now running on the two machines here...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBS
According to Garance A Drosihn:
> hostkey. Having all those files inside one directory makes that easy.
Peter has committed the diff, thanks Peter!
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999
On Fri, 25 Feb 2000, Ollivier Robert wrote:
> I just saw that openssh (thanks Mark!) is using /etc/ for its configuration
> file. As the author of the "--with-etcdir" option of SSH (back in '96) and
> for the sake of consistency, I'd like to create a /etc/ssh directory and
> move everything there
At 1:51 PM +0100 2/25/00, Ollivier Robert wrote:
>I just saw that openssh (thanks Mark!) is using /etc/ for its configuration
>file. As the author of the "--with-etcdir" option of SSH (back in '96) and
>for the sake of consistency, I'd like to create a /etc/ssh directory and
>move everything there
I'm not suprised to here this. The Makefiles in that directory are from
OpenBSD's version of openssh. If you want to build ssh manually, you
will need to build parts of /usr/src/secure/{lib,user.sbin,usr.bin} and
/usr/src/lib/libpam. The makefiles are for reference only.
Jim Bloom
[EMAIL PROTE
In message <[EMAIL PROTECTED]>, Ollivier Robert write
s:
>I just saw that openssh (thanks Mark!) is using /etc/ for its configuration
>file. As the author of the "--with-etcdir" option of SSH (back in '96) and
>for the sake of consistency, I'd like to create a /etc/ssh directory and
>move everythi
I just saw that openssh (thanks Mark!) is using /etc/ for its configuration
file. As the author of the "--with-etcdir" option of SSH (back in '96) and
for the sake of consistency, I'd like to create a /etc/ssh directory and
move everything there.
We have /etc/ssl, /etc/mail, /etc/ppp, /etc/uucp a
12 matches
Mail list logo
