[K12OSN] K12LTSP-4.2.0-Beta2 upgrade

[Jesse McDonnell]

I've upgraded my home K12LTSP-4.0.1-1 server to K12LTSP-4.2.0-beta2.  In the past, I've installed the "upgrades" onto a new partition. This time I did the real thing.  The upgrade is very slick and gnome feels faster on my intel p-90 client (onboard virge s3 and eepro100tx nic) than icewm was under 4.0.1. Very impressive!  Thanks Eric and Jim and all the other contributors to this wonderful project.  Unfortunately, the I-openers in my kids' rooms are a different story and I'll get into that below.  

There was one hiccup during the install. I was using LILO to boot 4.0.1. During the install I choose grub as the bootloader to be installed on the partition (/dev/hdb4) where the new kernel/4.2.0 was being installed over 4.0.1. The install proceeded without error but when it rebooted I still had the old boot options. Tried rebooting and doing an upgrade a couple of times choosing to install grub in /dev/hdb4 and /dev/hda. Neither worked and I ended up adding the new kernel to lilo.conf and re-running lilo manually. 

Now the problem - the i-openers don't get along with nfs anymore. They boot a home-rolled 2.4.21 nfs-swap patched kernel from flash and connect to the network via a linksys usb100tx adapter. They get an ip address and then hang "doing the pivot_root."  tail -f /var/log/messages shows that dhcp passes the address (192.168.0.6) , the mount request for /opt/ltsp/i386 is authenticated .....and that's as far as it gets. 

 tcpdump shows that packets are being fragemented and "ip reassembly time exceeded." The output of "tcpdump -i eth0 | grep ws006.ltsp" is below. This happens with the 2.4.21 kernel and another earlier kernel without nfs-swap both of which worked well with earlier versions of ltsp. 

I played around with hardware (different cat5 cables, different ports on the switch etc.) and replaced the nfs-utils and system-config-nfs rpms with earlier versions but the problem remains. Does the nfs daemon that comes with fc3 run over tcp/ip? Where are the rsize and wsize values of the exported /opt/ltsp/i386 set?  I grepped and found the mount parameters for the swapfiles in rc.sysinit but I cannot track them for the root directory. I'm hoping that adjusting these will allow me to get over this hurdle. 

Thanks!

Jesse McDonnell

tcpdump - i eth0 | grep ws006.ltsp output:

19:37:45.528349 arp who-has ws006.ltsp tell server.ltsp
19:37:45.529239 arp who-has server.ltsp tell ws006.ltsp
19:37:45.530572 arp reply ws006.ltsp is-at 00:e0:98:7e:f6:02
19:38:10.553564 IP ws006.ltsp > server.ltsp: icmp 556: ip reassembly time exceeded
19:42:34.966351 arp who-has server.ltsp tell ws006.ltsp
19:42:34.968422 IP ws006.ltsp.1420885366 > server.ltsp.nfs: 112 read [|nfs]
19:42:34.968843 IP server.ltsp.nfs > ws006.ltsp.1420885366: reply ok 1472 read
19:42:34.968861 IP server.ltsp > ws006.ltsp: udp
19:42:34.968868 IP server.ltsp > ws006.ltsp: udp
19:42:34.968874 IP server.ltsp > ws006.ltsp: udp
19:42:34.969012 IP server.ltsp > ws006.ltsp: udp
19:42:34.969132 IP server.ltsp > ws006.ltsp: udp
19:42:34.969260 IP server.ltsp > ws006.ltsp: udp
19:42:34.969388 IP server.ltsp > ws006.ltsp: udp
19:42:34.969515 IP server.ltsp > ws006.ltsp: udp
19:42:34.969643 IP server.ltsp > ws006.ltsp: udp
19:42:34.969770 IP server.ltsp > ws006.ltsp: udp
19:42:34.969897 IP server.ltsp > ws006.ltsp: udp
19:42:34.970033 IP server.ltsp > ws006.ltsp: udp
19:42:34.970162 IP server.ltsp > ws006.ltsp: udp
19:42:34.970288 IP server.ltsp > ws006.ltsp: udp
19:42:34.970402 IP server.ltsp > ws006.ltsp: udp
19:42:34.970531 IP server.ltsp > ws006.ltsp: udp
19:42:34.970658 IP server.ltsp > ws006.ltsp: udp
19:42:34.970785 IP server.ltsp > ws006.ltsp: udp
19:42:34.970912 IP server.ltsp > ws006.ltsp: udp
19:42:39.967590 arp who-has ws006.ltsp tell server.ltsp
19:42:39.971064 arp reply ws006.ltsp is-at 00:e0:98:7e:f6:02
19:43:04.970435 IP ws006.ltsp > server.ltsp: icmp 556: ip reassembly time exceeded