At least one of the following features is sorely needed on home networks, without the need to run OSX server.
I suspect that all the machinery is in place on OSX client, just not in your face thru the GUI. Moreover, some of these solutions would be a good introduction for IT people to get their hands dirty before introducing OSX server at work.
True authentication at login using one of the OSX client machines to provide authentication services
Creating users with a remote home directory
True graphical login (NOT screen sharing) a la Xwindow on the machine that has your actual environment.
Other ways of exploiting the presence of Airport Express as a home server
It is just a pain having things duplicated (even synced using .mac) with user accounts (each of which can have a life of its own) on every single machine in the house. Besides, there is stuff (e.g., /Developer/, /Library/WebServer/ and other system configs) that lives outside user directories.
My question is: would you consider providing documentation on these issues on DIYMcSrvr?
I don't have any experience in using OS X Server and don't know exactly how that component works. But as far as I can tell it looks a lot like a LDAP server. LDAP servers are available as open source so that shouldn't be a problem, add a GUI tool to administer it and you are almost there. The mail serup in DIYMacServer is able to use LDAP as well. I haven't found any info on how to use that in the client as well.
I however am no expert on LDAP, iI've dabbled with it last year but burnt my fingers on it. But if someone is willing to help set it up and help me learn it I'm very willing to add it to the documentation set.
Thisis valid for all usefull technologies currently not availble here. If someone wants to help to add more I'm more than willing to accomodate. There is still room for improvement! ;-)
16 Jun 2008
At least one of the following features is sorely needed on home networks, without the need to run OSX server.
I suspect that all the machinery is in place on OSX client, just not in your face thru the GUI. Moreover, some of these solutions would be a good introduction for IT people to get their hands dirty before introducing OSX server at work.
It is just a pain having things duplicated (even synced using .mac) with user accounts (each of which can have a life of its own) on every single machine in the house. Besides, there is stuff (e.g., /Developer/, /Library/WebServer/ and other system configs) that lives outside user directories.
My question is: would you consider providing documentation on these issues on DIYMcSrvr?
16 Jun 2008
I don't have any experience in using OS X Server and don't know exactly how that component works. But as far as I can tell it looks a lot like a LDAP server. LDAP servers are available as open source so that shouldn't be a problem, add a GUI tool to administer it and you are almost there. The mail serup in DIYMacServer is able to use LDAP as well. I haven't found any info on how to use that in the client as well.
I however am no expert on LDAP, iI've dabbled with it last year but burnt my fingers on it. But if someone is willing to help set it up and help me learn it I'm very willing to add it to the documentation set.
Thisis valid for all usefull technologies currently not availble here. If someone wants to help to add more I'm more than willing to accomodate. There is still room for improvement! ;-)