Richard Lowe writes: > The plan of record is that initial migration remains internal (I > wouldn't know the path, but I would assume /ws/onnv-gate), and > hopefully very shortly thereafter the open portion of the ON gate > moves to opensolaris.org.
True, but I don't think we've talked about access methods yet for the inside-the-SWAN portion. I suspect that the /ws automounts are problematic for the converted Nevada gates. As I understand it (and an hg expert should correct me ;-}), when hg runs with a file system path, it runs gate-side scripting in the context of the invoker or just refuses to run it at all. This means that if /ws/onnv-gate is open for push, gatelings will be able to walk around any gate scripts just by changing their local hg configuration. Plus, even in ordinary pull-only use, it means more of those annoying "Not trusting file ... from untrusted user gatekeeper, group staff" messages. That means that we really do need to stop usage of /ws/onnv-gate as a gate, and use hg the way it was meant to be used -- with ssh://onnv.sfbay/ instead. If /ws/onnv-gate exists at all, it needs to be just a copy of the source code itself, rather than an actual Mercurial repository. (I know some people cd over to the gate and run cscope; that usage should probably be preserved.) The details on those changes likely need to be in the heads-up messages. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
