[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Wine and Linux termincal services
Thank you Bert,
I will take what you did and test the system from here.
Thanks again.
I will keep the list informed of the progress.
Scott
Bert Obbink wrote:
> Scott Van Singel wrote:
>
> > Bert,
> >
> > It is good to see other people trying the same stuff. If you could point me in the right direction I will test them here at my work.
> > I went to LTSP.org and downloaded some files (not sure what I needed). I will try to work with that.
> > If you can tell me what Programs you are using, I will use the same and see if we can get this project done together.
> >
> > Thank you,
> >
>
> Scott, I will try to explain what I did so far. I will use a very direct way of writing to keep it short.
>
> I collected the following rpm's
>
> lts_core-2.07-0.i386.rpm
> lts_kernel_all-2.2-0.i386.rpm (supports most network drivers)
> lts_xagx-2.0-1.i386.rpm AGP video cards
> lts_xs3-2.0-1.i386.rpm S3 video
> lts_xs3v-2.0-1.i386.rpm S3
> lts_xvga-2.0-1.i386.rpm vga
> lts_xvga16-2.0-1.i386.rpm vga 16 color
> and
> etherboot-4.6.12.tar.gz
> etherboot-4.7.23.tar.gz
>
> I installed core and kernel:
> rpm -i –force lts lts_core-2.07-0.i386.rpm
>
> While installing it states what kind of Linux you are using, mine is SuSE 7.1
> The rpm creates a /tftpboot directory which is going to serve as a root for your clients.
>
> go to /tftpboot/lts/templates and start the ltsp_initialize script. You must start it with ./ !
> The scripts asks you al lot of questions about NFS. Just follow the guidelines.
>
> I use DHCP as a boot server. Cause I already had a dhcp server running I used that one as primary DHCP and forwarded it get the clients
> kernel from an other system, called boot server.
>
> The primary dhcp ip address: 100.10.10.72, the boot server is at 100.10.10.74
>
> Note: there maybe a bug in one of the scripts. It is possible that you have to add a directory by hand. Go to
> /tftpboot/lts/ltsroot/etc/X11/lib and make a directory xkb.
> Go to /tftpboot/lts/ltsroot/usr/X11R6/lib/X11 and make a link from xkb to /tftpboot/lts/ltsroot/etc/X11/xkb.
> Type ln -s xkb /etc/X11/xkb !!!!
> Cause the client finds his root after booting at /tftpboot/lts/ltsroot the link points to its own local etc !!!!
>
> DHCP server config file:
>
> ####################### begin of dhcpd.conf@bootserver ##################
> # Sample configuration file for ISCD dhcpd
> #
> # Don't forget to set run_dhcpd=1 in /etc/init.d/dhcpd
> # once you adjusted this file and copied it to /etc/dhcpd.conf.
> #
>
> default-lease-time 21600;
> max-lease-time 21600;
>
> option subnet-mask 255.255.255.0;
> option broadcast-address 100.10.10.255;
> #option routers 100.1.010.254;
> option domain-name-servers 100.10.10.72, 100.10.10.81;
> option domain-name "intern.kalamazoo.nl";
> option root-path "/tftpboot/lts/ltsroot";
>
> shared-network WORKSTATIONS {
> subnet 100.10.10.0 netmask 255.255.255.0 {
> }
> }
>
> group {
> use-host-decl-names on;
> option log-servers 100.10.10.74;
>
> host ws001 {
> hardware ethernet 00:A0:72:48:8D:B2;
> filename "/tftpboot/lts/vmlinuz.all";
> fixed-address 100.10.10.142;
> server-name "ws001.intern.kalamazoo.nl";
> #option routers 100.10.10.74;
> }
> host ws002 {
> hardware ethernet 00:60:33:90:1C:74;
> filename "/tftpboot/lts/vmlinuz.all";
> fixed-address 100.10.10.104;
> server-name "ws002.intern.kalamazoo.nl";
> #option routers 100.10.10.74;
> }
> host ws003 {
> hardware ethernet 00:80:12:89:31:76;
> filename "/tftpboot/lts/vmlinuz.all";
> fixed-address 100.10.10.102;
> server-name "ws003.intern.kalamazoo.nl";
> #option routers 100.10.10.74;
> }
> }
> ################### end of dhcpd.conf@bootserver #################
>
> If you have already a dhcp server running, you can add your boot servers dhcp by adding a line as:
>
> host ws005 {
> hardware ethernet 00:D0:67:09:BD:68;
> fixed-address 100.10.10.12;
> next-server 100.10.10.74; ## this is the "boot server"
> }
>
> It basically states to get more dhcp info from "next server"
>
> Install rpm -i –force lts_kernel_all-2.2-0.i386.rpm
> Install the video rpm's.
>
> Take a look at /tftpboot/lts/ltsroot/etc/lts.conf. I holds the lts configuration.
>
> ################### begin of lts.conf@bootserver #######################
> # Config file for the Linux Terminal Server Project (www.ltsp.org)
> #
>
> [Default]
> SERVER = 100.10.10.74
> XSERVER = XF86_S3
> X_MOUSE_PROTOCOL = "PS/2"
> X_MOUSE_DEVICE = "/dev/psaux"
> X_MOUSE_RESOLUTION = 400
> X_MOUSE_BUTTONS = 3
> USE_XFS = N
> LOCAL_APPS = N
> LOCAL_WM = N
> UI_MODE = GUI
>
> #------------------------------------------------------------------------
> #
> # Example of specifying X settings for a workstation
> #
> [ws001]
> XSERVER = XF86_S3
> #X_RES_1 = 800x600
> X_RES_1 = 1024x768
> X_HORZSYNC = 31-64
> X_VERTREFRESH = 55-85
> X_MODE_800x600 = 31.5 640 656 720 840 480 481 484 500
> #X_MODE_1024x768 = 31.3 1024 1048 1184 1328 768 771 777 806
>
> [ws002]
> XSERVER = XF86_SVGA
> X_RES_1 = 800x600
> X_HORZSYNC = 31-64
> X_VERTREFRESH = 55-85
> X_MODE_800x600 = 31.5 640 656 720 840 480 481 484 500
>
> [ws004]
> XSERVER = XF86_VGA16
> X_RES_1 = 640x480
> X_HORZSYNC = 31-64
> X_VERTREFRESH = 55-85
>
> ####################### end of dhcpd.conf@bootserver ##################
>
> You need to take care of the proper X_MODE_800x600 lines to get the display right.
>
> Install the video rpm's. Make sure they are placed in /tftpboot/lts/ltsroot/ltsbin.
>
> Untar the etherboot package. I used the older version, don;t know why. Cd into the etherboot directory and build the package. Cd src and
> type make. You have than many boot packages available. I you want to make a boot floppy go to the src directory and type make bin32/<your
> package>.fd0
> e.g. make bin32/eepro100.fd0. Have a writeable floppy in your drive, a boot image is placed on it directly.
>
> Put this floppy into a machine you want to boot and boot it. It should get a kernel from the boot server. If you X does not work properly
> than change the default run level in /tftpboot/lts/ltsroot/etc/inittab. It is the inittab the client uses.
>
> Add a "5: to the line I put "gives you a shell behind ... ". Enter ctrl-alt-f1 to go to a shell, and view your "virtual
> environment".ctrl-alt-f2 brings you back. Don't forget to remove it when you're ready and let students use your clients.
> ############### start of inittab @ .../ltsroot@bootserver ##################
> # initdefault can be '3' or '5'
> #
> # '3' to bring up the shell
> # '5' to bring up X-Windows or telnet (depending on UI_MODE)
> #
> id:5:initdefault:
> si::sysinit:/bin/sh /etc/rc.local
> #
> 1:35:respawn:/bin/sh -login ## < gives you a shell behind ctrl-alt f1
> #
> 2:2:respawn:/sbin/mingetty tty1 --noclear
> 3:2:respawn:/sbin/mingetty tty2
> #
> 4:5:respawn:/bin/sh /tmp/start_ws
>
> ############### end of inittab @ .../ltsroot@bootserver ##################
>
> If your client computer is running windows right now you can find its hardware address by running winipcfg.
>
> That's basically what It did so far. I did fiddle with some configs after I had the basis running, but thats was not really important.
> Just to understand the basics.
>
> Happy Fiddling
>
> Bert.
--
Scott Van Singel
Technology Director
Sturgis Public Schools
216 Vinewood
Sturgis, MI. 49091
Office: (616) 659-1512
Fax: (616) 651-1571
Email: svansingel@sturgis.k12.mi.us