Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 13561 invoked from network); 4 May 2008 13:43:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 May 2008 13:43:05 -0000 Received: (qmail 51520 invoked by uid 500); 4 May 2008 13:43:05 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 51510 invoked by uid 500); 4 May 2008 13:43:05 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 51499 invoked by uid 99); 4 May 2008 13:43:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 May 2008 06:43:05 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 May 2008 13:42:10 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A6FEE234C11B for ; Sun, 4 May 2008 06:38:57 -0700 (PDT) Message-ID: <736944175.1209908337682.JavaMail.jira@brutus> Date: Sun, 4 May 2008 06:38:57 -0700 (PDT) From: "Craig Macdonald (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4) tool to mount dfs on linux MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594093#action_12594093 ] Craig Macdonald commented on HADOOP-4: -------------------------------------- @Allen a) not sure what you mean here. Ideally, I'd like to use fuse_dfs_wrapper.sh in my fstab/automount lines, so it should have all env vars already set, if they can be derived at build or run time. b) This works fine. Permissions within fuse-dfs are a whole other kettle of fish, so I think I'll keep quiet until fuse-dfs is committed, then start another JIRA. It's just worth noting that if you want to share a fuse-dfs mount between multiple users, then the DFS permissions model will be broken. > tool to mount dfs on linux > -------------------------- > > Key: HADOOP-4 > URL: https://issues.apache.org/jira/browse/HADOOP-4 > Project: Hadoop Core > Issue Type: Improvement > Components: fs > Environment: OSs that support FUSE. Includes Linux, MacOSx, OpenSolaris... http://fuse.sourceforge.net/wiki/index.php/OperatingSystems > Reporter: John Xing > Attachments: fuse-dfs.tar.gz, fuse-dfs.tar.gz, fuse-dfs.tar.gz, fuse-dfs.tar.gz, fuse-dfs.tar.gz, fuse-hadoop-0.1.0_fuse-j.2.2.3_hadoop.0.5.0.tar.gz, fuse-hadoop-0.1.0_fuse-j.2.4_hadoop.0.5.0.tar.gz, fuse-hadoop-0.1.1.tar.gz, fuse-j-hadoopfs-03.tar.gz, fuse_dfs.c, fuse_dfs.c, fuse_dfs.c, fuse_dfs.c, fuse_dfs.c, fuse_dfs.sh, fuse_dfs.tar.gz, HADOOP-4.patch, HADOOP-4.patch, HADOOP-4.patch, Makefile, patch.txt, patch.txt, patch2.txt, patch3.txt, patch4.txt, patch4.txt, patch4.txt, patch5.txt, patch6.txt > > > tool to mount dfs on Unix or any OS that supports FUSE -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.