Hi Ralph,
done: Bug #1268452
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/222458
Title:
/lib/udev/hdparm Compares Against $DEVNAME.
To manage notifications about this bug go to:
Hi Guys,
I know this bug has been fixed one year ago, but here is one further point for
the /wishlist/:
== Add documentation of the new features (specify devices by UUID e.g.) to
hdparm manual page
and to the description header text in /etc/hdparm.conf...
--
You received this bug
Hi Tom, This bug is Fix Released. No further work will be done on it.
Your comment will be ignored. You need to find a closely related open
bug to request it or open a new one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:ubuntu/raring-proposed/hdparm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/222458
Title:
/lib/udev/hdparm Compares Against $DEVNAME.
To manage notifications about this bug go
This bug was fixed in the package hdparm - 9.42-1ubuntu1
---
hdparm (9.42-1ubuntu1) raring; urgency=low
* Merge from Debian unstable:
+ Adds support to the udev script for hdparm.conf stanzas that point at
a symlink of the device rather than the device itself. LP:
Not sure if I've done this right, but I've marked Bug #799312 as a
duplicate of this bug. Perhaps I should have marked this as the
duplicate, but I'm not sure how launchpad works just yet.
It appears to be dealing with the same issue however a more up to date
patch has been generated which works
I have also marked Bug #227705 as a duplicate of this bug as the patch
supplied in this bug seems to deal with the same issue and has been
patched more recently in Bug #799312.
Like I say, I'm not too sure if I should have marked this bug (222458)
and 227705 as duplicates of 799312 - as it
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: hdparm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/222458
Title:
Hello Jakob,
I'm using Ubuntu Intrepid. I don't know whether I experience that bug,
I have not looked at the apm settings yet. But I can do so if that's
helping anyone.
I currently only use /etc/hdparm.conf to set spindown_time (-S) and
acoustic_management (-M) on one of my drives (viz. the one
Bas, does that mean that you don't experience bug #318980 ? Which Ubuntu
version do you use?
--
/lib/udev/hdparm Compares Against $DEVNAME.
https://bugs.launchpad.net/bugs/222458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This uses -h instead of -L as suggested by Ralph. Additionally, it uses
some quoting for safety (empty $KEY, spaces inside).
** Attachment added: patch against /lib/udev/hdparm
http://launchpadlibrarian.net/21448610/hdparm.patch
--
/lib/udev/hdparm Compares Against $DEVNAME.
I confirm this bug, it's quite annoying. I have two drives and cannot
predict which one will be /dev/sda and which one will be /dev/sdb after
booting. Hence, the only thing I can do is select by the ids in
/dev/disk/by-id but this is not supported by the current udev-rules.
--
/lib/udev/hdparm
Addition: the proposed bugfix of Jakob works for me. After rebooting,
the disk parameters are indeed set to the values in /etc/hdparm.conf.
Thanks!
--
/lib/udev/hdparm Compares Against $DEVNAME.
https://bugs.launchpad.net/bugs/222458
You received this bug notification because you are a member of
Yes, bug #227705 may be a duplicate of this one, but I'm puzzled why it
still didn't work when you switched from the symlink to /dev/sda1. Did
you try the drive rather than the partition? /dev/sda.
I agree that, compared to init.d, the udev stuff seems hard to debug.
Perhaps we just don't have
Is this related to the problem I am having ?
See:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/227705
I'm having to continue using the init.d script as it isn't working from
udev. Note that the init.d script is still useful. How else are users
supposed to check whether their
I've just been trying to determine where, during the boot cycle,
/lib/udev/hdparm is being called for the permanently attached disks.
While I can see the devices in /var/log/udev, I don't think that the
/lib/udev/hdparm script is run correctly, or maybe it's called too early
in the boot process.
As long as $DISC won't end in a digit unless it's a partition digit to
be stripped off, that looks fine. But it should be -h not -L in dash(1)
as I said earlier.
--
/lib/udev/hdparm Compares Against $DEVNAME.
https://bugs.launchpad.net/bugs/222458
You received this bug notification because you
I'm pretty sure that all /dev/[sh]d[a-z] devices would not have a digit
at the end unless they're partitions.
I don't mind using -h instead of -L.
I need to do some more testing. While the above worked fine when running
/lib/udev/hdparm from command line. i am not entirely convinced yet that
it
I've run into this same problem, but I actually use /dev/disk/by-uuid/*
links, which all link to a partition on the given device, rather than
the device itself. I suggest the following as a fix for this as well as
the earlier suggested fix:
93c93,100
DISC=$KEY
---
if
Sounds quite useful.
Would you test if the attached /lib/udev/hdparm does what you want?
diff /lib/udev/hdparm /tmp/hdparm
93c93,98
DISC=$KEY
---
if [ -L $KEY ]
then
DISC=$(readlink -m $KEY)
else
fi
(missed that line on copy-paste)
--
/lib/udev/hdparm Compares Against $DEVNAME.
https://bugs.launchpad.net/bugs/222458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Would you test if the attached /lib/udev/hdparm does what you want?
if [ -L $KEY ]
I'm not in a position to test it right now, although looking at it in
context, I think it should work just fine. One comment,
/lib/udev/hdparm is a /bin/sh script which is dash on 8.04 but
Whilst you're in that script. What purpose does $ret have? AFAICS it
is assigned to but never used. Either it should be used or it could be
deleted altogether for clarity.
--
/lib/udev/hdparm Compares Against $DEVNAME.
https://bugs.launchpad.net/bugs/222458
You received this bug notification
23 matches
Mail list logo
