From: "Brian L. Stuart" <[EMAIL PROTECTED]>
> From: "Eric Van Hensbergen" <[EMAIL PROTECTED]>
> > On Thu, May 8, 2008 at 12:56 PM, Brian L. Stuart <[EMAIL PROTECTED]>
> wrote:
> > > - v9fs defines P9_OEXCL to be 4, where
> > > /sys/include/libc.h defines OEXCL to be 0x1000
> >
> > Which versio
-- Original message --
From: "Eric Van Hensbergen" <[EMAIL PROTECTED]>
>
> On Thu, May 8, 2008 at 12:56 PM, Brian L. Stuart <[EMAIL PROTECTED]> wrote:
> > - v9fs defines P9_OEXCL to be 4, where
> > /sys/include/libc.h defines OEXCL to be 0x1000
>
> Which ver
On Thu, May 8, 2008 at 12:56 PM, Brian L. Stuart <[EMAIL PROTECTED]> wrote:
> I've found something that looks odd in the way v9fs
> under Linux interacts with a fossil running on Plan 9.
> If I create a file by redirecting output, the shell
> seems able to happily create the file. If I try to
>
I've found something that looks odd in the way v9fs
under Linux interacts with a fossil running on Plan 9.
If I create a file by redirecting output, the shell
seems able to happily create the file. If I try to
cp a file, then it fails. The logs show the error
"unknown mode." As near as I can tel
