It has been reported by others and by myself that mc and mcedit tend to freeze the system. I found empirically that by killing gpm things are better. Recently, I refurbished an old 486 DX/2 and installed a SuSE 5.1 distro on it. mc worked perfectly to start with (with and without gpm). But when I configured eth0 and started the network, the problems with mc and mcedit showed their ugly face. Moreover, I observed that starting mc does not really freeze the machine in a definitive way - if I waited a minute or so, the mc display would come in and I could work again with this system. The behaviour is totally reproducible (desactivating the network eliminates the problem, reactivating it brings it in again). This is the point where I arrived with this. I wonder what is the exact explanation. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/