Jody Bruchon wrote:
> My main machine (the host) had an Athlon XP barbecue.
Heh - I had one over the weekend. Sorting out my Dad's computer, IDE cable got
in the way of the CPU fan and I didn't notice until it started a reset loop.
It took a couple of minutes before it cooled down enough for the motherboard
to be willing/able to report the CPU temperature - apparently it can't report
temperatures over 99 degrees C. Amazing thing it, it still works!
Cup of tea, anyone? :P
> I'll see what I can do, but I'll definitely need someone to mail me the
> ELKS source tarball again so I can put it back up.
Why put tarballs on a separate site when the SourceForge tools work? If CVS is
good to go, that's a lot easier to manage that manually patching and releasing
tarballs, especially when (and I'm being optimistic and not saying 'if') there
are multiple developers working on different things.
You could always create tarballs from a CVS export, and if SF host it then you
don't have to worry about your computer/bandwidth/etc.
> Also, I have full access to the entire ELKS project. Mail me if you
> need stuff done and I'll try to take care of it.
Do you have the SSH key needed for CVS commits?
Do you have the rights needed to add/remove project admins/developers?
I posted a PATCH a while back that adds the ability to select the root device
at compile time - I'd like that tested and committed, if possible.
--
Richard Wallman
Where are we going, and why am I in this handbasket?
-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
