No easy mounting of nfs shares (Maverick)

Thierry de Coulon tcoulon at
Mon Oct 4 20:36:06 UTC 2010

On Monday 04 October 2010, Jordon Bedwell wrote:
> Try using the soft, intr which will allow you to kill or interrupt the
> mount if the server is unavailable.  As far is it not showing up in the
> places menu, it will not, unless it's mounted.  So once it mounts it
> will then show up.

The part about only showing when mounted makes sens. And it works. However, I 
gues it works only helps not to create a panic if the server is off. It won't 
mount the share later if the server comes online.

> I forgot to mention previously too, that you can name the folders you
> add bookmarks to, so when you do: file:///mnt/share you can also rename
> it so you can do something like: 'file:///mnt/share name' to give it the
> places alias 'name' instead of share.

Actually if I static mount I do it in /<share name> so it's ok like that, but 
thanks for the more sofisticated way.

> Not being aggressive, I just happen to be a bit blunt, and I do
> apologise for it, but it just happens, out of my control.  I am happy to
> hear you might be switching to Debian based distros.

No problem. Actually, it's not such a switch. I've been using Mepis this last 
years, which is also Debian based (was even Ubuntu based for a time).

My favourite Notebboks are Thinkpads and (open)SuSE wroked best on those most 
of the time, but my new Edge seems to prefer Ubuntu.

> This is because in theory and application, SAMBA shares are broadcast,
> NFS shares are not.  Think of SAMBA as your computer in a typical home
> network, you announce and broadcast yourself, other people can find you
> by asking the router and then you click it, and it asks the computer
> what it has to offer and the computer tells your computer.  Think of NFS
> as a closed network with selective sharing, nobody broadcasts
> themselves, but some people offer sharing, if you know their information
> you can view that shared file.

Aha, yes, I understand better.

> Well, I can't say for sure.  I have a Mac Pro here, a really nice one
> but the thing is nothing more than a big foot rest. No, LOL, I don't use
> it for that, I just never use it. I used it for about a week and ended
> up back on my personal baby.

Actually mine is a "Hackintosh", I use it for video editing on two screens 
with Première. Kdenlive is getting better but that's one area where FOSS 
still has a lot to catch up.

> KDE 4 dropped a screwed a lot of things I heard.  I had a lot of friends
> switch from KDE to GNOME after KDE 4 came out, I could never see what
> the fuss was about, but I've never used KDE either. I did like the new
> KDE interface a bit, not much but a bit.  I still prefer GTK and GNOME
> over KDE and whatever it uses. That's personal preference though as I'm
> sure you already got.

I still consider KDE 3 Desktop to be the best, but it's dying away... Gnome at 
the moment is better than KDE 4, and the "Ambiance" theme is the first "dark" 
theme I find that is just good, others are way too dark.

I'd love that Gnome gets the "shutdown" option when you right-click on the 
Desktop, but I can live without.

> You can view your autofs logs in /var/log/messages this should give you
> a hint at what is going wrong hopefully.  Makes sure to double check
> nothing is sensitive in there before you go and post it on a mailing
> list. I have no problem with AutoFS either, which is why we should get
> you to grep your logs so we can see what is going wrong, perhaps there
> was a slip on the configuration you missed.

What am I supposed to grep for? I can't find anything with autofs, or even 
auto. Maybe autofs isn't loading at all?


"We live at a time when emotions and feelings count more than truth, an there 
is a vast ignorance of science" James Lovelock

More information about the ubuntu-users mailing list