Re: rlogin terminal settings messed up

2001-08-06 Thread Mark Murray

 Does anyone know what changed?
 (someone has suggested the change came about when PAM's session model was
 changed)

Following up on my previous message; I've asked re@ for permission
to MFC the fix.

M
-- 
Mark Murray
Warning: this .sig is umop ap!sdn

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: rlogin terminal settings messed up

2001-08-06 Thread Mark Murray

 For quite a while now (?3-4 months?) one's terminal settings are messed
 up when rlogin'ing into a FreeBSD from a FreeBSD-current one.  It used to
 be I could rlogin from an 80x24 Xterm, and the terminal settings on the
 remote box would also be 80x24.  Now COLUMNS=80 and ROWS and TERMCAP
 isn't set, so a very large number is assumed.
 
 Does anyone know what changed?

Hmm. rlogind(8) on STABLE and CURRENT is effectively identical, and
the bug does not show on a CURRENT-CURRENT rlogin session.

 (someone has suggested the change came about when PAM's session model was
 changed)

Hmm. Maybe I need to MFC login(1) some more. Please try that, and if it
works, lets get it committed.

STABLE's PAM modules and support are quite a bit behind CURRENT's.

What are your /etc/pam.conf entries for login? See if borrowing
any CURRENT entries helps you.

M
-- 
Mark Murray
Warning: this .sig is umop ap!sdn

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: rlogin terminal settings messed up

2001-08-06 Thread David O'Brien

On Mon, Aug 06, 2001 at 12:32:49PM +0100, Mark Murray wrote:
  For quite a while now (?3-4 months?) one's terminal settings are messed
  up when rlogin'ing into a FreeBSD from a FreeBSD-current one.  It used to
  be I could rlogin from an 80x24 Xterm, and the terminal settings on the
  remote box would also be 80x24.  Now COLUMNS=80 and ROWS and TERMCAP
  isn't set, so a very large number is assumed.
  
  Does anyone know what changed?
 
 Hmm. rlogind(8) on STABLE and CURRENT is effectively identical, and
 the bug does not show on a CURRENT-CURRENT rlogin session.

It does for me.  CURRENT-CURRENT or CURRENT-STABLE.

-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



rlogin terminal settings messed up

2001-08-05 Thread David O'Brien

For quite a while now (?3-4 months?) one's terminal settings are messed
up when rlogin'ing into a FreeBSD from a FreeBSD-current one.  It used to
be I could rlogin from an 80x24 Xterm, and the terminal settings on the
remote box would also be 80x24.  Now COLUMNS=80 and ROWS and TERMCAP
isn't set, so a very large number is assumed.

Does anyone know what changed?
(someone has suggested the change came about when PAM's session model was
changed)

-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message