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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

On the Windows machine I can see and read all the directories and files

BUT NO WRITE ACCESS

I have to go back on the Linux server and AFTER EACH BOOT re set all the permissions manually

I've set the NFS up correctly etc -- but I still manually have to do the permissions stuff as root.

Now I know there is a problem with USB drives in the fstab as when the fstab is processed the devices aren't ready yet so perhaps I could have a script that does the mount and the permissions after boot up

I don't know any shell scripting so was wondering if someone could post one for me

I need the 2 mounts as above and allow ALL members of group USERS to have read and write access to the directories /media/4windows1 and /media/4windows2 from the root downwards (and to be able to create new ones) --these disks are for public shares across the entire network.

An automatic script which ran after the system was booting would be quite an acceptable get around --I just don't want to have to enter this stuff manually each time.

if you have to reset the permissions each time you reboot this sounds like you use udev (udev creates everything in /dev/ dynamicly at boot and also resets the permissions) you can edit your udev rules so that when it boots it will give sda5 &sdb5 the corect permissions