On Sat, Jun 24, 2006 at 02:16:00PM +0200, Arjan van de Ven wrote:
> On Fri, 2006-06-23 at 19:41 -0500, Troy Benjegerdes wrote:
> > This patch changes the in-kernel AFS client filesystem name to 'kafs',
> > as well as allowing the AFS cache manager port to be set as a module
> > parameter. This is usefull for having a system boot with the root
> > filesystem on afs with the kernel AFS client, while still having the
> > option of loading the OpenAFS kernel module for use as a read-write
> > filesystem later.
>
> sounds weird... the filesystem it implements is afs.
> your change also breaks userspace, since the fs type is a mount option
> so your change is userspace visible and means people need to fix their
> scripts...
>
> maybe openafs should start using "openafs" as type; they're not in the
> kernel so they aren't yet bound by the userspace ABI....
This is the most idiotic argument I have ever heard, and completely
ignores reality. The kernel module is named already named "kafs", not "afs"
and *NOBODY* is using it because it does not have authentication or
read-write support.
If you want to talk about breaking userspace and existing scripts, the
AFS filesystem (of which the OpenAFS code is derived from) has existed
and been in production far longer than Linux.
( see http://portal.acm.org/citation.cfm?doid=35037.35059 )
At Iowa State University alone there are around 20K people that depend
on OpenAFS running on Linux for webmail service.
The only scripts I could think of that would be impacted by changing the
kernel afs mount name to 'kafs' would be the ones I am writing, and anything
David Howells has. That amounts to *maybe* 10 users.
If you really care about breaking long-standing userspace ABI's, will
you accept a patch allowing kAFS, OpenAFS, and Arla to register to
recieve a callback when the AFS syscall number is called?
Now, if you could suggest another way to have both the *experimental*
in-kernel AFS client and OpenAFS client with mounted filesystems, please
let me know.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
