public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nuitari <nuitari@melchior.nuitari.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Re: x86_64 optimization patches for glibc.
Date: Sun, 31 Jul 2005 14:52:03 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.63.0507311451250.2316@melchior.nuitari.net> (raw)
In-Reply-To: <e16d914c0507311146579d90e9@mail.gmail.com>

Same here for the USE flags.

I'm also starting to get used to these kinds of problems with mod_php & 
apache.

On Sun, 31 Jul 2005, Jared Lindsay wrote:

> Date: Sun, 31 Jul 2005 11:46:59 -0700
> From: Jared Lindsay <cinder.sub@gmail.com>
> Reply-To: gentoo-amd64@lists.gentoo.org
> To: gentoo-amd64@lists.gentoo.org
> Subject: Re: [gentoo-amd64] Re: Re: x86_64 optimization patches for glibc.
> 
> Yeah, netcat, hehe.
>
> emerge -pv netcat
> ...
> [ebuild  N    ] net-analyzer/netcat
> [110-r8]                       -GAPING_SECURITY_HOLE +crypt -ipv6
> -static 107 kB
>
> I would be interested in a USE flag for this glibc patch.
>
> On 7/31/05, Ben Skeggs <darktama@iinet.net.au> wrote:
>> Duncan wrote:
>>
>>> Brian Hall posted <20050731085600.65fc8657.brihall@pcisys.net>, excerpted
>>> below,  on Sun, 31 Jul 2005 08:56:00 -0600:
>>>
>>>
>>>
>>>> Perhaps a USE flag could be created to enable the glibc patches, then a
>>>> emerge --newuse could recompile glibc and the problem apps (or
>>>> everything); maybe a mini-howto document would also be helpful.
>>>>
>>>> I would certainly like an easy way to enable any "free" performance
>>>> boost I can get!
>>>>
>>>>
>>>
>>> Something like USE=dangerous-amd64-hack? <g>
>>>
>>> (Seriously, there at least used to be a local use flag
>>> USE=frickin-big-security-hole, or some such, on some app I can't remember
>>> at the moment.  Turns out a teacher was using that app in his class as a
>>> an example or something, so the dev left the ability to create it there,
>>> but with a USE flag nobody in their right mind would normally enable.  I
>>> wish I could remember what it was, but grepping use.local.desc for
>>> anything that might be related doesn't seem to bring it up.  Perhaps the
>>> app, or anyway the USE flag, has now been removed from portage?)
>>>
>>> The use.local.desc description could point to the bug, which is IIRC what
>>> the one above did, for those wanting more information about just why such
>>> a USE flag exists, and just why someone might be persuaded to enable it.
>>>
>>>
>>>
>> Are you talking about GAPING_SECURITY_HOLE?  If so, this flag is still
>> in use by the net-analyzer/netcat package.  It enables the "-E" (iirc)
>> switch
>> which allows you to do something like:
>>        nc -l -p 12345 -E /bin/bash
>>
>> This(or something close to it) would cause netcat to listen on port 12345,
>> and forward the person who connects to it a nice bash shell.
>>
>> Ben.
>> --
>> gentoo-amd64@gentoo.org mailing list
>>
>>
>
>
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-07-31 18:51 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-23 14:48 [gentoo-amd64] x86_64 optimization patches for glibc Simon Strandman
2005-07-23 16:36 ` Allan Wang
2005-07-23 17:08   ` Simon Strandman
2005-07-23 17:30     ` Allan Wang
2005-07-23 18:11       ` Jared Lindsay
2005-07-23 18:19         ` Allan Wang
2005-07-27 10:09     ` netpython
2005-07-27 16:11       ` [gentoo-amd64] " Duncan
2005-07-23 18:44   ` [gentoo-amd64] " Brian Litzinger
2005-07-25 22:24     ` Luke-Jr
2005-07-25 22:38       ` Olivier Crete
2005-07-26 15:40         ` Luke-Jr
2005-07-26 16:50           ` [gentoo-amd64] " Duncan
2005-07-26 17:02             ` Raffaele BELARDI
2005-07-26 17:49               ` Michael Edwards
2005-07-26 18:42                 ` [gentoo-amd64] " Duncan
2005-07-27  0:05             ` [gentoo-amd64] " Sami Samhuri
2005-07-27  2:50             ` Matt Randolph
2005-07-26  2:54       ` [gentoo-amd64] " Brian Litzinger
2005-07-23 16:39 ` Sean Johnson
2005-07-23 22:15 ` Matt Randolph
2005-07-23 22:36   ` Matt Randolph
2005-07-24  1:47     ` Sean Johnson
2005-07-24  3:36       ` Matt Randolph
2005-07-24  5:36         ` Ian McCulloch
2005-07-24  7:42           ` Jared Lindsay
2005-07-24 14:35             ` Simon Strandman
2005-07-24 18:13               ` Jared Lindsay
2005-07-25 20:08 ` Jeremy Huddleston
2005-07-25 21:34   ` Simon Strandman
2005-07-25 22:00     ` Jared Lindsay
2005-07-31 14:24     ` [gentoo-amd64] " Duncan
2005-07-31 14:56       ` Brian Hall
2005-07-31 16:23         ` [gentoo-amd64] " Duncan
2005-07-31 17:42           ` Ben Skeggs
2005-07-31 18:46             ` Jared Lindsay
2005-07-31 18:52               ` Nuitari [this message]
2005-08-01 13:51             ` [gentoo-amd64] " Duncan
2005-07-31 19:21       ` [gentoo-amd64] " Simon Strandman
2005-08-01  9:04       ` Jan Jitse Venselaar
2005-08-01 13:45         ` [gentoo-amd64] " Duncan
2005-08-01 17:03           ` Karol Krizka
2005-08-02 10:21             ` [gentoo-amd64] " Duncan
2005-08-02 19:41               ` Matt Randolph
2005-08-02 23:27                 ` [gentoo-amd64] hijacked! :) television (was: x86_64 optimization patches for glibc.) Sami Samhuri
2005-08-04  2:28                   ` Luke-Jr
2005-08-05  0:28                     ` Sami Samhuri
2005-08-05  7:43                       ` Arm Suwarnaratana
2005-08-09 10:29         ` [gentoo-amd64] Re: x86_64 optimization patches for glibc Simon Strandman
2005-07-26 17:40 ` [gentoo-amd64] " ardour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0507311451250.2316@melchior.nuitari.net \
    --to=nuitari@melchior.nuitari.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox