James,
Thanks for the links. One of the difficult things about coming up to
speed on the Hurd is that there are so many different websites with
lots of (sometimes conflicting) information. I didn't know that a
/proc filesystem already existed, but I did look for one. If I had
known, I might ha
On Wed, Mar 20, 2002 at 10:05:32PM -0800, Thomas Bushnell, BSG wrote:
> I think it would be clearest to have A open it twice, one for reading,
> and one for writing.
The problem is getting the two matched together without race.
The unique feature in my translator (which distinguishes it from a
no
On Thu, Mar 21, 2002 at 07:39:19PM -0700, Jon Arney wrote:
> Actually, I didn't even know it existed. If you point me at the source,
> I'll look at it and see if it's useful to me.
Might be at Neal's web site (ftp.walfield.org), or just try google.
James has a collection on his site, I read here
James Morrison <[EMAIL PROTECTED]> writes:
> On around line 93 of fstests/fstests.c, there is a malloc of size 0, what
> would
> be the point of that?
Beats me. The program is just for testing, that is, it was there so
that we could easily have any random bit of code easily compiled to be
run.
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> It's the canonical file interface. I mean, T is a translator on a node,
> A opens the node with O_RDWR and starts to write to it and read from it.
> Now when it has nothing more to write, I would like to signal the
> translator about it, so it can c
On Wed, Mar 20, 2002 at 08:40:18PM -0800, James Morrison wrote:
> Once reason I was able to keep my hurd box up for 7 weeks was that I used
> neal's proc filesystem which continued to work even after I couldn't use ps -a.
> I don't know why I couldn't use ps -a, but I couldn't.
It probably was j
Personal Plug: I have collected on my website all the translators I know of.
I'll the new procfs and httpfs this weekend. see hurd.dyndns.org
Once reason I was able to keep my hurd box up for 7 weeks was that I used
neal's proc filesystem which continued to work even after I couldn't use ps
Marcus,
Thanks for all your feedback. I've responded to most of the points
below.
> Do you know about Neal Walfields procfs which he wrote a couple years
> ago? He says it is broken but it might be worth looking into for you.
Actually, I didn't even know it existed. If you point me at the sou
Hi,
On around line 93 of fstests/fstests.c, there is a malloc of size 0, what
would
be the point of that?
Humm, fstests/opendisk.c and fstests/fdtests.c don't compile anymore, but I
suppose that is why they are commented out of the makefile.
Any just a few quick questions. Thanks.
On Wed, Mar 20, 2002 at 02:08:46PM -0800, Thomas Bushnell, BSG wrote:
> I'm pretty sure that's a bug; standard pipes shouldn't be
> bidirectional. Roland, what do you think?
In SVR4, they behave this way (acording to Stevens, who alos calls them
stream pipes).
> > What I was asking about is the
hai,
I have tried to develop the httpfs translator for
hurd...
Attaching herewith the code for the same.
I am beginner to Hurd donno to what extent it rises to
the expectation of Hurd Geeks.
It has a dependency on libxml2 library.
the libxml2 library is used for parsing the HTML
stream to get an
Hey,
Thanks, I'll get to testing this. did you look at any of neal's procfs
code?
I'm getting a 404 error though.
--- Jon Arney <[EMAIL PROTECTED]> 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 se
On Thu, Mar 21, 2002 at 09:25:19AM -0700, Jon Arney wrote:
> I've been busy the last week or so putting together a first pass at
> a Linux style /proc filesystem translator.
Do you know about Neal Walfields procfs which he wrote a couple years
ago? He says it is broken but it might be worth loo
Title: ÀÌ°÷Àº Á¦¸ñÀÔ´Ï´Ù
ÄÄÇ»Å͸¦ ÀÌ¿ëÇϽôµ¥ ²À ÇÊ¿äÇÑ ÄÄÇ»ÅÍ °ü·ÃÇÁ·Î±×·¥À»
¾öû Àú·ÅÇÑ °¡°Ý¿¡ ÆË´Ï´Ù
ÃÖ½ÅÇ®¹öÀü°ÔÀÓ. ÄÄÇ»ÅÍ°ü·ÃÇÁ·Î±×·¥. ¼ºÀνõð µîµî
ÄÄÇ»ÅÍ¿¡ °ü·ÃµÈ ¸ðµç½Ãµð°¡ ÀÖ½À´Ï´Ù
ÃֽŸñ·ÏÀÔ´Ï´Ù
¹°·Ð ½Å¿ëÀº ±âº»ÀÔ´Ï´Ù
¾ÐÃàÈÀϼÓÀÇ ³»¿ëÀ» º¸½ÅÈÄ Àüȳª ¸ÞÀÏ·Î ¿¬¶ôÁֽʽÿä
ÀÌ ¸ÞÀÏÀ»
Our chief concern to begin with is clean code reuse and consistency of the
terminal emulation for standard display devices. Turning the interface
inside out doesn't lose that.
But I am still on the fence about what the proper structure really is.
First are some feature concerns, with a garnish
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 L
Rather than just ignoring the offset, you should check for -1 and return
ESPIPE otherwise, so pread/pwrite fail as they should.
I'd say you should use getdport at the beginning and use io_read and the
like directly instead of read. That is more efficient and also shows what
the client calls look
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> I'm baffled. If it's a plain pipe, then you simply close the end
> you're writing on, and the reader gets EOF.
Well, I think there are systems where pipe gives you a bidirectional
pipe, but where shutdown on the pipe gives you the ENOTSOCK erro
Title: New Document
(¸ÕÀú, Çã¶ô ¾øÀÌ º¸³»µå¸°°Å Á˼ÛÇÕ´Ï´Ù. )
¾È³çÇϽʴϱî? °¡Á×°¡¹æ »ý»ê¾÷ü MATT(¸¶¶ß)ÀÔ´Ï´Ù. www.MATT.co.kr , [EMAIL PROTECTED]
¡Ú °¡Á×¼·ù°¡¹æ!! MATT(¸¶¶ß)ÀÇ À̺¥Æ®!!¡Ú
¡Ù´ë»ó: 2¿ù21ÀÏ~3¿ù29ÀÏ MATT¿¡¼ Á¦Ç°±¸¸ÅÇØÁֽŠ°í°´´Ôµé
¡Ù´ç÷ÀÚ ¼±Á¤¹æ¹ý: °øÁ¤ÇÑ Ãß÷À» Å
> You ought to set some flag somewhere so that you get the PIPE_BUF
> behaviour for pipes, but *not* for socketpairs, right?
The PIPE_BUF behavior is part of AF_LOCAL sockets.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/list
¡¡===¸ÃÓʼþʹÓà ¿ÆÌØÓʼþȺ·¢Èí¼þ ·¢ËÍ,ÓʼþÄÚÈÝÓë¿ÆÌØÈí¼þÎ޹ؿÆÌØÈí¼þ http://www.caretop.com===
___
Bug-hurd mailing list
[EMAIL
Hi,
kindly subscribe me.
Reddy
__
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailma
[EMAIL PROTECTED] (Niels Möller) writes:
> [EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
>
> > I'm baffled. If it's a plain pipe, then you simply close the end
> > you're writing on, and the reader gets EOF.
>
> Well, I think there are systems where pipe gives you a bidirectional
> pipe, bu
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> We are getting into muddy water again, because I was unprecise.
> If we call the application A, the translator T and the forked program P,
> then I have the normal file interface open(), read(), write() between A
> and T, and a bidirectional pipe cr
On Wed, Mar 20, 2002 at 04:40:32PM -0500, Marcus Brinkmann wrote:
> Would I use shutdown even for the file interface between A and T,
OTOH, the translator claims itself to be a pipe, so I guess shutdown
is perfectly feasible. Sorry for all the confusion. One has to take
the warning in the Hurd
Roland McGrath <[EMAIL PROTECTED]> writes:
> Saying "bidirectional pipe" is descriptive too. :-) They're the same thing.
> As we discussed in great detail here at the time, `pipe' now creates a
> bidirectional pipe, i.e. it creates a socketpair and does not call
> shutdown.
You ought to set some
On Wed, Mar 20, 2002 at 10:03:16PM +0100, Niels M?ller wrote:
> Does your run-translator get any interesting rpc if the process that
> opened the translated node calls shutdown on its fd?
I would think it gets the shutdown rpc :)
Marcus
___
Bug-hurd
On Wed, Mar 20, 2002 at 12:55:36PM -0800, Thomas Bushnell, BSG wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> > The implementation is using the Hurd's IO interface. It seems I was not
> > clear enough in my original mail. The translator creates a pipe to the
> > forked program, and t
On Tue, Mar 19, 2002 at 02:54:24PM -0800, Thomas Bushnell, BSG wrote:
> I'm baffled. If it's a plain pipe, then you simply close the end
> you're writing on, and the reader gets EOF.
>
> I assumed the implementation used socketpairs, where closing your
> writing half would prevent you from also
> Then you are using a bidirectional pipe: you should really call it a
> socketpair. (Exactly how are you creating it?)
Saying "bidirectional pipe" is descriptive too. :-) They're the same thing.
As we discussed in great detail here at the time, `pipe' now creates a
bidirectional pipe, i.e. it c
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> Now, suppose you have a program like wc that collects data and returns
> a summary of that data. It will read from stdin until it gets EOF, and
> then print from stdout. But if I use the above translator, I have only
> one filedescriptor, and I can
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> The implementation is using the Hurd's IO interface. It seems I was not
> clear enough in my original mail. The translator creates a pipe to the
> forked program, and translates io_read into a pipe read and io_write
> into a pipe write. The transl
On Wed, Mar 20, 2002 at 09:25:21PM +0100, Oystein Viggen wrote:
> It's cheating, but wouldn't the following in most cases do the same as
> filter?
>
> #!/bin/bash
> `showtrans $1 | cut -d \ -f 2-`
Sure, that's a neat trick, too (you might need to strip more options
from it that are specific to
* [Marcus Brinkmann]
> So I am considering to write a "filter" program that has two threads
> and takes a filename as an argument. One thread reads on stdin and
> writes to the opened file, the other thread reads from the file and
> writes to stdout. This should work rather well, and can be us
[EMAIL PROTECTED] (Niels Möller) writes:
> [EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
>
> > You want the "shutdown" call, which should do the right thing.
>
> Does shutdown work on plain pipes, or is it it necessary to use
> socketpair instead of pipe? (Not that that is usually a problem,
35 matches
Mail list logo
