From: Tejun Heo <htejun@gmail.com>
To: Scott James Remnant <scott@ubuntu.com>
Cc: Bruce Allen <ballen@gravity.phys.uwm.edu>,
roland.kletzing@materna.de,
Smartmontools Developers List
<smartmontools-devel@lists.sourceforge.net>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Mark Lord <liml@rtr.ca>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: regarding crazy head unloads
Date: Mon, 09 Jun 2008 10:56:35 +0900 [thread overview]
Message-ID: <484C8DD3.60502@gmail.com> (raw)
In-Reply-To: <1212400554.16559.33.camel@wing-commander>
Scott James Remnant wrote:
> On Fri, 2008-05-23 at 10:36 +0900, Tejun Heo wrote:
>
>> Attached are storage-fixup script which is to be called during boot and
>> resume and configuration file to go under /etc. The script can match
>> dmi and hal properties and execute commands on the matching devices.
>> The config file currently only contains three rules.
>>
> Could this not be done better inside HAL itself?
Could be. I really don't know about HAL. There were several problems
w/ HAL and I had to drop HAL dependency tho. HAL depends on a lot of
things and thus is started too late which makes it impossible to use in
early stages of boot (e.g. single mode). Another problem was that HAL
currently uses truncated ATA model ID string reported through SCSI
layer. The updated version is in the following git tree.
http://git.kernel.org/?p=linux/kernel/git/tj/storage-fixup.git;a=shortlog;h=master
If there's any better way to deal with this, I'll be happy to drop the
ugly script.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-06-09 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 1:36 regarding crazy head unloads Tejun Heo
2008-05-23 11:36 ` Tejun Heo
2008-06-02 9:55 ` Scott James Remnant
2008-06-09 1:56 ` Tejun Heo [this message]
2008-09-13 11:44 ` Bruce Allen
2008-09-30 5:36 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=484C8DD3.60502@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ballen@gravity.phys.uwm.edu \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=roland.kletzing@materna.de \
--cc=scott@ubuntu.com \
--cc=smartmontools-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).