Frederick,

I didn't/don't really want to switch to -current, but thanks for the tip.


Would it be a good idea to tarball the snapshot sources? It would take up a
bit of server space, but it would allow people who need a functionality onl=
y
available in -current to recompile kernels etc. without long and complex cv=
s
updating. Making the tarball wouldn't take long if done at the same time as
the snapshot.

Snapshots seem generally to be more reliable than a -current taken at
random. In fact I can't really see the point of snapshots without their
source being available at least to developers (but maybe they want people t=
o
test a specific snapshot/kernel).


I can only get poor modem access (which with my main box a Mac G4 running
NetBSD is a problem all by itself) here in the sticks, not even ISDN, no
cable or (A)DSL, and I can't afford the =A320k plus for having a T-whatever
installed (and I can't get right-of-way even if I could afford it), so I
can't really use cvs update even on a connected box.

Maybe I should move to the city! I can't even put up a satellite dish
outside. Would one work in the attic?

Sorry to stray OT.

-- Peter Fairbrother

> Frederick Bruckman wrote:

> On Sun, 10 Feb 2002, Peter Fairbrother wrote:
>=20
>> Is the kernel source used to build a snapshot available as a .tgz? If so=
,
>> where? I found the snapshot I needed
>>=20
>> /pub/NetBSD/arch/macppc/snapshot/20011221-1.5ZA on ftp.plig.org ,
>>=20
>> but not the source for it. I need to compile a kernel.
>>=20
>> I have some stand-alone NetSD boxes, and can't use CVSup.
>=20
> The easiest thing, would be to go with slightly newer sources, from
> the weekly source snapshot:
>=20
> ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/src/sys.tar.gz
>=20
> "config", "lex", and "yacc" were updated recently, so you may have
> trouble getting it to build. If you need to update lex and yacc, to
> build config, they live in usr.bin.tar.gz. If it builds at all, we're
> still at 1.5ZA, so then it shouldn't cause you any problems.
>=20
> Alternatively, you could try to turn back the newer tarball, by
> running "cvs update -D 2001-12-21" in it on a well connected host.
>=20
> Frederick
>=20