CRUX-ARM 3.0 - https://crux-arm.nu/

* Mounting /proc, /sys.
* Mounting filesystems... OK
* Populating /dev via mdev... OK
* Registering mdev as hotplug agent... OK
* Creating and mounting /dev/pts... OK
* Starting kernel log daemon... OK
* Setting hostname... OK
* Loading network loopback device... OK
* Saving boot messages... OK
* Trying to find and mount the media installer...
* Searching for the CRUX media...

• Found media on /dev/mmcblk0p1, CRUX media.

The system is coming up. Please wait.

Please press Enter to activate this console.
# fsck
fsck (busybox 1.21.1, 2013-11-01 23:47:28 UTC)
# e2fsck /dev/sda1
e2fsck 1.42.5 (29-Jul-2012)
ext2fs_check_if_mount: Can’t check if filesystem is mounted due to missing mtab file while determining whether /dev/sda1 is mounted.
e2fsck: e2fsck not compiled with HTREE support,

      but filesystem /dev/sda1 has HTREE directories.

e2fsck: Get a newer version of e2fsck!

/dev/sda1: WARNING: Filesystem still has errors

Possible solution –enable-htree in e2fsprogs configure

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.

Review all our source tree so that if one tries to use MAKEFLAGS should not fail.

Right now would have to set those parts that need to be forced to -j1.

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.