
Carlos E. R. wrote:
Hi,
I told Yast to update all updatables. It downloaded over a gigabit, it took the whole afternoon. It is a nuisance when it screeches over a network failure and doesn't retry till I come by the computer and tell it to retry.
Good point, YaST should either try to download automatically (after 60 seconds or so) or should give the opportunity to [ Retry Automatically ]. Anyway, this would need to be configurable: * Try automatically * Max tries (for not to end up in a loop) * Time wait Please, file an Enhancement request.
In the end, I told it to reboot, or perhaps halt; in any case, it halted. I booted again, and I saw the system running a long filesystem check because the root partition had not been cleanly umounted.
I thought this was a known bug with the RC1 DVD, but not with the installed system.
Yes, it was a bug in RC1 when rebooting from First Stage to Second Stage of the installation. Sometimes, there were two processes running under the /mnt path (/mnt == Installation chroot). These processes were: 'ntpd' and 'dhcpcd'. How exactly did you rebooted the system? I'm not sure, but I have a feeling that in a minimal installation I saw something like: reboot: fuser: command not found And 'fuser' is a command that can list or even kill processes running depending on the directory that they have open. Please, write mote details, you can additionally inspect the end of YaST logs: /var/log/YaST2/y2log Have a nice day Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic