From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: udevinfo output broken
Date: Tue, 27 Jan 2004 20:06:51 +0000 [thread overview]
Message-ID: <20040127200651.GA7974@suse.de> (raw)
udevinfo writes to fd 0, all the output is lost somehow.
olaf@ibook:~> /sbin/udevinfo -r
/dev/
olaf@ibook:~> i="`/sbin/udevinfo -r`"
/dev/
olaf@ibook:~> echo $i
olaf@ibook:~> i="`/sbin/udevinfo -r 2>&1`"
/dev/
olaf@ibook:~> echo $i
olaf@ibook:~>
--
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 reply other threads:[~2004-01-27 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 20:06 Olaf Hering [this message]
2004-01-27 21:12 ` udevinfo output broken Kay Sievers
2004-01-27 21:19 ` Olaf Hering
2004-01-27 21:54 ` Olaf Hering
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=20040127200651.GA7974@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).