All of lore.kernel.org
 help / color / mirror / Atom feed
From: Remi Turk <remi@a2zis.com>
To: Jonathan Lundell <jlundell@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Configure.help is complete
Date: Sat, 2 Jun 2001 20:27:04 +0200	[thread overview]
Message-ID: <20010602202704.F1297@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.21.0105311555250.17748-100000@weyl.math.psu.edu> <3B178E0E.A4530D47@egenera.com> <20010601145900.C12402@khan.acc.umu.se> <p05100308b73d672c7f2b@[207.213.214.37]>
In-Reply-To: <p05100308b73d672c7f2b@[207.213.214.37]>; from jlundell@pobox.com on Fri, Jun 01, 2001 at 08:45:17AM -0700

On Fri, Jun 01, 2001 at 08:45:17AM -0700, Jonathan Lundell wrote:
> >>  It allows a general interface to the kernel that does not require new
> >>  syscalls/ioctls and can be accessed from user space without specifically
> >>  compiled programs. You can use shell scripts, java, command line etc.
> >
> >Yes, and it's also totally non standardised.
> 
> It clearly fills a need, though, and has the distinct side benefit of 
> cutting down on the proliferation of ioctls. Sure, it's non-standard 
> and a mess. But it's semi-documented, easy to use, and v. general. 
> What's the preferred alternative, to state the first question another 
> way? For any single small project/driver, creating a new fs simply 
> isn't going to happen.
> -- 
> /Jonathan Lundell.

If I understand Al Viro correctly we'll get per driver filesystems
in 2.5 (based on ramfs) which you can union-mount on /proc
(possibly using autofs) to get the current /proc tree.

Happy Hacking.

-- 
Linux 2.4.5-ac6 #1 Fri Jun 1 17:12:42 CEST 2001

  reply	other threads:[~2001-06-02 18:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-31 17:24 Configure.help is complete Eric S. Raymond
2001-05-31 20:13 ` José Luis Domingo López
2001-05-31 18:23   ` Eric S. Raymond
2001-05-31 18:21     ` Alan Cox
2001-06-01  1:50     ` José Luis Domingo López
2001-05-31 19:48   ` Arjan van de Ven
2001-05-31 19:57     ` Alexander Viro
2001-06-01 12:43       ` Phil Auld
2001-06-01 12:59         ` David Weinehall
2001-06-01 15:45           ` Jonathan Lundell
2001-06-02 18:27             ` Remi Turk [this message]
2001-05-31 22:56 ` Nerijus Baliunas
  -- strict thread matches above, loose matches on Subject: below --
2001-05-31 20:12 BH
2001-05-31 20:42 ` Arjan van de Ven
2001-05-31 20:50   ` Eric S. Raymond
2001-05-31 21:22 ` Alan Cox

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=20010602202704.F1297@localhost.localdomain \
    --to=remi@a2zis.com \
    --cc=jlundell@pobox.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.