| 1 |
Canek Peláez Valdés <caneko@×××××.com> skribis: |
| 2 |
> On Mon, Mar 3, 2014 at 12:12 PM, Frank Peters <frank.peters@×××××××.net> wrote: |
| 3 |
> > Manually creating a /dev tree that perfectly reflects ones own system |
| 4 |
> > is rather trivial. That's how Linux used to be and that's how Linux, |
| 5 |
> > for the most part, still is. There is, or at least should be, no need |
| 6 |
> > for udev or any substitute for udev. |
| 7 |
> |
| 8 |
> If you want to create a /dev tree for a computer that never gets new |
| 9 |
> hardware connected via USB, bluetooth, or another bus, yeah, it's |
| 10 |
> pretty trivial. |
| 11 |
|
| 12 |
What’s hard? You create nodes for those devices. If you have a lot of |
| 13 |
devices, you create more nodes. With a script, you can create enough |
| 14 |
nodes to wrap the earth a few times over. All udev does is create and |
| 15 |
destroy nodes according to an unfathomable set of rules that changes |
| 16 |
all the time. |
Archives