RE: RE: [Xen-devel] [PATCH] xen-2.0: privileged port connections

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

> > Perhaps a better way to handle consoles would be to use 
> 'screend', and
> > then have incoming ssh connections dispatched to particular screen
> > sessions.
> 
> screen is what is commonly used to handle many (mostly 
> serial) consoles
> these days, so hooking into that is certainly something most sysadmins
> would consider a natural choice.

I think we've got resounding agreement on using screen.
 
> > > > 5) you still have to deal with xfrd
> > > 
> > > It seems to listen on *:8002 ... 
> > > Is there no authentication either? Sigh.
> > > 
> > > And we probably need to look into the event channel 
> (8001) as well.
> > 
> > Xfrd needs an option to listen only on localhost. (It's 
> still needed for
> > save/restore even if you don't use migrate).
> 
> We could just pass it an option during startup.

Yep, though it should be configurable from the xend config.

> > The event channel only ever needs to be localhost (and 
> could probably be
> > turned into a unix domain socket quite easily).
> 
> Sounds good. Let's do it.

Keep those patches coming! :-)

Thanks,
Ian


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id149&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel