On 3/17/06, Tobias Gerschner <[EMAIL PROTECTED]> wrote:
So how to proceed in this, do we need to try out some userspace tools?, if so, can you tell which tools are those, so that we could atleast try locally...
Hi,
> >
> > When this is done we can take care of Device Configuration. But for
> > now we have to take care of the proper handling of kernel to userspace
> > messages.
>
> I was going thru this UserSpace and Kernel stuffs(udev+hotplug).Ok, to
> configure the devices like Plug-n-Play, we have to use this.
>
> Here is a link for udev faq -
> http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ
>
> The "devices" here, does it mean "plug-n-play" devices or the already
> configured device like Monitor,CD-ROMs,Keyboard,Mouse etc...
>
> If it is "plug-n-play" device, then the udev+hotplug seems to be what we
> have to concentrate.And also , from the faq above, here is an extract,
>
> Q: Can I use udev to automount a USB device when I connect it?
> A: Technically, yes, but udev is not intended for this. All major
> distributions
> use HAL (http://freedesktop.org/wiki/Software_2fhal
> ) for this, which also
> watches devices with removable media and integrates into the desktop
> software.
>
> Alternatively, it is easy to add the following to fstab:
> /dev/disk/by-label/PENDRIVE /media/PENDRIVE vfat user,noauto 0 0
>
>
> This means that users can access the device with:
> $mount /media/PENDRIVE
> and doen't have to be root, but will get full permissions on the device.
> Using the persistent disk links (label, uuid) will always catch the
>
>
> same device regardless of the actual kernel name.
>
> USB and other removable medias should be handled by HAL?...
>
> If am wrong- in any aspect, i would be very happy if you correct me.
>
Yes,
but no matter which userspace tool is used. The configuration is
rather nonexisting at the moment. And it is completely distro
specific. We cannot just compile and install some software.
So how to proceed in this, do we need to try out some userspace tools?, if so, can you tell which tools are those, so that we could atleast try locally...
regards
--
Tobias Gerschner
Member of Board of Yoper Ltd. NZ
Knowing is not enough; we must apply. Willing is not enough; we must do.
_______________________________________________
yoper-dev mailing list
[email protected]
https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
--
Regards,
Chaks,
Yoper Ltd.
http://www.yoper.com
http://www.yoper.com/forum
--
The main aim of communication is clarity and simplicity. Simplicity means focussed effort.
_______________________________________________ yoper-dev mailing list [email protected] https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
