On Wed, Aug 14, 2013 at 09:38:12PM -0400, KOSAKI Motohiro wrote: > As you think makes no sense, I also think your position makes no sense. So, please > stop emotional word. That doesn't help discussion progress. Would you then please stop making nonsense assertions like "the fundamental rule here is to crash"? You could have started the whole thread with "I'm not sure about the failure mode, it can be better to hard fail because ..." and we could have debated on the details. Instead I now have to break the nonsense assertion. Of course the tension is way higher. > If the user was you, I agree. But I know the users don't react so. Yeah, users react super well to machines failing boot without any way to know what's going on. How is a good idea? > Again, there is no perfect solution if an admin is true stupid. We can just > suggest "you are wrong, not kernel", but no more further. I'm sure just kernel > logging doesn't help because they don't read it and they say no body read such There are things like automated reporting. The system is trying to use hotplug, right? It would have associated tools to do that, won't it? If you want to support it, build sensible tools and conventions around it and given how specialized / highend the whole thing is, it shouldn't be hard either. > plenty and for developer messages. I may accept any strong notification, but, > still, I don't think it's worth. Only sane way is, an admin realize their mistake > and fix themselves. Yes, we'll show them who's the boss. No, this is not how things are done in kernel. We don't crash to give admins a lesson. Do you even realize that this isn't completely deterministic? The machine might boot fine one time and fail the next time. What lesson would that teach the admin? Stay away from linux? > Huh? no fallback mean no additional code. I can't imagine no code makes runtime overhead. What fallback are you talking about? You need to report hotpluggable node somehow anyway. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
