Re: Is install42.iso lagging behind cd42.iso and individual packages?
Yesterday evening I downloaded the install42.iso, cd42.iso and all *.tgz packages from the i386 snapshots directory on the ftp.openbsd.org website. All files had a timestamp of Sept. 24. I then ran them through MD5 to make sure they matched the expected checksum. This morning I performed two OpenBSD installs on two VMware machines; one using the install42.iso image and the included *.tgz packages, and one using cd42.iso and the individual packages (which I made available via a local HTTP server). Once this was done I compared the dmesg output of both installs and noticed that the install42.iso machine's kernel date is Sept. 13 while the cd42.iso machine's kernel date is Sept. 24. A quick check of the MD5s of the *.tgz packages in the install42.iso file show that they are different from the packages on the FTP site? So I'm just wondering: in the i386 snaphots directory, do the *.tgz packages in the install42.iso file typically lag behind the individual packages available on the FTP site? Is the way to get the most recent binaries (from -CURRENT) of OpenBSD to use individual packages and *not* the install42.iso? Building the install##.iso files with the X sets requires a bit of clever management. While I was on my recent vacation Peter Valchev was building snapshots and he did not know about the new build sequence required to do this right. We'll try to make it simpler, of course... In the next snapshots, it will be OK again.
Is install42.iso lagging behind cd42.iso and individual packages?
Hi, Yesterday evening I downloaded the install42.iso, cd42.iso and all *.tgz packages from the i386 snapshots directory on the ftp.openbsd.org website. All files had a timestamp of Sept. 24. I then ran them through MD5 to make sure they matched the expected checksum. This morning I performed two OpenBSD installs on two VMware machines; one using the install42.iso image and the included *.tgz packages, and one using cd42.iso and the individual packages (which I made available via a local HTTP server). Once this was done I compared the dmesg output of both installs and noticed that the install42.iso machine's kernel date is Sept. 13 while the cd42.iso machine's kernel date is Sept. 24. A quick check of the MD5s of the *.tgz packages in the install42.iso file show that they are different from the packages on the FTP site? So I'm just wondering: in the i386 snaphots directory, do the *.tgz packages in the install42.iso file typically lag behind the individual packages available on the FTP site? Is the way to get the most recent binaries (from -CURRENT) of OpenBSD to use individual packages and *not* the install42.iso? Thanks, -Martin
Re: Is install42.iso lagging behind cd42.iso and individual packages?
On 9/29/07, Martin Gignac [EMAIL PROTECTED] wrote: Hi, Yesterday evening I downloaded the install42.iso, cd42.iso and all *.tgz packages from the i386 snapshots directory on the ftp.openbsd.org website. All files had a timestamp of Sept. 24. I then ran them through MD5 to make sure they matched the expected checksum. This morning I performed two OpenBSD installs on two VMware machines; one using the install42.iso image and the included *.tgz packages, and one using cd42.iso and the individual packages (which I made available via a local HTTP server). Once this was done I compared the dmesg output of both installs and noticed that the install42.iso machine's kernel date is Sept. 13 while the cd42.iso machine's kernel date is Sept. 24. A quick check of the MD5s of the *.tgz packages in the install42.iso file show that they are different from the packages on the FTP site? So I'm just wondering: in the i386 snaphots directory, do the *.tgz packages in the install42.iso file typically lag behind the individual packages available on the FTP site? Is the way to get the most recent binaries (from -CURRENT) of OpenBSD to use individual packages and *not* the install42.iso? For the installation file sets you can use the download script from http://www.bsdforums.org/forums/showthread.php?s=threadid=22727 Besides using these sets to create your own ISO you alternatively can use them in the environment friendly USB-mediazine method as described in http://www.bsdforums.org/forums/showthread.php?t=50433 =Adriaan=
Re: Is install42.iso lagging behind cd42.iso and individual packages?
For the installation file sets you can use the download script from http://www.bsdforums.org/forums/showthread.php?s=threadid=22727 Besides using these sets to create your own ISO you alternatively can use them in the environment friendly USB-mediazine method as described in http://www.bsdforums.org/forums/showthread.php?t=50433 Thanks for the tip. By the way, I found this in the misc@ archives: --- SNIP --- Adriaan wrote: A md5 -c MD5 fails for install42.iso Thats' an experimental feature, not necessarily kept in sync with the rest of the build process at the moment, and thus, the MD5 files may very well not match. Nick. --- SNIP --- I take it that for the time being install42.iso is not necessarily generated automatically right after a new snapshot build. That would explain why the file sets in the ISO file are older than the ones on the FTP site. The only thing that threw me off was that the timestamp for all files in the snapshot directory, including install42.iso, where the same. That's why I assumed it was a new (and up-to-date version). I guess everything is just copied over to the FTP site after a build, regardless of it was actually updated or not. -Martin
