we have some weird problems related to mdev

1. the /etc/rc script required an extra 'mdev -s' invocation to find the install media

2. after use fdisk, we can see new device nodes for these new partitions

for problem 2 there is a guy who related the same here http://stackoverflow.com/questions/8313196/mdev-racing-when-creating-and-deleting-device-node

anyway a deep review of mdev from busybox should be made to avoid these weird errors

we can also take ideas from http://sepen.it.cx/crux/ports/crux-3.0/sepen/mdev/

ATM we need to solve issues with wireless since only WEP/WPA/WPA2 is supported with wpa_supplicant enabled.

For example, 'iwconfig wlan0 essid foo' doesn't work.

We should think in a way to have enough documentation for every device support. That includes:

1) Installation

 Should support all devices if not it should be noted in one section called Exceptions or similar
 Should be homogeneous for branches
 In wikipages could be called https://crux-arm.nu/Documentation/GeneralSetup, the one we have now but is empty ATM

2) Postinstallation tips (per <device>)

 Dedicated tips only related to finish the installation not the configuration
 With a General section (if required) and a section per device supported(*)
 In wikipages could be called https://crux-arm.nu/Documentation/PostInstallation

3) Configuration tips (per <device>)

 Dedicated tips related to configurations, as for example prt-get.conf, ports per device: etc/ports/<device>.rsync, etc.
 With a General section (if required) and a section per device supported(*)
 In wikipages could be called https://crux-arm.nu/Documentation/ConfigurationTips, the one we have now but is empty ATM

* section per device supported could be in the form of another doc like ConfigurationTips.efikamx or ConfigurationTips/efikamx

or it could be implemented with links to files/per/device stored in our webspace

ideas?

It would be nice to redirect some part of the output while running the script.
With that ouput we could create a file like crux-arm-2.7-test1.packages or similar which should include a list with all package versions.
The result file will help us to create the Changelog's stuff, etc.