I think it would be a good idea for ebuilds for 2.6 kernels to automatically create the /sys directory which is used for sysfs (if it doesn't exist already). I've been running 2.6 for a while and didn't realize this should even be done, and it seems like a harmless thing to do. If there is some good reason to not do this, it would be nice to add something about it to the messages printed out at the end of an emerge. Reproducible: Always Steps to Reproduce:
Actually tseng and I were talking about this one night, and we thought it might be a good thing for the init scripts to automagically create a /sys if the kernel is 2.5+. I don't know if anybody looked into it after we talked about it, but maybe I can check what (if anything) has been done.
I do not see why the initscript should do this - they already handle the case where an /sys do exist, and warn if there is none. This is more a case where baselayout should create one like /proc is done, but until 2.6 goes mainline, I do not think it should so by default. Maybe if it detects a 2.6 kernel?
... Maybe the `eclass' should do this after merging a kernel if ${KV} >= KERNEL_VERSION(2,6,0)...
the new kernel-2 eclass should do this already. as for the originaly kernel eclass, I think thats a maintainer issue :)
