Yesterday I was manually stepping Smart to bring a flaky old Athlon Factory system up to date when Smart complained about a conflict between a new package and the existing old e2fsprogs rpm. To resolve, as I often do in similar not-so-smart Smart upgrade cases, I did rpm -d --nodeps on e2fsprogs, expecting to add it back on the next Smart run. Before the current run could complete, the system spontaneously rebooted. On reboot naturally fsck couldn't run, so I rebooted to another distro to run fsck on all partitions. On reboot into Factory, init still dropped me to repair mode and ro / due to "dirty" non / filesystem needing checking, which was a blatant lie. I suppose I should report this as a bug, but would like to see what others think. Ideas? On a related note (not-so-smart Smart), Smart reported db errors, requiring me to run rpm --rebuilddb, on about 10 different runs during yesterday's "session", spelled out in https://bugzilla.novell.com/show_bug.cgi?id=431722#c4 . -- "Everyone should be quick to listen, slow to speak, and slow to become angry." James 1:19 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org