From: Oren T. <ore...@hi...> - 2002-06-25 09:48:45
|
1. Write a network device that uses the code from slirp. This way a uml can access to the host's network resources without any special setup on the host. No root privilege is required for setting up routing or setting permission on TUN/TAP devices on the host, either. This is good only for outgoing connections, though. http://slirp.sourceforge.net/ 2. Intercept attempt to open /dev/initctl. Connect it to a special device that talks the init control protocol to the init process in the uml on one side and with mconsole or signals on the other side. This will make it possible to add a 'shutdown' command on the mconsole or even shutdown a uml gracefully with kill -HUP. Oren |
From: Henrik N. <hn...@ma...> - 2002-06-25 11:27:22
|
Oren Tirosh wrote: > 1. Write a network device that uses the code from slirp. This way a uml > can access to the host's network resources without any special setup on > the host. No root privilege is required for setting up routing or setting > permission on TUN/TAP devices on the host, either. This is good only for > outgoing connections, though. For that I think you just need to run slirp on a pty on the host and connect a uml tty to it with the proper boot argument, then run slip on that UML tty. > 2. Intercept attempt to open /dev/initctl. Connect it to a special device > that talks the init control protocol to the init process in the uml on one > side and with mconsole or signals on the other side. This will make it > possible to add a 'shutdown' command on the mconsole or even shutdown a uml > gracefully with kill -HUP. Note: not all systems use /dev/initctl. Depends on what kind of init you are using. What feels more useful is if mconsole could execute commands within the UML, allowing you to execute shutdown or telinit. But then you could ofcourse do this over a virtual terminal.. Regards Henrik |