kanenas wrote:
ok, now that i am straightened about the thread hijacking bit, lemme take a shot at short sentences. 10.1 looks ok for the most part. i think the update issue is mostly solved and my lcd problem is corrected. some areas where i still have some problems are: i have a very simple samba server setup thru yast2, all connections and printers work except when i try to open up a shared folder in a windoze machine from 10.1, the connection is refused. the same windoze machines are accessible from a second linux machine, running 32 bit suse 10.0, so i figure it is the winbind service in 10.1. the command "rcwinbind restart" gives an error message "winbind deamon not running, winbind pid exists in /var/run/samba". The windows connection service has been started in yast2. what am i missing?
Delete winbind pid in /var/run/samba and then try again. rcwinbind start
another nuance is that an rpm that has been downloaded to a local directory can not be installed thru yast any more. one must open a console and issue the rpm command, because yast "can't find" said rpm!
I have seen that mentioned somewhere, but can't find right now.
yet another nuance is somewhat extensive disk access, escpecially when firefox is running. with 2gb ram available the disk should not be checked every 5-10 seconds. any ideas? thanks, d.
Last time that bothered me it was SUSE-<something>, that was responsible for hotplug devices, looking for new devices, not really writing anything, but just activating HD controller and it's light. The other reason for HD activity might be pdflush demon, that saves on HD content of disk cache in RAM. This should not be disabled as it prevents data loss in case of power failure. It waits for 35 sec. after cache was changed and than writes on HD. -- Regards, Rajko. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com