From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ideas for helpful system io functions
Date: Tue, 5 Jan 2010 14:48:06 +0100 [thread overview]
Message-ID: <20100105134806.GD21460@nibiru.local> (raw)
In-Reply-To: <Pine.BSI.4.64.0912050822560.13404@malasada.lava.net>
* Tim Newsham <newsham@lava.net> wrote:
> ps. if you wanted to hide this ugliness of passing a buffer and
> fd to a child process instead of just passing an fd, you could
> still solve it in userland without a syscall. Write a library
> that does buffered IO. Include unget() if you like. Write the
> library in a way that you can initialize it after a fork/exec
> to pick up state from the parent (ie. by taking two fds,
> reading the buffer from the first, and continuing on with the
> 2nd when it is exhausted).
Not sure how things work on Plan9, but on GNU/Linux you could
even use LD_PRELOAD to overlay the read() libc function to
hide that magic, or even tweak libc for that.
BTW: how to do you in general think about having tweaked libc's
instead of all these "cross-platform libraries" ? For example,
I'm thinking about whether it's worth to change uclibc in a way
that it allows to plug-in userland-vfs'es.
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 174 7066481 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next prev parent reply other threads:[~2010-01-05 13:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 3:17 Sam Watkins
2009-12-05 3:36 ` Lyndon Nerenberg
2009-12-05 3:56 ` Sam Watkins
2009-12-05 4:03 ` Lyndon Nerenberg
2009-12-05 18:16 ` Tim Newsham
2009-12-05 18:24 ` Tim Newsham
2009-12-05 19:47 ` Bakul Shah
2009-12-07 12:24 ` roger peppe
2009-12-07 12:32 ` Charles Forsyth
2009-12-07 12:35 ` Francisco J Ballesteros
2009-12-07 13:42 ` Charles Forsyth
2009-12-07 16:10 ` erik quanstrom
2009-12-07 16:14 ` Francisco J Ballesteros
2009-12-07 14:13 ` Sam Watkins
2009-12-07 14:36 ` roger peppe
2009-12-07 19:11 ` Nathaniel W Filardo
2009-12-07 21:03 ` roger peppe
2009-12-08 12:51 ` matt
2009-12-07 12:06 ` Mechiel Lukkien
2009-12-07 12:31 ` roger peppe
2010-01-05 13:48 ` Enrico Weigelt [this message]
2010-01-05 15:53 ` Steve Simon
[not found] <<alpine.BSF.2.00.0912042029370.66255@legolas.yyc.orthanc.ca>
2009-12-05 4:47 ` erik quanstrom
2009-12-05 5:09 ` Lyndon Nerenberg
2009-12-05 5:11 ` Lyndon Nerenberg
2009-12-05 8:10 ` Sam Watkins
2009-12-05 11:44 ` Francisco J Ballesteros
2009-12-05 16:32 ` ron minnich
2009-12-05 17:01 ` Francisco J Ballesteros
2009-12-05 17:09 ` ron minnich
[not found] <<alpine.BSF.2.00.0912042210290.81688@legolas.yyc.orthanc.ca>
2009-12-05 13:26 ` erik quanstrom
2009-12-05 14:22 ` Sam Watkins
2009-12-05 17:47 ` Skip Tavakkolian
2009-12-05 17:56 ` Skip Tavakkolian
[not found] <<20091205081032.GJ8759@nipl.net>
2009-12-05 13:51 ` erik quanstrom
[not found] <<20091205194741.0697D5B76@mail.bitblocks.com>
2009-12-05 20:03 ` erik quanstrom
2009-12-05 20:24 ` Bakul Shah
[not found] <<20091205202420.855AD5B77@mail.bitblocks.com>
2009-12-05 20:27 ` erik quanstrom
2009-12-05 20:59 ` Bakul Shah
2009-12-06 7:45 ` Sam Watkins
2009-12-05 20:30 ` erik quanstrom
[not found] <<20091207120652.GB16320@knaagkever.ueber.net>
2009-12-07 12:19 ` erik quanstrom
2009-12-07 14:41 Francisco J Ballesteros
2009-12-07 15:11 ` roger peppe
[not found] <<8ccc8ba40912070814o2f2c7eb9s5887a31810eab12e@mail.gmail.com>
2009-12-07 16:24 ` erik quanstrom
2009-12-07 16:48 ` Francisco J Ballesteros
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=20100105134806.GD21460@nibiru.local \
--to=weigelt@metux.de \
--cc=9fans@9fans.net \
/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).