From: Bryce Porter <x86@advancenet.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Tom's /proc idea
Date: Sat Jan 20 16:53:01 2001 [thread overview]
Message-ID: <Pine.LNX.4.21.0101201751450.21109-100000@x86.dyn.cheapnet.net> (raw)
In-Reply-To: <20010120190101.EA68148BB5@cvs.gentoo.org>
Hello,
I am very interested in what Tom said about /proc and portage. I think if
we created a daemon that makes a socket on /proc it would be both
efficient and secure, while still being lightweight.
I think its an excellent idea.
Get back to me.
--
<=------------------------=>
Bryce Porter
bporter@advancenet.net
bporter33@usa.net
ICQ: 27282017
<=------------------------=>
parent reply other threads:[~2001-01-20 23:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20010120190101.EA68148BB5@cvs.gentoo.org>]
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=Pine.LNX.4.21.0101201751450.21109-100000@x86.dyn.cheapnet.net \
--to=x86@advancenet.net \
--cc=gentoo-dev@gentoo.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