From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net Subject: Re: [9fans] P9p's mount(1) on linux From: "Russ Cox" Date: Thu, 19 Jun 2008 11:10:19 -0400 In-Reply-To: <59247.81.47.192.163.1213873686.squirrel@webmail.kix.es> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20080619150936.218261E8C45@holo.morphisms.net> Topicbox-Message-UUID: c32a0c70-ead3-11e9-9d60-3106f5b1d025 Thanks for the patch, Uriel. The http://swtch.com/v9fs script stopped working a long time ago, and I never bothered to find out why. I've changed the text on that page, though clicking on the "date and checksums" link has always shown that the last update was October 2006. A few p9p programs--acme, tapefs, vacfs--now accept a -m option directing them to mount at a particular place in the directory tree, via 9pfuse. There is no option to mount via the Linux 9p module. I'm a little tired of the "Fuse sucks" meme. The fuse libraries are not so great, but the fuse kernel interface is completely reasonable, and arguably a better fit for Unix than 9P is. A lot of the hard work and churn in Eric's code is because he's trying to do a good translation from 9P to Unix VFS. Fuse lets the individual file servers take care of that, which is fine with me. Also, the FUSE kernel interface, in my experience, has been a bit more solid and certainly changes less often. I think that Fuse gets a bad rap mainly because the people using it to write file servers don't do a good job. I've never run into bugs in the fuse kernel driver itself. User-level file servers are an entirely new concept for most people (present company excluded), so it's not surprising that most of the people out there writing user-level file servers don't fully understand the issues in what they're implementing. But the Fuse kernel developers do. I wrote a new user-level file server a month ago, something I hadn't done in years, and I did it on Linux, using lib9p backed by 9pfuse. It was an entirely pleasant experience. Russ