lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADwDc1DXb3o0i-7NGZKFGwKU6Ybj703OHhUWgh0he9TcCFpW4g@mail.gmail.com>
Date:	Mon, 3 Sep 2012 14:24:21 -0700
From:	Joe Millenbach <jmillenbach@...il.com>
To:	"jirisl >> Jiri Slaby" <jirislaby@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Alan Cox <alan@...ux.intel.com>, linux-serial@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Josh Triplett <josh@...htriplett.org>,
	team-fjord@...glegroups.com
Subject: Re: [PATCHv2] tty: Added a CONFIG_TTY option to allow removal of TTY

On Mon, Sep 3, 2012 at 2:15 PM, Jiri Slaby <jslaby@...e.cz> wrote:
>
> On 09/03/2012 02:44 AM, Joe Millenbach wrote:
> > The option allows you to remove TTY and compile without errors. This
> > saves space on systems that won't support TTY interfaces anyway.
> > bloat-o-meter output is below.
> ...
> > --- a/drivers/tty/Kconfig
> > +++ b/drivers/tty/Kconfig
> > @@ -1,3 +1,14 @@
> > +config TTY
> > +     bool "Enable TTY" if EXPERT
> > +     default y
> > +     ---help---
> > +       Allows you to remove TTY support which can save space, and
> > +       blocks features that require TTY from inclusion in the kernel.
> > +       TTY is required for any text terminals or serial port
> > +       communication. Most users should leave this enabled.
> > +
> > +if TTY
> > +
> >  config VT
> >       bool "Virtual terminal" if EXPERT
> >       depends on !S390 && !UML
> > @@ -355,6 +366,8 @@ config TRACE_SINK
> >         If you select this option, you need to select
> >         "Trace data router for MIPI P1149.7 cJTAG standard".
> >
> > +endif # TTY
> > +
> >  config PPC_EPAPR_HV_BYTECHAN
> >       tristate "ePAPR hypervisor byte channel driver"
> >       depends on PPC
>
> Hmm, I wonder why do not you include EHV in the depends-on-tty list?
>
> thanks,
> --
> js
> suse labs

I do not have a Power PC system to test on, so during my testing I did
not notice that option would need TTY also.  Thanks for pointing that
out.  Before I spin a new patch is there anything else I should add?
I do not know of a way for me to easily test all the different CPU
specific configurations on my x86 based machines.

Joe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ