[fuse-devel] Re: kernel options

[Csaba H. <csa...@cr...>]

On 2006-01-02, Miklos Szeredi <mi...@sz...> wrote:
>> > So I think the proper solution is to make fuse_mount() take 'struct
>> > fuse_args' and let it handle the kernel options.  Since fuse_mount()
>> > is already arch specific, this wouldn't complicate the common code.
>> > 
>> > Does that sound workable?
>> 
>> The whole raw argument vector? Why not just the -o arguments, in a
>> parsed form? Or anything in a parsed form?
>
> Not worth it to introduce another data structure for this purpose IMO.
> Splitting the arguments is cheap, and it's only done at startup.  In
> this case simplicity is more important than performance.

My purpose was much rather avoiding code duplication than mounting at
the speed of light :)

Anyway.... I see. I suggest you to start the game, rewrite the mount
invocation code as you sketched and then I adjust the FBSD-specific code
similarly.

Csaba