kdesktopfollowed by return. This manual invocation works, and the KDE system then comes up normally. I am puzzled by what causes it, and do not see it under VMware with kernel 2.6, or on my test laptop. It is however present on the dvd when the iso is burned.
knoppix lang=usat the dvd prompt for the newer kernel (and
linux26is equivalvent); simply hitting return hangs the boot process. For the openMosix-enabled 2.4.27 kernel, type
linux24. We need to fix this in the isolinux.cfg file. Now fixed in 0.7.9.2.
KDE konsolelooks odd as the tree of process cannot be displayed. This works in
xterm. Probably a fonts issue. Fixed in 0.6.9.1.
o openMosix autodiscovery In my tests last night, two machines were not 'seeing' each other out of the box using autodiscovery. Following a hint at http://howto.ipng.be/openMosixWiki/index.php/FAQ I opted for a quick four-step correction: 1) edit /etc/hosts and a) remove the 'Knoppix' entry from the localhost definition and b) add a new entry for the hostname Knoppix with the actual (dhcp-provided) ip address, i.e. change the file to 192.168.1.100 Knoppix 127.0.0.1 localhost 2) edit /etc/default/openmosix.config and set/uncomment AUTODISC=0 to turn autodiscovery off 3) edit /etc/openmosix.map and define a simple three machine cluster via an entry 1 192.168.100.3 4) finally force a restart of openMosix via (as root) /etc/init.d/quantian-openmosix restart After doing that on all three machines, and starting 'openmosixview' as root then shows all machines and a test migration of a few Monte Carlo simulations worked without a glitch. I'd would welcome suggestions from those more familar with openMosix and autodiscoveryThis was fixed in 0.4.9.4 and 0.4.9.5 by explicitly configuring the eth0 interface.