A message for Linux.com registered users: We are in the process of making changes to the Linux forums. Starting Monday, 8/13/18 at 6:00 PM PT, you will be unable to access the forums. They will re-launch as soon as possible on Wednesday, 8/15/18 with new features and improved functionality. Thank you for your patience and stay tuned for the new improved forums.
Linux implementation for a Campus
So I've been tinkering back and forward about implementing a client/server Linux system for my campus as my third year project. But as of yet I only know that it is possible to do because I have read a lot of blogposts about people, specially in Finland, who have deployed Linux in schools.
So I want to implement Linux as a client/server system where the clients applications are managed by the server and kept up to date by it. But I don't know whether or not the applications should actually be located on the server or on the client. I got no clue if having the applications on the servers will place too much load on the network and becoming hard to scale. Or if having the applications on the clients will make the updating impossible, which hardly can be true but.
One thing that is sure is that /home must be on the server, mobile and mounted at login to the server. On campus there is an existing Windows system where each user has a small SMB share for saving some stuff. I want this to be attatched to the /home that the user is getting.
And I also want the Login to be inherited by the existing Windows System and that to be used against the Proxy Server.
Could someone explain to me how some of these things can be done, what Distribution I want to use for the server respective Clients and maybe point me somewhere explaining how something like this has been done before.
Why the heck aren't .svg files allowed as imeages nor file attatchments. Makes no sense to me. Where can I file a bug?
Now I had to first convert it to a GIMP .xcf to convert it to a .png that I could upload.
Here is how I for the moment think the system should be architectured: