In article <20040922110840.R18149@x9.ybpnyarg>,
walt <wa1ter@myrealbox.com> wrote:
> On Tue, 21 Sep 2004, Daniel Prather wrote:
>
> > In article <4512.192.168.0.2.1095819701.squirrel@192.168.0.2>,
> > justin@shiningsilence.com wrote:
> >
> > > > Yes, I've been doing it from the first virtual console. I did as you
> > > > said and let it run until it locked up, then tried ctrl-alt-escape.
> > > > Nothing :( No messages or anything are ever printed. It simply locks
> > > > up at random points as cvsup runs.
> > >
> > > What happens if you, say, download a very large file? Or if you download
> > > a tarball of the src/dfports ( http://dragon.bsdtech.com/DragonFly/ ) and
> > > ungzip/tar? I'm wondering if it's something with bad RAM or the drive,
> > > triggered by file activity.
> >
> > I tried that using fetch. It d/led the tarball just fine. I think did
> > "tar jxvf src.tar.bz2" and that proceeded without a hitch as well.
> > Soooooo, I'm stumped! :(
>
> I wonder if running cvsup from gdb would be helpful?
In a cruel twist of fate, I did run cvsup in gdb. It worked just fine
then, though I got *no* information out of it. How annoying is that? :)
So I got /usr/ports updated, but now I have no idea why cvsup wasn't
working to begin with. *grumble grumble*
Daniel Prather
MysticOne
mysticone@linuxpowered.com