Lines Matching refs:running

165   User-Mode Linux as if they were running under a normal kernel, like
292      hosts''  for the scoop on running UML on your system.
453   for the scoop on running UML on your system.
509      If the network is running, then you can telnet to the virtual
780   initial boot output will appear in the terminal that you're running
897      running 2.2
900      running 2.4.  Also, the TUN/TAP transport is able to use a
908      don't mind running the daemon in order to get somewhat better
932   running a prebuilt kernel from this site, everything is already
1203   The easiest way to get up and running is to let the setuid uml_net
1208   the setuid helper, use it to get up and running, then read the next
1247   There are a couple potential problems with running the TUN/TAP
1263   make sure that /usr/src/linux points to the headers for the running
1423      Also, the /dev/net/tun device must be writable by the user running
1511   setuid root if you're not running UML as root.  This is because the
1641   you ran the daemon with no arguments, running the UML on the same
2105   However, since UML is running on the host, it can access those
2336   can be used to check that a UML is running.  It's also a way of
2444   Note that a UML running with more than one CPU will have problems
2456   crazy, running all the jobs it didn't do earlier.
2490   You can have the kernel running under the control of gdb from the
2492   xterm with gdb running inside it.  The kernel will send some commands
2503   Not every bug is evident in the currently running process.  Sometimes,
2828   If you don't have the kernel running under gdb, you can attach gdb to
2844   you will get an xterm with gdb running in it.
2856   will fire up an xterm with gdb running in it.
2862   UML has support for attaching to an already running debugger rather
2900   o  Hit return in the shell, and UML will start running, and strace
2903      Note that this is different from running
3029   Let's see what's currently running:
3172   to that stack while the idle thread wasn't running.  This apparently
3906   o  It doesn't work on hosts running 2.4.7 (or thereabouts) or earlier.
3969   this down by running tcpdump on every interface the packets travel
4012   On i386 kernels, there are two ways of running the loop that is used
4032   If you're running an up to date kernel with an old release of
4045   happen in random places, or you try running the debugger to see what's
4047   host kernel.  If you're not running a stock Linus or -ac kernel, then
4085   line).  An xterm will start up with gdb running inside it.  Continue
4147   or by running ps on the host and finding the line that looks like
4574   Chris Reahard built a specialized root filesystem for running a DNS