On Tue, Jun 09, 2009 at 07:12:24PM +0200, Joerg Sonnenberger wrote:
> On Tue, Jun 09, 2009 at 10:37:29AM -0600, Theo de Raadt wrote:
> > The fact that you had to modify standards compliant code already in
> > the tree to make it work indicates a rather major problem.
>
> The changes for stdout / s
On Tue, Jun 09, 2009 at 10:37:29AM -0600, Theo de Raadt wrote:
> The fact that you had to modify standards compliant code already in
> the tree to make it work indicates a rather major problem.
The changes for stdout / stderr / stdin at least are valid,
the standard doesn't guarantee that they can
> FreeBSD tried this and reverted it. See the following thread
> for a discusion about it and various reasons for not doing it.
>
> http://www.mail-archive.com/cvs-...@freebsd.org/msg112466.html
No kidding.
The fact that you had to modify standards compliant code already in
the tree to make it w
FreeBSD tried this and reverted it. See the following thread
for a discusion about it and various reasons for not doing it.
http://www.mail-archive.com/cvs-...@freebsd.org/msg112466.html
On Tuesday 09 June 2009 2:22:51 am Paul Stoeber wrote:
> This is a recipe for bringing the system into a state
This is a recipe for bringing the system into a state where the
FILE type is opaque for libc users (unless they -D_EXPOSE__sFILE).
1. Apply the attached diff.
2. cd /usr/src/lib/libc && make && make install
3. Do step 3 of release(8).
After that transition, I changed "short _file
