From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] /proc and portage
Date: Sat Jan 20 13:19:01 2001 [thread overview]
Message-ID: <3A69EC25.3D9072F2@gottinger.de> (raw)
In-Reply-To: 20010119094715.B17728@tsuny.ctn.cogs.susx.ac.uk
Thomas Flavel wrote:
> Hi,
>
> I had an idea I dimsmissed which I thought I should post anyway, on the off chance that it
> might actually get used ;)
>
> I was thinking about how /proc is sometimes used as a bi-directional interface, for example I
> can "echo 1>/proc/whatever" to turn on ping flood protection or something similar. I was
> wondering how practical it would be to have a similar thing for portage?
>
> If I could say "echo gimp>/proc/portage/install" or "cat /proc/portage/packages" etc then
> this would mean that it would be very easy to write front ends for portage, plus with this
> minimal interface it would be very nice to use in scripts... I know it would be a massive
> kernel module, and probably too much effort to actually produce/maintain but I thought you
> should hear the idea... have a think about it please
Hmm, such a module whould make sense if it contains all the pachage management functions and
the whole /var/db/pkg stuff in a database typothing.
I thought about using SOAP over RPC-XML for an network based package management system.
If this thing could be implemented as a module it would be great I think.
Bye Achim
>
>
> - Tom
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-01-20 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 2:47 [gentoo-dev] /proc and portage Thomas Flavel
2001-01-20 13:19 ` Achim Gottinger [this message]
2001-01-20 18:15 ` drobbins
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=3A69EC25.3D9072F2@gottinger.de \
--to=320095285153-0001@t-online.de \
--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