Update of bug #28383 (project hurd):
Status:None => Wont Fix
Reproducibility:None => Every Time
Summary: Non-compliant access behavior? => Supplementary
groups aren't use by access()
J de Boyne Pollard, le Thu 24 Dec 2009 21:24:36 -0800, a écrit :
> ST> Then please tell that to gcc people, not me.
> ST> Then please tell that to gcc people, not me.
>
> *You* are the one *with* the problem. You are the appropriate person
> to talk to the gcc maintainers about *your* problem w
Hi,
Sergiu Ivanov wrote:
>> Maybe devnode can detect the access right of .MASTER first before it
>> calls file_name_lookup(). So if the user doesn't have write access
>> to .MASTER, it just makes its own node read-only. If the user want
>> to change the access right of the devnode node and want to
Hello,
On Fri, Dec 25, 2009 at 09:29:07PM +0800, Da Zheng wrote:
> Sergiu Ivanov wrote:
>
> > On Fri, Dec 25, 2009 at 05:09:40PM +0800, Da Zheng wrote:
> >> Sergiu Ivanov wrote:
> >>> - master_device = file_name_lookup (arg, 0, 0);
> >>> + master_device = file_name_lookup (arg, O_READ |
Sergiu Ivanov wrote:
> Hello,
>
> On Fri, Dec 25, 2009 at 05:09:40PM +0800, Da Zheng wrote:
>> Sergiu Ivanov wrote:
>>> - master_device = file_name_lookup (arg, 0, 0);
>>> + master_device = file_name_lookup (arg, O_READ | O_WRITE, 0);
>> What happens if .MASTER file is read-only? Certai
Hello,
On Fri, Dec 25, 2009 at 05:09:40PM +0800, Da Zheng wrote:
>
> Sergiu Ivanov wrote:
> > - master_device = file_name_lookup (arg, 0, 0);
> > + master_device = file_name_lookup (arg, O_READ | O_WRITE, 0);
>
> What happens if .MASTER file is read-only? Certainly,
> file_name_lookup
Sergiu Ivanov wrote:
> * 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-multiple
