On Saturday 17 August 2002 07:01, Stew Benedict wrote: For me this is a most exciting development from mdk, my favorite flavor, they seem to have the most intuitive ways and utilitys for setting up linux services. Wich is most bennificial to budding administrators like me.
within two weeks I will be building up a new terminal server, based on a dual athlon mobo, I will develop this server based on mdk9.0 so plan on lots of feedback from me. Once it is well hardened I will be replacing our aging dual xenon 450 terminal server. where did cluster nfs come from? this is the first I have heard of it, and it sounds like a much better way of handeling things than is common amongst those on the LTSP.org mail list and project. Where can I find more documentation on it? in your simple case did you have the automounter functioning? > On Sat, 17 Aug 2002, Brent Hasty wrote: > > I am looking forward with great anticipation to the integration of Linux > > Terminal Server service being added to 9.0. > > I'd be happy to see more feedback :) > > > A few questions: > > with the clients/terminals be able to have local devices like cd and fd0 > > functioning locally? > > Yes. You boot the kernel on the client machine, so the hardware seen is > that machine's hardware. The trick is the mount points. Terminal-server > provides /etc/fstab$$CLIENT$$ which is what the client machines see for > mount points. I just tried the simple case, adding standard cdrom and > floppy entries to this file, and making client mount points: > > -bash-2.05b$ ls -l /mnt/ > total 44 > drwxr-xr-x 2 root root 4096 Jul 23 03:06 cdrom/ > drwxr-xr-x 2 root root 4096 Aug 17 09:38 cdrom$$CLIENT$$/ > drwxr-xr-x 2 root root 4096 Aug 17 09:47 floppy$$CLIENT$$/ > > -bash-2.05b$ grep supermount /etc/fstab\$\$CLIENT\$\$ > none /mnt/cdrom supermount > fs=iso9660,dev=/dev/cdrom,--,codepage=850,iocharset=iso8859-1,ro,nosuid,uma >sk=0,nodev,exec 0 0 > none /mnt/floppy supermount > fs=vfat,dev=/dev/fd0,--,codepage=850,iocharset=iso8859-1,nosuid,umask=0,unh >ide,nodev 0 0 > > For multiple clients, I suspect you'll want to replace > /mnt/cdrom$$CLIENT$$ with /mnt/cdrom$$client-ip-address$$, so everyone is > not trying to use the same mount point. > > I'll add this basic case to the terminal server package. > > > ie: useres will not be running thier cd's to the administrators office, > > and will simply be able to insirt them into the drives included in thier > > terminal hardware? > > > > How about local sound? > > Yes, through the clusternfs use of the $$$CLIENT$$, each client machine > can have their own config files, so local sound should be able to be > setup. > > > Usb mice? > > Shouldn't be an issue. I'm using serial on this machine, but on PPC it's > mostly USB, and they're treated about the same. > > > Usb periferials like scanners? > > Should get mostly the same behaviour as the normal system. You may have to > do some manual config for the client, possibly. The problem you run into > is the server root fs is readonly, for some degree of security, so you > can't create client configs on-the-fly, sitting at the client machine. > > BTW - your mailer munged the Reply-To > > Stew Benedict -- "The place of the material world in the universe is that of an exquisitely beautiful precipitate or varied cloud-work in the universal Ęther, determined by a geometrical necessity...." ~ Professor John G. Macvicar1870 ~ Brent Hasty http://www.Hasty-Solutions.com
