Messages in this thread | | | Date | Fri, 26 Nov 2004 01:23:14 +0100 | From | Pavel Machek <> | Subject | Re: Suspend 2 merge: 35/51: Code always built in to the kernel. |
| |
Hi!
> > Kernel boot is not expected to be interactive. I'd do > > > > if (can_erase_image) > > printk("Incorrect kernel version, image killed\n"); > > else > > panic("Can't kill suspended image"); > > > > Comes down, again, to user friendliness. Just because I can erase the > image, doesn't mean I should. It may be that the user just pressed the > down arrow one too few times in lilo, and they really do have the right > kernel, but started the wrong one. Or it may be that they're still > setting up their initrd, didn't get it quite right, know that no damage > will be done and want to continue booting. We should let the user think > about what they want to do and then do it.
User friendlyness is nice, but I think "boot is not interactive" is stronger requirement than that.
> I need to get on with the work I planned on doing today, so I'm going to > hang up after sending this. That's not at all to say that I want you to > stop sending email; just that I won't be replying for a while.
No problem, I need some sleep. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |