On Mon, Mar 10, 2008 at 12:13 AM, Andrew Farris <lordmorgul(a)gmail.com> wrote:
Benjamin Kreuter wrote:
> On Thursday 06 March 2008 19:29:23 Chuck Ebbert wrote:
>> Sorry, we had to release with known bugs. A new kernel will be in
>> updates-testing very shortly.
>
> Why did you have to release with known bugs? Why not just wait until the bugs
> are fixed? The last three kernel updates broke suspend for me...
Then why are you installing them? If this kernel was known to break things,
then when it hits updates don't install it... not rocket science.
When the yum update applet reports that new updates are available, I
always choose to accept them without checking in advance whether or
not they will render my computer unusable.
Also if I did decide to check if the update would break my system, it
currently is not possible to tell pup to ignore this particular
update.
A try-catch mechanism could provide a fallback solution to kernels.
Kernels could be marked as bootable, not_checked and non_bootable, and
grub could check this flag/status file and switch to the first
bootable kernel if the default is marked as non_bootable. Perhaps a
feature like this is already available in grub?
--
Trond Danielsen