On Sat, Sep 22, 2001 at 22:42:43 +0400, Andrey A. Chernov wrote:
> On Sat, Sep 22, 2001 at 13:53:02 -0400, Robert Watson wrote:
> > is at best unhelpful, and more likely quite harmful. It was verified by a
> > number of FreeBSD developers on many of past releases, and on 4.4-RC, as
> > well as FreeBSD 5.0-CURRENT. The patch was tested on many of those
> I test in on my current -current changing "copyright" and "welcome" to
> various values and using "default" and "standard" and "me" but can't
> reproduce this bug. Please tell me EXACT how you test in in -current.
> To be double sure, you can check out very recent -current libutil and try
> it temporary moving your libutil out of the way.
> Could anybody else confirm this bug persent on very recent -current or not
Sorry for all that buzz, I am finally able to reproduce it on -current.
I can't do it previously simple because I don't have empty login class
field in /etc/passwd. This happens only with empty class field in passwd
and "default" class in ~/.login_conf. This is NOT the way LOGIN_CAP
supposed to work. It supposed to work as I describe in previous messages.
I'll work on the proper fix tomorrow.
Andrey A. Chernov
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message