From: Scott Tester <scott@smbc.com.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: ntfs.c failure in udev128 (with lseek() in util.c:405)
Date: Fri, 19 Sep 2008 00:12:41 +0000 [thread overview]
Message-ID: <48D2EE79.9040005@smbc.com.au> (raw)
http://bugs.gentoo.org/show_bug.cgi?id#7984 is more like my problem.
I've included myself on it. Bug 236635 deals with issues in udev127 and
gentoo specific hal rules (both of which I'm aware of.)
I'll resubmit this to linux-hotplug (via CC) as well.
Robby Workman wrote:
> On Thu, 18 Sep 2008 14:57:25 +1000
> Scott Tester <scott@smbc.com.au> wrote:
>
>
>> I re-emerged udev -128 (I'm using gentoo) then re-emerged hal-0.5.11*.
>> Still no go.
>>
>> ntfs.c line 145 calls util.c which then seems to fail on an lseek( )
>> call on line 405 with strerror(errno)="Invalid Argument".
>> Yet the arguments are identical with udev127 - only they succeed.
>>
>>
>> *the actual gentoo ebuild is hal-0.5.11-r3. (which includes the
>> udevadm patch you mentioned.)
>>
>
>
>
> See comment 26 in http://bugs.gentoo.org/show_bug.cgi?id#6635 -
> that's really not a solution, but it's worth seeing if it makes a
> difference on your system. Either way, this probably *is* a bug in
> udev since the hal rebuild still doesn't work. Whether you should file
> it on gentoo's bugzilla and/or send it back to the udev mail list is up
> to you - I'd probably do both. :-)
>
> -RW
>
>
--
Scott Tester
IT Department
SMBC www.smbc.com.au <http://www.smbc.com.au>
Sydney Missionary and Bible College
43 Badminton Road, Croydon NSW 2132
Phone: 02 9747 4780 ext 147
Mobile: 0411 145 584
reply other threads:[~2008-09-19 0:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48D2EE79.9040005@smbc.com.au \
--to=scott@smbc.com.au \
--cc=linux-hotplug@vger.kernel.org \
/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).