Linux Terminal Server Project (LTSP)

Hi ltsp-discuss

I have resolved my setup problem as reported below by adding the workstation
entries (i.e. ws001 192.168.0.1, etc..) to the /etc/hosts file on my Linux
server.

Thanks for all the help

Ian Hadley
Sydney, Australia
  -----Original Message-----
  From: Ian Hadley [mailto:ianh@...]
  Sent: Thursday, 4 July 2002 12:27 PM
  To: Ltsp-Discuss (E-mail)
  Subject: XServer Security Problem


  Hi ltsp-discuss

  I am having a problem with my pilot of LTSP (Version 3.0.4) running on Red
Hat 7.2.

  My server is running and appears to comply with the troubleshooting guides
however I am still having a problem with connecting to either Gnome or KDE.
I have reinstalled using different X Servers etc to no avail.  (Server is
P2-300 MMX with 256 MB RAM and 8 GB IDE disk, Intel EPro 10/100 network and
Rage IIC display controller (Intel LX chipset on the motherboard).

  I can boot a diskless PC and connect to the LTSP Server using the RUNLEVEL
3 option, BUT when I run /tmp/start_ws the Grey Screen appears with large X.
The X can be moved about with the mouse. (My diskless PC is AMD K6-2/450
with 256 MB RAM, 3Com 3C905TXM booting from floppy disk (i.e. not quite
diskless) the display controller is a NVIDIA Vanta with 16 MB Ram).

  Sometime later, two to three minutes or so I get the remains of the
XFree86.0.log error messages which includes the following.

   =====================================================
   Audit : wed jul 3 02:56:23 2002 : 391 XFree86: Client 1 rejected from IP
192.168.0.254 port 32783 Auth name : MIT-MAGIC-COOKIE-1 ID : -1

  Audit : wed jul 3 02:56:23 2002 : 391 XFree86: Client 1 rejected from IP
192.168.0.254 port 32784 Auth name : MIT-MAGIC-COOKIE-1 ID : -1

   Audit : wed jul 3 02:56:23 2002 : 391 XFree86: Client 1 rejected from IP
192.168.0.254 port 32785 Auth name : MIT-MAGIC-COOKIE-1 ID : -1

  Fatal Server Error :

   XDMCP Fatal Error : Session failed session 49494949494 failed for display
192.168.0.254:0 cannot open display

   ======================================================

  I saw that Stanley from Indonesia had a similar problem on the 24th June
2002.

  Can anyone assist me with solving this problem??????

  Many thanks in advance

  Ian
  Sydney, Australia

I continue to fumble my way around this system, trying to build my own
nbi kernel.  Can anyone send me a 'make xconfig' config file, and a note
of exact mknbi-linux options to build an nbi kernel on RH7.3.... I can
just about manage to select the right NIC, but the best I have got so
far is to boot up to 'unable to mount root fs'.

Shane

I am looking for a good way to access my local devices on my ltsp client.=
  I=20
am using ltsp to install software on client systems.  The idea is that I =
can=20
take the client system, plug it in, hook it up to my lan, and turn it on =
and=20
ltsp and a few scripts will do everything I need.

Part of the setup is formatting a blank hd in the client system.  I'm loo=
king=20
for ways to access the hard drive on the client system to first format it=
,=20
then copy over the system files I will need, then install GRUB or LILO on=
 it.

I'm currently reading through the documentation on ENBD, but I'm confused=
=2E =20
When I set up a box using LTSP, the box booting is the client and the one=
=20
supplying all the LTSP info and kernel is the server.  I'm not sure, but =
it=20
seems to me that once I get this running, since the drive I want to acces=
s is=20
on the client, for the purposes of ENBD ONLY, the client is the server.

Have others used ENBD?  Is this the only way or best way to access local=20
devices?  Can I use ENBD to be able to format the drives in the client=20
system?

Thanks!

Hal

Anyone building their own compact boxes.....
Yahoo have ENP-0615B's on-sale for $26 !!


Shane

Hi ltsp-discuss

I am having a problem with my pilot of LTSP (Version 3.0.4) running on Red
Hat 7.2.

My server is running and appears to comply with the troubleshooting guides
however I am still having a problem with connecting to either Gnome or KDE.
I have reinstalled using different X Servers etc to no avail.  (Server is
P2-300 MMX with 256 MB RAM and 8 GB IDE disk, Intel EPro 10/100 network and
Rage IIC display controller (Intel LX chipset on the motherboard).

I can boot a diskless PC and connect to the LTSP Server using the RUNLEVEL 3
option, BUT when I run /tmp/start_ws the Grey Screen appears with large X.
The X can be moved about with the mouse. (My diskless PC is AMD K6-2/450
with 256 MB RAM, 3Com 3C905TXM booting from floppy disk (i.e. not quite
diskless) the display controller is a NVIDIA Vanta with 16 MB Ram).

Sometime later, two to three minutes or so I get the remains of the
XFree86.0.log error messages which includes the following.

 =====================================================
 Audit : wed jul 3 02:56:23 2002 : 391 XFree86: Client 1 rejected from IP
192.168.0.254 port 32783 Auth name : MIT-MAGIC-COOKIE-1 ID : -1

Audit : wed jul 3 02:56:23 2002 : 391 XFree86: Client 1 rejected from IP
192.168.0.254 port 32784 Auth name : MIT-MAGIC-COOKIE-1 ID : -1

 Audit : wed jul 3 02:56:23 2002 : 391 XFree86: Client 1 rejected from IP
192.168.0.254 port 32785 Auth name : MIT-MAGIC-COOKIE-1 ID : -1

 Fatal Server Error :

 XDMCP Fatal Error : Session failed session 49494949494 failed for display
192.168.0.254:0 cannot open display

 ======================================================

I saw that Stanley from Indonesia had a similar problem on the 24th June
2002.

Can anyone assist me with solving this problem??????

Many thanks in advance

Ian
Sydney, Australia

...
> 
> Now would my DHCPD.CONF on the firewall shouldbe looking like the following
> ?
> 
> 
> #------------------------------------------------------------
> subnet 192.168.1.0 netmask 255.255.255.0
> {
>     option broadcast-address    192.168.1.255;
>     deny bootp;
>     option domain-name  "digl.dnsalias.com";
>     option domain-name-servers  192.168.1.1;
>     default-lease-time          86400;
>     max-lease-time              604800;
>     option netbios-dd-server    192.168.1.1;
>     option netbios-name-servers 192.168.1.1;
>     option netbios-node-type    8;
>     option subnet-mask          255.255.255.0;
>     range    192.168.1.65 192.168.1.250;
>     option routers 192.168.1.1;
> }
> host icue5 {
>         hardware ethernet 00:d0:09:27:67:55;    <---- Who's MAC address is
> this? LTSP server or workstation??
>         fixed-address 10.171.13.5;   <---- Who's IP address is this? LTSP
> server or workstation??
>         allow bootp;
>         server-name "pc65.digl.dnsalias.com";     <<------   LTSP MAchine?
>         next-server 192.168.1.65;                             <<------
> LTSP MAchine?
>         filename "/tftpboot/lts/vmlinuz-2.4.9-ltsp";
> }
> 
>
The only difference between running the dhcp server on the LTSP server vs running it on a separate server is the 'next-server' option. Without that option, dhcp assumes to tftp boot from the dhcp server.

You are on the right track here...but this may not yield the desired results. Since your option settings are all in your subnet declaration, your workstation (icue5) won't know anything about them. Try using the dhcpd.conf example supplied with ltsp or try this link and modify the example as required.
http://sourceforge.net/mailarchive/message.php?msg_id=1468998

Everything between the 'host icue5 {' and the next '}' applies to the workstation settings. So, the hardware ethernet is the workstation's mac address, the fixed address is the workstation's address, and the next-server is the LTSP server that you want the workstation to get the tftp boot from.

Oh yes, and make sure that your workstation fixed IP is not within the range of your subnet declaration...you don't want those overlapping.

You might want to make a copy of your existing dhcpd.conf file and then hack away. Remember that you need to restart the dhcp daemon after changes to the conf file. 

If you still run into problems, then re-send a current version of your dhcpd.conf file and we can try to help further.

cheers,
rob

> Well,  I've 
 > finally got off my butt and built new
 > LTSP kernel packages based on the 2.4.18 Linux kernel sources.
 > 
 > ...
 > 
 > Anyway, back to the kernel.  It's on the download page
 > now, and i've placed both the RPM and the TGZ packages there.
 > 
 > ...
 > 
 > Jim McQuillan
 > jam@...

I just downloaded the new kernel RPM: ltsp_kernel-3.0.4-0.i386.rpm
and tried to install it on my LTSP server (RedHat 7.3).
But it failed with:

# rpm -i ltsp_kernel-3.0.4-0.i386.rpm
error: unpacking of archive failed on file /opt/ltsp/i386/lib/modules/2.4.18-ltsp-1/kernel/fs/nls/nls_cp950.o;3d243957: cpio: MD5 sum mismatch

Has anybody else successfully installed this RPM under RedHat?

Horst

-- 
Horst Prote                   __o    Systemadministration Abt. FK und TI
Institut fuer Informatik    _`\<,_     prote@...
Universitaet Stuttgart     (_)/ (_)                Tel: +49 711 7816-348
Breitwiesenstr. 20/22, D-70565 Stuttgart           FAX: +49 711 7816-310

> The 'storage in the NIC where the PXE code resides, is, in fact an
> EEPROM, which is similar to 'FLASH'.  Really, it is an EPROM, that can
> be written to without removing it from the board....whether it is
> socketed, soldered on, or internal to the NIC controller is almost
> irrelevant.  A socketed one can be re-porgrammed in a PROM programmer
> without UV, as it is 'Electrically Erasable'.  Some uC programmers use
> them to test a program, as they can download each version of their
> program without removing, erasing programming, and replugging.  On
> slower systems, they use a ROM emulator, but on faster systems, the
> cable length introduces its own problems..

From a software person's POV, flash can be updated by software and even
treated like a sort of disk drive via an MTD driver. The rest can't.

> Having said all that, once the initial pxe load (eb-......lzpxe) has
> completed, can the client then do a 'normal' dhcp boot ?, or are there
> several stages to the process before the linux kernal can be loaded ?.

Once PXE has chained Etherboot, it's Etherboot and should behave just as
if you loaded Etherboot from ROM. Early on there were side effects of
using PXE on some systems, but no-one has complained recently.

Etherboot's PXE "support" does NOT use UNDI (the PXE nic independent
driver) or PXE DHCP and TFTP. Currently Etherboot unloads PXE, then
proceeds as normal: load nic driver, DHCP request, pull NBI...

If anyone feels motivated, adding PXE UNDI suport to Etherboot should be
quite straightforward, and this might be useful for sites which have
multiple nic types and a "PXE only" policy.

I figured it out. I read the actual ltsp setup file and I had the x_mode
wrong all along. I guess it really helps to read setup files before
thinking you can just wing it.

Thanks for the help.

Ken



On Tue, 2002-07-02 at 19:49, Ken wrote:
> In my lts.conf file I am using the mode lines I had in a working 2.08
> installation using the same client PC as I did on the old server,
> however the client is defaulting to the resolution of the server. Here
> is my lts.conf file. Let me know what I can change or what I'm doing
> wrong. Thanks
>=20
> [Default]
> 	SERVER             =3D 129.1.6.254
> 	XSERVER            =3D XF86_SVGA
> 	X_MOUSE_PROTOCOL   =3D "PS/2"
> 	X_MOUSE_DEVICE     =3D "/dev/psaux"
> 	X_MOUSE_RESOLUTION =3D 300
> 	X_MOUSE_BUTTONS    =3D 3
> 	USE_XFS            =3D N
> 	LOCAL_APPS         =3D N
> 	RUNLEVEL           =3D GUI
>=20
> #------------------------------------------------------------------------=
------
> #
>=20
> [cpacct]
>     X_RES_1         =3D 800x600
>     X_HORZSYNC      =3D 30-54
>     X_VERTREFRESH   =3D 50-120
>     X_MODE_800x600   =3D40 800 840 968 1056 600 601 605 628 +hsync +vsync
> #    X_HORZSYNC      =3D 31-62
> #    X_VERTREFRESH   =3D 55-90
> #    X_MODE_1024x768 =3D 75.00 1024 1048 1184 1328 768 771 777 806 -hsync
> -vsync
> #    X_MODE_640x480  =3D 25.17  640  648  744  784  480  482  484  509
> -hsync -vsync
>     RUNLEVEL        =3D 5
> #------------------------------------------------------------------------=
------
> #
>=20
>=20
> On Tue, 2002-07-02 at 13:11, Alessandro Selli wrote:
> > Il giorno 2 Jul 2002, Ken cos=EC ha scritto:
> >=20
> > |From: Ken <Kanderson8@...>
> > |To: LTSP List <ltsp-discuss@...>
> > |Date: 02 Jul 2002 06:15:03 -0700
> > |Subject: [Ltsp-discuss] lts.conf problem
> > |
> > |I'm having a resolution problem on my client terminal. It seems to be
> > |ignoring the lts.conf and opens up every time at 1024x768. I've added
> > |all the lines to  the lts.conf file to change it but nothing helps.
> >=20
> >   You should check the X server's startup messages.  Maybe the modeline=
s of
> > the resolutions you selected are found to be incompatible with the vide=
o card
> > you have and are discarded in favor of some other fallback modeline/res=
olution.
> >=20
> >=20
> >=20
> >=20
> >   Sandro
> >=20
> >=20
> >=20
> > --=20
> > Bellum se ipsum alet.
> >        La guerra nutre se stessa.
> >=20
> > Livio, "Ab urbe condita", XXXIV,9
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _____________________________________________________________________
> > Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
> >       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > For additional LTSP help,   try #ltsp channel on irc.openprojects.net
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> No, I will not fix your computer.
> http://thinkgeek.com/sf
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.openprojects.net

> The docs also mention that ISA cards MUST have the mod info specified o=
n the =

> kernel command line -- where is that configured in ltsp? =


Etherboot (or pxelinux) sets the kernel command line. Etherboot uses a
dhcp option, pxelinux tftps a config file.

Installed LTSP on  workstation - Compaq 4000 with 32Mb.
Running Redhat 7.2 on the Server. 
The workstation boots from floppy with no problem and login / opening 
programs is no problem. However when the cursor is moved the screen becomes 
unreadable.

Any assistance would be appreciated.

Kerry

FYI -- I found out I was booting with the 2.4.9 kernel -- in that kernal,=
 the=20
mod files are not in the /lib path, where linuxrc is looking for them.  T=
hey=20
are in the /usr/lib path.  I changed to use the 2.4.18 kernel, and it wor=
ks=20
perfectly now.


On Tuesday 02 July 2002 09:16 pm, Hal Vaughan wrote:
> Thanks to those who helped with the TFTPD problem -- it is working now =
and
> the kernal starts loading.  But there's another problem (so I thought I
> should create a new thread, since this is a different situation).
>
> Equipment: ASUS TUSI-M mobo, with SIS630 chipset and SIS900 chipset for=
 the
> built-in NIC.  I'm booting from a USB floppy, using a rom-o-matic image
> designed for a boot disk for my NIC chipset.  TFTP is now working just
> fine, but when the kernal is loading, it has trouble with the NIC mod. =
 I
> get: -----------------------------------------------------------
> /lib/modules/2.4.9-ltsp-6/kernel/drivers/net/sis900.o: insmod /lib/modu=
les
> /2.4.9-ltsp-6/kernel/drivers/net/sis900.o failed
> /lib/modules/2.4.9-ltsp-6/kernel/drivers/net/sis900.o insmod sis900 fai=
led
>
> ERROR!  Failed to install the NIC driver module!
> =09This could be caused by the wrong module for your particular
> =09network interface card.  Double check the 'option-129' entry
> =09in your /etc/dhcpd.conf file.
>
> Kernel panic:  Attempted to kill init!
> -----------------------------------------------------------
> (Yes, I get 2 error messages stating the insmod failed, the first inclu=
des
> the entire pathname, the second only the name.)
>
> On first try, the 'option-129' entry in the dhcpd.conf was commented ou=
t
> (as it was in the example I had.  I uncommented it and replaced the
> original text (about another NIC) with SIS900.  When it still failed, a=
nd I
> saw the error message was in lower case, I changed it to sis900, and it
> still won't load. I can't see this being the wrong module, since it
> corresponds to the boot image I'm using.
>
> So what's up with this?
>
> Hal
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> No, I will not fix your computer.
> http://thinkgeek.com/sf
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.openprojects.net