From: Eric Wong <normalperson@yhbt.net>
To: raindrops@librelist.org
Subject: unix_diag in upcoming Linux 3.3 kernel
Date: Thu, 1 Mar 2012 02:37:51 +0000 [thread overview]
Message-ID: <20120301023751.GA22900@dcvr.yhbt.net> (raw)
In-Reply-To: <20120301023751.GA22900@dcvr.yhbt.net>
Hi all, I noticed this building a release candidate the other
day. It looks like we won't have to parse /proc/net/unix
on new systems.
It'd be much appreciated if anybody has some free cycles to look at it
and add support for it to Raindrops. We'll probably still have to
support parsing /proc/net/unix for another ~5-10 years since the rest of
the world takes a while to catch up.
We should even try to fall back on EINVAL/ENOSYS in the case raindrops
is compiled on a new machine and run on an old one (unfortunate, but i
happens, I've had to deal with for accept4() in kgio :<).
parent reply other threads:[~2012-03-01 2:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20120301023751.GA22900@dcvr.yhbt.net>]
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
List information: https://yhbt.net/raindrops/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120301023751.GA22900@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=raindrops@librelist.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/raindrops.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).