missing checksum?

[File Shepard]

In the root of OpenBSD/5.0 on ftp.openbsd.org and the ftp3 mirror
there's no SHA or md5 or anything for checking the files downloaded from
there. Is this right?

I've spent several days downloading sys.tar.gz and src.tar.gz over a
modem connection, and I'd like to check what I downloaded, other than
doing gunzip -t

Thanks, Alan AB1JX

[Joachim Schipper]

This is what I got (no SHA256 file either):

$ sha1 src.tar.gz sys.tar.gz
SHA1 (src.tar.gz) = befa275d27cb351fbd829594092f857257cfce5f
SHA1 (sys.tar.gz) = b2bc1a570c85dc6ab27d0a1830d229cb62715fee

Note that you can update these tarballs over anynomous CVS/cvsync/etc,
that may help with authenticity as well.

Finally, I'm almost positive that sys.tar.gz is a subset of src.tar.gz.

Joachim

[File Shepard]

For some reason I never bothered to figure out if sys.tar.gz is a subset
of src.tar.gz, but I don't think so, at least not a complete subset.

src.tar.gz goes as /usr/src and sys.tar.gz gets put into /usr/src/sys
(but doesn't create the sys subdirectory). I think there's something in
/usr/src/sys from unpacking src.tar.gz, but it's not a complete set.
You need sys.tar.gz if you want to build a kernel.

ports.tar.gz and src.tar.gz contain the ports and src directories, but
sys.tar.gz doesn't. It'll splatter files all over the place and make a
mess if you just untar it. I've gotten so I create directories like
/usr/ports1 when I can't remember, then put the tarball into it and
unpack. If it made a subdirectory it's a simple matter to cd into
ports1 and do something like mv ports .. then delete ports1, easier than
cleaning up if you erred the other way.

Thank you for the SHA output. You wouldn't happen to have done xenocara
(the X source) as well by any chance?

Alan

[John McGrail]

On 2012-02-09, File Shepard <no...@nowhere.org> wrote:
> For some reason I never bothered to figure out if sys.tar.gz is a subset
> of src.tar.gz, but I don't think so, at least not a complete subset.
>

From some notes I took a year or so ago ... The contents of sys.tar.gz
are included in src.tar.gz on official install CDs. However, on the ftp
site they comes as two separate tarballs.

I presume this is to make it easier for people who have done ftp installs
and want to build a custom kernel. They don't have to download all the
source.

> src.tar.gz goes as /usr/src and sys.tar.gz gets put into /usr/src/sys
> (but doesn't create the sys subdirectory).

In both 4.9 and 5.0, sys.tar.gz includes ./sys/ in the path of all the
files and can be untarred directly in /usr/src.

>
> I think there's something in
> /usr/src/sys from unpacking src.tar.gz, but it's not a complete set.

As near as I was able to determine, sys.tar.gz is the complete contents of
/usr/src/sys/.

> You need sys.tar.gz if you want to build a kernel.
>
> ports.tar.gz and src.tar.gz contain the ports and src directories, but
> sys.tar.gz doesn't. It'll splatter files all over the place and make a
> mess if you just untar it. I've gotten so I create directories like
> /usr/ports1 when I can't remember, then put the tarball into it and
> unpack. If it made a subdirectory it's a simple matter to cd into
> ports1 and do something like mv ports .. then delete ports1, easier than
> cleaning up if you erred the other way.
>

You should probably read the release man page. It'll explain where the
tarballs go and what you can move elsewhere.

--
rat...@food.skaterat.net
All foods should be removed to reply

[John McGrail]

On 2012-02-09, John McGrail <rat...@food.skaterat.net> wrote:
>>
>> I think there's something in
>> /usr/src/sys from unpacking src.tar.gz, but it's not a complete set.
>
> As near as I was able to determine, sys.tar.gz is the complete contents of
> /usr/src/sys/.
>

oops forgot to include ... and the ftp src.tar.gz file does not include
any of ./sys.

[Joachim Schipper]

File Shepard <no...@nowhere.org> wrote:
> For some reason I never bothered to figure out if sys.tar.gz is a subset
> of src.tar.gz, but I don't think so, at least not a complete subset.
>
> src.tar.gz goes as /usr/src and sys.tar.gz gets put into /usr/src/sys
> (but doesn't create the sys subdirectory). I think there's something in
> /usr/src/sys from unpacking src.tar.gz, but it's not a complete set.
> You need sys.tar.gz if you want to build a kernel.
>
> ports.tar.gz and src.tar.gz contain the ports and src directories, but
> sys.tar.gz doesn't. It'll splatter files all over the place and make a
> mess if you just untar it. I've gotten so I create directories like
> /usr/ports1 when I can't remember, then put the tarball into it and
> unpack. If it made a subdirectory it's a simple matter to cd into
> ports1 and do something like mv ports .. then delete ports1, easier than
> cleaning up if you erred the other way.

The FAQ suggests that the CD and FTP src.tar.gz differ in this respect.
Which is confusing.

> Thank you for the SHA output. You wouldn't happen to have done xenocara
> (the X source) as well by any chance?

$ sha1 xenocara.tar.gz
SHA1 (xenocara.tar.gz) = a0d3e5acc829c9941fdc67eb62d084037bfcbaae

Having a fast connection is rather nice. ;-)

(You may want to look at devio.us as well; it's an easy way to get a
shell account on a better-than-modem connection.)

Joachim

[File Shepard]

Thanks again for the SHA.

I have a devio.us account: I'm ab1jx. I use it for downloading big
things from sites where I can't resume downloads. I split it and
download pieces. They run 4.7, same as my laptop.

From the 2 CD versions I have:

4.4's src.tar.gz is 127715972 bytes
4.7's src.tar.gz is 152430557 bytes

In 4.7 at least sys IS contained in src.tar.gz, I peeked with mc.
There's no separate sys.tar.gz on there.

I can see why they'd separate them though, most people would only need
one or the other. sys.tar.gz if you're going to build a kernel,
src.tar.gz if you're going to apply non-kernel patches. (like to ssh)

Alan