The iotop ebuild warnings should state more clearly, what kernel flags, in which kernel it is missing. (Besides mentioning that these are kernel flags!) Reproducible: Always Steps to Reproduce: 1. emerge iotop (some requiered Kernel options not set) Actual Results: * Messages for package sys-process/iotop-0.2.1: * CONFIG_TASK_IO_ACCOUNTING: is not set when it should be. * CONFIG_TASKSTATS: is not set when it should be. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. Expected Results: * Messages for package sys-process/iotop-0.2.1: * Your Kernel in dir <dir> /your current kernel is missing the * following features: * CONFIG_TASK_IO_ACCOUNTING: is not set when it should be. * CONFIG_TASKSTATS: is not set when it should be. * Please check to make sure these options are set correctly. * The features can be found in the kernel config at * General setup --->"Export task/process statistics through netlink" * Failure to do so may cause unexpected problems.
I'll be maintaining this now, looking at bugz next week.
(In reply to comment #0) > Expected Results: > * Messages for package sys-process/iotop-0.2.1: > * Your Kernel in dir <dir> /your current kernel is missing the No, /usr/src/linux is the only thing we can check reliably. If the user has a different symlink there then the ebuild would be lying. We can't really check and instead only offer helpful hints. > * following features: > * CONFIG_TASK_IO_ACCOUNTING: is not set when it should be. > * CONFIG_TASKSTATS: is not set when it should be. > * Please check to make sure these options are set correctly. > * The features can be found in the kernel config at > * General setup --->"Export task/process statistics through netlink" This is beyond the scope of ebuilds. There is more than one way to configure a kernel and we assume that the user knows how to search in their preferred way to configuring the kernel. Thanks but I'm afraid that I will leave the message as is.
