[Coco] nitros9 level3
Gene Heskett
gheskett at wdtv.com
Sat Oct 20 22:29:58 EDT 2012
On Saturday 20 October 2012 22:09:39 Aaron Wolfe did opine:
> On Sat, Oct 20, 2012 at 9:44 AM, Gene Heskett <gheskett at wdtv.com> wrote:
> > On Saturday 20 October 2012 09:35:49 Aaron Wolfe did opine:
> >> On Fri, Oct 19, 2012 at 11:37 PM, Lothan <lothan at newsguy.com> wrote:
> >> > The current NitrOS-9 repository uses Mercurial, so if the old CVS
> >> > repository has been disabled you can get to it via hg on Linux or
> >> > TortoiseHG on Windows. The URL for the Mercurial repository is
> >> >
> >> > http://nitros9.hg.sourceforge.net:8000/hgroot/nitros9/nitros9
> >>
> >> A word of warning to anyone using CVS: It will still 'work', but
> >> what you get will not be the current source.
> >> I'm not sure what CVS is serving up, but it isn't the same as what
> >> mercurial gives you. Wasted some time here for sure.
> >
> > Aaron: I have installed mercurial, and configured my bashrc's to
> > include the /etc/bash_completion.d/mercurial file.
> >
> > But the hgrc files installed are empty of any active content, and from
> > reading the man pages I don't have a clue what to put in them. Are
> > there any examples extant that can be shared?
> >
> > Once that has been solved, what would a command line to pull the repo
> > with hg look like?
> >
> > And one to just pull any updates without destroying any local work
> > since the last pull?
>
> I'm going to trust you were answered by others, because I honestly
> don't know much about hg at all.
> clone to get the source, that's about the extent of my knowledge :)
> I was just warning people that had used CVS in the past that CVS is
> not delivering current code.
>
Got it, built it already. And found a missing file, which when found in an
older tree, is 6309 only code with no cpu switches in it. That file(s) are
nitros.asm and end.asm. Missing totally from the level3 subdir, and
according to locate, is not present in the mercurial clone at all.
But, I did find something that the coco can do but linux can't!
Pay attention to these screen scrapes:
{t2|08}/DD/NITROS9/6309L2/SCRIPTS:dir ../../../../../../nitros9
Directory of ../../../../../../nitros9 2012/10/20 21:48
6309L2 6309L3 3.2.9 COLORZAP.DSK HRSDOS.os9
DSKS 3.2.9a dw3install boottrack-gene DW-stf
dd.b09 DW3TREE cmds.os9 OS9Gen Cobbler
dsave.out Directory of ../../../../../../nitros9 2012/10/20 21:48
6309L2 6309L3 3.2.9 COLORZAP.DSK HRSDOS.os9
DSKS 3.2.9a dw3install boottrack-gene DW-stf
dd.b09 DW3TREE cmds.os9 OS9Gen Cobbler
dsave.out
Count the backup levels in the prompt, then in the command line.
gene at coyote:/opt/nitros9/level3/coco3/modules$ ls
../../../../../../../nitros9
ls: cannot access ../../../../../../../nitros9: No such file or directory
I am 5 levels up, but used 6 levels of backtracking.
Linux CAN do it one level at a time however.
gene at coyote:/opt/nitros9/level3/coco3/modules$ cd ..
gene at coyote:/opt/nitros9/level3/coco3$ cd ..
gene at coyote:/opt/nitros9/level3$ cd ..
gene at coyote:/opt/nitros9$ cd ..
gene at coyote:/opt$ cd ..
gene at coyote:/$ cd ..
gene at coyote:/$ cd ..
gene at coyote:/$
Go figure... But it can sure break a nitros9 build script on a linux box.
And I get to keep all the pieces. :)
Aha, found it. In linux, /opt is not the root of the filesystem. So in
order for that to work, you must also add the /opt to the path being
accessed.
Like this:gene at coyote:/opt/nitros9/level3/coco3/modules$ ls
../../../../../../../../../opt/nitros9
3rdparty bootman ChangeLog defs docs level1 level2 level3 lib
makefile ReadMe rules.mak scripts TODO
Works, but can that be used in a script? I see no reason why not.
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
Cheers, Gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
<Mercury> LordHavoc: I'm already insane.
<Coderjoe> damn straight. or curvy, crooked, or what have you
More information about the Coco
mailing list