On Sun, Mar 8, 2015 at 4:10 PM, Harald Becker <[email protected]> wrote: > 1) Starting up a system with mdev usually involves the same steps to mount > proc, sys and a tmpfs on dev, then adding some subdirectories to /dev, > setting owner, group and permissions, symlinking some entries and possibly > mounting more virtual file systems. This work need to be done by the > controlling startup script, so we reinvent the wheel in every system setup.
This wheel is not particularly hard to reinvent. More importantly, it is written in shell commands everyone understands and can debug/change if needed. > I like to extend the syntax of mdev.conf with some extra information and add > code into mdev to allow to do this operation in a more simplified way, but > still under full control of the system maintainer. Those extra entries will > only be executed whith "mdev -s" not during hotplug. The syntax has been > chosen to not (horribly) break existing mdev.conf setups. > > Current major syntax of mdev.conf: > > [-][envmatch]<device regex> <uid>:<gid> <permissions> [...] > [envmatch]@<maj[,min1[-min2]]> <uid>:<gid> <permissions> [...] > $envvar=<regex> <uid>:<gid> <permissions> [...] > > - Additional syntax to mount (virtual) file systems: > > MOUNTPOINT UID:GID PERMISSIONS %FSTYPE [=DEVICE] [OPTIONS] mdev rules are complicated already. Adding more cases needs adding more code, and requires people to learn new "mini-language" for mounting filesystems via mdev. Think about it. You are succumbing to featuritis. You like how "mdev -s" magically populated /dev with all necessary stuff... ...almost, and you have a bright idea "let's fix that 'almost', so that I can do initial setup just via mdev -s". This is how all bloated all-in-one disasters start. Fight that urge. That's not the Unix way. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
