From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <140e7ec30806191339wd627c39pc83976af545fde38@mail.gmail.com> Date: Fri, 20 Jun 2008 04:39:58 +0800 From: sqweek To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5d375e920806181842t77de05f8v91bb7bd0c4d91819@mail.gmail.com> <5d375e920806182005g34befcfbg8d3870764fe90bf4@mail.gmail.com> Subject: Re: [9fans] P9p's mount(1) on linux Topicbox-Message-UUID: c367b8fe-ead3-11e9-9d60-3106f5b1d025 On Thu, Jun 19, 2008 at 11:53 PM, Eric Van Hensbergen wrote: > Whatever function deals with passing the options to the mount system > call needs the modification. The few changes that are there may be > fixed by me doing a better job and supporting old names for options, > but it won't help for the kernels already in circulation. I've just updated to 2.6.25 which means I finally had to fix 9mount to work with the >= 2.6.24 mount options. Dealt with backwards compatibility by simply adding both the pre AND post 2.6.24 mount options (which was suggested by uriel or jyujin on IRC awhile back). So, mounting works, but v9fs's option string appears to be screwed, which I was relying on for 9umount (to prevent unmounting things mounted by other users). Which is not the best plan, but I'm not sure how else to do it... > Basically it will probably be best to structure it as a > "mount helper" and ship it in its own package. I'm not sure how mount helpers work... would you have to be root to use it that way? -sqweek