From: Jeff Dike <jdike@ka...> - 2002-03-18 01:01:31
I made a couple of changes to uml_switch. First, I versioned the connect
protocol, which was way overdue. Second, I made it optional to supply the
data socket on the command line. Requiring the user to provide both was a
mistake from the start. What happens now is that uml_switch generates a
data socket on the fly and tells UML what it is in a reply to the connect
In the interest of not loading down the command line with compatibility
requirements forever, I decided to change the format.
uml_switch users will need to change their scripts (and fingertips) to use
one of the following:
uml_switch -unix <control socket>
uml_switch -compat-v0 <control socket> <data socket>
The default, with no arguments, is equivalent to:
uml_switch -unix /tmp/uml.ctl
The '-compat-v0' preserves the ability of uml_switch to talk to old UMLs
(i.e. 2.4.18-7 and earlier). It must appear before the '-unix'. With
'-compat-v0', uml_switch can talk to both old and new UMLs. Without it,
it can only talk to new ones.
The UML command line (and mconsole config command) has been similarly
changed. Instead of
Supplying <data> is non-fatal. It just produces a warning message and ignores
The new patch and utilities tarball will be released simulataneously, so
just cutting over to the new stuff will be possible.
Get latest updates about Open Source Projects, Conferences and News.