Date: Sun, 24 Aug 2008 05:48:21 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-hackers@freebsd.org Subject: Re: What is difference between /etc/rc called programs and ones called after login prompt shows up Message-ID: <20080824054821.1c9d923d@gumby.homeunix.com.> In-Reply-To: <bef9a7920808231902w190dbdffjb1068901e513625d@mail.gmail.com> References: <bef9a7920808230334p4b509e18t1b8a84e9eb7c98b5@mail.gmail.com> <20080823153354.2ed632d4@peedub.jennejohn.org> <bef9a7920808231338s79c78f14w1b8b65f31ffc6d33@mail.gmail.com> <20080823231349.5941d9f3@gumby.homeunix.com.> <20080824003920.34f6bf51@gumby.homeunix.com.> <bef9a7920808231902w190dbdffjb1068901e513625d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 23 Aug 2008 22:02:14 -0400 "Aryeh Friedman" <aryeh.friedman@gmail.com> wrote: > Thanks that did it... but you're incorrect in saying it is only ntfs > it is all fuse based fs's I had a the same error when doing a fuse-ssh > mount to my machine at work I meant only ntfs out of all the other entries in your fstab. If PATH isn't exported then the question became: why are any of the mounts or fscks succeeding? Presumably all the fuse filesystems are mounted in the same way mount -t foo --> mount_foo --> mount_fusefs as opposed to mount -t foo --> mount_foo for native filesystems. Since it turns out that only the mount_foo --> mount_fusefs call needs a PATH variable, all fuse filesystems will fail if PATH isn't exported, but no native filesystem will be affected.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080824054821.1c9d923d>