Date: Mon, 21 Sep 2009 12:21:09 +0200 From: hv <hv@tuebingen.mpg.de> To: ruby@FreeBSD.org Subject: [suggestion]: avoiding portupgrade failure to upgrade/installing ports when home is on automounted directory.. Message-ID: <27C0279D-3305-474A-B41F-BF0FCF173350@tuebingen.mpg.de>
next in thread | raw e-mail | index | archive | help
Hi, Preferring to install/upgrade as a normal user w/ sudo, it is, =20 probably not a real bug, but annoying, that portupgrade fails on =20 *some* ports mysteriously like this: .. ! shells/bash (bash-4.0.24) (Permission denied - /.amd_mnt/kaa/=20 host/home/hv) .. As you see, my Homedir ist automounted via NFS. If i change beforehand =20= to a local writable directory (like /tmp) the same command succeeds =20 (with an also annoying warnig: /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:1148: warning: Insecure =20= world writable dir /tmp/. in PATH, mode 041777 Why not allow installing with sudo, even if located on a remote =20 Homedir ? If root (who is nobody on the remote filesystem and therefore no =20 allowed to access it (permissions 700) wants to put some temporary =20 status info, why not implicitly put it into some local dir (eg. root's =20= home) ? Regards -- Henry Vogt <hv@tuebingen.mpg.de> (Fon: ++49-7071-601-511, Fax: -826) Campus Max-Planck-Institute, Spemannstr. 32-41, T=FCbingen, Germany
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27C0279D-3305-474A-B41F-BF0FCF173350>