Carl Lowenstein wrote: >> > But if the files go in /var, which is a separate mounted file system, >> > why is YaST2 telling me that / is nearly full? "Your shields are >> > dangerously low!"
The Yast-Online-Update through SuSE 10.0 used /var/lib/YaST2/you/mnt/[arch]/update/[version]/patches as the available patch directory, and /var/lib/YaST2/you/installed as a list of packages. Your's are clearly going somewhere else (/tmp maybe ?) You might be able to find out by selecting a single package, then doing a find on / to look for the root part of the package name. But In looking through the forums, I can't see this particular error, however (running out of room on root). You might email Marcus Meissner <[EMAIL PROTECTED]> - could be something they haven't run into before. You should be able to reach YaST2 from the KDE or Gnome menus though, and run the libzypp update using Yast, rather than the built in update tool (which was patched and supposedly fixed in June, but you can't fix it if you can't install anything right). As I was contemplating installing 10.1 soon, but I had heard bad things about the new package management/update system in 10.1. Seems that Yast-Online-Update is being abandoned in favor of Libzypp as the backend software with the Zenworks Management Daemon (ZMD/RUG) as the GUI, and that basically it's broken in one way or another for most users. Linux Journal suggesting abandoning the Suse tools in favor of the SMART package manager. David Looney -- Never put off until tomorrow that which can be done the day after tomorrow. - Mark Twain -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
