Re: Non-compliant access behavior?

ST> But compliancy is also about the common behavior, ST> and here gcc assumes some behavior of access(). Wrong again. The problems with access() and what one should do instead of using access(), have been hashed out some 15 years since. These include what one should do in order to be properly po

Re: Non-compliant access behavior?

J de Boyne Pollard, le Thu 24 Dec 2009 09:51:01 -0800, a écrit : > ST> The problem I encountered is that I couldn't run gcc over > ST> files in a directory which belonged to a group my I was in. > ST> I hope you'll too find it quite surprising.   > > Only inasmuch as gcc is even using access(), wh

[PATCH] Devnode: Fix the pseudo-master device port opening flags.

* devnode/devnode.c (parse_opt): Open the pseudo-master devide port with O_READ | O_WRITE flags to allow subsequent device creation. --- Hello, Originally, devnode would open the pseudo-master device port with 0 flags. These flags are stored by eth-multiplexer in the peropen structure and the su

[PATCH] Add the .MASTER node to the eth-multiplexer.

* eth-multiplexer/device_impl.c (ds_device_open): Handle the .MASTER node specially. * eth-multiplexer/multiplexer.c (main): Create the .MASTER node. * eth-multiplexer/netfs_impl.c (master_node): New variable. (lookup): Handle the lookups for .MASTER specially. (netfs_add_dirents): Add the .MASTER

Re: [PATCH 1/2] Fix some minor issues.

Hello, On Mon, Aug 10, 2009 at 11:11:41PM +0300, Sergiu Ivanov wrote: > > diff --git a/eth-multiplexer/vdev.c b/eth-multiplexer/vdev.c > index dac9802..6fb88d0 100644 > --- a/eth-multiplexer/vdev.c > +++ b/eth-multiplexer/vdev.c > @@ -135,7 +135,10 @@ add_vdev (char *name, int size, > >vdev-

Re: Non-compliant access behavior?

ST> That's why I put a question mark in the subject. And that's why you were told the answer. ST> The problem I encountered is that I couldn't run gcc over ST> files in a directory which belonged to a group my I was in. ST> I hope you'll too find it quite surprising.   Only inasmuch as gcc is ev

Re: review of modifications of eth-multiplexer

Hello, On Thu, Dec 24, 2009 at 05:44:20PM +0800, Da Zheng wrote: > Sergiu Ivanov wrote: > > > I see. The question, then, is whether it is appropriate to push the > > whole Hurd source tree with Zheng's changes to the incubator, or > > would it be better to have a separate repository for that? > >

Re: [PATCH] Add the .MASTER node to the eth-multiplexer.

Hello, On Thu, Dec 24, 2009 at 05:52:48PM +0800, Da Zheng wrote: > Sergiu Ivanov wrote: > > > On Wed, Dec 23, 2009 at 08:52:33AM +0800, Da Zheng wrote: > >> netfs_attempt_lookup locks this node and the node is unlocked by > >> libnetfs, right? I forget a lot:-) So why can the second lookup not > >

Re: review of modifications of eth-multiplexer

Sergiu Ivanov wrote: > Hello, > > On Wed, Dec 23, 2009 at 03:51:16PM +0100, olafbuddenha...@gmx.net wrote: >> On Tue, Dec 22, 2009 at 11:25:51PM +0200, Sergiu Ivanov wrote: >> >>> but looking at the commit history in your hurd.git repository, I can >>> see that there are commits concerning the mul

Re: [PATCH] Add the .MASTER node to the eth-multiplexer.

Sergiu Ivanov wrote: > Hello, > > On Wed, Dec 23, 2009 at 08:52:33AM +0800, Da Zheng wrote: >> netfs_attempt_lookup locks this node and the node is unlocked by >> libnetfs, right? I forget a lot:-) So why can the second lookup not >> wait until the first one finishes? > > I've tried to remove the

Re: Non-compliant access behavior?

J de Boyne Pollard, le Wed 23 Dec 2009 12:41:30 -0800, a écrit : > ST> Apparently access() restricts itself to the real gid, without > ST> including supplementary group IDs. > > As IEEE 1003.1:2004 says, at least by omission, it should. There's no > mention of supplementary group IDs in the defin

Re: What would it take....

Samuel Thibault wrote: > Good morning :) Good afternoon:-) > > Da Zheng, le Thu 24 Dec 2009 08:50:14 +0800, a écrit : >> So has network-transparent IPC been removed from microkernel or not? > > See DEVELOPMENT: > > Support for NORMA was removed on 2006-03-20. >

Re: hurd/trans/hello.c changes

Hello, On Thu, Dec 24, 2009 at 12:32:53PM +0530, Shakthi Kannan wrote: > --- On Thu, Dec 24, 2009 at 12:42 AM, Sergiu Ivanov > | Printing to a file is nothing fancy: the fprintf functions should > | suffice. > \-- > > I would appreciate if I could see a working example. When I use > fprintf(stdou