[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[K12OSN] K12LTSP 4.2 beta 7



Following my email of 6-Dec, I've made a "clean install" of 4.2 beta 7. 
It duly swapped over my eth0 & eth1, which could be a problem if eth0
were an on-board Gigabyte port, but it's OK on this system.

Copied /var/named/chroot over to my upgraded system, along
with /etc/named.conf. Presto! both thin and thick clients connect OK.
Must have put something out when I messed around with eth0 & eth1 first
time around.

I'm still puzzled by Evolution's calendar. It's working OK again, but
definitely refused to appear on at least two occasions, despite a good 5
minutes' wait.

So moving back to "in-house production mode".

Many thanks for all the hard work. FC3 has lots going for it.

Regards,

John Ingleby
************

-------- Forwarded Message --------
From: John Ingleby <john coronet co uk>
To: k12osn redhat com
Subject: K12LTSP 4.2 beta & FC3
Date: Mon, 06 Dec 2004 18:06:43 +0000
Sadly I've decided to revert to our 3.1.2 office network after using
the 4.2 beta for a weekend or so. Firebird and Evo 2 are lovely to
work with but we found three problems which I've been unable 
to resolve in spite of much Googling and bug searching:

1. PCs attached to the LTSP network wouldn't connect to the Internet,
   although the thin clients worked just fine. Could this be related 
   to the upgrade to BIND 9? - because I couldn't find some DNS zone 
   files that are present in 3.1.2 in the "jailed" /var/named. Or 
   perhaps 3.1.2 just tolerates problems in my DNS setup that I'm not
   aware of.

2. FC3 was determined to switch eth0 (on the motherboard) and eth1 
   (an older BNC-terminated PCI card), and in the end I had to 
   "force" the assignment by rebooting the server with eth1 removed. 
   Modifying /etc/modprobe.conf or /etc/sysconfig/hwconf has no effect.

3. Evolution 2 "lost" my calendar after rebooting. I did wait for it, 
   thinking it might be the kind of delay that others have mentioned, 
   but it never reappeared.

If anyone has heard of solutions for these, I'd love to know, because 4.2
is shaping up to a really impressive system.

John Ingleby
************



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]