Re: Misc issues/problems with installation of latest debian-edu sarge cd
Konstantinos Margaritis wrote:
> I'll go straight to the point:
>
> 1. .X11-unix and .ICE-unix take too long to initialize at boot time, I
> don't know why, there doesn't seem to be much disk activity any
> ideas?
Does this happen every time you log in, or only the first time for every
user ?
> 2. Well, this was actually fixed with the help from Finn-Arne, but I
> thought i'd mention the fix, in case someone else has the same setup.
> Basically, the school doesn't use 10.0.2.1 to connect to the
> Internet, and there is no router as all schools in Greece are
> connected to a central school network which uses the 10.x.x.x
> netgroup. So I had to follow the dummy ethernet device trick.
> But, as the DHCP server from the school network also adds entries to
> the resolv.conf, following Finn-Arne's advice, I had to:
> a) install resolvconf package
resolvconf is installed by default as of today
> b) add the following entries to /etc/network/interfaces:
> auto dummy0
> iface dummy0 inet static
> address 10.0.2.2
> netmask 255.255.254.0
> broadcast 10.0.3.255
> dns-nameserver 10.0.2.2
> dns-search interno
I think maybe this setting would be better:
auto dummy0
iface dummy0 inet static
address 10.0.2.2
netmask 255.255.255.255
(you wont find any other machine on the dummy0 interface)
> That fixed everything.
Good.
> 3. All LTSP clients used serial mice, so I had to edit the LTSP
> configuration file /opt/ltsp/i386/etc/lts.conf (which doesn't exist
> by default, maybe we should add a template file and just comment
> everything out for the user to fill?) and add the following lines:
>
> [Default]
> USE_XFS = Y
> X_MOUSE_PROTOCOL = "Microsoft"
> X_MOUSE_DEVICE = "/dev/ttyS0"
>
>
> 4. Screen resolution for the LTSP clients. I couldn't find any info on
> that in any configuration file I searched. I tried adding the
> following line to /opt/ltsp/i386/etc/lts.conf but it didn't work:
> X_MODE_0 = 1024x768
I've looked in /opt/ltsp/i386/etc/init.d/ltsp-client-setup, and it seems
like X_MODE_0 is missing. I guess it would be easy to patch it in, but
even easier would be to create a separate XF86Config-4 file for the
client(s).
It will also speed up the boot process a bit :)
> 5. frequent NFS stalls. This is probably the most serious problem. On
> the same 100Mbps network of 12 lowend LTSP clients on a switch and a
> beefy server, previous installation of Skolelinux (old generation of
> LTSP packages) was quite fast in booting and loading applications.
> Now, I get quite frequent messages:
> NFS server 192.168.0.254 does not respond, still trying (or similar, I
> am not in the lab right now).
Could it be a locking issue ?
Check if the client is using locking on the server ..
> One of the teachers informed me that after 2 hours of waiting only 3
> of the 12 LTSP clients booted and he had to reboot them one by one
> manually afterwards.
> I cannot explain why this is happening, Finn-Arne suggested that the
> new LTSP packages consume much more network resources than previous
> versions, but it seems too much of a slowdown -if it can be called
> that- for me. I tried checking for lost interrupts
> in /proc/interrupts, just in case there is a buggy ethernet driver in
> the kernel, but to no avail. Any ideas that I could check?
I just checked on one of my lessdisks clients, this is options used for
the rootfs:
ro,v3,rsize=32768,wsize=32768,hard,udp,nolock,addr=10.0.2.10
(reported by issuing mount on the booted client)
> On the same issue of NFS, I also noticed that all NFS mounts are done
> without setting rsize/wsize to 8192. AFAIK, using these settings is
> recommended for better performance, is there a reason they are not
> set? I did try to set them but I failed to find the configuration
> file to set them up (I thought they'd be in /opt/ltsp/i386/etc/fstab
> but they were not :-/). Any ideas on this also?
The root fs for the clients are mounted from the initrd
>From the conf-file, it looks like it's using these options
ro,async,nolock
It looks like that is the same options that were used by lessdisks as
well (they both use the same tool, but different versions)
> 6. Xkb Keymap switching on the LTSP clients.
> It just works fine now right out of the box, thanks to the NG LTSP
> packages which don't include the problematic XF86 3.x, which means I
> can and will suggest Skolelinux to be installed to the Greek schools,
> I waited for this moment a long time and I'm so happy, I'll let you
> know about this! :-)
>
> 7. Translation for ldm. It doesn't appear to be translatable, at least
> I couldn't find a .pot file for it. Is it planned to be translated?
I dont know of any plans, but I can confirm that it's not translated to
norwegian neither :(
--
Finn-Arne Johansen
faj@bzz.no http://bzz.no/
Leverandør av support på, drift og videreutvikling av Skolelinux-løsninger
Reply to: