Linux Users stored on an OpenBSD server?

[Hypoon]

I mentioned this in another post, but it didn't get much publicity so I'll ask it more directly here. In Windows you can set up a domain server and store user profiles on that server. Then you can set up other Windows machines to be able to log in using the user profiles stored on the server. My question, is how do you do this so that the Server is running OpenBSD, and all the other machines are running Linux?

[genesus]

I found this online. Its not exactly a walkthrough; however, with what it says it shouldn't take you too long to figure out. Basically, obsd server and linux thin clients. You won't really have to go through all of the setup that you would with an xp domain server. You basically just use ssh and login to your profile on the server.

Personally, I've really enjoyed OpenBSD, despite numerous naysayers

I've actually used OpenBSD as an LTSP server. The clients are web
terminals used in a library to view the card catalog. It was slightly
more hassle to set up than a standard installation that uses Linux, but
once everything was configured it worked beautifully. If you want my
installation notes on the process i would be happy to send them
privately (to avoid list clutter) on request.

My setup was with the clients configured to run everything locally
(using the server simply as a filesystem). I did a bit of experimenting
running applications on the OpenBSD server and having them display on
the Linux clients. I was able to get it to work by displaying the
application through an SSH tunnel. Unfortunately, the clients i was
using (LTSP Jammin-125, an older model they don't seem to sell anymore)
were a bit too slow to perform well while handling all the SSH
encryption. Someone who understands X11 configuration better than i
should be able to set it up without needing the SSH tunnel which would
probably have made it fast enough to be useable.

[Hypoon]

That sounds cool, but it's not quite what I'm looking for. What you mentioned sounds as though you might as well be running Unix on the client machines as well. I'm talking about running Linux on the client machines, and the server just simply stores the user settings, to be accessed and applied upon login on one of the client machines. Sorry, it's kind of hard to explain. Here's a different perspective... You boot up one of the computers, and you'd get a client screen where you enter your username and password and log on with all your settings and etc... That's exactly what I want except if you change a setting on one client, next time you log on from another computer I want the change to have taken effect on that computer as well. It's still not really clear what I'm trying to say, but I hope that makes it a bit more understandable. Linux clients are the key things though, and I figure that the server running Unix makes it all the more complicated.

[cipherus]

LDAP has this functionality

[Hypoon]

Good, good. That'll probably be what I use...