A few more notes. There are no CD or DVD iso images. This release is currently only installable as a network install. When mirroring this release, it is best to do rsync, and to use the hardlink option (-H). This is because there is alot of duplication, and we have created hard links for those duplicates. Instructions are available at https://www.scientificlinux.org/download/mirroring/mirror.rsync Did I mention that this isn't for production use. Thank You - Troy Dawson - Connie Sieh Troy Dawson wrote: > The Scientific Linux developers are pleased to announce our "Very Alpha > Release" of Scientific Linux 5.0 > > This is not for production use. > This release will change *dramatically* before the final release. > You have been warned. > > Below are the changes from The Upstream Vendor Beta 2 release > > -Connie Sieh > -Troy Dawson > > ----------------------------------------------------------------------------- > > INFO > ----------------------------------------------------------------------------- > > Web Site > https://www.scientificlinux.org > > FTP > ftp://ftp.scientificlinux.org/linux/scientific/5rolling/ > > Mailing Lists > [log in to unmask] Development of Scientific Linux > [log in to unmask] Users of Scientific Linux > supporting each other > [log in to unmask] Announcements concerning > Scientific Linux > [log in to unmask] Announcements about Security Errata > > > ----------------------------------------------------------------------------- > > ADDED compared to vendor > ----------------------------------------------------------------------------- > > nedit > NEdit is a GUI text editor for the X Window System and Motif. > > nedit-5.5-10.i386.rpm > > > ------------------------------------------------------------------------- > Changed RPMS compared to vendor > ------------------------------------------------------------------------- > yum-3.0-5.5.SL.noarch.rpm > yum-conf-50-0.2.rolling.SL.noarch.rpm > gdm-2.16.0-19.SL.1.i386.rpm > > There are minimal changes compared to the "vendor" release. We have > changed the "rpms" that are required to be changed. These changes are > defined by the "vendor". > > redhat-logos-4.9.8-1.SL.3.noarch.rpm > redhat-artwork-5.0.5-21.SL.1.i386.rpm > sl-release-5.0-1.i386.rpm > sl-release-notes-5.0-2.i386.rpm > > ----------------------------------------------------------------------------- > > /Client /Server /VT /Workstation /Cluster /ClusterStorage > ----------------------------------------------------------------------------- > > TUVv5b2 consists of 2 cd sets, Server and Client. Each cd set has a > group of directories which contain the actual rpms. On the Client cd > this consists of Client,Workstation and VT. On the Server cd this > consists of Server,VT, Cluster, ClusterStorage. The VT directory > contains the same rpms on each cd. > The Cluster, ClusterStorage and Workstation directories do not have any > common rpms. The Client and Server directories contain many common rpms > along with many unique rpms. I have combined the 2 cd sets into 1 big > tree. If a rpm is in multiple directories I have made it via a hard > link to save disk space > > We are not sure if we will keep this big tree of directories or not. It > has the advantage as having the same tree structure as RHELv5b2. > > To install the rpms in /VT /Workstation /Cluster /ClusterStorage you > need to enter V for VT and W for Workstation and C for Cluster and S for > ClustorStorage at the "key" prompt in the installer. This is code from > TUVv5b2. It will be changed in our next beta. > So to install all of these you would put in > > VWCS > > at the "keys" prompt > > --------------------------------------------------------------------------- > /SRPMS/ > --------------------------------------------------------------------------- > At the moment, TUV SRPM's are still on the TUV's publically available > ftp server. When we get them up, they will be at > > scientific/5rolling/SRPMS/vendor/original > > Our modified SRPMS are at > > scientific/5rolling/SRPMS/ > > ------------------------------------------------------------------------- > There were some RPMS that did not build yet. For those packages we have > used the publically available packages from TUV. The largest of these > is openoffice. There are about 7 other smaller packages where we have > done this as well. > ------------------------------------------------------------------------- >