unsubscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 29 Jul 2001, Matthew Jacob wrote:
> 'truss clear |& tee /tmp/x'?
ok, I figured out the clear issue...I didn't have entries in termcap for
the QNX terminals (of course, not know that QNX used odd terminal names,
...). I'm still wondering, though, if there is such a thing as lost+found
in
Okay, had a storm here and power went out and fizzed a little, going
between on and off, until it finally shut off. Now, this is the first
time that I've actually had something like this happen, and have bad
things happen after fbsd rebooted.
First off, is there such a thing as lost+found? Also
On Fri, 27 Jul 2001 [EMAIL PROTECTED] wrote:
> either of the following works. the other configurations are now
> considered ambiguous. (the point is, if you specify prefixlen < 128
> you don't need to say the peer's address)
>
> # ifconfig inet6 A prefixlen X (X can be
When I compiled/installed -current, and started setting things up again, I
noticed that gif devices now expect IPv6 prefix lengths of 128. Most
providers use 127, and some even use 64 as prefix lengths for tunnels. I
was just curious why the change was made to only support prefix lengths of
128.
> So you have the line,
>
> sshdsession requiredpam_permit.so
Yep. In pam.conf, regarding ssh I have the following lines:
sshdauthrequiredpam_nologin.so
sshdauthrequiredpam_unix.so try_first_pass
sshdaccount requiredpam_unix.so
sshd
Not sure if this is actually freebsd-current ralated, but when I was last
in 4.3-release, I do recall having used rsa authentication correctly, and
I can't find info anywhere else.
When I try to log into ssh (from anyway, even locally) using my rsa key,
it opens the session, and then immediately
