The NZ Linux Resource

[klug] Shared /home over LAN

Nathan Cook nathan at coast-computers.co.nz
Sun Sep 11 12:53:43 NZST 2005


Maybe LDAP is a better choice for you as it seems to scale well 
according to a view people around, so if you are planning on adding a 
number of workstations more to the current setup then stay with what you 
have, although NIS may be easier for you. Really though the choice is yours.

The linux networking page has a page on setting up NIS. Although you 
could wipe the LDAP server you have and install a fresh install and go 
from there which means learning LDAP or just following instructions ;)

To go the TS route might mean an upgrade to the network to GB especially 
if you get a few PC's running 3D processes, plus the server would need 
to be either dual CPU or a Dual Core CPU, but you won't really know 
until it is tested, plus a SCSI/SATA RAID 5 would help to.

klug.member.lancer at xoxy.net wrote:

> Thanks for your reply.
>
> The original guy who set us up recommended LDAP over NIS. When I asked 
> for some documentation on, say, how to add another computer if I 
> needed to, he directed me to 
> http://www.linuxhomenetworking.com/linux-adv/ldap.htm
>
> Are there any real reasons to choose one over the other? At least I 
> now appear to have two guidelines to try out, and certainly I want to 
> trial this to make sure I can do it before bawking up the real Mcoy.
>
> One of the more serious problems that is / has been occurring is that 
> if the internet service provider (Paradise) gets disconnected, the 
> entire LDAP driven LAN fails along with it, resulting in no one being 
> able to log into any computers for even so much as using a word 
> processor (not a good look for me in front of the whole school). I'm 
> not certain whether this would have something to do with standard LDAP 
> misconfiguration or whether the network guy has put something extra of 
> his own in place "for security reasons" which he hasn't told me about 
> and which may be falling over once the internet link fails.
>
> Do any of you network gurus out there have an incling as to what might 
> be causing this and how to tweak it right?
>
> Any ideas on things which I should check?
>
> Lance.
>
>
> Nathan Cook - nathan at coast-computers.co.nz wrote:
>
>> You will need to setup a NIS server and then the NIS clients. It's 
>> too much detail to go into here but have a look here: 
>> http://www.tldp.org/HOWTO/NIS-HOWTO/index.html
>>
>> There is plenty there to keep you going for a few nights, I would set 
>> up 2 PCs to test and run through a few scenarios before going live, I 
>> can if you like lend you my spare PC for a few weeks if need be, it's 
>> not much but will do the trick for testing (500mhz, 256mb RAM, 40gb 
>> HDD).
>>
>> Regards
>>
>> Nathan
>>
>> klug.member.lancer at xoxy.net wrote:
>>
>>> Can anyone point me to where I can learn how to make a shared /home 
>>> directory over a LAN setup like in our school? The guy who set that 
>>> up did a nice job and all but there are some fairly major bugs and 
>>> he's hard to get hold of. To be honest, I'm starting to get 
>>> frustrated by the errors and the inability to get hold of him, but I 
>>> don't want to go into too much detail on a public forum like this 
>>> and think it's best if I start all over but learn to do things for 
>>> myself.
>>>
>>> Basically, I want to know how to make one machine the file server, 
>>> where the /home dirs are linked to the drive on that machine, so all 
>>> saved work from students goes to one place instead of being 
>>> duplicated on each machine, individual permissions intact. Obviously 
>>> adding new student accounts etc will have to have identical user 
>>> IDs. I'm not sure if I also want to share other DIRs like /bin etc. 
>>> Common permissions would be nice (e.g: I can ban any student from 
>>> playing a given game setting permissions on only one computer).
>>>
>>> I am not wanting to make a dumb terminal situation where the central 
>>> computer has to be really powerful, or one computer has to do all 
>>> the hard drive / memory tasks of the many machines - that would slow 
>>> everyone down. /home access is all I'm really wanting at least for now.
>>>
>>> I am also interested in the antiporn set up as mentioned before 
>>> (like having one machine as the internet gateway for the others) but 
>>> for now setting up the LAN /home dir is my priority. I understand 
>>> the network guru used LDAP for the current setup, but my experience 
>>> in this is zilch.
>>>
>>> Can anyone point me to where I can learn this stuff fast enough to 
>>> have set it up myself within the next week or so? (e.g: not a large 
>>> thesis of many possibilities - I am a slow reader). Last time I 
>>> asked a forum this I explained what I wanted in great detail, and 
>>> all I got was "your network - up to youy how you go about it", which 
>>> was not helpful.
>>>
>>> Thanks in advance.
>>> Lance.
>>>
>>> _______________________________________________
>>> KLUG mailing list
>>> KLUG at linux.net.nz
>>> http://www.linux.net.nz/cgi-bin/mailman/listinfo/klug
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> KLUG mailing list
>> KLUG at linux.net.nz
>> http://www.linux.net.nz/cgi-bin/mailman/listinfo/klug
>>
>>
>>
>
>
> _______________________________________________
> KLUG mailing list
> KLUG at linux.net.nz
> http://www.linux.net.nz/cgi-bin/mailman/listinfo/klug
>
>
>




More information about the KLUG mailing list If you have any questions or comments about this page, email the Webmaster
Design Copyright © 1998-2005 Linux.net.nz