1
0
mirror of git://projects.qi-hardware.com/openwrt-xburst.git synced 2024-11-05 15:34:59 +02:00
openwrt-xburst/target/linux/uml
nbd b80f2ac036 disable crash logging for uml, it cannot possibly work there anyway
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22326 3c298f89-4303-0410-b956-a3cf2f4a3e73
2010-07-21 15:02:53 +00:00
..
config disable crash logging for uml, it cannot possibly work there anyway 2010-07-21 15:02:53 +00:00
image define a shared IMG_PREFIX variable used as a basename for image files, it contains board & subtarget infos (if appropriate) allowing subtargets to share the same bin directory without overwriting each other's files 2010-04-12 23:15:56 +00:00
patches-2.6.32 target/uml: fix memcpy export on x86_64 with gcc < 4.3 (closes: #6918) 2010-05-02 04:20:03 +00:00
patches-2.6.33 [uml] add upstream patch to fix linking failures on '__rela_iplt_end' 2010-04-30 12:20:24 +00:00
patches-2.6.34 [uml] add upstream patch to fix linking failures on '__rela_iplt_end' 2010-04-30 12:20:24 +00:00
Makefile update kernel versions 2010-07-19 11:34:03 +00:00
README [uml] update README after r18624 2009-12-07 16:56:00 +00:00

Openwrt inside a user mode linux.  Why would we even want this many ask?

There are potentially a lot of reasons, one obvious one to me, it allows
folks to 'kick the tires' without actually flashing up any hardware.  It's
also a great environment for porting over packages, you can get a package
fully functional in the uclibc root environment inside a uml without actually
disturbing your 'real router', and then rebuild for a specific target once
it's fully tested.

This is a first stab at a build that 'just works' and there will be more
cleanup to come.  The simple directions are:-

Configure for uml target
Configure with an ext2 root file system
build it all

In your bin directory you will find a kernel and an ext2 root file system
when it's finished.  Just run it like this:-

bin/uml/openwrt-uml-vmlinux ubd0=bin/uml/openwrt-uml-ext2.img con=null ssl=null ssl0=fd:0,fd:1 con0=null,fd:2

The uml will start, and eventually the serial console of the uml will be at your
console prompt.  If you would like it in xterms, substitute con=xterm and con0=xterm.
No networking is configured, but, it's a starting point.  The resulting file system
has just enough free space to start kicking the tires and playing in the world of
'embedded routers' along with all the resource restrictions that come with that
world.  

To configure networking and more, refer to the user mode linux documentation online.
A quick start goes along this line.  install the uml-utilities packages so you have
the uml switch in and running, then add a command param to your uml start like this

eth0=daemon,00:01:01:01:01:01,unix,/<your uml switch control socket here>

With that in, and uml networking actually functional (can be a challenge at times),
you should be able to ifconfig the interface and talk to the host side, or, if you
bridged the uml switch to your host network, you should be able to run udhcp and be
away with networking off to the world.  Again, if you are unfamiliar with uml and
uml networking, please read the docs and how-to stuff available on the net.  It does
take some fiddling to get it started and working right the first time, but after that,
it opens up a whole new world of virtual machines.



http://user-mode-linux.sourceforge.net/