From: Benjamin R. <br...@al...> - 2001-12-24 15:43:51
|
Jeff Dike wrote: > br...@cs... said: > >>1) When UML is aborted with a KILL signal or a HUP (connection abort), >>there are UML process that hang around. Is this a bug or did I do >>something wrong? >> > > Are you killing the tracing thread alone, or are you hitting everything? Basically I'm telnetting to the machine and then closing the telnet session after starting linux. > > Hitting everything is a popular way of forcibly shutting down UML. Killing > the tracing thread will do what you want, but not yet. > > Do you know about the mconsole halt command? In most situations, that's > probably the best way to go. If UML is screwed up enough, it won't react > to that and a killall is probably called for. Yeah, we will be using UML for writing some simple kernel modules, so I would like to be able to tell the students they can just hit ^C. Plus, I don't want our server to get bogged down with aborted linux sessions. > > >>PS - Are there any other published experiences with using UML in a >>classroom environment would be highly appreciated! >> > > Have you seen http://user-mode-linux.sourceforge.net/case-studies.html? > > One of the case studies is a good-sized virtual network for students to > experiment with without messing up the physical ethernet. Yes I saw that one. I'm looking for something documented the problems that were encountered and how they were overcome... (So I have an idea what to expect.) ben |