[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: kernel source tarballs for current?
ctm is for low bandwidth. If you only need kernel sources,
the whole /sys/ subdir of the repository is 100mb. This would
get you the most functionality. If you used rsync to update the
repository on a machine on the net, then you could ferry only
the files that are more recent than the last time you ferried
the repositry home. I would do this if I were in your shoes,
especially if your laptop has 100mb free (plus room as things
grow) and a network connection at home to your home machines.
(actually this would be alot less than 100mb if you only
got the sparc kernel code, but would require abit more rsync
If you had uucp or something similar at home, where you could
get email but nothing else, ctm would be the obvious choice.
As you suggest, you could definately shuttle ctm deltas in
your pail 'o bits.
Which method is entirely up to your preference.
On Fri, Jan 21, 2000 at 05:30:19PM -0500, OpenBSD Bob wrote:
> > > www.openbsd.org/anoncvs.html also suggests to use the ksrc-common and
> > > ksrc-sparc modules, which will get you a kernel tree of current only for
> > > sparc.
> OK... I looked at the ctm tree. For the sake of discussion.....
> IFF I am only wanting a current set of sources, are the ctm base files
> what I am after, rather than a cvs tree, for use on a remote machine,
> not connected to the net? If my machines were on the net, cvs would
> be the best choice. But, since I manually need to ferry the sources
> to my home network, via tape or a cd or a laptop, it would seem that
> the ctm tree would be the way to go. Yes/No?????
Todd Fries .. email@example.com