[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linux style /proc filesystem translator && httpfs

From: James Morrison
Subject: Re: Linux style /proc filesystem translator && httpfs
Date: Wed, 20 Mar 2002 18:04:55 -0800 (PST)


  Thanks, I'll get to testing this.  did you look at any of neal's procfs

 I'm getting a 404 error though.

--- Jon Arney <jarney1@cox.net> wrote:
> Hi all,
> I've been busy the last week or so putting together a first pass at
> a Linux style /proc filesystem translator.  It seems to have barely
> enough smarts in it now to support the 'procps' package (not that
> procps is better than the native Hurd utilities).  The intent here
> was to start with a Linux-2.4 style /proc filesystem and then move
> on to bigger and better by supporting a 'native' Hurd mode /proc
> filesystem which models the Hurd's behavior better rather than
> just emulating a Linux style /proc.  i.e. rather
> than /proc/<pid>/* we might have /proc/tasks/<pid>/<thread>/*
> and /proc/tasks/<pid>/<children>/* and other cool stuff.  
> It would also be possible for /proc to only show processes owned
> or grouped by you so that you can't see other users processes.
> The biggest problem with the Linux-2.4 /proc filesystem emulation
> is that many of the things available under Linux's /proc filesystem
> either have no equivalent under the Hurd, or are not redily
> available through existing data structures/RPCs because it's a
> fundamentally different architecture.
> If anyone's interested, I've put it out at
> http://orac.ensor.org:8080/hurd/hurd-procfs/
> with some documentation on what it is, what it does, etc.
> Let me know if you can't get to it because I've had problems
> from time to time with the network.
> The beauty (and danter) of the Hurd is that it's an entirely
> independent package and doesn't need to be compiled into the
> /hurd tree.  It supports the traditional
> automake;autoconf;./configure;make scheme.

 Thank you, I'm having a slight problem with httpfs because it isn't done
this way.

 Now getting to httpfs:
   1: Please make source tarballs compilable outside the hurd source.
      That is don't include Makeconf until the translator is ready to be part
      of the hurd source.
   2: Please, if you do include Makeconf, please include either Makefile.in,
      with or without a configure script.
   3: Since httpfs is supposed to be compiled as part of the hurd source
      Makeconf needs to be edited to include the appropriate libxml headers.

 If need be I'll make a self-contained tarball of httpfs this weekend, and send
a Makefile patch here.
 Sorry about bitching, I just want to compile and play with cool things out of
the box ;).  Note: libxml2 is compiled for Debian GNU/Hurd.

James Morrison
   University of Waterloo
   Computer Science - Digital Hardware
   2A co-op

Anyone refering this as 'Open Source' shall be eaten by a GNU

Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards®

reply via email to

[Prev in Thread] Current Thread [Next in Thread]