On Thu, 2003-05-01 at 08:23, dep wrote:
i agree with you. my complaint is not that suse should have written a good or better or all-encompassing acpi implementation. nor is it that suse is responsible for every line of code in five cds of software.
instead it is that this is not an unknown problem, and where suse *does* have control -- yast, documentation, and making it easy for users who encounter problems to troubleshoot -- it has fallen short so far. and that it would be *easy* to make it so that would-be users who hit a snag can quickly and fairly painlessly overcome it. the acpi implementation situation is a problem. how yast deals with it is a problem. the former problem cannot quickly be solved. the latter can be quickly solved.
Perhaps. I don't know. That's at least a more reasonable request than what it was sounding like you were saying earlier. Either way, most people don't seem to have a problem, so perhaps this is why nothing has been done. I don't know. Preston