Lines Matching refs:attach

478      lines and consoles''  to see how to attach the consoles to
582   It is possible to attach UML serial lines and consoles to many types
586   You can attach them to host ptys, ttys, file descriptors, and ports.
591   o  hook two virtual machines together by having one attach to a pty
592      and having the other attach to the corresponding tty
631   There are a number of different types of channels to attach a UML
633   attach to.
659      This will make UML attach the device to the specified tty (i.e
667   will attach UML's console 1 to the host's /dev/tty3).  If the tty that
687      This will attach the UML devices to the specified host port.
711   This channel has the advantage that you can both attach multiple UML
720   If you attach the main console to a portal, then the UML boot will
732      attach a UML device to it.  This is most commonly used to put the
813   You can attach two virtual machines together with what amounts to a
836   Log in, make sure that it has no getty on that serial line, attach a
958   This sets up eth0 inside the virtual machine to attach itself to the
1218   The format of the command line switch to attach a device to a TUN/TAP
1227   For example, this argument will attach the UML's eth0 to the next
1648   will cause the eth0 driver to attach itself to the daemon correctly.
2528   o  attach to the thread you are interested in
2828   If you don't have the kernel running under gdb, you can attach gdb to
3006   I run gdb and attach pid 1935.
3084   before gdb can attach it:
3114   Now I detach from the signal thread, attach to the fsck thread, and
3467   attach to it with gdb.  This is done by sending it a SIGUSR1, which is
4178   attach to it.  So, this is how the fancy footwork goes:
4196   Detach from the tracing thread and attach to that other thread:
4206        (host gdb)  attach pid
4252   process should not have gone to sleep and stayed asleep.  Then attach