Hello As a new SuSE 5.3 user I have a few questions and observations. 1 I have a problem mounting my SuSE machine from RH4.1 Vanderbilt. Yes I will in due course load SuSE on that m/c but it needs a considerable hardware upgrade. The problem is that: mount -t nfs SuSE:/ /SuSEmnt ie mounting the SuSE root sytem onto a mount point on the RH system, enables me to do ls /SuSEmnt which gives all the SuSE root directories, as expected but ls -l /SuSEmnt or any other operation to look at the real files, gives a Permissions denied message. I have checked that the /etc/exports file on the SuSE m/c is mounted (rw,no_root_squash) and that root has UID and GID of zero(0) on both machines and everything else I can think of but to no avail. Mounting the other way round is not a problem. Any clues? I have posted a question on the Manchester mailing list, which contains some experts, but no solution has been forthcoming other than checking with showmount and rpcinfo etc. 2 I have a few observations re YaST. 2.1 One of the PC's which has SuSE 5.3 mounted had, it turned out, a dodgy hard disk and a sligtly flaky CD. With YaST, (whats this with capitals other than at the beginning of a word? From now on, it is yast and suse to save my little finger!) you cannot go into fdisk proper so I could not get into the disk system. You only have the opportunity to format the partition as native Linux and swap. I think this should be changed to allow the user to access fdisk, as the RH installation tool does. This also helped on another machine where the partitioning had to be changed but I couldn't repartition for MSDOS. 2.2 I had a number of cases (I think due to the CD) where an error -1 or worse -2 arose during installation. Yast (well you have to have a capital letter at the beginning of the sentence) just returns to the Start Installation and then tries to reinstall the failed package again. This does not exercise the CD and so the same occurs all over again. The solution I used was to restart completely but I think yast should (i) skip over a faulted package and collect them all for a final installation try at the end and (ii) provide a proper Back and Abort facility. The Abort does not work properly. 3 Someone posted that they were wondering what SuperSocket7 board worked. On a separate PC, which is actually dedicated to Windows at the moment, dispalyed via VNC on my susebox, I have 5.3 mounted OK. The board is a TX Pro 100 with an AGP slot, model M577, and 128Mb of 100MHz memory. I had problems with the AGP slot and so currently have an S3Virge card in it and I found that you needed to put the CD on IDE2 as master since the installation froze if it was a slave on IDE1. Since this motherboard comes in at 41UKP, it is a good bargain. I am running the AMD K6/II 350 Mhz chip quite OK on it. TIA for suggestions re 1 above John - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e