> Thanks, I have it setup that way now. Good. Logging in as root removes all protection from yourself and others - write access to destroy the whole system. From a normal user, damage is limited to the files the user has write access too (i.e. no damage can be done to prevent the system from booting), memory use, disk space, and network bandwidth/quota. Of course with a virtual machine, you can also copy the virtual disk file and recover from damage very quickly.
> Next project to sort out my network. I have read quite a few web pages on > how > to do this, but am still as confused as ever :-) I am not so much concerned > with this machine with VMPlayer, but my older machine that is purely suse > 10.1 now. I want it to connect to my xp machine. I am looking for a step by > step quide that makes sense. All the hardware is fine, just this samba stuff > I dont quite get and am confused about the different language used. It asks > for folder names etc and I have no clue what to type in. Edit /etc/samba/smb.conf and add the workgroup name as used on your xp box. For getting access to shares on the xp box, you need to supply two bits of information: 1) The host name of the xp box, the share name, and the associated user code and password 2) The name of an empty directory on Linux in which the xp share will appear. yast is the correct tool to configure this. The workgroup can be configured in yast->network services->windows domain membership, which also appears to be all there is to accessing xp shares. The rest is done by each individual user, and there are probably a number of ways of doing it. KDE has some linneighbourhood function somewhere. THere's also KDE->System->Network->KNetAttach which should do all you want. Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
