Re: [autofs] Re: [ANNOUNCE] Important update - autofs 4.1.4 release

2005-04-13 Thread Ian Kent
On Thu, 14 Apr 2005, Ian Kent wrote: > On Wed, 13 Apr 2005, Jeff Moyer wrote: > > > > > This new version has regressed since beta2 for /net mounts in my > > environment. A simple ls of /net/ will now show the contents of > > /net//exporteddir. So, for example, we have devfiler which exports >

Re: [autofs] Re: [ANNOUNCE] Important update - autofs 4.1.4 release

2005-04-13 Thread Ian Kent
On Wed, 13 Apr 2005, Jeff Moyer wrote: > ==> Regarding [autofs] Re: [ANNOUNCE] Important update - autofs 4.1.4 > release; [EMAIL PROTECTED] adds: > > raven> On Sun, 10 Apr 2005 [EMAIL PROTECTED] wrote: > >> Hi all, > >> > >> Here is autofs 4.1.4. > > raven> There were a couple of mistakes in t

Re: [autofs] Re: [ANNOUNCE] Important update - autofs 4.1.4 release

2005-04-13 Thread Jeff Moyer
==> Regarding [autofs] Re: [ANNOUNCE] Important update - autofs 4.1.4 release; [EMAIL PROTECTED] adds: raven> On Sun, 10 Apr 2005 [EMAIL PROTECTED] wrote: >> Hi all, >> >> Here is autofs 4.1.4. raven> There were a couple of mistakes in the release. raven> The kernel patches have been updated a

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Miklos Szeredi
> > > Yet, the results from stat() don't distinguish the number spaces, > > > and "ls" doesn't map the numbers to names properly in the wrong > > > space. > > > > Well you can use "ls -n". It's up to the tools to present the > > information you want in the way you want it. If a tool can't do tha

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Jamie Lokier
Miklos Szeredi wrote: > > Yet, the results from stat() don't distinguish the number spaces, > > and "ls" doesn't map the numbers to names properly in the wrong > > space. > > Well you can use "ls -n". It's up to the tools to present the > information you want in the way you want it. If a tool ca

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Miklos Szeredi
> > I have a little project to imlement a "userloop" filesystem, which > > works just like "mount -o loop", but you don't need root privs. This > > is really simple to do with FUSE and UML. > > That would be a nice way to implement those rarely used old > filesystems that aren't really needed in

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Jamie Lokier
Miklos Szeredi wrote: > I have a little project to imlement a "userloop" filesystem, which > works just like "mount -o loop", but you don't need root privs. This > is really simple to do with FUSE and UML. That would be a nice way to implement those rarely used old filesystems that aren't really

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Jamie Lokier
Miklos Szeredi wrote: > > Look up the rather large linux-kernel & linux-fsdevel thread "silent > > semantic changes with reiser4" and it's followup threads, from last > > year. > > Wow, it's 700+ messages. I got through the first 40, and already feel > dizzy :) It's easier if you skip the ones b

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Miklos Szeredi
> Look up the rather large linux-kernel & linux-fsdevel thread "silent > semantic changes with reiser4" and it's followup threads, from last > year. Wow, it's 700+ messages. I got through the first 40, and already feel dizzy :) > It's already been tried. You will also find sensible ideas on wha

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Jamie Lokier
Miklos Szeredi wrote: > > > Aren't there some assumptions in VFS that currently make this > > > impossible? > > > > I believe it's OK with VFS, but applications would be confused to death. > > Well, there really is one issue -- dentries have exactly one parent, so > > what do you do when opening a

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Jamie Lokier
> > > A nice implemention of it in FUSE could push it along a bit :) > > > > Aren't there some assumptions in VFS that currently make this > > impossible? > > I believe it's OK with VFS, but applications would be confused to death. > Well, there really is one issue -- dentries have exactly one pa

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Miklos Szeredi
> > Aren't there some assumptions in VFS that currently make this > > impossible? > > I believe it's OK with VFS, but applications would be confused to death. > Well, there really is one issue -- dentries have exactly one parent, so > what do you do when opening a file with hardlinks as a director

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Jan Hudec
On Wed, Apr 13, 2005 at 11:14:10 +0200, Miklos Szeredi wrote: > > > There are uses for both. For example today I was updating the tar ball > > > which is used to create the var file system for a new chroot. I > > > certainly > > > want to see corretly setup owner/permissions when I look into t

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Jan Hudec
On Tue, Apr 12, 2005 at 21:08:25 +0200, Miklos Szeredi wrote: > > There was a thread a few months ago where file-as-directory was > > discussed extensively, after Namesys implemented it. That's where the > > conversation on detachable mount points originated AFAIR. It will > > probably happen at

Re: [RFC] FUSE permission modell (Was: fuse review bits)

2005-04-13 Thread Miklos Szeredi
> > There are uses for both. For example today I was updating the tar ball > > which is used to create the var file system for a new chroot. I certainly > > want to see corretly setup owner/permissions when I look into that tar > > ball using a FUSE fs... > > If I'm updating a var filesystem

Re: O_NONBLOCK for regular files

2005-04-13 Thread Greg Banks
On Wed, 2005-04-13 at 16:31, Trond Myklebust wrote: > on den 13.04.2005 Klokka 16:03 (+1000) skreiv Greg Banks: > > > Any other issues? > > > > Greg. > > Well, I'm sa bit curious as to what "iap->ia_valid |= ATTR_NO_BLOCK" > will do. AFAICS, there is nothing that actually tests for it. fs/xfs/l