perm mount LAN ntfs share, have to remount on reboot
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
mount only lasts 'til the next reboot. You need to put the share mounting info in /etc/fstab in the correct format.
BTW, I don't know if fstab can accommodate the username, password info.; or, more important, if it would be safe to put them in fstab. (On my system, fstab is world readable.)
Using the above, I now find the remote shares on my desktop (they ARE simply icons, right?) and in myComputer.
However, I get a 'permissions denied' error, which makes sense I guess. As I have noatime disabled locally, I'm sure the above permissions part is wrong... no username/password found in that line.
fstab is a "suck-ass" way to mount network drives, who's presence you can never quite guarentee. i'd very very strongly suggest you look over autofs which can mount defined locations on access, not on boot. as such you're much less likely to have filesystems hanging on the remote machien going awol etc...
I'd prefer to have access through fstab, particularly for music.
autofs is more for mounting when needed, isn't it?
You're saying that the filesystems (rather than the access) would hang at times? That makes sense, similar to shares that are removed yet linger in network places (windows)? But, if mounted properly (with correct permissions set), wouldn't that lesson a possibility?
read up on autofs, the use is absolutely no different, you will always see fiels in the right place when you look for them, whether they are msuic or films or anything.
if you mount a network file system, if that network file system becomes unreachable for some reason, then the client system often hangs whilst it tries and tries to reach that remote node, which has been stolen and chucked in the back of dodgy pete's van. if you use autofs then when you aren't directly using it, the connection is unmounted, so when it's stolen, the kernel on your system doesn't still think it's there, so there's no problem, other than the theft report to the police.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.