SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If I understood it well, the problem is that udev is updated with new functionality, and the hdparm is not "following" the update. If that is the case, why the hdparm is not upgraded as well.
From Changelogs I've found out that last upgrade was in late 2008:
Code:
Sun Dec 7 01:37:48 CST 2008
a/hdparm-9.3-i486-1.tgz: Upgraded to hdparm-9.3.
Am I the only one having this issue?
Last edited by semiRocket; 08-30-2009 at 11:15 AM.
Reason: packages version
Nobody noticed that it was a problem until after 13.0 released. This is what -current is for, folks -- if it had come across the radar earlier, it would have been a relatively trivial update.
I've got it on the TODO for this -current cycle now.
I knew of this issue before 13.0 was released, unfortunately I didn't know where the exact problem is (my hd, linux or slackware) until now. I'm still learning Linux on the way, so I'm probably not the right person for debugging stuff.
Quote:
Originally Posted by rworkman
I've got it on the TODO for this -current cycle now.
Ok, at least the issue is now known by a developer.
Last edited by semiRocket; 08-31-2009 at 05:40 AM.
I knew of this issue before 13.0 was released, unfortunately I didn't know where the exact problem is (my hd, linux or slackware) until now. I'm still learning Linux on the way, so I'm probably not the right person for debugging stuff.
The fact that you found the problem and solution on your own is a good sign :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.