On 4/8/06, Jürg Billeter <[EMAIL PROTECTED]> wrote:
>
> Ah, you're talking about mounting on demand, I don't call that
> automounting as it can be misleading. So as recap, what I call
> automounting is: plug in your usb stick, do nothing, stick gets mounted
> (optionally window appears with content
Jürg Billeter wrote:
Ah, you're talking about mounting on demand, I don't call that
automounting as it can be misleading. So as recap, what I call
automounting is: plug in your usb stick, do nothing, stick gets mounted
(optionally window appears with content). You call automounting: plug in
your
Joe Ciccone wrote:
I havn't been following this thread too closely
No kidding...
but, from what I can
tell about the way dbus/hal are integrated into the system. Without them
I don't know how much hardware interaction the software will have. When
you plug in your usb drive it won't be detecte
Randy McMurchy wrote:
> On Fri, 2006-04-07 at 16:05 -0700, Dan Nicholson wrote:
>
>
> But the "you don't need HAL thing" with others saying the userspace
> app is dependent on HAL, just has me totally confused at this point.
>
>
A lot of the packages don't *require* build and function, Building
On Fri, 2006-04-07 at 16:05 -0700, Dan Nicholson wrote:
> Andy seems to have left the building, but I recall that he was using
> the header sanitization script when that topic was hot on lfs-dev.
> I'd bet that he's using newer kernel headers.
Seeing how that about 4-5 people have given replies,
On 4/7/06, Joe Ciccone <[EMAIL PROTECTED]> wrote:
> Randy McMurchy wrote:
> > But you never answered my question, what did you do to get inotify to
> > work on a stock LFS system. It is becoming clear to me now, but how
> > you're getting inotify to work is still a mystery to me.
> >
> I figured ou
Randy McMurchy wrote:
> But you never answered my question, what did you do to get inotify to
> work on a stock LFS system. It is becoming clear to me now, but how
> you're getting inotify to work is still a mystery to me.
>
I figured out why I have it, I have /usr/include/sys/inotify.h provided
On Fri, 2006-04-07 at 15:39 -0700, Dan Nicholson wrote:
> I believe inotify got into the released version of the kernel in
> 2.6.13. So, you could get the header from there.
FWIW:
[EMAIL PROTECTED]: find /usr/src/linux* -name inotify.h
/usr/src/linux-2.6.14.3/include/linux/inotify.h
/usr/src
On Sat, 2006-04-08 at 00:35 +0200, Jürg Billeter wrote:
> I thought he just didn't compile gnome-vfs with HAL support, that's
> indeed not necessary for automounting. As previously written,
> gnome-volume-manager is the gnome automounter, not gnome-vfs, and
> gnome-volume-manager has an unconditio
On 4/7/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> On Fri, 2006-04-07 at 16:23 -0600, Archaic wrote:
>
> > Add inotify.h and a newer kernel. ;) There are patches for inotify
> > support for the llh used in trunk, but I don't recall where.
>
> Sorry to be so lame in my knowledge about this stuff
On Fre, 2006-04-07 at 17:22 -0500, Randy McMurchy wrote:
> On Sat, 2006-04-08 at 00:14 +0200, Jürg Billeter wrote:
>
> > It's the other way round. udev notifies HAL of new devices, older HAL
> > versions call fstab-sync to create fstab entries on demand and
> > the /etc/fstab change gets noticed b
On Fri, 2006-04-07 at 16:23 -0600, Archaic wrote:
> Add inotify.h and a newer kernel. ;) There are patches for inotify
> support for the llh used in trunk, but I don't recall where.
Sorry to be so lame in my knowledge about this stuff, but where does
one get inotify.h? And exactly what version of
On 4/7/06, Archaic <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 07, 2006 at 05:18:50PM -0500, Randy McMurchy wrote:
> >
> > But you never answered my question, what did you do to get inotify to
> > work on a stock LFS system. It is becoming clear to me now, but how
> > you're getting inotify to work is
On Sat, 2006-04-08 at 00:14 +0200, Jürg Billeter wrote:
> It's the other way round. udev notifies HAL of new devices, older HAL
> versions call fstab-sync to create fstab entries on demand and
> the /etc/fstab change gets noticed by FAM which notifies gnome-vfs.
I understand everything you're say
On Fri, Apr 07, 2006 at 05:18:50PM -0500, Randy McMurchy wrote:
>
> But you never answered my question, what did you do to get inotify to
> work on a stock LFS system. It is becoming clear to me now, but how
> you're getting inotify to work is still a mystery to me.
Add inotify.h and a newer kern
On 4/7/06, Andrew Benton <[EMAIL PROTECTED]> wrote:
>
> Exactly right. It's worked for more than a year, it worked with FAM and
> it works with Gamin. If Gnome VFS can now use inotify directly it makes
> me wonder if Gamin is still needed.
No, they're trying to get rid of it. But, alas, not every
On 4/7/06, Andrew Benton <[EMAIL PROTECTED]> wrote:
> Randy McMurchy wrote:
> > When you plug in a device, there is no filesystem for that device yet,
> > so how does FAM notify anything?
>
> I don't know
Possibly it isn't FAM at all. Randy might be right.
> > And then what does it notify so tha
On Fri, 2006-04-07 at 23:09 +0100, Andrew Benton wrote:
> Exactly right. It's worked for more than a year, it worked with FAM and
> it works with Gamin. If Gnome VFS can now use inotify directly it makes
> me wonder if Gamin is still needed.
Cool.
But you never answered my question, what did y
On Fre, 2006-04-07 at 23:09 +0100, Andrew Benton wrote:
> Dan Nicholson wrote:
> > Probably having newer kernel headers. From gnome-vfs configure, it
> > checks for linux/inotify.h or sys/inotify.h (from glibc-2.3.90+) to
> > enable inotify. This is what I got with l-l-h-2.6.12.0 and
> > glibc-2.
On Fre, 2006-04-07 at 16:48 -0500, Randy McMurchy wrote:
> On Fri, 2006-04-07 at 14:40 -0700, Dan Nicholson wrote:
>
> > In that case, I'm guessing fam (gamin) is providing the notification.
>
> This is a good discussion, I am going to learn something here. It was
> my understanding that the File
Dan Nicholson wrote:
Probably having newer kernel headers. From gnome-vfs configure, it
checks for linux/inotify.h or sys/inotify.h (from glibc-2.3.90+) to
enable inotify. This is what I got with l-l-h-2.6.12.0 and
glibc-2.3.6:
FS monitor backends: fam
In that case, I'm guessing f
Randy McMurchy wrote:
When you plug in a device, there is no filesystem for that device yet,
so how does FAM notify anything?
I don't know
And then what does it notify so that an appropriate fstab entry is
created. And what tells the operating how to create that fstab entry?
The fstab entri
On Fri, 2006-04-07 at 14:40 -0700, Dan Nicholson wrote:
> In that case, I'm guessing fam (gamin) is providing the notification.
This is a good discussion, I am going to learn something here. It was
my understanding that the File Alteration Monitor is used to tell the
operating system when there a
On 4/7/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> On Fri, 2006-04-07 at 22:20 +0100, Andrew Benton wrote:
>
> > FS monitor backends: inotify fam
>
> I didn't know inotify worked with the current LFS setup. My
> installations don't show an inotify enabled FAM. What do you do
> dif
On Fri, 2006-04-07 at 22:20 +0100, Andrew Benton wrote:
> Probably inotify. From the gnome-vfs buildlog
> Gnome VFS configuration summary:
>
> IPv6 support:yes
> SSL support: yes
> Avahi support: no
> Howl supp
Randy McMurchy wrote:
And what mechanism, if not D-Bus, tells the system that plug-in hardware
has been introduced to the system? This isn't a test, I just simply
don't know and am curious.
Probably inotify. From the gnome-vfs buildlog
Gnome VFS configuration summary:
IPv6 support:
On Fri, 2006-04-07 at 21:26 +0100, Andrew Benton wrote:
> It's only an optional dependency. Gnome-VFS and Gnome-2.14 works fine
> without HAL or D-Bus. I plug in some flash memory and it automatically
> mounts it as /dev/sda1 on /mnt/mp3. Some problem with HAL or D-Bus is no
> reason not to us
Randy McMurchy wrote:
Not sure what do about this HAL/D-Bus thing. Best I can tell GNOME
2.14.0 wants the bleeding edge HAL/D-Bus. Gnome-VFS wants HAL-0.5.7.
It's only an optional dependency. Gnome-VFS and Gnome-2.14 works fine
without HAL or D-Bus. I plug in some flash memory and it automatic
On Fri, 2006-04-07 at 12:00 -0700, Dan Nicholson wrote:
> That's a good question that needs to be pursued. I don't follow KDE
> at all, so I wouldn't know where to look for this info. Do you know
> which KDE applications use HAL?
Well, there are only two packages to get KDE up and running (plus
On 4/7/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> On Fri, 2006-04-07 at 13:20 -0500, Bruce Dubbs wrote:
>
> > Thanks Dan. It is interesting, but I'm not sure where to go with this
> > right now.
>
> Can of worms!
I'm not proposing adding pam_console to the book. Just put it out
there for in
On Fri, 2006-04-07 at 13:20 -0500, Bruce Dubbs wrote:
> Thanks Dan. It is interesting, but I'm not sure where to go with this
> right now.
Can of worms!
Not sure what do about this HAL/D-Bus thing. Best I can tell GNOME
2.14.0 wants the bleeding edge HAL/D-Bus. Gnome-VFS wants HAL-0.5.7.
This i
Dan Nicholson wrote:
> On 4/5/06, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>> As far a PAM goes, we could point to
>> http://www.kernel.org/pub/linux/libs/pam/modules.html for external PAM
>> modules.
>>
>> pam_console is from Red Hat. If we need it, I think we would have to
>> extract it from the s
On 4/5/06, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>
> As far a PAM goes, we could point to
> http://www.kernel.org/pub/linux/libs/pam/modules.html for external PAM
> modules.
>
> pam_console is from Red Hat. If we need it, I think we would have to
> extract it from the source RPM as I can't find a
33 matches
Mail list logo
