![](https://seccdn.libravatar.org/avatar/4b6e0b79d8a9358a3b524347b87a96f9.jpg?s=120&d=mm&r=g)
On the premise that the chief reason for buying CDs (other than being nice, of course) is to be able to do a "slap it in and have it all" installation; and given that there are now a number of downloadable security patches for 8.0; and given that SuSE seems to have pretty good revision control: Are the CD box sets labeled in such a way as to indicate what date the software therein is patched up to, and if so what is the current date/cut number that one would expect to see if purchasing from SuSE's web site, as well as in the retail channel? Couldn't find this information on the web site. I am in the USA. -- Fred Morris m3047@inwa.net
![](https://seccdn.libravatar.org/avatar/16ffa7b99ae567ca710622b9f14bb5e6.jpg?s=120&d=mm&r=g)
On the premise that the chief reason for buying CDs (other than being nice, of course) is to be able to do a "slap it in and have it all" installation; and given that there are now a number of downloadable security patches for 8.0; and given that SuSE seems to have pretty good revision control:
Are the CD box sets labeled in such a way as to indicate what date the software therein is patched up to
SuSE doesn't change the CDs of a distribution once it's out. The amount of updates available for 8.0 exceeds 1 CD by a long shot, partly due to the fact that KDE was updated completely 3 times, and partly due to the fact that each single update is offered as normal .rpm and also as .patch.rpm. I have argued with SuSE before that those .patch.rpm are a waste of time and bandwidth. There is an update CD available for 8.0, but I don't think it has the latest KDE 3.0.2. It's easy to make one yourself: mirror the updates directory from some server, using rsync with these excludes: *kde*-3.0-* *kde*-3.0.1-* kde1/kdemultimedia3.rpm zq1/kdebase3.spm *.patch.rpm (you can save another 100M or so by excluding those KDE translations you don't use) (use --exclude-from). There's an sdb article on how to make a SuSE patch CD (mainly it's keeping the correct directory structure). You can test this with YOU. The difference between calling YOU and patch CD from yast is that the former allows you to specify a disk directory. The disk directory must also have patch CD format. It's easy to keep a number of machines current then, though it's still dog-slow to run ("download" patch info from hard disk, takes aaaages for a few kilobytes, select packages, "download" packages, i.e. copy from disk to same disk, check package signatures, yeah good idea, but of course you've done it already done after download). Oh yes, you need to symlink all .rpm to .patch.rpm as well. IMHO YOU leaves considerable scope for a lot of improvements. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.orcon.net.nz/ Please do not CC list postings to me.
![](https://seccdn.libravatar.org/avatar/3930549650aca5f71fcb2f94a038bbcb.jpg?s=120&d=mm&r=g)
SuSE doesn't change the CDs of a distribution once it's out. The amount of updates available for 8.0 exceeds 1 CD by a long shot, partly due to the fact that KDE was updated completely 3 times, and partly due to the fact that each single update is offered as normal .rpm and also as .patch.rpm. I have argued with SuSE before that those .patch.rpm are a waste of time and bandwidth.
There is an update CD available for 8.0, but I don't think it has the latest KDE 3.0.2. It's easy to make one yourself: mirror the updates directory from some server, using rsync with these excludes:
*kde*-3.0-* *kde*-3.0.1-* kde1/kdemultimedia3.rpm zq1/kdebase3.spm *.patch.rpm
For the overhead data (the .patch.rpm and who needs the sources) I got the same opinion? For the rest not. If you run Online Update Yast gets you the only needed files. I got a fat Installation (4BG, not all packages) inculding all developement packages of my installed packages as well as all libraries and sources for compiling since there is no other way to install not included software like mplayer or any other usefull stuff. Yast needed not more than 100 MB for downloading for all past released updates. If you install everything then do not wonder about fat downloads! Philippe
participants (3)
-
m3047@inwa.net
-
Philippe Vogel
-
Volker Kuhlmann