Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 May 2001 23:43:06 +0300 (EEST)
From:      Maxim Sobolev <sobomax@mail-in.net>
To:        dima@unixfreak.org
Cc:        arch@FreeBSD.ORG
Subject:   Re: cvs commit: src/usr.sbin/kbdcontrol kbdcontrol.1 kbdcontrol.c
Message-ID:  <200105272043.f4RKgro04676@mail.uic-in.net>
In-Reply-To: <20010527185557.E96703E28@bazooka.unixfreak.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 27 May 2001 11:55:57 -0700, Dima Dorfman wrote:
> Maxim Sobolev <sobomax@mail-in.net> writes:
> > On Sat, 26 May 2001 17:47:38 -0700 (PDT), Dima Dorfman wrote:
> > > dd          2001/05/26 17:47:38 PDT
> > > 
> > >   Modified files:
> > >     usr.sbin/kbdcontrol  kbdcontrol.1 kbdcontrol.c 
> > >   Log:
> > >   Add a -c option which clears the history buffer using the new
> > >   CONS_CLRHIST ioctl.
> > 
> > Does it really belong to kbdcontrol(1)? For me it looks
> > counter-intuitive as this feature has nothing to do with
> > keyboard at all. IMO this (and `-h' BTW) option should be
> > moved into vidcontrol(1).
> 
> I agree, but please think of backwards compatibility.  -c is young
> enough that moving it to vidcontrol is no problem.  -h, however, is
> different; it's already in -stable, and has been there for a long
> time.  I suggest that we move both to vidcontrol, and have `kbdcontrol
> -h` print a "this option is now option -X in vidcontrol" or something
> similar.

I do not see a big problem here. `-h' option in kbdcontrol(1)
is not an option that used by luser very frequently. Just a entry
in appropriate relnotes could be sufficient IMO.

> I'll do the necessary work for this.

Des already done this work. Please see -arch archives.

> > This also would solve bootstrap issue.
> 
> Not quite.  It would just hide it until somebody adds an option to
> kbdcontrol which really does belong there.  The fact that we have a
> highly system-specific (i.e., depends on intricacies in the kernel)
> tool being used to bootstrap the system is still a problem.

Yes, I understand this. Actually I was talking about this
specific problem.

-Maxim

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105272043.f4RKgro04676>