From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevinfo output broken
Date: Tue, 27 Jan 2004 21:54:31 +0000 [thread overview]
Message-ID: <20040127215431.GA11951@suse.de> (raw)
In-Reply-To: <20040127200651.GA7974@suse.de>
On Tue, Jan 27, Olaf Hering wrote:
> On Tue, Jan 27, Kay Sievers wrote:
>
> > On Tue, Jan 27, 2004 at 09:06:51PM +0100, Olaf Hering wrote:
> > > udevinfo writes to fd 0, all the output is lost somehow.
> > >
> > > olaf@ibook:~> i="`/sbin/udevinfo -r 2>&1`"
> > > /dev/
> >
> > Seems like a klibc feature :)
> > libc works as expected.
>
> _fwrite gets 0x1 as f, calls fileno() which decrements it and passes it
> to write().
No idea if this is correct:
--- klibc-0.98/klibc/include/stdio.h 2004-01-22 21:56:49.000000000 +0100
+++ klibc/klibc/include/stdio.h 2004-01-27 22:50:27.000000000 +0100
@@ -15,9 +15,9 @@
struct _IO_file;
typedef struct _IO_file FILE;
-#define stdin ((FILE *)0)
-#define stdout ((FILE *)1)
-#define stderr ((FILE *)2)
+#define stdin ((FILE *)1)
+#define stdout ((FILE *)2)
+#define stderr ((FILE *)3)
#ifndef EOF
# define EOF (-1)
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-27 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 20:06 udevinfo output broken Olaf Hering
2004-01-27 21:12 ` Kay Sievers
2004-01-27 21:19 ` Olaf Hering
2004-01-27 21:54 ` Olaf Hering [this message]
2004-01-27 22:05 ` Greg KH
2004-01-28 0:39 ` [klibc] " H. Peter Anvin
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=20040127215431.GA11951@suse.de \
--to=olh@suse.de \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).