© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The reason that I filed this as a bug is because I have a config that works perfectly on 2.6 kernels that I cannot get working on 3.13 or 4.1 kernels.
I figure there are two possible reasons:
1) The feature has become broken and needs to be fixed.
2) Something changed in how the feature works and now it requires a different config.
I think it's probably number 1. If it is number 2, then I will need to know the new way of configuring it, and I would expect to file a bug against ldirectord.
I'm not sure how to go about it, but if there's a way to load a system with a 2.6.32 kernel, prove that it works right, and then step through each kernel release after that, we could figure out which specific release broke it.