Versatile embedded environment Files

Please also refer to the project's wiki page 
https://sourceforge.net/apps/trac/bclash/wiki/WikiStart
This should contain the most uptodate information and should be better 
maintained then this readme.

	1) Access on serial console
A simple getty is sprawned from inittab on/dev/ttyS0 if your system's serial 
port is elsewhete you might want to change that befor writing your image to 
the embedded system

	2) Root password
Default root password is: 
root

	3) Root filesystem
To make the system 100% ctash proof the system's initialization scripts leave 
root mounter read only. If you need to change something just do a 
"mount -o remount,rw /" to have root filesystem ReadWrite enabled and once 
you're done do "mount -o remount,ro /" to put it back in Read Only.

	4) IP addresses
Unless otherwise configured these are the defaults:
eth0 first tries dhcp if it's uplinked otherwise comes up with 192.168.254.1/24
eth0:1 comes up by default with 192.168.128.1/24

	5) SSH access
On first boot dsa keys, if none are found in /etc/dropbear, will be created 
for dropbear 

	6) http
A simple "It works!" will be displayed in servers root URL

	7) What's included
-A nearly full busybox build
-udev
-iptables
-pppd
-dnsmasq
-at
-usb_modeswitch
-sqlite3
-php (bothe command line intrepreter and cgi intrepreter)
-dropbear ssh server and client
-Ordinary client side wireless tools (missing wpa_supplicant thoug because 
	I supposed that most people will be doing AP with this not clients)
-hostapd (for making AP's)
-uboot environment variable management utilities (fw_printenv fw_setenv)

	8) What's not included but required for booting
Boot loader and kernel are not included. You must ither download them or build
them yourself for your hardware if none are avalible. Appart from intell where 
the bootloader and kernel could be unified the other non intel based platforms
cannot be unified. For instance the hardware differences between Sharp Zaurii 
and plug devices sheva plug family that all share ARM processor cannot use the 
same kernel nor the same boot loader as each needs to be custom build for the
specific hardware. Furthermore even kernels for the Zauri need to be built 
specifically for different faury families c7xx c5xxx c6xxx and cx000 do not 
share the same kernels. On the other hand the userspace binaries can run in a
variaty of platforms just so long as the kernel supports that paricular binary 
format. This is largly why kernels are not bundled wuth the root filesystem 
tarball.  

	9) Licemse related stuff
The whole environment is built from open source software that is released 
ither with GPL license or BSD license or bothe.
The licenses if not included in the package can be downloaded from the 
relative homepages or from the web sites of each component. I'm sorry for not 
including them in the distribuited system image but targeting embedde systems 
space is an issue. If anybody feels upset by this please contact me and we 
will find together a solution that satisfies both.
In particular the whole environment was specifically built to feel as much as
possible like Slackware and actually quite a few things came right out of 
the Slackware distribution itself (or whatever ort was avalibe for the target 
platform like for instance armedslack for the arm platform), some others come 
from there but have been adapted for the busybox based system and the rest 
was built spefifically for clashNG.    

	10) Installing
ClashNG is in it's early stage so if you concider using ir now you should know 
what you're doing. Here is a very sinthetic list on how you might go about
installing clashNG on your system. There are many ways to do the required 
steps listed below so untill I document properly a relatively safe way you 
will need to document yourself where ypu're lacking. OpenWRT dockstar 
installation instructions are quite good so you might like to start reading 
from there (http://wiki.openwrt.org/toh/seagate/dockstar):
-unpack the main clashNG tarbal for your architecture somewhere 
-unpack in the same place the appropriate kernel tarball
-remove kernel unecessary modules and frimware if yoy're stuck for space
-create the target image with jffs2 or ubi tools (make sure the kernel you are
  using has in kernel support for the target image you will be using)
-write your image to the internal flash of your device at the appropriate 
  mtd or offset so that your boot loader will not be wiped out
-configure your boot loader to load kernel from the appropriet mtd or offset
-configure your boot loader with the appropriate parameters for mounting the 
  root filesystem

Alternatively if you wrap the root filesystem in an ext* filesystem on a usb 
storage stick and you have a valid initrd for your setup you could use Jeff's 
uboot fro debian to boot from the usb stick