On 3/17/06, Tobias Gerschner <[EMAIL PROTECTED]> wrote:
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,
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.
Hi,
2006/3/17, Chakkaradeep C C <[EMAIL PROTECTED]>:
> Hi All,
>
> We were discussing of configuring devices.I was discussing the same in some
> indian irc channels.Everyone were telling me that the best would be to use
> the RedHat's system-config-* programs (earllier it was redhat-config-* ) and
> modify it to Yoper's way.
>
> This is rather a "may be" step and it might work or not work.But theres
> nothing wrong in trying it out.
>
> I would be happy if people could download the src rpms of these
> system-config-* from FC website and try in their machines.One of the mirrors
> is ftp://ftp.oss.eznetsols.org/linux/fedora/4/SRPMS/
>
> The main programs we need to consider are,
> 1) system-config-display
> 2) system-config-printer
> (extra can be added by anyone.......)
>
> Once we find them working, we can redesign the GUI alone and leave the
> coding as such.
>
> If people agree with this step, then we can proceed testing each tool and
> come out with a result.They are very small tools and making them work should
> not take more time.We lack in configuration and this has to be dealt
> seriously.
>
> Please put in your comments...
Yes, Yoper lacks configuration tools. But this is not the (my) point (
at the moment) .
The problem is that the kernel development moves more and more into a
direction where it sends event signals to user space. These signals
are usually handled by udev + hal + dbus whatever.
What Yoper currently NOT has is the userspace event handling. In big
parts it's pretty nonexisting. And the problem is that you cannot use
other distros tool easily. You can look at them writing your own
scripts / event-handlers. But it always comes back to doing it on your
own.
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.
If am wrong- in any aspect, i would be very happy if you correct me.
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
