I've looked in the archives and not seen (ot at least, not recognised) anything relevant, and I'm sure this problem is *obvious* to those in the know, but it is foxing me.
I connect to my server using ssh usingf putty from a Windows box. When I start a UML machine I use the following:
linux ubd0=Debian-3.0r2.ext2 ubd3=swapfs ssl=null con0=fd:0,fd:1 \ umid=debbie-01 \ con=pts root=/dev/ubd0 \ eth0=tuntap,,,172.20.20.59
That's OK, but it doesn't give the ssh session back! I'm assuming that this is because of the "con0=fd:0,fd:1" above. No problems, I just start another ssh session to the "host" and use "screen" to access the vc I desire through the /dev/pts/x device.
When I 'who' on the host it shows pts/0 for the original host session and on the client once started it shows ttyx, depending on the pts device I chose.
Ideally I'd like the ssh session back so that I could start more UML sessions. But primarily I think I need a better understanding of what all these darn pts, tty, con and ptys are, so my first request is for some reference that explains the meaning and inter-relationships of all these things. I've looked at the "Setting up serial lines and consoles" page, and tried to understand it and will continue to do so, but I haven't yet grasped it. Does anyone known of a tutorial or something that describes these Linux devices in a way that novice can understand. Anything would do, even if written at a 7-year old's reading level. Pretty pictures would be good too! <grin>.
I have of course, experimented. If I do anything to the "con0=fd:0,fd:1" bit above the console session on the ssh (putty) session just hangs without producing a list of vcs. As you might expect. And I cannot then access the UML machine and have to kill it.
Ideally I'd like to kick off, one, two, three, four, UML machines, and get back the ssh session and be able to access the UML machines via screen. Is this unreasonable? <grin>
Cliff,
You're very close. Your ssh session isn't being given up because your uml is holding your stdin,stdout by using con0=fd:0,fd:1. The trick is to start screen with a command from your ssh session. This way, your screen session can let go of the pts that's associated with your ssh session.
I've used a command like this before: screen -dmS uml01 /home/uml01/startuml.sh
This forces screen to start in detached mode, with a session id of uml01, so it's easy to type when you want to do a screen -r later. It executes the command startuml.sh which would naturally be your uml startup script. A logical extension of this would be:
ssh [EMAIL PROTECTED] screen -dmS uml01 /home/uml01/stgartuml.sh
This would start up your session, and since screen detaches itself, ssh returns immediately. You just have to ssh back as user uml01 and connect to that screen to see the console messages. It should be possible, however, to pipe those console messages thru logger(1) so you can read them via syslog. Add that to your startuml.sh script.
I believe that tools more sophisticated than this already exist. Google for umld and umlazi, IIRC.
Jed
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
