| 1 |
On Tue, May 15, 2012 at 04:56:15AM +0300, Maxim Kammerer wrote |
| 2 |
|
| 3 |
> I don't know at what state udev was 3 or 4 years ago, but mdev can: |
| 4 |
> |
| 5 |
> 1. Populate /dev (now unnecessary due to devtmpfs). |
| 6 |
> 2. Handle ownership, permissions and symlinks to /dev nodes once they |
| 7 |
> appear, according to simple rules (can be probably done with inotify). |
| 8 |
> 3. Act as /sbin/hotplug, typically doing something equivalent to this one-liner: |
| 9 |
> [ "${ACTION}" = add -a -n "${MODALIAS}" ] && modprobe -qb "${MODALIAS}" |
| 10 |
|
| 11 |
That's *EXACTLY* what I want and need. To borrow an old emacs joke, |
| 12 |
udev is a mediocre OS that lacks a lightweight device manager. |
| 13 |
|
| 14 |
> I don't think mdev can do anything else. Building any serious |
| 15 |
> framework on top of mdev seems pointless to me, since it will probably |
| 16 |
> end up as a small subset of udev core reimplemented with scripts. |
| 17 |
|
| 18 |
I *DON'T WANT* "a serious framework", I want a lightweight device |
| 19 |
manager... period... end of story. Stick with the unix principle of one |
| 20 |
app doing one thing well. mdev is enough for the vast majority of people. |
| 21 |
|
| 22 |
-- |
| 23 |
Walter Dnes <waltdnes@××××××××.org> |
Archives