It does now.
Use the following paths:
ssh://elpaso.eng//export/gate-hg
ssh://elpaso.eng//export/gate-hg/usr/closed
...and it should work correctly.
You may prepend "username@" to "elpaso.eng," but by default, it should
connect as you.
--Mark
On Wed, 16 Jul 2008, Will Fiveash wrote:
> Date: Wed, 16 Jul 2008 11:59:28 -0500
> From: Will Fiveash <William.Fiveash at Sun.COM>
> To: scm-migration-dev at opensolaris.org
> Cc: gatekeeper at onnv.eng.sun.com
> Subject: will the ON gate system run an hg daemon?
>
> On Mon, Jul 14, 2008 at 06:59:29PM -0600, Mark J. Nelson wrote:
>> ------ Developer Responsibilities, aka What You Need To Do NOW ------
>>
>> 1. Follow the tools flag day from last week:
>>
>> http://www.opensolaris.org/os/community/on/flag-days/pages/2008071001/
>>
>> 2. Unless you're integrating into snv_95 or snv_96, stop procrastinating.
>> Switch to Mercurial. NOW.
>>
>> 3. If you're managing a project gate or need more sophisticated knowledge
>> or Mercurial, then read the Mercurial book: http://hgbook.red-bean.com/
>>
>> ...this is particularly useful (required reading?) if you're
>> accustomed to peeking under the hood (ie using SCCS or manipulating
>> the nametable) in TeamWare. This tool is much different, and you
>> should not expect to bypass it, or muck about with the way it stores
>> files.
>>
>> 3. Really. Switch now. The wx2hg script is part of SUNWonbld; read the
>> man page and follow it. Take a clone of the internal or external onnv
>> gate:
>>
>> internal (open): /net/elpaso.eng/export/gate-hg
>> internal (closed): /net/elpaso.eng/export/gate-hg/usr/closed
>>
>> external (open-only): ssh://anon at hg.opensolaris.org/hg/onnv/onnv-gate
>>
>> ...and go for it.
>
> In regards to point #3, will elpaso.eng/onnv.sfbay support an ssh/hg
> service as hg.opensolaris.org does? I ask this because the time to
> clone a gate to my system in Austin, TX varies greatly depending on the
> protocol used to transfer the data:
>
> $ timex hg clone ssh://anon at hg.opensolaris.org/hg/onnv/onnv-gate
> destination directory: onnv-gate
> requesting all changes
> adding changesets
> adding manifests
> adding file changes
> added 7107 changesets with 97565 changes to 50605 files
> updating working directory
> 45608 files updated, 0 files merged, 0 files removed, 0 files unresolved
>
> real 15:50.05
> user 1:46.08
> sys 25.74
>
> $ timex hg pull -u -r onnv_94 /net/elpaso.eng/export/gate-hg
> Not trusting file /net/elpaso.eng/export/gate-hg/.hg/hgrc from untrusted user
> daemon, group other
> pulling from /net/elpaso.eng/export/gate-hg
> requesting all changes
> adding changesets
> adding manifests
> adding file changes
> added 7056 changesets with 97244 changes to 50537 files
> 45551 files updated, 0 files merged, 0 files removed, 0 files unresolved
>
> real 4:14:38.71
> user 2:03.01
> sys 43.32
>
> So cloning a gate via NFS takes about 4 hours longer than doing it via
> ssh/hg.
>
> Note that I'm able clone a Teamware gate in MPK to my Austin system
> using a script called clone_ws that takes about 16 minutes. The script
> is probably doing something similar to an hg clone via ssh/hg in that it
> just transfers the SCCS delta files via a compressed stream then does
> the sccs gets and creates the nametable locally.
>
> --
> Will Fiveash
> Sun Microsystems Inc.
> http://opensolaris.org/os/project/kerberos/
>
