On Sat, 2009-05-16 at 06:10 -0600, Matthew Burgess wrote:
> That said, it was already planned to migrate pkg-config across to LFS
> as so many packages are adopting it, it makes sense to have it part of
> a base system.
True enough - these days, it's really on a par with autoconf, automake,
and li
On Sat, 16 May 2009 16:54:50 +1200, Simon Geard wrote:
> On Thu, 2009-05-14 at 13:12 -0500, DJ Lucas wrote:
>> Hehe...should've sent this Sunday as I had intended to do. The
>> util-linux requirement kills the new release...have to wait till
>> LFS-6.5/7.0. 0.5.11 seems to be stable with the u
On Thu, 2009-05-14 at 13:12 -0500, DJ Lucas wrote:
> Hehe...should've sent this Sunday as I had intended to do. The
> util-linux requirement kills the new release...have to wait till
> LFS-6.5/7.0. 0.5.11 seems to be stable with the udevadm patch, but I'll
> review what the distros are doing t
On Thu, 2009-05-14 at 13:12 -0500, DJ Lucas wrote:
> Simon Geard wrote:
> >
> > Your timing is impeccable - they finally released 0.5.12 yesterday :)
>
> Hehe...should've sent this Sunday as I had intended to do. The
> util-linux requirement kills the new release...have to wait till
Yes, I ju
On Thu, May 14, 2009 at 6:27 PM, lux-integ wrote:
> could you tell where to find this patch please? I already looked
> unsuccessfully at:-
> http://www.linuxfromscratch.org/patches/downloads/hal/ AND
> http://www.linuxfromscratch.org/patches/downloads/patch/
The patch is under
http://www.linuxfr
On Thursday 14 May 2009 07:12:05 pm DJ Lucas wrote:
> 0.5.11 seems to be stable with the udevadm patch
could you tell where to find this patch please? I already looked
unsuccessfully at:-
http://www.linuxfromscratch.org/patches/downloads/hal/ AND
http://www.linuxfromscratch.org/patches/downloa
Simon Geard wrote:
>
> Your timing is impeccable - they finally released 0.5.12 yesterday :)
>
Hehe...should've sent this Sunday as I had intended to do. The
util-linux requirement kills the new release...have to wait till
LFS-6.5/7.0. 0.5.11 seems to be stable with the udevadm patch, but I
On Thu, 2009-05-14 at 01:50 -0500, DJ Lucas wrote:
> I realize that this post is very old. I'm now playing catch-up. Do
> you, by chance, have a reference for that recommendation? I'm preparing
> to commit hal-0.5.11 and hal-info-20081022 with only the
> udevinfo/udevadm patch. Are there oth
Simon Geard wrote:
> You've hit one of a couple of problems in hal 0.5.11 that prevent it
> from running unmodified on newer kernel and udev versions. Running the
> 0.5.12 candidate is the recommendation from the hal developers... I've
> been doing so for about 5 months now without problem.
Simon
On Sun, 2009-04-12 at 22:40 -0700, Chris Burel wrote:
> ...After much trial and error, I tried installing hal 0.5.12rc1, which
> seems to have fixed the problem. Now I get 143 devices listed by
> hal-devices instead of 5.
Missed your original post, sorry, but you've come up with the right
answer
...After much trial and error, I tried installing hal 0.5.12rc1, which seems
to have fixed the problem. Now I get 143 devices listed by hal-devices
instead of 5.
On Sun, Apr 12, 2009 at 2:34 AM, Chris Burel wrote:
> It looks like this goes all the way up to udev. I don't get any uevent
> when
It looks like this goes all the way up to udev. I don't get any uevent when
I insert a cd in either of my drives.
> udevadm monitor --env
monitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent
and then nothing. If I manually
I suppose I should mention that I'm using
HAL 0.5.11
dbus 1.2.4, built Dec 4 2008, so that's before the permissive branch was
released. I don't really know the details of the split in dbus.
Should I try hal 0.5.12rc1?
On Sat, Apr 11, 2009 at 1:58 PM, Chris Burel wrote:
> ~$> hal-find-by-proper
~$> hal-find-by-property --key 'block.device' --string '/dev/sr0' --verbose
Found 0 device objects with string property block.device = '/dev/sr0'
~$> hal-find-by-property --key 'block.device' --string '/dev/sr1' --verbose
Found 0 device objects with string property block.device = '/dev/sr1'
~$> hal
14 matches
Mail list logo
