https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c13 Maciej Pilichowski <bluedzins@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P4 - Low |P2 - High Status|NEEDINFO |NEW InfoProvider|bluedzins@wp.pl | Severity|Minor |Major --- Comment #13 from Maciej Pilichowski <bluedzins@wp.pl> 2011-07-08 12:27:01 UTC --- First of all let's straighten few things: * "unusual tweak" -- please give some statistics to back up "unusual", thanks * mounting partition -- there is /etc/mtab to check before doing any operation on partition, if it is mounted or not. This is not rocket science so please don't say, my setup is strange or unusual. This is Unix world * Yast is doing KERNEL update for Christ sake, if this is low priority operation so then what is high priority? Blindly going after non-existing files on non-existing (not-mounted) partition is terribly lack of imagination and terrible quality, I would not like to "accused" that it is my fault because I dared to unmount /boot partition
Um, so how would you update the kernel if /boot is not mounted or mounted in read-only mode?
"Dear user please mount /boot partition in read-write mode in order to update the kernel". Displaying messages is too hard?
And why do you have such setup?
Because it fit my needs.
That's really unusual and strange...
No, this is not strange. /boot partition for normal work is not needed at all. You can find a couple of reasons why it is wise to unmount it (and how to setup it) if you google for it.
I quickly went through all yast sources and I could not find any "not mounted" error, and in the logs I also didn't find anything. Could you be more specific? When exactly was the warning displayed? A screenshot would be very helpful...
a) I think there is problem with lack of the message, not with the message, so I would worry about the process which does NOT display it b) warning was displayed while restoring all selected rpms which I thought were causing the problems with the system c) screenshot would mean, repeating all the steps now -- which is pretty dangerous to my system, so sorry, but "no" for sure
Deltas contain only the difference from the original package to the updated version and thus cannot be used for downgrade (they don't contain the needed data) so in this case full RPMs are used. That's expected behavior.
I know, you asked what I did, so I explained.
(Decreasing the severity because of the unusual manual tweak...)
Setting it back, because of not statistically founded assumptions. Kernel is the core of the system, kernel update algorithm is lousy (every programmer will tell you that), incorrect update can cost user ALL the data and a lot of time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.