Re: openssl
I do not think it will. You will notice that there is nothing in that directory newer than 2012. The RHEL support matrix is at https://access.redhat.com/support/policy/updates/errata If you need errata support for RHEL 4 then I suggest you purchase a RHEL 4 subscription and "purchase annual Add-on subscriptions called Extended Life Cycle Support (ELS) that provide similar support to Production Phase 3 through March 31, 2017" . Red Hat does not publish the srpm to the ELS support packages in the public ftp area . -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov On Fri, 4 Mar 2016, Paul Casteels wrote: Thanks for the link. I hope it will become available there in a few days.= Kind regards Paul Casteels
Re: openssl
On Thu, 3 Mar 2016, Paul Casteels wrote: For the DROWN security vulnerability a patch for RHEL4 was released by Re= dHat: openssl-0.9.7a-43.23.el4.ia64.rpm openssl-devel-0.9.7a-43.23.el4.ia64.rpm Is there any chance it will become available for SL4? It does not seem to be available via the "free" ftp.redhat.com site. -rw-r--r--5 ftp ftp 2816961 Feb 01 2012 openssl-0.9.7a-43.18.el4.src.rpm lftp ftp.redhat.com:/pub/redhat/linux/updates/enterprise/4AS/en/os/SRPMS> -- -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: Vbox with new Kernel vers. 3.10.0-327.3.1(SL7.1)
On Tue, 29 Dec 2015, Yasha Karant wrote: On 12/28/2015 01:37 PM, S A wrote: Hi, I was out for holiday last week and came back to my SL 7.1 desktop needing a slew of updates. I had been running VirtualBox-5.0-5.0.10_104061_el7-1.x86_64 against kernel-3.10.0-229.14.1.el7.x86_64 with out issue. After installing the latest kernel mentioned by Etienne, and attempting to rebuild the vboxdrv modules, I had similar failures. Afterward, I attempted to upgrade to VirtualBox-5.0-5.0.12_104815_el7-1.x86_64, I discovered the libdevmapper issue noted in the previous post which prevented the newer version from installing. It seems that there is a VirtualBox bug filed against the EL7.2 3.10.0-327 kernel noted here: https://www.virtualbox.org/ticket/14866 which may be causing the issues you are encountering. Unfortunately, the testing build for EL7: https://www.virtualbox.org/download/testcase/VirtualBox-5.0-5.0.11_104721_el7-1.x86_64.rpm, does not install due to the same libdevmapper issue. I had hoped maybe the devmapper issue was introduced in builds between the latest testbuild and the release build for 5.0.12, no such luck. I have device-mapper-libs-1.02.93-3.el7_1.1.x86_64 installed, but it seems that the VirtualBox package is calling for device-mapper-libs-1.02.97, which doesn't seem to be available for SL7. The CentOS and Oracle Linux public yum repo's latest version is device-mapper-libs-1.02.107-5.el7.x86_64. Is that in the pipeline for release to SL7 soon? Thanks! I am confused. As I thought I understood the current EL situation, Red Hat owns CentOS and distributes EL full source, per GPL, Linux, etc., licenses, through CentOS for all non-RH rebuilds (e.g., Oracle) to use (sans Red Hat logos, services, etc.). In this case, two questions: (1) Is Fermilab/CERN not funded well enough to have the same rebuliding/packaging resources as Oracle just to rebuild from the RH CentOS sources, and thus is delayed in production binary (RPM) release compared to Oracle? Both Fermilab and CERN are funded through their respective governments that support fundamental research. CERN is NOT involved in SL 7 . (2) If (1) is true, during the interval before the "current" RH production release is a SL release, can one simply use the CentOS or Oracle RPMs (e.g., in this case, device-mapper-libs-1.02.107-5.el7.x86_64.rpm) to maintain compatibility with Oracle licensed-for-free products (e.g., VirtualBox)? Yasha Karant device-mapper-libs-1.02.107-5.el7.x86_64.rpm is available via the "rolling" repo now. -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: some naive question from new user
On Sun, 13 Dec 2015, Albert wrote: Dear: I am a new Scientific user and I've got some naive questions. I would be appreciated if somebody can give me some advice. (1) I found there are different iso file from: http://ftp1.scientificlinux.org/linux/scientific/7x/x86_64/iso/ If I would like to install X64 plus 32 bit environment libraries, which one should I download? I am going to do some professional computational work under Scientific Linux, and many software may need various libraries such as: python, libsqt, libstdc, gcc, boost, perl and so on. Either of the DVD ones. Would the following iso be sufficient for my purpuse? SL-7-Everything-Dual-Layer-DVD-x86_64-2015-04-07-7.1.iso 06-Apr-2015 11:376.6G Yes but as the name suggests you need to burn to a dual layer DVD. (2) How can we install the 32bit library? I rember there is no any options of selecting 32bit library during the first refreshing installing Redhat. I don't know what's the situation of SL-7.. Same for SL 7. (3) If some library is missing from above DVD file, where can I can something additonal? How can we add local iso to software repository? How can we add a online address to software repository? You can use YUM to install packages after the initial install via online access as this is available by default. Adding ISO as a software repository would require that you make a "something.repo" file in /etc/yum.repos.d/ . Look at existing ones for a example of what to do. (4) Recently I bough a very new laptop HP pavilion SE 15 and the Wlan is intel dual band wireless ac 3165. I am just wondering, will SL-7 support WIFI in the laptop? I suspect so as Intel is fairly well supported. Thank you very much Albert -- -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: to devel - gdal-libs rpm dep failure
On Wed, 16 Dec 2015, lejeczek wrote: On 15/12/15 15:52, Connie Sieh wrote: On Tue, 15 Dec 2015, lejeczek wrote: --> Running transaction check ---> Package gdal-devel.x86_64 0:1.11.2-1.el7 will be updated ---> Package gdal-devel.x86_64 0:1.11.2-2.el7 will be an update ---> Package gdal-libs.x86_64 0:1.11.2-1.el7 will be updated ---> Package gdal-libs.x86_64 0:1.11.2-2.el7 will be an update --> Processing Dependency: libpoppler.so.46()(64bit) for package: gdal-libs-1.11.2-2.el7.x86_64 --> Finished Dependency Resolution Error: Package: gdal-libs-1.11.2-2.el7.x86_64 (epel) are we missing newer poppler in the repos? regards There is a newer poppler in 7.2 that provides the 46 version of the library . We do not have 7.2 out yet but are working on it. ok, why gdal depens on it alread? I'm running 7.1 with yum-conf-sl7x. -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov gdal is from EPEL . They must have built it against the newer poppler. -- -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: to devel - gdal-libs rpm dep failure
On Tue, 15 Dec 2015, lejeczek wrote: --> Running transaction check ---> Package gdal-devel.x86_64 0:1.11.2-1.el7 will be updated ---> Package gdal-devel.x86_64 0:1.11.2-2.el7 will be an update ---> Package gdal-libs.x86_64 0:1.11.2-1.el7 will be updated ---> Package gdal-libs.x86_64 0:1.11.2-2.el7 will be an update --> Processing Dependency: libpoppler.so.46()(64bit) for package: gdal-libs-1.11.2-2.el7.x86_64 --> Finished Dependency Resolution Error: Package: gdal-libs-1.11.2-2.el7.x86_64 (epel) are we missing newer poppler in the repos? regards There is a newer poppler in 7.2 that provides the 46 version of the library . We do not have 7.2 out yet but are working on it. -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: Will this evolution fix be in our 7 updates?
On Thu, 19 Nov 2015, ToddAndMargo wrote: https://rhn.redhat.com/errata/RHBA-2015-2226.html According to the above link this is part of 7.2 . So we will release it as part of 7.2 . -Connie Sieh
Re: installing devtoolset-3 on sl6x
With Devtoolset 3 TUV made it part of Software Collections vs having it be its own product. So you need the softwarecollections repo rpm. ftp://ftp.scientificlinux.org/linux/scientific/6x/external_products/softwarecollections/yum-conf-softwarecollections-1.0-1.el6.noarch.rpm -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov On Tue, 3 Nov 2015, Ken Teh wrote: I dont seem to be able to install devtoolset-3 on an sl6x x86_64 system. I've done it successfully with devtoolset-2 on an i686 system. My procedure is 1. Wget the yum-conf-devtoolset rpm and install it. 2. Then, when I do a # yum --enablerepo=devtoolset install devtoolset-3-toolchain it just comes back and says no such available package. Though the package is listed clear as day on the mirror. I've tried this on 2 different systems and the result is the same. I'm baffled. What am I missing? Thanks.
Re: Creating a new install tree for SL 7 rolling + other RPMs
Hi Torsten, The lorax tool should get you where you are going. It ships within SL7. Pungi should also be looked into. Depends on where in the "tree" building process you want to be. Pungi builds the "rpm" tree part of a RHEL release. It takes as input kickstart files which specify where to get rpms from and which rpms to place in the tree. This is known as the "gather" step of Pungi. Pungi also can call "lorax" to build the files that reside in /images/ which include boot.iso and the pxe files. Pungi can take the full build tree and create the 'DVD' install media. So it depends on what you have to start with and what you want as the result. -connie > Pat This doc might help: https://fedoraproject.org/wiki/Anaconda/Features/Lorax-TreeBuilder https://www.brianlane.com/creating-the-anaconda-bootiso-with-lorax.html On 10/15/2015 06:54 AM, Torsten Luettgert wrote: Hello all, I'm looking for a way to create own "install media" - an install repo tree would be fine, too, because the boxen I'm setting up are all installed via PXE from an nfs tree. In SL6, there was this revisor thingy (http://scientificlinux.org/documentation/customize-sl-for-your-site/) which looks perfect; there is no revisor in SL7, though, and I think I remember it being discontinued. Is there a replacement which enables me to throw a truckload of RPMs on top of the SL7.1 install RPMs and create an install tree from them? Thanks for help and best regards, Torsten P.S.: if anyone's interested, the background is this: I'm working on an internal product which sets up a bunch of KVM machines working together in a defined way (heavily firewalled, intricate internal networking etc.); a test run will create and configure 21 machines from scratch and takes a whopping 19 hours now. A lot of time is wasted during the installs for pulling and installing updates, setting up other repos and installing needed packages from there, then re-checking for updates during the first configuration run (I'm using salt for this). A customized tree would speed things up a lot. -- Pat Riehecky Scientific Linux developer Fermi National Accelerator Laboratory www.fnal.gov www.scientificlinux.org
Re: clang and Scientific Linux
--047d7bd9006e956b96051cfc958d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have installed Scientific Linux. I would like to use clang. I see that clang is not part of the yum repository. I downloaded the latest Fedora zip from clang.llvm.org and installed clang in /usr/local When I go to run clang I get an error that GLIBCXX 3.4.20 is not available. I have found in libstdc++ =E2=80=8BGLIBCXX =E2=80=8B 3.4 to 3.4.19, but not GLIBCXX 3.4.20 =E2=80=8B.=E2=80=8B My version of gcc installed is 4.8.3 9.3l7 =E2=80=8B. I have looked for solutions on the web and many are partial or requiring complete source build of clang. I might be able to use a previous version or so of clang to that version that wants to use GLIBCXX 3.4.19 or less, but since clang was not installed via yum, I'm not certain how to download grade it properly. Are there any recommendations from this list on how to (uninstall/re-install) install clang on Scientific Linux? I understand that Scientific Linux is a variant of Fedora. Many of the tasks recommended for Fedora apply to Scientific Linux, but I'm still lost as my administration skills are being tasked. Thanks for the help and education. Keith Smith =E2=80=8B --047d7bd9006e956b96051cfc958d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable If you installed Scientific Linux 6 or 7 then clang is available via the epel repo. yum --enablerepo=epel install clang -Connie Sieh
Re: unfortunate bind dns attack
hold the 6.7 security updates and were hoped to be released on Wed 3rd=20 (presumably US time). Ooops. I meant 6rolling-security. These are going out now for SL 6 . -Connie Sieh Hi, I see many 6_7 updates now dropping into the 6x tree on server. However we seem to be missing the 'glibc-2.12-1.166.el6_7.1.src.rpm' build in both rolling and the 6x tree. glibc-2.12-1.166.el6_7.1 is a bug fix , not a security errata. Yesterday only security errata were released. If you want glibc-2.12-1.166.el6_7.1 is is available in the 6rolling tree at ftp://ftp.scientificlinux.org/linux/scientific/6rolling/ Note that 6rolling contains SL 6.7 Beta 1 . lftp ftp.scientificlinux.org:/linux/scientific/6rolling/x86_64/os/Packages ls glibc* -rw-r--r--1 ftp ftp 4556324 Jul 24 14:14 glibc-2.12-1.166.el6.i686.rpm -rw-r--r--1 ftp ftp 3996164 Jul 24 14:19 glibc-2.12-1.166.el6.x86_64.rpm -rw-r--r--1 ftp ftp 14885212 Jul 24 14:19 glibc-common-2.12-1.166.el6.x86_64.rpm -rw-r--r--1 ftp ftp 1008264 Jul 24 14:14 glibc-devel-2.12-1.166.el6.i686.rpm -rw-r--r--1 ftp ftp 1007848 Jul 24 14:19 glibc-devel-2.12-1.166.el6.x86_64.rpm -rw-r--r--1 ftp ftp627884 Jul 24 14:19 glibc-headers-2.12-1.166.el6.x86_64.rpm -rw-r--r--1 ftp ftp 1197132 Jul 24 14:14 glibc-static-2.12-1.166.el6.i686.rpm -rw-r--r--1 ftp ftp 1454756 Jul 24 14:19 glibc-static-2.12-1.166.el6.x86_64.rpm -rw-r--r--1 ftp ftp171592 Jul 24 14:19 glibc-utils-2.12-1.166.el6.x86_64.rpm -Connie Sieh
Re: unfortunate bind dns attack
I thought that 7x and 7rolling were supposed to be one and the same? 7x is the latest released version. 7rolling is the current test version. -Connie Sieh
Re: unfortunate bind dns attack
=20 I believe there was an announcement stating 7rolling-security was being u= sed to=20 hold the 6.7 security updates and were hoped to be released on Wed 3rd=20 (presumably US time). Ooops. I meant 6rolling-security. These are going out now for SL 6 . -Connie Sieh
Re: SL7x MariaDB updated packages
--_000_EC2DF6068869624FB2FA3090B1162BAE4472A2D336srvmail04clsi_ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable To all: I notice that the version of the various MariaDB packages in the 7x/x86_64/= os/Packages/ repo are all currently 5.5.41. Would we expect any coming upda= ted packages to MariaDB to appear in the security or fastbugs directories a= s appropriate, just like the former SL6x MySQL 5.1 packages did? (The equivalent Oracle MySQL repo and the MariaDB.org repo have a 5.5.44, s= o I was wondering what to expect) Regards, Tim We just provide what we get from TUV(Redhat). Note that RedHat commonly backports both features and errata from newer versions to older versions. -Connie Sieh
Re: perf command in SL
On Fri, 5 Jun 2015, Mahmood Naderan wrote: --=_Part_7118608_232083198.1433534050251 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, According tot he wikipedia entry for perf, it should be available in kern= els 2.6.31 Currently, the installed kernel on my SL-6.3 is=C2=A0 SL-6.3 2.6.32-279.5.1= .el6.x86_64. However, there is no package for perf or linux-tools. Do you have any idea? =C2=A0Regards, Mahmood --=_Part_7118608_232083198.1433534050251 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit htmlbodydiv style=color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13pxdiv dir=ltr id=yui_3_16_0_1_1433531929167_14206span id=yui_3_16_0_1_1433531929167_14319 style= class=Hi,brAccording tot he wikipedia entry for perf, it should be available in kernels gt; /span2.6.31/divdiv id=yui_3_16_0_1_1433531929167_14259 dir=ltrbr/divdiv id=yui_3_16_0_1_1433531929167_14262 dir=ltrCurrently, the installed kernel on my SL-6.3 isnbsp; SL-6.3 2.6.32-279.5.1.el6.x86_64. However, there is no package for perf or linux-tools./divdiv id=yui_3_16_0_1_1433531929167_14318 dir=ltrbr/divdiv id=yui_3_16_0_1_1433531929167_14367 dir=ltrDo you have any idea?br/divdiv id=yui_3_16_0_1_1433531929167_14205nbsp;/divdiv id=yui_3_16_0_1_1433531929167_14161 class=signatureRegards,brMahmood/div/div/body/html --=_Part_7118608_232083198.1433534050251-- [root@# yum list perf* Available Packages perf.x86_64 2.6.32-504.16.2.el6 sl-security perftest.x86_64 2.2-1.el6 sl -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: do we have a bugzilla?
Just post here with your issue. -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov On Wed, 27 May 2015, ToddAndMargo wrote: On 05/27/2015 01:34 PM, Konstantin Olchanski wrote: On Wed, May 27, 2015 at 01:21:09PM -0700, ToddAndMargo wrote: Do we have a bugzilla specific for SL issues? It would be a pointless write-only bit bucket if it existed. What few problems are SL specific seem to be handled on this mailing list quite efficiently. If you do provide some bugzilla, a) it will quickly fill up with gunk that has nothing to do with SL (32-bit wine does not work) b) it will create a false expectation that SL maintainers have an obligation to fix all and every bug within 5 minutes of it being filed. If you merely want a historical record of issues that is better than a google search of archives of this mailing list, then go here: http://scientificlinuxforum.org/ I want to file a bug against the live DVD -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~
Re: SL 7.1 PXE install: xfs not found
I will research this. -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov On Fri, 24 Apr 2015, Michel Jouvin wrote: I double-checked the kernel version used and the kernel version of the=20 modules provided by initrd (using lsinitrd, I should have done it=20 before) with SL 7.1: in fact, they are both the same, 3.10.0.229. But=20 when PXE booting vmlinuz+initrd, I end up with kernel modules for=20 3.10.0.123 (version from 7.0) in /lib/modules... How this is possible? I=20 removed the initrd file checked with lsinitrd to ensure that I was=20 getting an error when booting about the missing file so I am really=20 using this initrd file... I am lost... Any idea is welcome! Michel Le 24/04/2015 17:52, Michel Jouvin a =C3=A9crit : Hi, I don't know if this is related in some ways to the other recent=20 thread about SL 7.1, PXE install. I'm struggling with SL7.1 (and I=20 have the same pb with CentOS 7.1) when trying to do a PXE install of a=20 machine using the last versions of images/pxeboot/vmlinuz and=20 initrd.img. The install fails when trying to set the default=20 filesystem type to XFS (that I don't use on this machine) because the=20 xfs module is not found. Looking at console (ALT/F2), I saw that the=20 kernel version provided by vmlinuz (uname -r) is not matching the=20 kernel version for which modules are provided in initrd=20 (/lib/modules). If I take vmlinuz and initrd from SL7.0 I don't see=20 the problem (but I am not sure I can install 7.1 booting with=20 vmlinuz/initrd from 7.0). Is it expected ? Am I doing a trivial mistake ? Or is there an issue ?
Re: Installation source not populated for SL 7.0
On Fri, 6 Feb 2015, Lezama, Damian wrote: Hi, I'm trying to do a net install of SL 7.0 in a VirtualBox VM. When the machi= ne boots the network interface is disabled, I can enable it and get connect= I assume this is after the SL 7 install is done. ivity, but the list of repos is empty. Do I have to manually enter the sour= ces? What are the urls? Thanks Damian The base yum repo's are defined in sl-release which is installed by default. -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: Installation source not populated for SL 7.0
On Fri, 6 Feb 2015, Lezama, Damian wrote: My problem is that I can't even start the installation. -Original Message- From: Connie Sieh [mailto:cs...@fnal.gov]=20 Sent: Friday, February 06, 2015 11:26 AM To: Lezama, Damian Cc: SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV Subject: Re: Installation source not populated for SL 7.0 On Fri, 6 Feb 2015, Lezama, Damian wrote: Hi, I'm trying to do a net install of SL 7.0 in a VirtualBox VM. When the=20 machi=3D ne boots the network interface is disabled, I can enable it and= =20 get connect=3D I assume this is after the SL 7 install is done. ivity, but the list of repos is empty. Do I have to manually enter the=20 sour=3D ces? What are the urls? Thanks Damian The base yum repo's are defined in sl-release which is installed by default= . -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov The DVD iso image is easier to install since no network is needed. The install url is http:/sldist.fnal.gov/linux/scientific/7/x86_64/os -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: Docker
On Fri, 30 Jan 2015, Yasha Karant wrote: On 01/30/2015 10:32 AM, Brett Viren wrote: Yasha Karant ykar...@csusb.edu writes: For example, will a legally licensed MS Win application that does not run under Wine/CrossOver work under Docker under SL 7 the same as it would under VirtualBox with a full install of say MS Win 8.1 (soon MS Win 10)? Docker containers run on Linux (the kernel) so, no, if your application requires honest-to-badness MicroSoft Windows don't plan on using Docker. Can one make a Docker application package on the target host (e.g., SL 7) or does one need first a full install of the (virtual) base I don't know what target (host? guest?) means here. The application, say A, runs under environment (OS) X, not environment Y. One wants A under Y. The target is Y. Can one build A under Y using the appropriate chunks from X with Docker, or does one re-build (dockerise) A under X for target Y? In the first event, one only needs to be running Y; in the second event, one needs to be running X to build for Y. A Docker image is a full OS (minus the kernel). To start you write one line in a Dockerfile like: FROM fedora:20 and do a docker build You can follow up this line with additional instructions (such as yum install ...) to further populate. If you have a second image that shares some portion of these instructions, or as you add more instructions, any prior existing layer is reused. I don't find a lot of bases for SL but there are ways to add new base OSes from first principles (CMS has some scripts in github) and there are established ones for centos. -Brett. Presumably, any application that will run under CentOS, in particular, CentOS 7 that is the RHEL source release for other ports, such as SL 7, should be able to run under SL. My understanding is that SL 7 is not built from the actual RHEL 7 source that is used to build RHEL 7 that is licensed for fee, but from the RHEL packaged CentOS source (CentOS now effectively being a unit of Red Hat, a for-profit corporation) that is used to build CentOS 7 (that, as with SL 7, is licensed for free as a binary installable executable system that requires no building from source per se). Yasha SL is built from the source that Red Hat has provided . It is built from the same source that all rebuilds can build from. There is no such thing as RHEL packaged CentOS source . -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: Docker
On Mon, 2 Feb 2015, Yasha Karant wrote: On 02/02/2015 11:35 AM, Connie Sieh wrote: On Fri, 30 Jan 2015, Yasha Karant wrote: On 01/30/2015 10:32 AM, Brett Viren wrote: Yasha Karant ykar...@csusb.edu writes: For example, will a legally licensed MS Win application that does not run under Wine/CrossOver work under Docker under SL 7 the same as it would under VirtualBox with a full install of say MS Win 8.1 (soon MS Win 10)? Docker containers run on Linux (the kernel) so, no, if your application requires honest-to-badness MicroSoft Windows don't plan on using Docker. Can one make a Docker application package on the target host (e.g., SL 7) or does one need first a full install of the (virtual) base I don't know what target (host? guest?) means here. The application, say A, runs under environment (OS) X, not environment Y. One wants A under Y. The target is Y. Can one build A under Y using the appropriate chunks from X with Docker, or does one re-build (dockerise) A under X for target Y? In the first event, one only needs to be running Y; in the second event, one needs to be running X to build for Y. A Docker image is a full OS (minus the kernel). To start you write one line in a Dockerfile like: FROM fedora:20 and do a docker build You can follow up this line with additional instructions (such as yum install ...) to further populate. If you have a second image that shares some portion of these instructions, or as you add more instructions, any prior existing layer is reused. I don't find a lot of bases for SL but there are ways to add new base OSes from first principles (CMS has some scripts in github) and there are established ones for centos. -Brett. Presumably, any application that will run under CentOS, in particular, CentOS 7 that is the RHEL source release for other ports, such as SL 7, should be able to run under SL. My understanding is that SL 7 is not built from the actual RHEL 7 source that is used to build RHEL 7 that is licensed for fee, but from the RHEL packaged CentOS source (CentOS now effectively being a unit of Red Hat, a for-profit corporation) that is used to build CentOS 7 (that, as with SL 7, is licensed for free as a binary installable executable system that requires no building from source per se). Yasha SL is built from the source that Red Hat has provided . It is built from the same source that all rebuilds can build from. There is no such thing as RHEL packaged CentOS source . -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov Please correct me if I am in error. RHEL, binary licensed for fee, is built from a source that RH does not seem to release. Rather, RH releases, through the RH subsidiary CentOS and a GIT mechanism, a source for all rebuilds, supposedly including CentOS. Thus, SL and CentOS are built from the same source, but the actual RHEL source may or not may in fact (claims to the contrary notwithstanding) be the same, as no one outside of RH or a RH licensee actually sees the source for RHEL. If RHEL also is built through a GIT mechanism, I am assuming that the Internet path to the RHEL GIT is not the same as that to the public rebuildable CentOS GIT. In the event that Fermilab or CERN has licensed the actual RHEL 7 source as a RHEL licensee, would personnel at either non-RH entity be allowed to comment if in fact there were non-trivial differences between the actual RHEL 7 source and the rebuildable CentOS 7 source? Trivial differences would be the presence of RH logos and splash screens, each of which is replaced by whatever the rebuilder is using (SL for the SL rebuild) -- but all of the internal intellectual property references in the source code still (presumably) mentions RH in both the actual RHEL 7 source and the CentOS 7 rebuildable source. Yasha Karant I compared all of the RHEL 7 RC src.rpm's that were available on ftp.redhat.com with the reconsituted src.rpm's from git.centos.org and they were the same. -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: SL 7x x86_64 install issues
On Thu, 18 Dec 2014, Mr. Taylor Woods wrote: htmlhead/headbodydiv style=font-family: Verdana;font-size: 12.0px;divGood morning,/div divnbsp;/div divI downloaded SL 7x x86_64 last evening, tried to install, it asked to do an update before the install, then started the install process then after 5 minutes I got a white box covering the screen...then after 2 minutes screen froze. My question, is this normal also does it matter I loaded this distro on a Alienware laptop that has more than enough resources to handle. Please advise./div divnbsp;/div divTaylornbsp;nbsp;br/ nbsp;/div div class=signatureSent from the Scientific Linux 6.5 desktop of Taylor Woodsbr/ taylor.wo...@linuxmail.orgbr/ (404)536-7773br/ br/ This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited./div/div/body/html Which install image did you use? Url please. -- Connie J. Sieh Computing Services Specialist III Fermi National Accelerator Laboratory 630 840 8531 office http://www.fnal.gov cs...@fnal.gov
Re: SL 7 gnome workplace switcher, panel widgets
On Fri, 17 Oct 2014, Yasha Karant wrote: On SL 6, I have a small icon on the bottom panel task bar that appears as a N x N (N = 3 for my choice) matrix and that can be used to switch between workspaces and drag open application windows from one workspace to another. I cannot find this for SL 7 gnome, nor can I find the way to add widgets to panels -- the menu that will pop up from a click on the panel and that starts with Add to Panel. I have found *alacarte*-3.*7*.90-8.el7.noarch RPM http://rpmfind.net/linux/RPM/centos/7.0.1406/x86_64/Packages/alacarte-3.7.90-8.el7.noarch.html from the CentOS 7 (official RedHat non-supported EL) distro. Any suggestions for the other gnome desktop utilities? Yasha Karant Note that alacarte-3.7.90-8.el7.noarch.rpm is also in the SL 7 repo. -Connie Sieh
Re: Posted for testing: Scientific Linux 7.0 x86_64 RELEASE CANDIDATE 1
On Fri, 26 Sep 2014, Andras Horvath wrote: Can the RC be updated to the final version? What do you mean by updated ? -Connie Sieh Thanks, Andras On Fri, 26 Sep 2014 09:29:05 -0500 Pat Riehecky riehe...@fnal.gov wrote: Scientific Linux 7.0 x86_64 RELEASE CANDIDATE 1 - Sep 26, 2014 == Information == Fermilab's intention is to continue the development and support of Scientific Linux and refine its focus as an operating system for scientific computing. Today we are announcing a release candidate of Scientific Linux 7. We continue to develop a stable process for generating and distributing Scientific Linux, with the intent that Scientific Linux remains the same high quality operating system the community has come to expect. THIS IS NOT A PRODUCTION RELEASE OF SCIENTIFIC LINUX 7.0 NOTE: Please review the SL Release Notes along with The Upstream Vendor's Release Notes: http://ftp.scientificlinux.org/linux/scientific/7.0/x86_64/release-notes/ https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/index.html There is a great deal of information within those documents not listed here. Send comments/issues/test reports to: SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV == Media == You can find the release media at: http://ftp.scientificlinux.org/linux/scientific/7.0/x86_64/iso/ NOTE: The 'everything' dvd image requires a Dual-Layer (DL) compatible drive for both burning and booting off of. Alternatively the livecd-iso-to-disk utility is able to convert this to USB successfully. A USB device of sufficient size is required. Alternatively you can utilize the dd command to write the raw image to a USB device. http://ftp.scientificlinux.org/linux/scientific/7.0/x86_64/release-notes/#_how_to_make_a_bootable_usb_installer == UEFI Secure Boot == The status of UEFI Secure Boot for Scientific Linux is noted in detail at: http://ftp.scientificlinux.org/linux/scientific/7.0/x86_64/release-notes/#_about_uefi_secure_boot Booting SL7 with Secure Boot enabled works but requires a manual step. This is because the shim has not been signed by the UEFI CA. Instructions are included within the SL7 Release Notes. NOTE: The kernels in sl7-security have not yet been built with the SL7 Secure Boot Certificate and may not function in secure boot environments.
Re: debug debuginfo for sl7
On Fri, 19 Sep 2014, lejeczek wrote: are these missing from SL7 yum repositories? regards. P. We are still in Beta . debuginfo packages should be available shortly. -Connie Sieh
Re: Boot hangs / loops
On Thu, 10 Jul 2014, Dormition Skete (Hotmail) wrote: In looking at my previous post, it occurred to me that =93fsck didn=92t = help=94 was not very explanatory. fsck finds no errors on /dev/sda6 (my / file system) fsck found and fixed 2 errors in my /dev/sda7 (home) file system. I=92ve run this on both several times today, and it finds them both = clean every time now. It still will not boot. =20= Have you tried commenting out all of the lines in the fstab that are not needed for booting. You should verify that /dev/sda6 and /dev/sda7 are the actual partitions that you think they are. -Connie Sieh
Re: Scientific Linux 7 ALPHA
On Mon, 7 Jul 2014, Konstantin Olchanski wrote: On Mon, Jul 07, 2014 at 04:52:22PM -0500, Connie Sieh wrote: The iso in http://ftp.scientificlinux.org/linux/scientific/7rolling/x86_64/iso/ Yes. To burn to a DVD you will need a Dual Layer DVD . USB installer or bust! Go for it. Just checked, the CentOS 7 ISO image explictely supports dd to USB flash. This is as opposed to the SL6.5 ISO images where dd to USB flash are not bootable. I created a newer version of the SL6.5 ISO images that worked with dd. Please indicate exact image url that was used for this test. (SLC 6.5 (CERN) iso image dd to USB flash is also bootable). I am only partially aware of severe magic required to make bootable USB flash devices (spent 2 days last week making an SL 6.5 USB flash bootable - grub1 - error 18, extlinux - boot error and cannot load ldlinux.c32, depending on which extlinux, grub2 finally booted, but no SL6.5 grub2 RPMs, had to cross-build it myself), but if SLC, CentOS and Ubuntu can do it, no excuse for not having it in SL. P.S. But I have no idea how this integrates with using a site-specific kickstart file, the best I can tell, the ISO image is read-only and it is impossible to put my kickstart file inside it, so I still have to do what I do with my USB installer if I want to run kickstart installs from USB. P.P.S. But maybe this does not matter as I do many installs by cloning. (saves time on all the post-install customizations). P.P.P.S. But cloning does not run the RH installer (anaconda) which proved an eccelent hardware test - machines that crash, hang and fail during installation tend to be faulty and also fail in normal use, machines that can boot and run the installer from start to finish tend to be stable in normal use. -Connie Sieh
Re: Scientific Linux 7 ALPHA
On Fri, 4 Jul 2014, Nico Kadel-Garcia wrote: On Thu, Jul 3, 2014 at 5:17 PM, Pat Riehecky riehe...@fnal.gov wrote: Users interested in Scientific Linux 7 ALPHA can review: http://listserv.fnal.gov/scripts/wa.exe?A2=ind1407L=scientific-linux-develT=0X=30246605F08F0DC7EDP=74 -- Pat Riehecky Scientific Linux developer http://www.scientificlinux.org/ OK, I'm *impressed*. Did our faithful packagers work from an RHEL susbscription's SRPM's, or resolve the confusing new layout of the https://git.centos.org repository? There was already a copy in my local rsync mirror, and I'm happy to install from there and keep the lod off your servers. Getting the alpha into people's hands this quickly is one of the reasons I've come to personally prefer Scientific Linux over CentOS. Many of the packages were built from the src.rpms provided by TUV for the public release candidate for RHEL 7 that was released in April. All of the packages that were released after the Release Candidate were built from TUV source from git.centos.org . -Connie Sieh
Re: Scientific Linux 7 ALPHA
On Fri, 4 Jul 2014, Yasha Karant wrote: As has been made clear, no conspiracy in terms of getting the matter ported -- simply a possibly different set of impediments to building from source. (Anyone checked if the Oracle EL7 port is done yet? What about the Princeton port?) The conspiracy will be visible if there are significant performance degradations of CentOS 7 source compared to real RHEL source build distros/ports, and if RHEL 7 intended codes (as from the commercial sector) do not work on the CentOS based distros. The real conspiracy, if any, would be for security compromises left open in the CentOS based ports compared with the RHEL real source based distro. This was done in short order, not long after CentOS released pre-production distros. CentOS, as a division of Red Hat, presumably had a simpler job than the SL team, unless of course there were sub-rosa details from Red Hat to CentOS that also then went to SL. Is SL still a separate distro, or is it in fact a CentOS SIG/variant (probably the latter given that RHEL source was not used, but rather CentOS)? SL is still a separate distro. From the announcement These packages were built at Fermilab from TUV's sources. . A practical question: will any alpha or beta SL 7 distro based install be able to change into 7x production or will a full reinstall be required? It is suggested that a new install be done as we do not know what issues would happen with the continued use of this pre production version. Yasha Karant On 07/04/2014 04:37 AM, Bill Maidment wrote: Pat That's amazing work by you guys. So much for all the conspiracy theories ;-) Cheers Bill -Original message- From:Pat Riehecky riehe...@fnal.gov Sent: Friday 4th July 2014 7:23 To: SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV Subject: Scientific Linux 7 ALPHA Users interested in Scientific Linux 7 ALPHA can review: http://listserv.fnal.gov/scripts/wa.exe?A2=ind1407L=scientific-linux-develT=0X=30246605F08F0DC7EDP=74 -- Pat Riehecky Scientific Linux developer http://www.scientificlinux.org/ -Connie Sieh
Re: Scientific Linux 7 ALPHA
On Mon, 7 Jul 2014, Arturo Fatturi wrote: Hi. The iso in http://ftp.scientificlinux.org/linux/scientific/7rolling/x86_64/iso/ This is 6.2 Gb, is this right? Yes. To burn to a DVD you will need a Dual Layer DVD . Arturo -Connie Sieh
Re: Scientific Linux 7 ALPHA
On Mon, 7 Jul 2014, Konstantin Olchanski wrote: On Mon, Jul 07, 2014 at 03:29:45PM -0500, Connie Sieh wrote: On Mon, 7 Jul 2014, Arturo Fatturi wrote: Hi. The iso in http://ftp.scientificlinux.org/linux/scientific/7rolling/x86_64/iso/ This is 6.2 Gb, is this right? Yes. To burn to a DVD you will need a Dual Layer DVD . What is this talk about burning DVDs? The year is 2014 and we do not even have any DVD players on most computers. USB installer or bust! Go for it. -Connie Sieh
Re: Scientific Linux 7 ALPHA
On Mon, 7 Jul 2014, Yasha Karant wrote: CentOS-7.0-1406-x86_64-DVD 06-Jul-2014 17:33 4148166656 4 148 166 656 bytes should fit on one single layer DVD, as a DVD+R Single Layer 4,700,372,992 bytes DVD-R Single Layer 4,707,319,808 bytes Presumably, the production version of SL 7 should be approximately the same size. We did release a install DVD for SL 6 and 2 DVD's for the everything install . It was hard to figure out what should be on a single DVD as there are many differences of opinion on what belongs on it. I note that only X86-64 is available; have I missed something about supported ISAs, or will there also be an IA-32 port/distribution as well? TUV is only releasing X86-64 . -Connie Sieh Yasha Karant On 07/07/2014 01:29 PM, Connie Sieh wrote: On Mon, 7 Jul 2014, Arturo Fatturi wrote: Hi. The iso in http://ftp.scientificlinux.org/linux/scientific/7rolling/x86_64/iso/ This is 6.2 Gb, is this right? Yes. To burn to a DVD you will need a Dual Layer DVD . Arturo -Connie Sieh
Re: geteltorito script seems to be out-of-date
On Mon, 23 Jun 2014, Charles Elsaesser wrote: --1564165522-744755268-1403569075=:21797 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable =0Ageteltorito seems to be out-of-date on SL systems.=0A=0ALast version see= ms to be 0.5=0A=0AThe updated script can be found at=0Ahttp://www.uni-koble= nz.de/~krienke/ftp/noarch/geteltorito/geteltorito=0Asee https://bugs.debian= .org/cgi-bin/bugreport.cgi?bug=3D611784=0A=0Ageteltorito is also out-of-dat= e on systems=0A=0A2.6.32-431.20.3.el6.x86_64 : Linux localhost 2.6.32-431.2= 0.3.el6.x86_64 #1 SMP Thu Jun 19 14:01:59 CDT 2014 x86_64 x86_64 x86_64 GNU= /Linux=0Ageteltorito -v=0AVersion: 0.4 =0A=0ALinux asus-x75vc__charles.alph= anet 3.15.1-1.el6.elrepo.x86_64 #1 SMP Tue Jun 17 16:35:45 EDT 2014 x86_64 = x86_64 x86_64 GNU/Linux=0Ageteltorito -v=0AVersion: 0.4 =0A=0A3.10.33-rt32.= 34.el6rt.x86_64 : Linux localhost.localdomain 3.10.33-rt32.34.el6rt.x86_64 = #1 SMP PREEMPT RT Wed May 28 09:57:12 CEST 2014 x86_64 x86_64 x86_64 GNU/Li= nux=0Ageteltorito -v=0AVersion: 0.4 --1564165522-744755268-1403569075=:21797 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable htmlbodydiv style=3Dcolor:#000; background-color:#fff; font-family:He= lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fo= nt-size:12ptbr style=3D class=3Dgeteltorito seems to be out-of-date= on SL systems.br style=3D class=3Dbr style=3D class=3DLast ver= sion seems to be 0.5br style=3D class=3Dbr style=3D class=3DThe= updated script can be found atbr style=3D class=3Dhttp://www.uni-kob= lenz.de/~krienke/ftp/noarch/geteltorito/geteltoritobr style=3D class=3D= see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D611784br style= =3D class=3Dbr style=3D class=3Dgeteltorito is also out-of-date = on systemsbr style=3D class=3Dbr style=3D class=3D2.6.32-431.20= .3.el6.x86_64 : Linux localhost 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 1= 9 14:01:59 CDT 2014 x86_64 x86_64 x86_64 GNU/Linuxbr style=3D class=3D= geteltorito -vbr style=3D class=3DVersion: 0.4 br style=3D class= =3Dbr style=3D class=3DLinux asus-x75vc__charles.alphanet 3.15.1-1.el6.elrepo.x86_64 #1 SMP Tue Jun 17 = 16:35:45 EDT 2014 x86_64 x86_64 x86_64 GNU/Linuxbr style=3D class=3Dg= eteltorito -vbr style=3D class=3DVersion: 0.4 br style=3D class=3D= br style=3D class=3D3.10.33-rt32.34.el6rt.x86_64 : Linux localhost= .localdomain 3.10.33-rt32.34.el6rt.x86_64 #1 SMP PREEMPT RT Wed May 28 09:5= 7:12 CEST 2014 x86_64 x86_64 x86_64 GNU/Linuxbr style=3D class=3Dgete= ltorito -vbr style=3D class=3DVersion: 0.4 br style=3D class=3D= br style=3D class=3D/div/body/html --1564165522-744755268-1403569075=:21797-- Where did you get geteltorito from? -Connie Sieh
Re: aufs.ko
On Wed, 28 May 2014, n.chandra sekhar wrote: --047d7bdc08ac76350504fa70914c Content-Type: text/plain; charset=UTF-8 I installed aufs rpm on scientific Linux 6 , after installing aufs rpm i am not able to find aufs.ko. I need aufs.ko to load aufs in to the kernel at run time Where did you get a aufs rpm? -Connie Sieh please some body help on this its very urgent. --047d7bdc08ac76350504fa70914c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable div dir=3Dltrdivbr/divdivI installed aufs rpm on scientific Lin= ux 6 , after installing aufs rpm i am not able to find aufs.ko. I need aufs= .ko to load aufs in to the kernel at run time=C2=A0/divdivbr/divdi= vplease some body help on this its very urgent.=C2=A0/div /div --047d7bdc08ac76350504fa70914c--
Re: Any 7 rumors?
On Thu, 15 May 2014, Dag Wieers wrote: On Tue, 8 Apr 2014, ToddAndMargo wrote: Any rumors as to when EL 7 will be out? There was an announcement today from Red Hat about a virtual event named Redefining the Enterprise OS at June 10. The content seems to be centered around RHEL7 features and functionality, so there is a big chance that this is around the time RHEL7 goes GA. I can only find this link online from a tweet: http://buff.ly/1uwrDQw Beware that even when RHEL7 goes GA in June, I wouldn't put it into production until RHEL7.1, possibly RHEL7.2 (about a year later) after rigorous testing and integration. (Likely depends on your use-case though) The RHEL 7 Public Release Candidate has been out since April 21. Our complete guess is June or early July. So This redefining the OS sounds probable. Only guessing . -connie
Re: Bombono DVD load/install
On Tue, 6 May 2014, Taylor Woods wrote: --089e0122ebb029382c04f8c61842 Content-Type: text/plain; charset=UTF-8 Ok I don't think I am insane, but I am trying to load Bombono DVD on SL 6.5, I found it on the website, tried to download it for 64 bit no go, What did you try? Details please. tried from RPM list site way too many to choose from but I tried one no Way too many what to choose from. Details please. good any suggestions on how to load this? I have done this before but this is on another system and I don't remember. Any suggestions? More detail is needed about what you have tried already. -Connie Sieh Taylor Woods 3J Computer Associates Plc From the desk of Taylor Woods: Just one man and his computer Success is not measured by the amount of failures but by the amount of attempts to accept failure as NOT an option Taylor Woods jtwoods0...@gmail.com (404)536-7773 This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply e-mail so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. --089e0122ebb029382c04f8c61842 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable div dir=3Dltrdiv class=3Dgmail_default style=3Dfont-family:comic sa= ns ms,sans-serifOk I don#39;t think I am insane, but I am trying to load= Bombono DVD on SL 6.5, I found it on the website, tried to download it for= 64 bit no go, tried from RPM list site way too many to choose from but I t= ried one no good any suggestions on how to load this? I have done this befo= re but this is on another system and I don#39;t remember. Any suggestions?= br /divdiv class=3Dgmail_default style=3Dfont-family:comic sans ms,sans-= serifbrbr/divdiv class=3Dgmail_default style=3Dfont-family:comi= c sans ms,sans-serifTaylor Woodsbr/divdiv class=3Dgmail_default st= yle=3Dfont-family:comic sans ms,sans-serif 3J Computer Associates Plcbr/divdiv class=3Dgmail_default style=3Df= ont-family:comic sans ms,sans-serifbrbr clear=3Dall/divdivdiv = dir=3Dltrdivspan style=3Dcolor:rgb(0,0,0);font-family:Arial;font-siz= e:mediumFrom the desk of Taylor Woods: Just one man and his computerbr /span/divdivspan style=3Dcolor:rgb(0,0,0);font-family:Arial;font-si= ze:mediumbr/span/divdivspan style=3Dcolor:rgb(0,0,0);font-famil= y:Arial;font-size:mediumquot;Success is not measured by the amount of fa= ilures but by the amount of attempts to accept failure as NOT an optionquo= t;=C2=A0/span/div divspan style=3Dcolor:rgb(0,0,0);font-family:Arial;font-size:mediumb= r/span/divdivspan style=3Dcolor:rgb(0,0,0);font-family:Arial;font-= size:mediumTaylor Woodsbr/span/divdivspan style=3Dcolor:rgb(0,0= ,0);font-family:Arial;font-size:mediuma href=3Dmailto:jtwoods0601@gmail= .com target=3D_blankjtwoods0...@gmail.com/abr (404)536-7773brbr/span/divdivspan style=3Dcolor:rgb(0,0,0);font= -family:Arial;font-size:mediumThis electronic mail (including any attachm= ents) may contain information that is privileged, confidential, and/or othe= rwise protected from disclosure to anyone other than its intended recipient= (s). Any dissemination or use of this electronic mail or its contents (incl= uding any attachments) by persons other than the intended recipient(s) is s= trictly prohibited. If you have received this message in error, please noti= fy us immediately by reply e-mail so that we may correct our internal recor= ds. Please then delete the original message (including any attachments) in = its entirety. Thank you./spanbr /divdivbr/divdivbr/divdivbr/divdivbr/divbr/div= /div /div --089e0122ebb029382c04f8c61842--
Re: heartbleed and openssl update
On Thu, 10 Apr 2014, William Lutter wrote: I see this link relative to openssl and heartbleed exploit... https://www.openssl.org/news/secadv_20140407.txt A missing bounds check in the handling of the TLS heartbeat extension can be used to reveal up to 64k of memory to a connected client or server. Only 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including 1.0.1f and 1.0.2-beta1. Affected users should upgrade to OpenSSL 1.0.1g. Users unable to immediately upgrade can alternatively recompile OpenSSL with -DOPENSSL_NO_HEARTBEATS. 1.0.2 will be fixed in 1.0.2-beta2. My SL 6.5 lists openssl-1.0.1e-16.el6_5.7.x86_64 openssl098e-0.9.8e-17.el6_2.2.x86_64 openssl-devel-1.0.1e-16.el6_5.7.x86_64 so, it is a vulnerable version of openssl. No, that is the updated version. TUV backports security errata. They key is the .7 in el6_5.7 . Question 1 I enabled fastbugs in sl-other.repo and well as usual enables in sl.repo, however, do not see an update for openssl. Will there be one forthcoming from SL or have I missed the proper repository to get it? I have no server on this PC, so I am not worried yet. It was released on Tuesday morning. Question 2 I surmise that older versions of openssl on older SLs are not impacted such as openssl-0.9.8e-26.el5_9.1.i686 Not impacted. Bill Lutter -Connie Sieh
Re: Apache repository
On Tue, 8 Apr 2014, Werf, C.G. van der (Carel) wrote: Does anyone know of a decent RHEL6/SL6/Centos6 repository where a newer ver= sion of Apache is available then the 2.2.15 of SL.repo ? On our current SL5-webserver I intalled Apache 2.2.23 from webtatic.repo. We are now planning to run Apache on SL6, but the webtatic.sl6 does not pr= ovide Apache anymore. Regards, Carel van der Werf Apache 2.4 is currently in beta (closed beta) via Software Collections 1.1 . See http://developerblog.redhat.com/2014/03/20/rhscl-1-1-beta-available-apache-mongodb/ There is also a example of using apache 2.4 from Software Collections 1.1 here http://developerblog.redhat.com/2014/04/08/apache-with-various-php-versions-using-scl/#more-411758 The above article lists a COPR repo which has test versions available. Note I do not suggest using the test versions in production. http://copr-be.cloud.fedoraproject.org/results/rhscl/httpd24/epel-6-x86_64/ Assuming that httpd24 is released as part of Software Collections 1.1 then it should be available in SL Software Collections after TUV releases the src.rpm and we have had time to build them. -Connie Sieh
Re: Any experience with the Intel Z87 chipset?
On Tue, 18 Mar 2014, Steve Gaarder wrote: I'm looking at getting some machines based on the Intel Z87 chipset. Has anyone tried SL6 on this? I'm wondering how well the graphics and ethernet work with the stock SL drivers. thanks, Steve Gaarder System Administrator, Dept of Mathematics Cornell University, Ithaca, NY, USA gaar...@math.cornell.edu I recently built a system with the following motherboard using Z87 chipset. GA-Z87X-UD4H http://www.gigabyte.us/products/product-page.aspx?pid=4488#ov I installed SL 5 x86_64 and everything works fine except for a message about not supporting audio over hdmi. The board has other audio. The ethernet works fine and so does the video builtin to the i7-4770K . -Connie Sieh
Re: Upgraded to SL 6.5 - no ethernet
On Thu, 13 Mar 2014, Larry Linder wrote: On one of our development systems the Internet quit working after a power failure and a reboot. We suspect that that a new kernel was downloaded by Yum and never took effect till a reboot occurred sometime later. History: We know that the realtech driver for chip set RTL 8111/8168B works with SL 5.4 - 5.10. The problem is with SL 6.1 - 6.5. Same box same hardware. A long time ago we installed a special kernel from ELRepo.org to fix the problem with SL 6.4. SL 6.4 later was updated to SL 6.5 and still no Ethernet - ifconfig shows that it can receive but not transmit as before. Would it be appropriate to reinstall the kernel-lt-3.10.32-1.el6.elrepo.x86_64.rpm date 28 Feb. 14 to fix the problem. Second question: How do you turn automatic updates OFF. Larry Linder You can boot with the prior kernel to verify that it is a newer kernel that caused the net to not work. It should still be on your system. -Connie Sieh
Re: Is there something wrong with sl-indexhtml?
On Thu, 6 Feb 2014, ToddAndMargo wrote: # yum install sl-indexhtml Loaded plugins: priorities, refresh-packagekit, security 44 packages excluded due to repository priority protections Setting up Install Process Resolving Dependencies -- Running transaction check --- Package sl-indexhtml.noarch 0:6-6.5.sl6.1 will be installed -- Finished Dependency Resolution ... Error unpacking rpm package sl-indexhtml-6-6.5.sl6.1.noarch error: unpacking of archive failed on file /usr/lib/firefox/defaults/preferences/firefox-branding.js;52f3e263: cpio: lstat Verifying : sl-indexhtml-6-6.5.sl6.1.noarch 1/1 Failed: sl-indexhtml.noarch 0:6-6.5.sl6.1 Do you know which exact repo this was gotten from? -Connie Sieh
Re: Centos / Redhat announcement and Scientific Linux update
On Wed, 8 Jan 2014, Connie Sieh wrote: We are in the process of researching/evaluating this news and how it impacts Scientific Linux. -Connie Sieh -- Update on Scientific Linux On January 7, Red Hat and CentOS announced that they joined forces (http://www.centos.org). Since Scientific Linux relies on Red Hat Enterprise Linux source code, this is of great interest to the Scientific Linux project. We have been learning more about their plans and considering the possibilities for Scientific Linux. We've had conversations with CentOS and Red Hat, and between Fermilab and CERN. We plan further discussions with these groups and also with other contributors to and users of Scientific Linux. No final decisions have been made, but we can provide an update on our thoughts so far. Fermilab and CERN remain committed to the original goal of Scientific Linux: providing a stable, well-supported, open-source platform which meets the needs of high-energy physics experiments. The fact that this platform is used by people outside of that community is something we appreciate and will be a factor in any decisions going forward. There are still many questions to pursue as the details of CentOS Special Interest Groups continue to evolve. The anticipated release of Red Hat Enterprise Linux 7 presents an opportunity to consider forming/joining a CentOS Special Interest Group (http://www.centos.org/about/governance/sigs/) and producing Scientific Linux 7 as a CentOS variant (http://www.centos.org/variants/). The variant structure may allow greater flexibility in adapting the distribution to scientific needs. The framework and relationship structure of CentOS Special Interest Groups is still under heavy discussion on the CentOS development list. This is only being evaluated for Scientific Linux version 7. Security and other updates for the current Scientific Linux versions 5 and 6 will continue uninterrupted. We expect the process for SL 5 and 6 support to remain essentially the same, with the only substantive change being that source code will come from centos.org rather than redhat.com. We expect this change to be transparent to all users. There will be many more details to fill in, and we'll try to keep everyone in the Scientific Linux community informed as we continue to explore the options the Red Hat / CentOS partnership presents. -Connie Sieh
RE: Scientific Linux 6.5 RC 2 i386/x86_64 is now available for testing
There was a last minute issue that had to be fixed. The following multilibs were missing from the x86_64 install tree . libibverbs-rocee-1.1.7-1.el6.i686.rpm libibverbs-rocee-devel-1.1.7-1.el6.i686.rpm libmlx4-rocee-1.0.5-1.el6.i686.rpm These have been added to the install tree and the DVDs have been reimaged. Thanks to Stephan Wiesand for finding this issue. We expect to release this on January 30, 2014 if there are no issues reported. On Wed, 22 Jan 2014, Connie Sieh wrote: Scientific Linux 6.5 RC 2 i386/x86_64 DOWNLOAD INFO Network Install Images: http://ftp.scientificlinux.org/linux/scientific/6.5/i386/os/images/boot.iso http://ftp.scientificlinux.org/linux/scientific/6.5/x86_64/os/images/boot.iso DVD Install Images: http://ftp.scientificlinux.org/linux/scientific/6.5/i386/os/iso/ http://ftp.scientificlinux.org/linux/scientific/6.5/x86_64/iso/ Changes compared to 6.5 BETA 1 Install DVD and Everything DVDs support UEFI in non secure mode. If there are no big issues this will be released as 6.5 on January 27 , 2014 . -Connie Sieh
Scientific Linux 6.5 RC 2 i386/x86_64 is now available for testing
Scientific Linux 6.5 RC 2 i386/x86_64 DOWNLOAD INFO Network Install Images: http://ftp.scientificlinux.org/linux/scientific/6.5/i386/os/images/boot.iso http://ftp.scientificlinux.org/linux/scientific/6.5/x86_64/os/images/boot.iso DVD Install Images: http://ftp.scientificlinux.org/linux/scientific/6.5/i386/os/iso/ http://ftp.scientificlinux.org/linux/scientific/6.5/x86_64/iso/ Changes compared to 6.5 BETA 1 Install DVD and Everything DVDs support UEFI in non secure mode. If there are no big issues this will be released as 6.5 on January 27 , 2014 . -Connie Sieh
Re: Developer Toolset 2
On Wed, 15 Jan 2014, Devin A. Bougie wrote: Hi, All. Just incase we=92ve overlooked it, any updates on the expected re= lease of the Developer Toolset 2 for SL would be greatly appreciated. There are issues with rebuilding eclipse. We are deciding how to handle this issue. -Connie Many thanks, Devin=
Re: Installation DVD missing EFI support
On Sun, 12 Jan 2014, Akemi Yagi wrote: On Fri, Jan 10, 2014 at 2:05 PM, Connie Sieh cs...@fnal.gov wrote: On Thu, 26 Dec 2013, Connie Sieh wrote: On Thu, 26 Dec 2013, =D7=A6=D7=91=D7=99=D7=A7=D7=94 =D7=94=D7=A8=D7=9E= =D7=AA=D7=99 wrote: Therefore, Anaconda assumes that the system isn't UEFI, and makes wrong decisions, which cause SL to not boot, until manually hacked. I have updated a SL 65 Install DVD image for you to test. If needed I ca= n make the same changes to the SL 6.4 Install DVD image. ftp://ftp.scientificlinux.org/linux/scientific/6.5/x86_64/iso/SL-65-x86_6= 4-2013-12-27-Install-DVD.iso -Connie Sieh Within my limited test, SL-65-x86_64-2013-12-27-Install-DVD.iso seems to work in UEFI mode. Might be worth doing this for SL 6.4 as well. Akemi Akemi, Thanks for testing. -connie sieh
Re: Installation DVD missing EFI support
On Thu, 26 Dec 2013, Connie Sieh wrote: On Thu, 26 Dec 2013, צביקה הרמתי wrote: --089e013d19ccbc51d004ee7158e4 Content-Type: text/plain; charset=ISO-8859-1 Hi. The installation DVD (SL-64-x86_64-2013-03-18-Install-DVD) has /EFI/BOOT directory, but it's missing the important .efi file. Thus, the DVD isn't recognized by UEFI firmware as EFI capable booting media, and it can be booted only using legacy (BIOS) booting. That's making further problems, because according to https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-Boot-x86.html: Therefore, the installed system must boot using the same firmware that was used during installation. You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI. Therefore, Anaconda assumes that the system isn't UEFI, and makes wrong decisions, which cause SL to not boot, until manually hacked. Researching . I have updated a SL 65 Install DVD image for you to test. If needed I can make the same changes to the SL 6.4 Install DVD image. ftp://ftp.scientificlinux.org/linux/scientific/6.5/x86_64/iso/SL-65-x86_64-2013-12-27-Install-DVD.iso -Connie Sieh -Connie Sieh Thanks, Zvika --089e013d19ccbc51d004ee7158e4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable div dir=3Drtldiv style=3Ddirection:ltrdiv style=3Ddirection:ltr= Hi./divdiv style=3Ddirection:ltrThe installation DVD (SL-64-x86_64-20= 13-03-18-Install-DVD) has quot;/EFI/BOOTquot; directory, but it#39;s mis= sing the important quot;.efiquot; file./div div style=3Ddirection:ltrThus, the DVD isn#39;t recognized by UEFI fir= mware as EFI capable booting media, and it can be booted only using quot;l= egacyquot; (BIOS) booting./divdiv style=3Ddirection:ltrbr/divdi= v style=3Ddirection:ltr That#39;s making further problems, because according to a href=3Dhttps:/= /access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html= /Installation_Guide/ch-Boot-x86.htmlhttps://access.redhat.com/site/docume= ntation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-Boot-x8= 6.html/a :/div div style=3Ddirection:ltrquot;/divdiv style=3Ddirection:ltrThere= fore, the installed system must boot using the same firmware that was used = during installation. You cannot install the operating system on a system th= at uses BIOS and then boot this installation on a system that uses UEFI./d= iv div style=3Ddirection:ltrquot;/divdiv style=3Ddirection:ltrbr= /divdiv style=3Ddirection:ltrTherefore, Anaconda assumes that the syst= em isn#39;t UEFI, and makes wrong decisions, which cause SL to not boot, u= ntil manually hacked./div div style=3Ddirection:ltrbr/divdiv style=3Ddirection:ltrThanks,= /divdiv style=3Ddirection:ltrZvika/div/div/div --089e013d19ccbc51d004ee7158e4--
Re: Installation DVD missing EFI support
On Thu, 26 Dec 2013, צביקה הרמתי wrote: --089e013d19ccbc51d004ee7158e4 Content-Type: text/plain; charset=ISO-8859-1 Hi. The installation DVD (SL-64-x86_64-2013-03-18-Install-DVD) has /EFI/BOOT directory, but it's missing the important .efi file. Thus, the DVD isn't recognized by UEFI firmware as EFI capable booting media, and it can be booted only using legacy (BIOS) booting. That's making further problems, because according to https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-Boot-x86.html: Therefore, the installed system must boot using the same firmware that was used during installation. You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI. Therefore, Anaconda assumes that the system isn't UEFI, and makes wrong decisions, which cause SL to not boot, until manually hacked. Researching . -Connie Sieh Thanks, Zvika --089e013d19ccbc51d004ee7158e4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable div dir=3Drtldiv style=3Ddirection:ltrdiv style=3Ddirection:ltr= Hi./divdiv style=3Ddirection:ltrThe installation DVD (SL-64-x86_64-20= 13-03-18-Install-DVD) has quot;/EFI/BOOTquot; directory, but it#39;s mis= sing the important quot;.efiquot; file./div div style=3Ddirection:ltrThus, the DVD isn#39;t recognized by UEFI fir= mware as EFI capable booting media, and it can be booted only using quot;l= egacyquot; (BIOS) booting./divdiv style=3Ddirection:ltrbr/divdi= v style=3Ddirection:ltr That#39;s making further problems, because according to a href=3Dhttps:/= /access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html= /Installation_Guide/ch-Boot-x86.htmlhttps://access.redhat.com/site/docume= ntation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-Boot-x8= 6.html/a :/div div style=3Ddirection:ltrquot;/divdiv style=3Ddirection:ltrThere= fore, the installed system must boot using the same firmware that was used = during installation. You cannot install the operating system on a system th= at uses BIOS and then boot this installation on a system that uses UEFI./d= iv div style=3Ddirection:ltrquot;/divdiv style=3Ddirection:ltrbr= /divdiv style=3Ddirection:ltrTherefore, Anaconda assumes that the syst= em isn#39;t UEFI, and makes wrong decisions, which cause SL to not boot, u= ntil manually hacked./div div style=3Ddirection:ltrbr/divdiv style=3Ddirection:ltrThanks,= /divdiv style=3Ddirection:ltrZvika/div/div/div --089e013d19ccbc51d004ee7158e4--
Re: openssl-1.0.1e-15 - openssl-1.0.1e-16 update?
On Sat, 7 Dec 2013, Kelsey Cummings wrote: Looks like RH botched the upgrade to openssl-1.0.1e-15, any chance that the .16 update could be pushed out ASAP? The .15 release advertises support for curves it doesn't support which arguably is quite a bit worse than not supporting EC in the first place. https://bugzilla.redhat.com/show_bug.cgi?id=1022468 It was already pushed out. lftp sldist:/linux/scientific/6.4/x86_64/updates/security ls -ltr openssl-1.0.1e-15.el6.i686.rpm openssl-1.0.1e-15.el6.x86_64.rpm openssl-1.0.1e-16.el6_5.i686.rpm openssl-1.0.1e-16.el6_5.x86_64.rpm -Connie Sieh
Re: sl-fastbugs update
On Thu, 19 Dec 2013, Paul Hein wrote: I have a several machines running SL 6 and I want to turn on sl-fastbugs repo to update the software for all the non-critical bugs. The problem is the computers originally had SL 6.1 installed on them and updating with sl-fastbugs repo enabled updates only the software with the recent bug fixes. I see that the sl-fastbugs repos exist for previous versions. Is there an easy way to update all those bug fixes? I have tried to create a repo to access a previous version but failed. Here is the repo file: [sl-fastbugs] name=Scientific Linux 6.4 - x86_64 - fastbug updates baseurl=http://ftp.scientificlinux.org/linux/scientific/6.4/x86_64/updates/fastbugs/ http://ftp1.scientificlinux.org/linux/scientific/6.4/x86_64/updates/fastbugs/ http://ftp2.scientificlinux.org/linux/scientific/6.4/x86_64/updates/fastbugs/ ftp://ftp.scientificlinux.org/linux/scientific/6.4/x86_64/updates/fastbugs/ #mirrorlist=http://ftp.scientificlinux.org/linux/scientific/mirrorlist/sl-fastbugs-6.txt enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-sl file:///etc/pki/rpm-gpg/RPM-GPG-KEY-dawson And here is the errors I got when I tried to use it: # yum --disablerepo=\* --enablerepo=sl-6.4-fastbugs.repo update Loaded plugins: downloadonly, priorities, refresh-packagekit, security Repository sl-fastbugs is listed more than once in the configuration Error getting repository data for sl-6.4-fastbugs.repo, repository not found Thank you for any help you can give. Paul The repo name in the above example is sl-fastbugs , it is the name between the [ ] yum --disablerepo=\* --enablerepo=sl-fastbugs update -Connie Sieh
Re: Software Collections 1.0 is available for testing for SL 6
On Wed, 16 Oct 2013, Yi Ding wrote: Does anyone know what the right way to build these from SRPMs is? Not sure why you want to rebuild since we already provide the binaries. We will use python27 for this example. You have define scl to be python27 when you are building the python27 packages. Or you can build python27-1-10.el6.src.rpm which will provide python27-build-1-10.el6.x86_64.rpm. The python27-build-1-10.el6.x86_64.rpm package provides /etc/rpm/macros.python27-config which defines scl. --- (x86_64)# more macros.python27-config %scl python27 --- Then you can install python27-build-1-10.el6.x86_64.rpm . Note you will have to uninstall python27-build-1-10.el6.x86_64.rpm and install another [package]-build which will define scl for that package . Additional dependencies are scl-utils-build . -Connie Sieh Thanks, Yi On Thu, Sep 26, 2013 at 10:42 AM, Connie Sieh cs...@fnal.gov wrote: On Wed, 25 Sep 2013, Ben wrote: On Wed, Sep 25, 2013 at 10:02:14AM -0500, Connie Sieh wrote: On Wed, 25 Sep 2013, Matthieu Guionnet wrote: thanks for this very good news ! the repository is sl-testing ! does it mean that it'll be later on main repo sl ? Why you don't create a new repo like you've done for devtoolset ? It will be in the same directory tree as devtoolset when final. A choice from RedHat ? ? Will you need some (good) fell-back on a specific mailing-list ? You can send reports to this list. Thanks for providing these packages. I installed and ran python27 python33 - both looked fine (didn't do any significant testing though). -Ben Ben, Thanks for testing. -Connie Sieh
Re: Software Collections 1.0 is available for testing for SL 6
On Thu, 17 Oct 2013, Yi Ding wrote: --089e01229ed41b6a8304e8f287f5 Content-Type: text/plain; charset=ISO-8859-1 Thanks Connie. I'm trying to get devtoolset-2 to build on the opensuse build service, but haven't had much luck so far. Devtoolset 2 is more complicated than Devtoolset 1 . It contains a newer eclipse but to build that eclipse you need build dependencies from Fedora 19 . -Connie Sieh Cheers, Yi On Thu, Oct 17, 2013 at 10:38 AM, Connie Sieh cs...@fnal.gov wrote: On Wed, 16 Oct 2013, Yi Ding wrote: Does anyone know what the right way to build these from SRPMs is? Not sure why you want to rebuild since we already provide the binaries. We will use python27 for this example. You have define scl to be python27 when you are building the python27 packages. Or you can build python27-1-10.el6.src.rpm which will provide python27-build-1-10.el6.x86_**64.rpm. The python27-build-1-10.el6.x86_**64.rpm package provides /etc/rpm/macros.python27-**config which defines scl. --**--** --- (x86_64)# more macros.python27-config %scl python27 --** --**--- Then you can install python27-build-1-10.el6.x86_**64.rpm . Note you will have to uninstall python27-build-1-10.el6.x86_**64.rpm and install another [package]-build which will define scl for that package . Additional dependencies are scl-utils-build . -Connie Sieh Thanks, Yi On Thu, Sep 26, 2013 at 10:42 AM, Connie Sieh cs...@fnal.gov wrote: On Wed, 25 Sep 2013, Ben wrote: On Wed, Sep 25, 2013 at 10:02:14AM -0500, Connie Sieh wrote: On Wed, 25 Sep 2013, Matthieu Guionnet wrote: thanks for this very good news ! the repository is sl-testing ! does it mean that it'll be later on main repo sl ? Why you don't create a new repo like you've done for devtoolset ? It will be in the same directory tree as devtoolset when final. A choice from RedHat ? ? Will you need some (good) fell-back on a specific mailing-list ? You can send reports to this list. Thanks for providing these packages. I installed and ran python27 python33 - both looked fine (didn't do any significant testing though). -Ben Ben, Thanks for testing. -Connie Sieh --089e01229ed41b6a8304e8f287f5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable div dir=3DltrThanks Connie. =A0I#39;m trying to get devtoolset-2 to bu= ild on the opensuse build service, but haven#39;t had much luck so far.di= vbr/divdivCheers,/divdivYi/div/divdiv class=3Dgmail_extra= br brdiv class=3Dgmail_quoteOn Thu, Oct 17, 2013 at 10:38 AM, Connie Sie= h span dir=3Dltrlt;a href=3Dmailto:cs...@fnal.gov; target=3D_blank= cs...@fnal.gov/agt;/span wrote:brblockquote class=3Dgmail_quote = style=3Dmargin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex div class=3DimOn Wed, 16 Oct 2013, Yi Ding wrote:br br blockquote class=3Dgmail_quote style=3Dmargin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex Does anyone know what the quot;rightquot; way to build these from SRPMs i= s?br /blockquote br/div Not sure why you want to rebuild since we already provide the binaries.br br We will use quot;python27quot; for this example.br br You have define quot;sclquot; to be quot;python27quot; when you are bui= lding the quot;python27quot; packages. =A0Or you can build quot;python27= -1-10.el6.src.rpmquot; which will provide python27-build-1-10.el6.x86_u= /u64.rpm. =A0The python27-build-1-10.el6.x86_u/u64.rpm package provide= s /etc/rpm/macros.python27-u/uconfig which defines quot;sclquot;.br --u/u--u/u-= --br (x86_64)# more macros.python27-configbr %scl python27 --u/u= --u/u---br br Then you can install python27-build-1-10.el6.x86_u/u64.rpm . =A0Note yo= u will have to uninstall python27-build-1-10.el6.x86_u/u64.rpm and inst= all another [package]-build which will define quot;sclquot; for that pack= age .br br Additional dependencies are scl-utils-build .span class=3DHOEnZbfont c= olor=3D#88br br -Connie Sieh/font/spandiv class=3DHOEnZbdiv class=3Dh5br br blockquote class=3Dgmail_quote style=3Dmargin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex br Thanks,br Yibr br br On Thu, Sep 26, 2013 at 10:42 AM, Connie Sieh lt;a href=3Dmailto:csieh@f= nal.gov target=3D_blankcs...@fnal.gov/agt; wrote:br br blockquote class=3Dgmail_quote style=3Dmargin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex On Wed, 25 Sep 2013, Ben wrote:br br =A0On Wed, Sep 25, 2013 at 10:02:14AM -0500, Connie Sieh wrote:br blockquote class=3Dgmail_quote style=3Dmargin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex br blockquote class=3Dgmail_quote style=3Dmargin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex On Wed, 25 Sep 2013, Matthieu Guionnet wrote:br br
Re: Software Collections 1.0 is available for testing for SL 6
On Wed, 25 Sep 2013, Ben wrote: On Wed, Sep 25, 2013 at 10:02:14AM -0500, Connie Sieh wrote: On Wed, 25 Sep 2013, Matthieu Guionnet wrote: thanks for this very good news ! the repository is sl-testing ! does it mean that it'll be later on main repo sl ? Why you don't create a new repo like you've done for devtoolset ? It will be in the same directory tree as devtoolset when final. A choice from RedHat ? ? Will you need some (good) fell-back on a specific mailing-list ? You can send reports to this list. Thanks for providing these packages. I installed and ran python27 python33 - both looked fine (didn't do any significant testing though). -Ben Ben, Thanks for testing. -Connie Sieh
Re: UEFI SL 6x boot
On Tue, 24 Sep 2013, Yasha Karant wrote: Let me see if I understand the current situation. This question was prompted by the question of a colleague attempting to use OpenSuSE (not SL nor TUV) on UEFI Secure Boot who was not able to get a reliably booted running operating environment. The colleague wondered if SL would fare better. Depending upon the particular BIOS or BIOS equivalent, using MS Windows 8, it may be possible to disable Secure Boot and allow for SL to be Using is not the official status, it is Windows 8 logo use that dictates secure boot. And if it is enabled then it is required to have a way to disable it. Please give the vendors a chance with turning secure boot off. booted. Secure Boot, and many other technologies put forward by, through, or under the auspices of the monopoly primarily exist to move forward the market share, return on investment, and general economic wealth of the monopoly (not a surprise in oligopolistic non-market economics). SL with Fermilab participation is participating in projects that will allow SL to boot on UEFI Secure Boot hardware without the use of any This is only planned for SL 7 as RHEL 7 is expected to have secure boot ability. monopoly operating environment software or applications -- Microsoft not required. Presumably, TUV is participating as well as TUV supported-for-fee environments must be able to reliably boot and run on UEFI Secure Boot platforms without the use of monopoly software to enable the booting process. Apple is not a matter for discussion because Apple provides the entire hardware and software package, and does not allow the use of MacOS on non-Apple hardware platforms. Presumably VirtualBox and other means to allow MS Windows to run as a guest environment has or will have some means to provide UEFI Secure Boot to MS Windows guests requiring such. Since the requirement is to be allowed to use the windows 8 logo not sure that this would be a issue . At present, there is no production Linux that will reliably run on all hardware platforms that use UEFI Secure Boot That is true if you include Windows ARM systems because of the inability to disable Secure Boot . x86_64 systems are a work in progress. Depends on your definition of production Linux. Ubuntu 12.04.4 LTS should work. -Connie Sieh but only MS Windows envirnoments will do so on any hardware platform that proclaims compliance with the monopoly (certification). Is the above substantially correct as of this instant? Yasha Karant On 09/24/2013 04:40 PM, Connie Sieh wrote: On Tue, 24 Sep 2013, Nico Kadel-Garcia wrote: --001a11c379ecc5abcb04e7297e9d Content-Type: text/plain; charset=ISO-8859-1 Down, boy. Scientific Linux is behind the times on available tools, because our favorite upstream vendor has not yet released tools. Tools to work with have been tested, effectively, with Fedora, and I expect our favorite upstream vendor will include tools with release 7.x, which is not yet in alpha or beta release. Check out http://docs.fedoraproject.org/en-US/Fedora/18/html-single/UEFI_Secure_Boot_Guide/index.htmlfor a good breakdown of the issues and trade-offs. UEFI is part of the old Palladium project from Microsoft, relabeled as Trusted Computing. It is aimed squarely at DRM and vendor lock-in, not security, for reasons that I could spend a whole day discussing.In the meantime, yes, you can disalbe it for SL booting if needed, and reasonably expect our favorite upstream vendor to have shims available when version 7 is publishedL they're already working well with recent Fedora releases. I'd also *expect* those shims to be workable for SL 7, but someone may have to plunk down some cash to get some keys signed, and spend some extra effort to maintain the security needed for the relevant shims to work well with SL kernels and environments. Last week at LinuxCon North America the shim developers were still developing. I attended the UEFI Plugfest last week as part of Linux Con. Microsoft gave a presentation on UEFI signing. The presentation will be posted to uefi.org website. We are working on this. Fermilab is a member of the UEFI forum . -Connie Sieh On Tue, Sep 24, 2013 at 11:53 AM, Yasha Karant ykar...@csusb.edu wrote: Secure boot is enabled. Evidently, the only means to disable secure boot requires that a secure boot loader/configuration program be running -- e.g., the MS proprietary boot loader (typically, supplied as part of MS Windows 8) must be used to disable secure boat if the UEFI actually permits this to be disabled (I have heard of some UEFI implementations that do not permit secure boot truly to be disabled). If Linux cannot handle this issue, then Linux is finished on all generic (e.g., not Apple that supplies both the hardware and operating environment software under a restrictive proprietary for-profit intellectual property license) X86-64 hardware, as (almost?) all current such hardware is MS 8 (UEFI secure
Re: UEFI SL 6x boot
On Tue, 24 Sep 2013, Yasha Karant wrote: To be specific, my colleague is using the licensed-for-free binary download of current OpenSuSE that nominally supports UEFI Secure Boot -- and it does not work in fact on the hardware he has. He did experiment with a licensed copy of MS Win 8, and it would install on the same platform without this issue (but absolutely is not what he wants or is willing to use as a primary -- non-Virtual-Box running under -- OS. Did your colleague discuss these issues with the hardware vendor to make sure what he was doing was correct? Did he research/contact OpenSuSE about his secure boot issues? -connie sieh On 09/24/2013 09:55 AM, Connie Sieh wrote: On Tue, 24 Sep 2013, Yasha Karant wrote: This thread started because my colleague is using SuSE and tried Ubuntu -- and both failed to secure boot properly from the generic hardware to which he upgraded. This failure prompted a question about SL (as a no-fee option for a TUV enterprise, commercial, supported, production Linux base). Evidently, the current answer for SL is that it is not UEFI Secure Boot enabled, and SL 6x cannot reliably be installed upon such systems -- depending upon the quirks (or proprietary generosity) of the actual BIOS supplier. OpenSuSE supports secure boot not SuSE as I stated earlier. I am sure it is only recent versions of OpenSuSE, Fedora and Ubuntu that support 'secure boot. See the following for more info. In particular pages 12 and 17. There are references to youtube videos on page 18 showing Windows 8 dual booting with Ubuntu 12.10 . http://events.linuxfoundation.org/sites/events/files/slides/LinuxConUEFIandLinuxBresniker.pdf It is efi compliant. If the bios vendor does not allow secure boot to be turned off then one should converse with said vendor. -connie sieh Yasha Karant On 09/24/2013 09:04 AM, Connie Sieh wrote: On Tue, 24 Sep 2013, Yasha Karant wrote: Secure boot is enabled. Evidently, the only means to disable secure boot requires that a secure boot loader/configuration program be running -- e.g., the MS proprietary boot loader (typically, supplied as part of MS Windows 8) must be used to disable secure boat if the UEFI actually permits this to be disabled (I have heard of some UEFI implementations that do not permit secure boot truly to be disabled). If the system is Windows 8 logo compatible and is x86_4 then a way to disable secure boot must be provided by the hardware vendor. This is commonly done via a option in the bios. This requirement is part of the microsoft windows 8 logo requirements. Note the method of disabling is not defined by the UEFI spec. So each vendor may do it differently. The only hardware that does not permit secure boot to be disabled is arm based Windows. The Windows logo requirements at at work here. If Linux cannot handle this issue, then Linux is finished on all generic (e.g., not Apple that supplies both the hardware and operating environment software under a restrictive proprietary for-profit intellectual property license) X86-64 hardware, as (almost?) all current such hardware is MS 8 (UEFI secure boot) compliant. At the moment Fedora, SuSE , Ubuntu all can handle secure boot. It is expected that RHEL 7 will also handle it. It is also possible to sign your own kernel and place your keys in the bios. -connie Yasha Karant On 09/23/2013 10:29 PM, Connie Sieh wrote: On Mon, 23 Sep 2013, Yasha Karant wrote: A colleague who uses SuSE non-enterprise for his professional (enterprise) workstations has now attempted to load the latest SuSE on a machine with a new generic (aftermarket) gamer UEFI X86-64 motherboard. It does not properly boot. I do not have any UEFI motherboards, and thus no experience with SL6x on such motherboards. Is secure boot enabled in the UEFI ? Does anyone? Does SL6x boot correctly (and easily) on a UEFI motherboard? If so, he may switch to SL. Yes as long as secure boot is disabled . Yasha Karant -connie sieh
Re: UEFI SL 6x boot
On Tue, 24 Sep 2013, Yasha Karant wrote: Secure boot is enabled. Evidently, the only means to disable secure boot requires that a secure boot loader/configuration program be running -- e.g., the MS proprietary boot loader (typically, supplied as part of MS Windows 8) must be used to disable secure boat if the UEFI actually permits this to be disabled (I have heard of some UEFI implementations that do not permit secure boot truly to be disabled). If the system is Windows 8 logo compatible and is x86_4 then a way to disable secure boot must be provided by the hardware vendor. This is commonly done via a option in the bios. This requirement is part of the microsoft windows 8 logo requirements. Note the method of disabling is not defined by the UEFI spec. So each vendor may do it differently. The only hardware that does not permit secure boot to be disabled is arm based Windows. The Windows logo requirements at at work here. If Linux cannot handle this issue, then Linux is finished on all generic (e.g., not Apple that supplies both the hardware and operating environment software under a restrictive proprietary for-profit intellectual property license) X86-64 hardware, as (almost?) all current such hardware is MS 8 (UEFI secure boot) compliant. At the moment Fedora, SuSE , Ubuntu all can handle secure boot. It is expected that RHEL 7 will also handle it. It is also possible to sign your own kernel and place your keys in the bios. -connie Yasha Karant On 09/23/2013 10:29 PM, Connie Sieh wrote: On Mon, 23 Sep 2013, Yasha Karant wrote: A colleague who uses SuSE non-enterprise for his professional (enterprise) workstations has now attempted to load the latest SuSE on a machine with a new generic (aftermarket) gamer UEFI X86-64 motherboard. It does not properly boot. I do not have any UEFI motherboards, and thus no experience with SL6x on such motherboards. Is secure boot enabled in the UEFI ? Does anyone? Does SL6x boot correctly (and easily) on a UEFI motherboard? If so, he may switch to SL. Yes as long as secure boot is disabled . Yasha Karant -connie sieh
Re: UEFI SL 6x boot
On Tue, 24 Sep 2013, Yasha Karant wrote: This thread started because my colleague is using SuSE and tried Ubuntu -- and both failed to secure boot properly from the generic hardware to which he upgraded. This failure prompted a question about SL (as a no-fee option for a TUV enterprise, commercial, supported, production Linux base). Evidently, the current answer for SL is that it is not UEFI Secure Boot enabled, and SL 6x cannot reliably be installed upon such systems -- depending upon the quirks (or proprietary generosity) of the actual BIOS supplier. OpenSuSE supports secure boot not SuSE as I stated earlier. I am sure it is only recent versions of OpenSuSE, Fedora and Ubuntu that support 'secure boot. See the following for more info. In particular pages 12 and 17. There are references to youtube videos on page 18 showing Windows 8 dual booting with Ubuntu 12.10 . http://events.linuxfoundation.org/sites/events/files/slides/LinuxConUEFIandLinuxBresniker.pdf It is efi compliant. If the bios vendor does not allow secure boot to be turned off then one should converse with said vendor. -connie sieh Yasha Karant On 09/24/2013 09:04 AM, Connie Sieh wrote: On Tue, 24 Sep 2013, Yasha Karant wrote: Secure boot is enabled. Evidently, the only means to disable secure boot requires that a secure boot loader/configuration program be running -- e.g., the MS proprietary boot loader (typically, supplied as part of MS Windows 8) must be used to disable secure boat if the UEFI actually permits this to be disabled (I have heard of some UEFI implementations that do not permit secure boot truly to be disabled). If the system is Windows 8 logo compatible and is x86_4 then a way to disable secure boot must be provided by the hardware vendor. This is commonly done via a option in the bios. This requirement is part of the microsoft windows 8 logo requirements. Note the method of disabling is not defined by the UEFI spec. So each vendor may do it differently. The only hardware that does not permit secure boot to be disabled is arm based Windows. The Windows logo requirements at at work here. If Linux cannot handle this issue, then Linux is finished on all generic (e.g., not Apple that supplies both the hardware and operating environment software under a restrictive proprietary for-profit intellectual property license) X86-64 hardware, as (almost?) all current such hardware is MS 8 (UEFI secure boot) compliant. At the moment Fedora, SuSE , Ubuntu all can handle secure boot. It is expected that RHEL 7 will also handle it. It is also possible to sign your own kernel and place your keys in the bios. -connie Yasha Karant On 09/23/2013 10:29 PM, Connie Sieh wrote: On Mon, 23 Sep 2013, Yasha Karant wrote: A colleague who uses SuSE non-enterprise for his professional (enterprise) workstations has now attempted to load the latest SuSE on a machine with a new generic (aftermarket) gamer UEFI X86-64 motherboard. It does not properly boot. I do not have any UEFI motherboards, and thus no experience with SL6x on such motherboards. Is secure boot enabled in the UEFI ? Does anyone? Does SL6x boot correctly (and easily) on a UEFI motherboard? If so, he may switch to SL. Yes as long as secure boot is disabled . Yasha Karant -connie sieh
Re: Software Collections 1.0 is available for testing for SL 6
On Tue, 24 Sep 2013, Connie Sieh wrote: The following software collection products are now available for testing for SL 6. Use --enablerepo=sl-testing to enable yum to access these products. More info on these products is available at http://developerblog.redhat.com/2013/09/12/rhscl1-ga/ https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Developer_Guide/chap-RHSCL.html A Redhat webinar about software collections is available tommorow. Info is at http://developerblog.redhat.com/2013/09/13/webinar-technical-intro-to-red-hat-software-collections/ Even more references http://www.redhat.com/developerexchange/DevExchange_bring_order_into_your_packaging_madness_with_software_collections-mmaslano.pdf http://www.redhat.com/developerexchange/DevExchange-from-conventional-rpm-to-software-collections-kabrda.pdf -Connie Sieh mariadb55 mysql55 nodejs010 perl516 php54 postgresql92 python27 python33 ruby193 -Connie Sieh
Re: UEFI SL 6x boot
On Tue, 24 Sep 2013, Nico Kadel-Garcia wrote: --001a11c379ecc5abcb04e7297e9d Content-Type: text/plain; charset=ISO-8859-1 Down, boy. Scientific Linux is behind the times on available tools, because our favorite upstream vendor has not yet released tools. Tools to work with have been tested, effectively, with Fedora, and I expect our favorite upstream vendor will include tools with release 7.x, which is not yet in alpha or beta release. Check out http://docs.fedoraproject.org/en-US/Fedora/18/html-single/UEFI_Secure_Boot_Guide/index.htmlfor a good breakdown of the issues and trade-offs. UEFI is part of the old Palladium project from Microsoft, relabeled as Trusted Computing. It is aimed squarely at DRM and vendor lock-in, not security, for reasons that I could spend a whole day discussing.In the meantime, yes, you can disalbe it for SL booting if needed, and reasonably expect our favorite upstream vendor to have shims available when version 7 is publishedL they're already working well with recent Fedora releases. I'd also *expect* those shims to be workable for SL 7, but someone may have to plunk down some cash to get some keys signed, and spend some extra effort to maintain the security needed for the relevant shims to work well with SL kernels and environments. Last week at LinuxCon North America the shim developers were still developing. I attended the UEFI Plugfest last week as part of Linux Con. Microsoft gave a presentation on UEFI signing. The presentation will be posted to uefi.org website. We are working on this. Fermilab is a member of the UEFI forum . -Connie Sieh On Tue, Sep 24, 2013 at 11:53 AM, Yasha Karant ykar...@csusb.edu wrote: Secure boot is enabled. Evidently, the only means to disable secure boot requires that a secure boot loader/configuration program be running -- e.g., the MS proprietary boot loader (typically, supplied as part of MS Windows 8) must be used to disable secure boat if the UEFI actually permits this to be disabled (I have heard of some UEFI implementations that do not permit secure boot truly to be disabled). If Linux cannot handle this issue, then Linux is finished on all generic (e.g., not Apple that supplies both the hardware and operating environment software under a restrictive proprietary for-profit intellectual property license) X86-64 hardware, as (almost?) all current such hardware is MS 8 (UEFI secure boot) compliant. Yasha Karant On 09/23/2013 10:29 PM, Connie Sieh wrote: On Mon, 23 Sep 2013, Yasha Karant wrote: A colleague who uses SuSE non-enterprise for his professional (enterprise) workstations has now attempted to load the latest SuSE on a machine with a new generic (aftermarket) gamer UEFI X86-64 motherboard. It does not properly boot. I do not have any UEFI motherboards, and thus no experience with SL6x on such motherboards. Is secure boot enabled in the UEFI ? Does anyone? Does SL6x boot correctly (and easily) on a UEFI motherboard? If so, he may switch to SL. Yes as long as secure boot is disabled . Yasha Karant -connie sieh --001a11c379ecc5abcb04e7297e9d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable div dir=3DltrdivdivdivDown, boy.brbr/divScientific Linux is= behind the times on available tools, because our favorite upstream vendor = has not yet released tools. Tools to work with have been tested, effectivel= y, with Fedora, and I expect our favorite upstream vendor will include tool= s with release 7.x, which is not yet in alpha or beta release. Check out a= href=3Dhttp://docs.fedoraproject.org/en-US/Fedora/18/html-single/UEFI_Sec= ure_Boot_Guide/index.htmlhttp://docs.fedoraproject.org/en-US/Fedora/18/ht= ml-single/UEFI_Secure_Boot_Guide/index.html/a for a good breakdown of the= issues and trade-offs.br br/divUEFI is part of the old quot;Palladiumquot; project from Micros= oft, relabeled as quot;Trusted Computingquot;. It is aimed squarely at DR= M and vendor lock-in, not security, for reasons that I could spend a whole = day discussing.In the meantime, yes, you can disalbe it for SL booting if n= eeded, and reasonably expect our favorite upstream vendor to have shims ava= ilable when version 7 is publishedL they#39;re already working well with r= ecent Fedora releases. I#39;d also *expect* those shims to be workable for= SL 7, but someone may have to plunk down some cash to get some keys signed= , and spend some extra effort to maintain the security needed for the relev= ant shims to work well with SL kernels and environments.br /div/divdiv class=3Dgmail_extrabrbrdiv class=3Dgmail_quoteO= n Tue, Sep 24, 2013 at 11:53 AM, Yasha Karant span dir=3Dltrlt;a href= =3Dmailto:ykar...@csusb.edu; target=3D_blankykar...@csusb.edu/agt;/= span wrote:br blockquote class=3Dgmail_quote style=3Dmargin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1exSecure boot is enabled. =A0Evidently, the on= ly means to disable secure boot requires that a secure boot
Re: UEFI SL 6x boot
On Mon, 23 Sep 2013, Yasha Karant wrote: A colleague who uses SuSE non-enterprise for his professional (enterprise) workstations has now attempted to load the latest SuSE on a machine with a new generic (aftermarket) gamer UEFI X86-64 motherboard. It does not properly boot. I do not have any UEFI motherboards, and thus no experience with SL6x on such motherboards. Is secure boot enabled in the UEFI ? Does anyone? Does SL6x boot correctly (and easily) on a UEFI motherboard? If so, he may switch to SL. Yes as long as secure boot is disabled . Yasha Karant -connie sieh
Re: Developer Toolset 2?
On Mon, 16 Sep 2013, Herb Thompson wrote: --047d7bf0f67a99d51d04e689b1c4 Content-Type: text/plain; charset=ISO-8859-1 As a happy and appreciative user of the SL build of Developer Toolset 1, I can't resist asking if the SL team has any plans to provide a build of the newly released version 2? Working on it. -Connie Sieh --047d7bf0f67a99d51d04e689b1c4 Content-Type: text/html; charset=ISO-8859-1 div dir=ltrAs a happy and appreciative user of the SL build of Developer Toolset 1, I can#39;t resist asking if the SL team has any plans to provide a build of the newly released version 2?brbr/div --047d7bf0f67a99d51d04e689b1c4--
Re: New Install of 6.4 - no Internet step 2, 3, 4 -- 5 - What works Does not
On Wed, 14 Aug 2013, Larry Linder wrote: Gigabyte 970A-DS3 with Quad core AMD. SL 5.8 loads and everything works. Fedora 19 loads and everything works. kernel linux 3.9.5-301.fc19 SL 6.4 loads and when network is set up. Realtech on board chip set RTL 8168/811E as marked on chip. Network will not connect. Ping 192.168.0.1 - router and it runs ping and no return from router. ifconfig eth0 receives data but TX is always 0. Tried different drivers for realtech chip - nothing worked and most would fail when you restart no eth0. Fresh install of 6.4 with network set up - same result - no network TX. Loaded new Kernel from Elrepo.kernel-it-3.0.89-el6.elrepo.x86_64.rpm Installed with rpm -i *.rpm. rebooted system touched key to select new kernel at boot. ifconfig eth0 receives data and transmits data. network now connects and everything now works. Conclusion is the kernel supplied in 6.4 has a mistake somewhere, realtech driver and hardware are good. Does SL 6.3 work out of the box? Each point release has many kernel changes. If it is known if 6.3 works but 6.4 does not then that helps to pins down when the problem was induced. -Connie Sieh r8168 driver works with SL5.8. Installing new kernel solved the problem. r8169 driver is used with Fedora 19. Have learned more than I wanted to know. Thank you all for your help. Larry Linder On Tuesday 13 August 2013 11:57 am, Larry Linder wrote: On Monday 12 August 2013 10:41 am, Larry Linder wrote: On Friday 09 August 2013 12:44 pm, you wrote: On Fri, Aug 9, 2013 at 7:19 AM, Larry Linder larry.lin...@micro-controls.com wrote: Have you looked at ELRepo? Particularly, FAQ#4 at http://elrepo.org/tiki/FAQ may help you find the right driver for the NIC. Akemi The problem with the MB's using RTL8168/8111 has been know for a few years. The 32 bit version of SL 6.2 works - have not verified it. We need to use SL 64 our system. Installed Windows 7 on a spare disk, Internet found and worked - hardware is checked. Downloaded new driver from realtech.com for RTL8168/8111 and sneaker net ed it over to SL 6.4 box applied the new driver. New driver must have a problem with the 64 bit interface - or SL 6 X _64 code is broken somewhere. Did you have a chance to identify your device IDs (see above, my note)? I have a system with the following NIC: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02) The motherboard is GA-MA785GM-US2H. I use ELRepo's driver from kmod-r8168-8.032.00-1.el6.elrepo.x86_64. The OS is SL 6.4 (64-bit) but this machine has been running SL for at least 3 years with no apparent network trouble. Akemi Tried the driver from elrepo.X86.64 - did not work - A direct install of SL6.4 resulted in eth0 receiving data but not transmission. Installing new driver resulted in eth0 not being recognized. Ping quit - no eth0 found. ifconfig confirms that there is not eth0. We had to enable IOMMU on mother board and then Fedora 19 live would load. The driver used was in Fedora 19 was R1869- Internet was working. Tried using r1869 with SL 6.4 and eth0 was not listed in ifconfig Numerous people on net said that SL 6.4 32 bit version would load and Ethernet worked. May try this a later today to verify it. Reloading SL 6.4 from DVD this AM to use system as an isolated box. Any help would be appreciated. Learned more about drivers than I wanted to know. Comment: Fedora 19 with the latest Gnome desktop is written for a tablet. It only takes 6 mouse clicks to do anything useful - Hope RH 7 will allow a person to select an older version of KDE or Gnome. I would hate to think of the number of mouse ites injuries we could have. Is there a number of simpler desktops available. The new KDE is useless, Gnome in Fidora 19 is terrible so where do people who need a no BS computer go? Thank You All Larry Linder The mystery of why there is no Internet on 6.4 using the Gigabyte board become more confusing. We were looking at our hardware list and decided that boxes deployed two years ago had essentially the same NIC stuff and they worked with 5.5 - 5.9. We loaded 5.8 into new Gigabyte hardware and guess what it worked perfectly !!! The 6.4 DVD was down loaded and checked and everything matches. There is something wrong in the Gnome system network set up. SL 5.8 has a very different network setup. We got pretty suspicious when we loaded updated driver and new Kernel 3.0.8 and same result. Too many people stated that this worked. SL 6.4 is loading for the nth time and we will use another scheme to setup network. Thank You All Larry Linder
Re: libdvdread 4.1 vs 4.2 backport
On Thu, 8 Aug 2013, Andrew Z wrote: --001a1133c3ee9435d204e3753faf Content-Type: text/plain; charset=ISO-8859-1 Gentlemen, i'm a bit confused here with version numbers for libdvdread. one i have installed: Installed Packages Name: libdvdread Arch: x86_64 Version : 4.1.4 Release : 0.3.svn1183.el6 Size: 145 k Repo: installed From repo : sl At the same time linuxtech has a higher number in BACKPORT? http://pkgs.org/centos-6-rhel-6/linuxtech-backports-x86_64/libdvdread-devel-4.2.0-2.el6.x86_64.rpm.html my (mis) understanding that backport is for _older_ versions ? and another question is there a 4.2 for 6.4? Version 4.1.4-0.3.svn1183.el6 is in 6.4 . -Connie Sieh Thank you AZ --001a1133c3ee9435d204e3753faf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable div dir=3DltrdivdivdivGentlemen,br/div=A0i#39;m a bit confus= ed here with version numbers for libdvdread.brbr/divone i have instal= led:brInstalled PackagesbrName=A0=A0=A0=A0=A0=A0=A0 : libdvdreadbrArc= h=A0=A0=A0=A0=A0=A0=A0 : x86_64br Version=A0=A0=A0=A0 : 4.1.4brRelease=A0=A0=A0=A0 : 0.3.svn1183.el6brSiz= e=A0=A0=A0=A0=A0=A0=A0 : 145 kbrRepo=A0=A0=A0=A0=A0=A0=A0 : installedbr= From repo=A0=A0 : slbrbr/divAt the same time linuxtech has a higher n= umber in BACKPORT?brdiva href=3Dhttp://pkgs.org/centos-6-rhel-6/linux= tech-backports-x86_64/libdvdread-devel-4.2.0-2.el6.x86_64.rpm.htmlhttp://= pkgs.org/centos-6-rhel-6/linuxtech-backports-x86_64/libdvdread-devel-4.2.0-= 2.el6.x86_64.rpm.html/abr br/divdivmy (mis) understanding that backport is for _older_ versions= ?brbr/divdivand another question is there a 4.2 for 6.4?brbrTh= ank youbrAZbrbr/div/div --001a1133c3ee9435d204e3753faf--
Re: libdvdread 4.1 vs 4.2 backport
On Thu, 8 Aug 2013, Andrew Z wrote: Thank you Connie, I have it installed. But I wonder about 4.2? We get libdvdread from TUV . You could put in a bugzilla requesting it be updated to newer version in future RHEL 6 releases. -Connie Sieh On Aug 8, 2013 4:13 PM, Connie Sieh cs...@fnal.gov wrote: On Thu, 8 Aug 2013, Andrew Z wrote: --001a1133c3ee9435d204e3753faf Content-Type: text/plain; charset=ISO-8859-1 Gentlemen, i'm a bit confused here with version numbers for libdvdread. one i have installed: Installed Packages Name: libdvdread Arch: x86_64 Version : 4.1.4 Release : 0.3.svn1183.el6 Size: 145 k Repo: installed From repo : sl At the same time linuxtech has a higher number in BACKPORT? http://pkgs.org/centos-6-rhel-**6/linuxtech-backports-x86_64/** libdvdread-devel-4.2.0-2.el6.**x86_64.rpm.htmlhttp://pkgs.org/centos-6-rhel-6/linuxtech-backports-x86_64/libdvdread-devel-4.2.0-2.el6.x86_64.rpm.html my (mis) understanding that backport is for _older_ versions ? and another question is there a 4.2 for 6.4? Version 4.1.4-0.3.svn1183.el6 is in 6.4 . -Connie Sieh Thank you AZ --001a1133c3ee9435d204e3753faf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable div dir=3Dltrdivdivdiv**Gentlemen,br/div=A0i#39;m a bit confus= ed here with version numbers for libdvdread.brbr/divone i have instal= led:brInstalled PackagesbrName=A0=A0=A0=A0=**A0=A0=A0 : libdvdreadbrArc= h=A0=A0=A0=A0=A0=A0=A0 : x86_64br Version=A0=A0=A0=A0 : 4.1.4brRelease=A0=A0=A0=A0 : 0.3.svn1183.el6brSiz= e=A0=A0=A0=A0=A0=A0=A0 : 145 kbrRepo=A0=A0=A0=A0=A0=A0=A0 : installedbr= From repo=A0=A0 : slbrbr/divAt the same time linuxtech has a higher n= umber in BACKPORT?brdiva href=3Dhttp://pkgs.org/** centos-6-rhel-6/linux= http://pkgs.org/centos-6-rhel-6/linux= tech-backports-x86_64/**libdvdread-devel-4.2.0-2.el6.** x86_64.rpm.htmlhttp://= pkgs.org/centos-6-rhel-6/**linuxtech-backports-x86_64/** libdvdread-devel-4.2.0-=http://pkgs.org/centos-6-rhel-6/linuxtech-backports-x86_64/libdvdread-devel-4.2.0-= 2.el6.x86_64.rpm.html/abr br/divdivmy (mis) understanding that backport is for _older_ versions= ?brbr/divdivand another question is there a 4.2 for 6.4?brbrTh= ank youbrAZbrbr/div/div --**001a1133c3ee9435d204e3753faf--
Re: New Install of 6.4 - no Internet
On Wed, 7 Aug 2013, Larry Linder wrote: Not really the place for this but I need some neural help. New prototype system for SL 6.4 -=20 Installed as a custom install - so we can get disks labeled as we need them. Set up everything but could not access the Internet. Since this is a new= =20 Gigabyte GA-970A-DS3, AMD quad core, 16G of dram and a couple of TByte=20 disks. Used the Ethernet install tool on GNOME and it all looked good - addresses= =20 checked, router, gateway etc. When I ran ping 192.168.0.1 - address of our router =46rom 192.168.0.111 icmp_seq=3D1 Destination Host Unreachable and then=20 insufficient memory error The second time I ran pingit gave the same result but no memory error. Added a known good 10/100 Ethernet board and used next address and the exac= t=20 same result. Used eth1 for new board and eth0 for the MB Ethernet. 3 rd attempt was an install - upgrade with command line linux - asknetwork Set this up as it asked with offset address of 192.168.0.112,mask,gateway = =20 metric =3D 1 reboot and same result. This appears to be some kind of Firewall problem. In SL5.8 you had the=20 option of setting it promiscuous and then it all worked and it was easy to= =20 add the required firewall protections. But this network is inside the pla= nt=20 so we do not check everything. Would like to turn Firewall stuff off to see if problem goes away but could= =20 find little info on it . I am convinced that HW is good, tested cable drop and was able to connect i= t=20 to another box and Ethernet worked. 4. Next will be an install with a live CD and see if we can make the=20 connection with it. Any ideas as to where to look or how to disable security stuff. Thank You=20 Larry Linder What does ifconfig show? -Connie Sieh
Re: Large filesystem recommendation
On Wed, 24 Jul 2013, Ray Van Dolson wrote: On Wed, Jul 24, 2013 at 01:59:03PM -0400, John Lauro wrote: What is recommended for a large file system (40TB) under SL6? In the past I have always had good luck with jfs. Might not be the fastest, but very stable. It works well with being able to repair huge filesystems in reasonable amount of RAM, and handle large directories, and large files. Unfortunately jfs doesn't appear to be supported in 6? (or is there a repo I can add?) Besides for support of 40+TB filesystem, also need support of files 4TB, and directories with hundreds of thousands of files. What do people recommend? Echoing what others have said, sounds like XFS might be the best option if you can find a repository with a quality version (EPEL perhaps?) Do you have issues with the xfs that is provided in SL 6? -Connie Sieh Interesting on the Backblaze and ext4 thing. While ext4 itself may support this larger file system size, I'm not sure if the default ext4tools will?? Could be a risk to investigate if you go this route. Other options I can think of: - btrfs (not sure if something like EPEL provides a release with this) - ZFS on Linux (for the adventurous only, but I believe they have a version that works well with RHEL). Personally, I'd go XFS. Ray
Re: Red Hat Developer Toolset (C++11) ?
On Tue, 16 Jul 2013, Paul Robert Marino wrote: Sure  you can for the most part where do you think scientific linux came from.  But you don't need a license to get them they are all on Red Hat's public FTP server along with all the other SRPMS for every other free speech or open source piece of software they support. Really the FTP site is the safe bet for that because they won't post SRPM's for any proprietary code on their public FTP server but the ones you get off of access.redhat.com may include proprietary code. The BETA SRPMS are NOT on Red Hat's public FTP server. I am not a lawyer so this is only a opinion and not legal advice. I do NOT think you can redistribute the result since you obtained the SRPM via RHN and not via the public ftp server. -Connie Sieh -- Sent from my HP Pre3 On Jul 16, 2013 13:58, Yi Ding yi.s.d...@gmail.com wrote: This isn't devtoolset specific, but if someone were to get the SRPMs for devtoolset-2 Beta (by using a RHEL license), and were to recompile them would they be able to redistribute them? On Tue, May 14, 2013 at 5:51 PM, Connie Sieh cs...@fnal.gov wrote: On Tue, 14 May 2013, Graham Allan wrote: Thanks, this is wonderful! I wonder how I managed to miss that? I forgot to announce it.  Will do so soon.  In class this week. -Connie Sieh Graham On Tue, May 14, 2013 at 12:07:33PM -0500, Pat Riehecky wrote: The Scientific Linux build is available at: http://ftp.scientificlinux.org/linux/scientific/6x/external_products/devtoo lset/ Pat On 05/14/2013 12:04 PM, Graham Allan wrote: I was just wondering if this ever went anywhere? Obviously I appreciate the no promises part :-) Was it too much of a nightmare to build? I saw that CentOS got to the stage of having a test build available (http://people.centos.org/tru/devtools/) though I haven't looked at it. Graham On 9/17/2012 9:50 AM, Yi Ding wrote: Awesome.  This should be really useful for us (finally a modern era compiler on RHEL supported by Redhat).  Let me know if you want any beta testers. On Wed, Sep 12, 2012 at 4:59 PM, Connie Sieh cs...@fnal.gov wrote: On Wed, 12 Sep 2012, Patrick J. LoPresti wrote: Red Hat has released a compilation environment supporting C++11 as part of the Red Hat Developer Toolset for RHEL 6.x: https://access.redhat.com/knowledge/docs/Red_Hat_Developer_Toolset/ I am curious to know whether anybody has recompiled this for Scientific Linux, whether anybody has an interest in doing so, etc. I have.  Working
Re: Building debug info package
On Thu, 11 Jul 2013, Adam Bishop wrote: I'm trying to build a debug info package from http://ftp.scientificlinux.or= g/linux/scientific/6.4/SRPMS/vendor/freeradius-2.1.12-4.el6_3.src.rpm - how= ever I've not been successful so far. You do not need to build your own debuginfo package unless you change the code. We build all of the debuginfo packages automatically. All of the debuginfo packages for Scientific Linux 6 are located in ftp://ftp.scientificlinux.org/linux/scientific/6x/archive/debuginfo/ -Connie Sieh Adding %debug_package to the spec file and using 'rpmbuild -bb' generated: freeradius-debug-2.1.12-4.el6.x86_64.rpm But not debuginfo - it seems the package name needs to be correct for gdb t= o be able to correctly identify the symbols. What changes do I need to make to the spec file/command to generate a corre= ctly named and populated debug info file (as per http://ftp.scientificlinux= .org/linux/scientific/6.4/archive/debuginfo/freeradius-debuginfo-2.1.12-4.e= l6_3.x86_64.rpm)? Thanks, Adam Bishop gpg: 0x6609D460 Janet, the UK's research and education network. Janet(UK) is a trading name of Jisc Collections and Janet Limited, a=20 not-for-profit company which is registered in England under No. 2881024=20 and whose Registered Office is at Lumen House, Library Avenue, Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238
Re: New person publishing security errata
On Wed, 12 Jun 2013, Yasha Karant wrote: Are these errata from US-CERT (for the Fermilab component), ENISA (for the CERN component), TUV, or a combination of (which, other?) sources? Are the errata characterised by the level of severity? They are all TUV just as they have always been. The level of severity is what TUV assigns to them. The announcement of these are sent to the scientific-linux-errata mailing list. The packages are placed in the security directory of each tree. This is where the nightly yum security update expects to find them. Again this is has it has always been. Note that there are a few packages that have been promoted to security status and those are selinux-policy and tzdata. There have been promoted because they were causing problems when they were not updated with other security errata even though there is no documented dependency on them. Again this is as it has been for many years. Do these errata encompass both notifications and links to required package updates to address the errata? I do not understand the question. -Connie Sieh Yasha Karant On 06/12/2013 08:36 AM, Connie Sieh wrote: I am glad to announce that we have added Bonnie King as one of the people who will be publishing security errata. She will be publishing security errata this week. -Connie Sieh
Re: Red Hat Developer Toolset (C++11) ?
On Tue, 14 May 2013, Graham Allan wrote: Thanks, this is wonderful! I wonder how I managed to miss that? I forgot to announce it. Will do so soon. In class this week. -Connie Sieh Graham On Tue, May 14, 2013 at 12:07:33PM -0500, Pat Riehecky wrote: The Scientific Linux build is available at: http://ftp.scientificlinux.org/linux/scientific/6x/external_products/devtoolset/ Pat On 05/14/2013 12:04 PM, Graham Allan wrote: I was just wondering if this ever went anywhere? Obviously I appreciate the no promises part :-) Was it too much of a nightmare to build? I saw that CentOS got to the stage of having a test build available (http://people.centos.org/tru/devtools/) though I haven't looked at it. Graham On 9/17/2012 9:50 AM, Yi Ding wrote: Awesome. This should be really useful for us (finally a modern era compiler on RHEL supported by Redhat). Let me know if you want any beta testers. On Wed, Sep 12, 2012 at 4:59 PM, Connie Sieh cs...@fnal.gov wrote: On Wed, 12 Sep 2012, Patrick J. LoPresti wrote: Red Hat has released a compilation environment supporting C++11 as part of the Red Hat Developer Toolset for RHEL 6.x: https://access.redhat.com/knowledge/docs/Red_Hat_Developer_Toolset/ I am curious to know whether anybody has recompiled this for Scientific Linux, whether anybody has an interest in doing so, etc. I have. Working on releasing it. It is a bit more complicated to compile than the standard SL. Have to modify the build system to handle it. No promises of course (disclaimer).
Re: On-line update diagnostics
On Thu, 11 Apr 2013, Yasha Karant wrote: After updating my IA-32 image SL 6 laptop to SL 6.4 using the update pathway from the automatically displayed anaconda GUI using the approximately 4Gbyte update/install DVD, rebooting and using the system, the red badge (Update Applet 2.28.3) with a bang appeared on the upper panel. The claim is presented for 148 updates. I attempted to use the automatically displayed GUI updater that is invoked from the red badge icon. In addition to be exceptionally slow because of poor USA DSL bandwidth at my home, the following diagnostics appeared: Traceback (most recent call last): File /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2798, in install_signature self.yumbase.getKeyForPackage(pkg, askcb = lambda x, y, z: True) File /usr/lib/python2.6/site-packages/yum/__init__.py, line 4765, in getKeyForPackage result, errmsg = self.sigCheckPkg(po) File /usr/lib/python2.6/site-packages/yum/__init__.py, line 2189, in sigCheckPkg sigresult = rpmUtils.miscutils.checkSig(ts, po.localPkg()) File /usr/lib/python2.6/site-packages/rpmUtils/miscutils.py, line 67, in checkSig fdno = os.open(package, os.O_RDONLY) OSError: [Errno 2] No such file or directory: '/var/cache/yum/i386/6.4/adobe-linux-i386/packages/AdbeRdr9.5.4-1_i486linux_enu.rpm' could not add package update for lcms2-2.3-2.el6(i686)epel: lcms2-2.3-2.el6.i686 I cancelled the update and will try again later. 1. Does anyone know what is causing the above (recall that the DVD 6.4 upgrade was successful)? Someone removed /var/cache/yum/i386/6.4/adobe-linux-i386/packages/AdbeRdr9.5.4-1_i486linux_ enu.rpm 2. As the on-line update is VERY slow for my situation, I attempted to let the process run overnight unattended. Is there anyway to do this automated install so that it will simply skip those packages that fail (as the above) without requiring root password authentication intervention, similar to the -y switch on fsck. I realize that such automation is not ideal, but it would be less total time to re-install from DVD in the event that the process resulted in a no-boot or highly unstable system. Thanks for any insight. Yasha Karant -Connie Sieh
Re: On-line update diagnostics
On Thu, 11 Apr 2013, Yasha Karant wrote: Konstantin, I do not do so deliberately -- but the mechanism I mentioned is the one that EL presents. The script you provide is not part of any howto that I can find -- and most of the time, neither my students/research associates or I have the time to research and develop/test such things unless necessary. (In some cases, as with the current Nvidia CUDA 5 setup, we do out of necessity.) Thank you for the contribution. A related question: is there a way to burn an update DVD that will contain the files that your script downloads and uses so that the update can be burned on a machine with decent network bandwidth (e.g., accessing the LambaRail or whatever the current name is for this research backbone) and then utilized locally without accessing any network? In other words, going to the repo list authorized for a machine -- how does one get just the updated (update) rpm (etc.) files that are needed and how does one organize these on the DVD image so that your script will use these from said DVD? Use rsync to download the files to a directory. Burn the files to media. Modify the /etc/yum.repos.d/ security config file to point to the dvd. Since rsync only downloads changed/new files then the bandwidth is less than copying the full directory all the time. If the local network is faster you could change the /etc/yum.repos.d/ security config file to point to your mirror that you created above. -Connie Sieh Thanks, Yasha On 04/11/2013 09:57 AM, Konstantin Olchanski wrote: Yasha - of all possibilities you always choose the most painful, without fail. I update SL6.x to SL6.4 using this script. Running the SL installer (anaconda) unnecessary pain. #!/bin/sh YES=-y cat /etc/redhat-release uname -a /bin/ls -ltr /boot | grep vmli | tail -1 yum clean all yum $YES --releasever=6.4 update sl-release yum clean all yum $YES update yum* rpm* yum $YES update K.O. On Thu, Apr 11, 2013 at 09:38:21AM -0700, Yasha Karant wrote: After updating my IA-32 image SL 6 laptop to SL 6.4 using the update pathway from the automatically displayed anaconda GUI using the approximately 4Gbyte update/install DVD, rebooting and using the system, the red badge (Update Applet 2.28.3) with a bang appeared on the upper panel. The claim is presented for 148 updates. I attempted to use the automatically displayed GUI updater that is invoked from the red badge icon. In addition to be exceptionally slow because of poor USA DSL bandwidth at my home, the following diagnostics appeared: Traceback (most recent call last): File /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2798, in install_signature self.yumbase.getKeyForPackage(pkg, askcb = lambda x, y, z: True) File /usr/lib/python2.6/site-packages/yum/__init__.py, line 4765, in getKeyForPackage result, errmsg = self.sigCheckPkg(po) File /usr/lib/python2.6/site-packages/yum/__init__.py, line 2189, in sigCheckPkg sigresult = rpmUtils.miscutils.checkSig(ts, po.localPkg()) File /usr/lib/python2.6/site-packages/rpmUtils/miscutils.py, line 67, in checkSig fdno = os.open(package, os.O_RDONLY) OSError: [Errno 2] No such file or directory: '/var/cache/yum/i386/6.4/adobe-linux-i386/packages/AdbeRdr9.5.4-1_i486linux_enu.rpm' could not add package update for lcms2-2.3-2.el6(i686)epel: lcms2-2.3-2.el6.i686 I cancelled the update and will try again later. 1. Does anyone know what is causing the above (recall that the DVD 6.4 upgrade was successful)? 2. As the on-line update is VERY slow for my situation, I attempted to let the process run overnight unattended. Is there anyway to do this automated install so that it will simply skip those packages that fail (as the above) without requiring root password authentication intervention, similar to the -y switch on fsck. I realize that such automation is not ideal, but it would be less total time to re-install from DVD in the event that the process resulted in a no-boot or highly unstable system. Thanks for any insight. Yasha Karant
Re: sockets and scientific linux security
On Mon, 8 Apr 2013, Charles Campbell wrote: Hello! I'm pretty sure that I'm running into a security blockade. I have several small example sockets programs which have compiled and worked in the past on other platforms. However, they are not working under SL 6.3, even when I change ports multiple times. I have: * disabled SELINUX (I first tried setenforce 0 as root to make it simply permissive, but no luck, so I disabled it instead) * turned iptables off: /etc/init.d/iptables stop Still, after having done both of these, I can't get a simple socket and client example to work. The /var/log/messages file simply shows my shutting off of iptables. Is there another thing that I can do to get some simple sockets examples to work? I figure once I have located the problems, I can begin to attack the rules needed to get it to work. Regards, and thank you, Chip Campbell What does not work about them? What port numbers are you using? Running as what user? -Connie Sieh
Re: NFS problem on ls command
On Thu, 28 Mar 2013, Evan Sather wrote: --enig2VHUROTADOEVHDNAEQDLT Content-Type: multipart/alternative; boundary=020008050902010202030501 This is a multi-part message in MIME format. --020008050902010202030501 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thank you, Tam! I will keep an eye on the bug report. *Evan Sather* Linux System Administrator High Energy Physics Argonne National Laboratory On 03/28/2013 12:16 PM, Tam Nguyen wrote: We ran into this issue couple of weeks ago. There is a ticket about this bug with the NFS v3+4. Our work around was to mount it with a different version of NFS.=20 https://bugzilla.redhat.com/show_bug.cgi?id=3D736394#c13 is also referenced by http://bugs.centos.org/view.php?id=3D6241. -T On Thu, Mar 28, 2013 at 12:58 PM, Evan Sather esat...@anl.gov mailto:esat...@anl.gov wrote: Hi Everyone, We're experiencing NFS-related problems after viewing home directories on SL6 desktops. SL5 clients do not experience this problem. The NFS server is a SL5 machine. One of our desktops outputs this: [user@host1 ~]$ ls -ltr |tail ls: reading directory .: Invalid argument Another of our desktops outputs this: [user@host2 ~]$ ls -l ls: reading directory .: Too many levels of symbolic links Has anyone else seen this or a similar issue? Does anyone have any suggestions? --=20 *Evan Sather* Linux System Administrator High Energy Physics Argonne National Laboratory And even more info at http://thread.gmane.org/gmane.comp.file-systems.ext4/37022 -Connie Sieh
Re: NFS problem on ls command
On Thu, 28 Mar 2013, Evan Sather wrote: --enig2GQLSDWJADQIIIAUXHNWJ Content-Type: multipart/alternative; boundary=090004020404060409070304 This is a multi-part message in MIME format. --090004020404060409070304 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Everyone, We're experiencing NFS-related problems after viewing home directories on SL6 desktops. SL5 clients do not experience this problem. The NFS server is a SL5 machine. One of our desktops outputs this: [user@host1 ~]$ ls -ltr |tail ls: reading directory .: Invalid argument Another of our desktops outputs this: [user@host2 ~]$ ls -l ls: reading directory .: Too many levels of symbolic links Has anyone else seen this or a similar issue? Does anyone have any suggestions? --=20 *Evan Sather* Linux System Administrator High Energy Physics Argonne National Laboratory Evan, We are trying to pin down which versions of the client software have this issue. We know that the server side changed via a bug fix in SL 5.9 via the 2.6.18-348 kernels. We are trying to figure out a way to predict the issue on the client side. So What kernel version do you have on the server? What arch is the server? What kernel version is on the client? What are the versions of nfs-utils* ? What arch is the client? Thanks -Connie Sieh
Re: automatic updates and compiling vim
On Wed, 13 Feb 2013, Charles Campbell wrote: Hello! My computer at work has been set to do automatic updates, and I generally try to keep my version of vim on the bleeding edge. However, on Feb 1 I was no longer able to compile vim with gui-enabled using gtk, shortly after automatic updates were set up. So far, none of the following has helped me get vim compiling properly: * I removed gtk and re-installed it * I've installed several other gtk related packages Did these come from SL? * I tracked a problem down to a missing glibconfig.h; got one off the net, put it into /usr/include, and now I'm getting a missing typedef for Did you install the rpm that contains glibconfig.h from SL? GSystemThread: || In file included from /usr/include/glib/gasyncqueue.h:34, || from /usr/include/glib.h:34, || from /usr/include/gobject/gtype.h:26, || from /usr/include/gobject/gboxed.h:26, || from /usr/include/glib-object.h:25, || from /usr/include/gio/gioenums.h:30, || from /usr/include/gio/giotypes.h:30, || from /usr/include/gio/gio.h:28, || from /usr/include/gdk/gdkapplaunchcontext.h:30, || from /usr/include/gdk/gdk.h:32, || from /usr/include/gtk/gtk.h:32, || from conftest.c:23: /usr/include/glib/gthread.h|268 error| expected specifier-qualifier-list before 'GSystemThread' /usr/include/glib/gthread.h|336 error| expected ';', ',' or ')' before '*' token /usr/include/glib/gthread.h|337 error| expected ';', ',' or ')' before '*' token /usr/include/glib/gthread.h|338 error| expected ';', ',' or ')' before '*' token There are more issues. It seems that the update messed up glib and gtk. What was the original error ? Any ideas on how to fix this? I can get a motif-enabled gui for vim running, but it doesn't support the Luxi Mono font which I really like. Thank you, Charles Campbell -Connie Sieh
Re: SL 5.9 yum-conf questions.
On Mon, 11 Feb 2013, Franchisseur Robert wrote: Hello, I am a bit confused with yum-conf versus yum-conf-5x which I used to use, by doing : yum -y shell yum-5x with yum-5x containing : erase yum-conf install yum-conf-5x run exit So I have a few questions about that. It seems I cannot remove any more yum-conf as it contains other repos. Isit OK to just disable sl-security.repo andenable sl5x-security.repo ? I also noticed that there is no longer [sl-security-jdk] to disable gpgcheck for jdk, is it normal ? Since we have not included jdk , as it is scheduled for End Of Life in February 2013(now), then we do not need the jdk repos anymore. My previous adobe.repo have been renamed but the new yum-conf-adobe has not been installed and seems to be empty. Thanks for your help. --=20 Best regards, Robert FRANCHISSEUR Apollo_gist :-)___ | Robert FRANCHISSEUR Phone : +33 (0)950 635 636 | | 30 rue Ren=E9 Hamon Phone : +33 (0)1 46 78 37 29 | | F-94800 VILLEJUIFe-mail : Robert at Franchisseur . fr | ---
Scientific Linux SL 5.9 for i386 RC2 is now available for testing
We will release this RC2 as released on Feb 5, 2013 unless we hear about a important issue. Scientific Linux SL 5.9 for i386 Feb 5, 2013 Items marked with a * indicate changes since 5.8 See SL.documentation for Upstream vendor release notes. Send comments/issues/test reports to scientific-linux-de...@fnal.gov -- Table of contents DOWNLOAD INFO ADDED compared to Enterprise 5 UPDATED compared to Enterprise 5 Installer/legal modifications REMOVED compared to Enterprise 5 CHANGED by Upstream Vendor /contrib SRPMS HARDWARE REQUIREMENTS LIMITATIONS INFO ERRATA RPMS that have not built yet _ DOWNLOAD INFO _ http://ftp.scientificlinux.org/linux/scientific/59/i386/ http://ftp1.scientificlinux.org/linux/scientific/59/i386/ ftp://ftp.scientificlinux.org/linux/scientific/59/i386/ - ADDED compared to vendor - 915resolution 915resolution is a tool to modify the video BIOS of the 800 and 900 series Intel graphics chipsets. This includes the 845G, 855G, and 865G chipsets, as well as 915G, 915GM, and 945G chipsets. This modification is necessary to allow the display of certain graphics resolutions for an Xorg or XFree86 graphics server. 915resolution's modifications of the BIOS are transient. There is no risk of permanent modification of the BIOS. This also means that 915resolution must be run every time the computer boots inorder for it's changes to take effect. 915resolution is derived from the tool 855resolution. However, the code differs substantially. 915resolution's code base is much simpler. 915resolution also allows the modification of bits per pixel. 915resolution-0.5.3-6.el5 alpine Alpine is a tool for reading, sending, and managing electronic messages. Alpine is the successor to Pine and was developed by Computing Communications at the University of Washington. Our version of alpine 2.00 has the following changes compared to our 1.0 version An /etc/alpine/pine.conf.sample file is installed, no longer overwriting an existing pine.conf Therefore an existing pine.conf in /etc/alpine will be left untouched even after the upgrade. For an installation from scratch it is advantageous to copy the sample conf file to pine.conf, but alpine works also without it. Users are now able to use a .alpine.passfile This version of alpine when it writes to a large old Unix mailbox format email area can be very slow. The best solution to this is to convert your old Unix mailbox files to mix format mail files. More info can be obtained from Evaluation of file formats: http://mailman2.u.washington.edu/pipermail/alpine-info/2008-July/000971.html Problem description: http://mailman2.u.washington.edu/pipermail/alpine-info/2009-February/thread.html#1658 Conversion : http://www.phwinfo.com/forum/comp-mail-imap/198358-mailutil-mix-file-size.html alpine-2.02-2.el5 AUFS Aufs is a stackable unification filesystem such as Unionfs, which unifies several directories and provides a merged single directory. Aufs is an entirely re-designed and re-implemented Unionfs. aufs-0.20090202.cvs-6.sl5 * kernel-module-aufs-2.6.18-348.el5-0.20090202.cvs-6.sl5.i686.rpm * kernel-module-aufs-2.6.18-348.el5PAE-0.20090202.cvs-6.sl5.i686.rpm * kernel-module-aufs-2.6.18-348.el5xen-0.20090202.cvs-6.sl5.i686.rpm cfitsio CFITSIO is a library of C and FORTRAN subroutines for reading and writing data files in FITS (Flexible Image Transport System) data format. CFITSIO is widely used in the astronomical community. cfitsio-3.100-1.el5 cfitsio-devel-3.100-1.el5 dkms This package contains the framework for the Dynamic Kernel Module Support (DKMS) method for installing module RPMS as originally developed by Dell. * Updated dkms to the latest version from EPEL * dkms-2.2.0.3-1.el5 dropit dropit's intended purpose is to remove directories entries from a PATH shell variable value, which has colon separated fields. dropit is usable in sh, ksh, and csh shell script files. dropit-1.2-1 fftw FFTW is a C
Scientific Linux SL 5.9 for x86_64 RC2 is now available for testing
We will release this RC2 as released on Feb 5, 2013 unless we hear about a important issue. --- Scientific Linux SL 5.9 for x86_64 Feb 5, 2013 Items marked with a * indicate changes since 5.8 See SL.documentation for Upstream vendor release notes. Send comments/issues/test reports to scientific-linux-de...@fnal.gov -- Table of contents DOWNLOAD INFO ADDED compared to Enterprise 5 UPDATED compared to Enterprise 5 Installer/legal modifications REMOVED compared to Enterprise 5 CHANGED by Upstream Vendor /contrib SRPMS HARDWARE REQUIREMENTS LIMITATIONS INFO ERRATA RPMS that have not built yet _ DOWNLOAD INFO _ http://ftp.scientificlinux.org/linux/scientific/59/x86_64/ http://ftp1.scientificlinux.org/linux/scientific/59/x86_64/ ftp://ftp.scientificlinux.org/linux/scientific/59/x86_64/ - ADDED compared to vendor - 915resolution 915resolution is a tool to modify the video BIOS of the 800 and 900 series Intel graphics chipsets. This includes the 845G, 855G, and 865G chipsets, as well as 915G, 915GM, and 945G chipsets. This modification is necessary to allow the display of certain graphics resolutions for an Xorg or XFree86 graphics server. 915resolution's modifications of the BIOS are transient. There is no risk of permanent modification of the BIOS. This also means that 915resolution must be run every time the computer boots inorder for it's changes to take effect. 915resolution is derived from the tool 855resolution. However, the code differs substantially. 915resolution's code base is much simpler. 915resolution also allows the modification of bits per pixel. 915resolution-0.5.3-6.el5 alpine Alpine is a tool for reading, sending, and managing electronic messages. Alpine is the successor to Pine and was developed by Computing Communications at the University of Washington. Our version of alpine 2.00 has the following changes compared to our 1.0 version An /etc/alpine/pine.conf.sample file is installed, no longer overwriting an existing pine.conf Therefore an existing pine.conf in /etc/alpine will be left untouched even after the upgrade. For an installation from scratch it is advantageous to copy the sample conf file to pine.conf, but alpine works also without it. Users are now able to use a .alpine.passfile This version of alpine when it writes to a large old Unix mailbox format email area can be very slow. The best solution to this is to convert your old Unix mailbox files to mix format mail files. More info can be obtained from Evaluation of file formats: http://mailman2.u.washington.edu/pipermail/alpine-info/2008-July/000971.html Problem description: http://mailman2.u.washington.edu/pipermail/alpine-info/2009-February/thread.html#1658 Conversion : http://www.phwinfo.com/forum/comp-mail-imap/198358-mailutil-mix-file-size.html alpine-2.02-2.el5 AUFS Aufs is a stackable unification filesystem such as Unionfs, which unifies several directories and provides a merged single directory. Aufs is an entirely re-designed and re-implemented Unionfs. aufs-0.20090202.cvs-6.sl5 * kernel-module-aufs-2.6.18-348.el5-0.20090202.cvs-6.sl5.x86_64.rpm * kernel-module-aufs-2.6.18-348.el5xen-0.20090202.cvs-6.sl5.x86_64.rpm cfitsio CFITSIO is a library of C and FORTRAN subroutines for reading and writing data files in FITS (Flexible Image Transport System) data format. CFITSIO is widely used in the astronomical community. cfitsio-3.100-1.el5 cfitsio-devel-3.100-1.el5 dkms This package contains the framework for the Dynamic Kernel Module Support (DKMS) method for installing module RPMS as originally developed by Dell. * Updated dkms to the latest version from EPEL * dkms-2.2.0.3-1.el5 dropit dropit's intended purpose is to remove directories entries from a PATH shell variable value, which has colon separated fields. dropit is usable in sh, ksh, and csh shell script files. dropit-1.2-1 fftw FFTW is a C subroutine library for computing the Discrete Fourier Transform
Re: How to add from SL 6x bootable install DVD
On Fri, 18 Jan 2013, Yasha Karant wrote: During the installation process of SL 6x from a bootable installation DVD, there is an opportunity to configure in detail the selection of the actual applications and utilities (packages) that one wants. If for some reason an error is made, in part due to the lack of a confirmation prompt if the install widget is hit, and the system proceeds to install producing a bootable system from the machine local hard drive, is there a way to get back to this section of the install process from a running system (as root) using the same DVD? I do not want to use the add/remove software pull down menu item that seems to require repositories over a network, not from the local machine DVD -- unless the add/remove software GUI utility can be pointed to the boot-able install DVD. I also do not want to re-install from scratch. I typically do use the update process over the network, as well as the GUI add/remove software from repositories -- or yum from a command line -- for specific applications/utilities, but not for the long laundry list during an initial installation. You could use a kickstart file to script the original install. This makes it very easy to reinstall to the original . The kickstart file defines what packages are to be installed. One advantage is that there is no opportunity to click poorly as the whole install is hands off. kickstart will not help you fix up a install it will only help with the original install being very reproducable . -Connie Sieh Yasha Karant
Re: java vulnerability
On Thu, 17 Jan 2013, Ken Teh wrote: What's the status of the java package that's installed on SL6x? java-1.6.0-openjdk. Is it vulnerable to this java security flaw that made the national news this week? Cyber is advising us to remove it but a lot of packages depend on it. The biggie is LibreOffice. I thought that the biggest issue was with Java 7 and not Java 6. -connie Thanks!
Re: java vulnerability
On Thu, 17 Jan 2013, Connie Sieh wrote: On Thu, 17 Jan 2013, Ken Teh wrote: What's the status of the java package that's installed on SL6x? java-1.6.0-openjdk. Is it vulnerable to this java security flaw that made the national news this week? Cyber is advising us to remove it but a lot of packages depend on it. The biggie is LibreOffice. I thought that the biggest issue was with Java 7 and not Java 6. And as Pat said a specific CVE should help answer this. -Connie Sieh -connie Thanks!
Re: java vulnerability
On Thu, 17 Jan 2013, Connie Sieh wrote: On Thu, 17 Jan 2013, Connie Sieh wrote: On Thu, 17 Jan 2013, Ken Teh wrote: What's the status of the java package that's installed on SL6x? java-1.6.0-openjdk. Is it vulnerable to this java security flaw that made the national news this week? Cyber is advising us to remove it but a lot of packages depend on it. The biggie is LibreOffice. I thought that the biggest issue was with Java 7 and not Java 6. And as Pat said a specific CVE should help answer this. Synopsis: Important: java-1.7.0-openjdk security update Issue Date:2013-01-16 CVE Numbers: CVE-2013-0422 CVE-2012-3174 was released yesterday for SL 5 and 6 . -Connie Sieh -Connie Sieh -connie Thanks!
Re: Provide ipa package?
On Fri, 4 Jan 2013, Orion Poplawski wrote: Any chance that SL6 might provide the ipa package? It already has many ipa packages. [root@localhost /]# yum list ipa\* Loaded plugins: refresh-packagekit, security Installed Packages ipa-client.x86_642.2.0-16.el6@sl ipa-python.x86_642.2.0-16.el6@sl Available Packages ipa-admintools.x86_642.2.0-16.el6sl ipa-gothic-fonts.noarch 003.02-4.2.el6 sl ipa-mincho-fonts.noarch 003.02-3.1.el6 sl ipa-pgothic-fonts.noarch 003.02-4.1.el6 sl ipa-pki-ca-theme.noarch 9.0.3-7.el6 sl ipa-pki-common-theme.noarch 9.0.3-7.el6 sl ipa-pmincho-fonts.noarch 003.02-3.1.el6 sl ipa-server.x86_642.2.0-16.el6sl ipa-server-selinux.x86_642.2.0-16.el6sl -Connie Sieh -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 http://www.nwra.com
Re: changes in gcc 3.4 compatibility rpms between SLF5 and 6
On Tue, 11 Dec 2012, Kenneth Herner wrote: Hello, I am attempting to build root 5.28 as part of testing some legacy = software, and for maximum compatibility I would like to use gcc/g++/g77 = 3.4 when building. I've installed all of the appropriate compatibility = rpms on two machines, one running SLF 5.7 and the other 6.3. When I = build on the SLF 5.7 machine everything works fine. When I do the same = thing on the SLF 6.3 machine it works until almost the end, where I get = the following error: g77 -m32 -O2 -o bin/g2root main/src/g2root.o \ -Llib lib/libminicern.so \ /usr/lib/gcc/x86_64-redhat-linux/3.4.6/libfrtbegin.a = /usr/lib/gcc/x86_64-redhat-linux/3.4.6/32/libg2c.so -lnsl -lm -ldl = -pthread -rdynamic /usr/lib/gcc/x86_64-redhat-linux/3.4.6/libfrtbegin.a: could not read = symbols: File in wrong format collect2: ld returned 1 exit status A common reason for the above error is using a 32bit library/archive when a 64 bit one is expected and vice versa. A default install for SL5 installs many i386 packages in addition to the x86_64 packages for a x86_64 install. On SL6 only x86_64 packages are installed. -Connie Sieh make: *** [bin/g2root] Error 1 When I do rpm -qf /usr/lib/gcc/x86_64-redhat-linux/3.4.6/libfrtbegin.a I = get compat-gcc-34-g77-3.4.6-19.el6.x86_64 for SLF6, and compat-gcc-34-g77-3.4.6-4.1.x86_64 for SLF 5.7. Are there any changes in this package that would cause an = error such as the one above? It looks like it's the same version of the = compiler, but something important must have changed between version 4 = and 19. Does anyone have an idea regarding a workaround? Many thanks, Ken=
Re: SL 6 etc. on ARM CPU units
On Mon, 10 Dec 2012, Konstantin Olchanski wrote: On Sat, Dec 08, 2012 at 05:17:06PM -0800, Joseph Areeda wrote: I'm pretty sure there are Debian ports for ARM including RasberryPi. I am more interested in getting the SL userland running on the ARM machines. There is a RHEL 6 rebuild for arm called RedSleeve. http://www.redsleeve.org . -Connie Sieh K.O. Here's an interesting project out of the UK http://www.southampton.ac.uk/~sjc/raspberrypi/ where the guy built a 64 node cluster using Lego for the supports. I'm also sure it was a lot of work like others have mentioned. Perhaps when the upstream providers get the kernel and the drivers going in the Fedora and RedHat branches we'll see SL7 or 8 available for ARM also. Joe On 12/07/2012 11:27 AM, Konstantin Olchanski wrote: Please do not confuse 3 separate issues: 1) Linux userland: this is pretty much universal and will run on any CPU as long as you have a cross-compiler and as long as the autoconf tools do not try too hard to prevent you from cross-compiling the stuff. 2) Linux kernel: is also pretty much universal and assumes very little about the CPU. There *is* some assembly code that needs to be ported when you move between CPUs (say from hypothetical SuperARM to hypothetical HyperARM). I believe current versions of Linux kernel have this support for all existing ARM CPU variations. 3) Linux device drivers: in the PC world devices are standardized around the PCI bus architecture (from the CPU, PCIe looks like PCI, on purpose) and most devices drivers are universal, so if you have a PCI/PCIe based ARM machine with PC-type peripherals (South Bridge, ethernet, video, etc), you are good to go. If you have an ARM machine with strange devices (i.e. the RaspberryPI), you have to wait for the manufacturer to release the specs, then you can write the drivers, then you can run Linux. Rinse, repeat for the next revision of the CPU ASIC (because they moved the registers around or used a slightly different ethernet block). It helps if you have some standardized interfaces, for example on the RaspberryPI you have standard USB, so you can use all supported USB-Wifi adapters right away. 4) boot loader: is different for each type of machine, each type of boot device media. period. (Even on PCs there is no longer any standard standard - some use old-school BIOS booting, others use EFI boot, some need BIOS/ACPI help, some do not). This makes it 4 issues, if you count the first (linux userland) non-issue. K.O. On Fri, Dec 07, 2012 at 01:01:36PM -0600, SLtryer wrote: On 10/23/2012 12:37 PM, Konstantin Olchanski wrote: An ARM platform does not exist. Unlike the PC platform where PC hardware is highly standardized and almost any OS can run on almost any vendor hardware, the ARM platform is more like the early Linux days where instead of 3 video card makers there were 23 of them, all incompatible, all without Linux drivers. If you had the wrong video card, too bad, no soup for you. In the ARM world, there is a zoo of different ARM processors, all incompatible with each other (think as if each Android device had a random CPU - a 16-bit i8086, or a 32-bit i386, or a 64-bit i7 - the variation in capabilities is that high). Then each device contains random i/o chips connected in it's own special way - there is no PCI/PCIe bus where everything is standardized. There are several WiFi chips, several Bluetooth, USB, etc chips. Some have Linux drivers, some do not. As result, there is no generic Linux that will run on every ARM machine. Not to be argumentative, but I always believed that the advantage of *nix* was that it could be ported to numerous platforms, regardless of hardware. You even mention the early Linux days, when there was little or no standardization of PC hardware. Yet, the platform didn't disappear from use simply because there might have been porting issues, most of which were caused more by proprietary secrets and hardware defects than the ever-present fact of diversity of hardware. But one could make the same argument even today: That there are many different CPU platforms, e.g., and that they are not standardized. One example I am thinking of is the Intel v. Amdahl CPU compatibility issue. Even though most of the Linux system will run on either without modification, there are still some unique issues to each of them; from having worked and studied VirtualBox, there are differences in how each manufacturer chose to implement the ring structure that permits virtualization to work as nicely as it does on these platforms. For the most part, they are compatible, but the kernel developers have to be aware of certain implemention issues, including a bug in the Intel CPU platform that requires a VirtualBox workaround (for optimizing the code or something; I forget). And this is in addition to Linux supporting umpteen different processing platforms besides
Re: SC Linux 6.2 Python 2.6 /usr/lib64/python2.6/smtplib.py host/port confusion.
On Fri, 9 Nov 2012, Mick Timony wrote: Hello, I am running Python 2.6.6-29.el6_3.3 on Scientific Linux 6.2.=20 Basically the Python SMTP code opens a socket and passes the host and por= t arguments in the wrong order. There is a related Python bug report but it= looks like the problem may only be fixed in Python 2.7 and 3.2: http://bugs.python.org/issue13163 line number 273 in /usr/lib64/python2.6/smtplib.py opens a socket with th= e following arguments: return socket.create_connection((port, host), timeout) The arguments are in the wrong order and it should be: return socket.create_connection((host, port), timeout) create_connection is defined as def create_connection(address, timeout=3D_GLOBAL_DEFAULT_TIMEOUT): at line number 540 in=20 /usr/lib64/python2.6/socket.py=20 The second line of code in the functions does the following: host, port =3D address Which means that host will be assigned the port value and port will be assigned to the host. Will there be a fix for this for SC 6.2? We only provide patches via TUV. So TUV will have to put a patch in. Do you have example python code that uses smtplib.py and fails? -Connie Sieh Thanks Mick Timony
Distribution and Web server were down earlier today
Earlier today starting at 7:30 am CDT we had a scheduled power outage. The computer center room hosting the following Scientific Linux systems went down and is in the process of service restoration. www.scientificlinux.org ftp.scientificlinux.org ftp1.scientificlinux.org rsync.scientificlinux.org listserv that serves the Scientific Linux mailing lists The whole building is on UPS/Generator. There was a fire sensor which tripped the Emergency Power OFF of the computer room that houses these systems. The computer room is slowing getting back online. Since the listserv system is in this computer room I have not been able to send out a notice of this outage until now. -Connie Sieh
Re: Distribution Servers Downtime - 30 minutes on Oct 18 2012 6:00 CDT
On Tue, 16 Oct 2012, Alan Bartlett wrote: On 16 October 2012 23:42, Connie Sieh cs...@fnal.gov wrote: snip For your local time you can run date -d '2011-10-06 09:00 CDT' Ahem, cough. Might I suggest the more appropriate -- date -d '2012-10-18 06:00 CDT' Alan. That is what happens when you use someone else email and change most of it but not all of it :-) -Connie Sieh
Distribution Servers Downtime - 30 minutes on Oct 18 2012 6:00 CDT
The distribution servers rsync.scientificlinux.org, ftp.scientificlinux.org, ftp1.scientificlinux.org, and ftp2.scientificlinux.org will be going down on: Thursday October 18, 2012 at 06:00am CDT (Chicago) Affected Machines: * rsync.scientificlinux.org * ftp.scientificlinux.org * ftp1.scientificlinux.org * ftp2.scientificlinux.org Why Downtime: Network Services will change network paths on network that has the backing store for the above servers. Begin Downtime: October 18, 2012 at 06:00am CDT (Chicago) End Downtime: October 18, 2012 at 06:30am CDT (Chicago) The downtime is expected to last for less than 30 minutes. For your local time you can run date -d '2011-10-06 09:00 CDT' Thank you for your patience while we perform this maintenance. -Connie Sieh
http://www.scientificlinux.org Server Downtime - 30 minutes on Oct 18 2012 6:00 CDT
The web server http://www.scientificlinux.org will be unavailable on: Thursday October 18, 2012 at 06:00am CDT (Chicago) Affected Machines: * http://www.scientificlinux.org Why Downtime: Network Services will change network paths on network that contains the above server. Begin Downtime: October 18, 2012 at 06:00am CDT (Chicago) End Downtime: October 18, 2012 at 06:30am CDT (Chicago) The downtime is expected to last for less than 30 minutes. For your local time you can run date -d '2011-10-06 09:00 CDT' Thank you for your patience while we perform this maintenance. -Connie Sieh
Re: RedHat Developer Toolset : equivalent for SL 5 or 6?
On Thu, 27 Sep 2012, Jeff McWilliams wrote: The Red Hat Developer Toolset seems to be a more updated version of the gcc compiler, debugger, and binutils, including gcc/g++ 4.7 It appears to be available for both RHEL 5 and RHEL 6 users. Is there an equivalent set of packages available for SL 5 or SL 6? I am working on building them for SL 5 and SL 6. -Connie Sieh Thanks, Jeff
Re: boot,iso and proxy
On Fri, 17 Aug 2012, Andrew Z wrote: --002354790f403afb2304c777aa0b Content-Type: text/plain; charset=ISO-8859-1 Hello, will i be able to install the SL using the network install iso ( http://ftp1.scientificlinux.org/linux/scientific/6x/x86_64/iso/SL-63-x86_64-2012-08-02-boot.iso) if i have to go thru the corporate proxy? I vaguely remember it used to be a problem some time back ( few years ago?).. thank you AZ The install should work via a proxy. -Connie Sieh --002354790f403afb2304c777aa0b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,br=A0will i be able to install the SL using the network install iso= (a href=3Dhttp://ftp1.scientificlinux.org/linux/scientific/6x/x86_64/iso= /SL-63-x86_64-2012-08-02-boot.isohttp://ftp1.scientificlinux.org/linux/sc= ientific/6x/x86_64/iso/SL-63-x86_64-2012-08-02-boot.iso/a) if i have to g= o thru the corporate proxy? br I vaguely remember it used to be a problem some time back ( few years ago?)= ..brthank youbrAZbrbr --002354790f403afb2304c777aa0b--
Re: How to build a custom ISO?
On Thu, 16 Aug 2012, Artifex Maximus wrote: Hello! Is there any recommended way to create a custom ISO installer? I have no X on my SL just pure console. I've read that revisor is old and not supported but pungi is great. I've tried pungi under Fedora 17 for cross build without success (packages were downloaded but some problems with anaconda at building boot image stage). CentOS 6.3 does not have pungi. I think SL does not have pungi as well. So revisor is the only tool for building such images here in SL land? It is what we use to build SL 6 . Revisor is include in the release along with the config files used to build the release. -Connie Sieh Bye, a
Re: Does yum have a changelog or release notes feature?
On Wed, 15 Aug 2012, Nathan wrote: Is there some way to see at least a summary of why a package is being updated? In Gentoo, for example, every updated ebuild has changelog notes summarizing what/why/how the update is different than the previous version, and you can view them by running something like 'emerge --pretend --changelog (some-package)'. Is there anything like that for yum? Specifically, I'm interested in what's changing in minor kernel updates, but it would be nice to find a way to do this with any package so I don't have to rely on Google so much. ~ Nathan I know that you asked about yum but rpm can do it rpm -q --changlog some installed package or rpm -qp --changlog some rpm -Connie Sieh
Re: sl 6.2 can't reboot or shutdown, may something wrong with iptables
On Sat, 11 Aug 2012, Tuan Pengfei wrote: --14dae9340525f877db04c6f82b7b Content-Type: text/plain; charset=ISO-8859-1 I am sorry, i forget to give my system info: Linux localhost.localdomain 2.6.32-220.23.1.el6.x86_64 #1 SMP Mon Jun 18 09:58:09 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux Lenovo g430 This is my first time i use sl. It runs good with rhel 6.0 slackware 13.xx and fedora 1x these years. On Sat, Aug 11, 2012 at 3:07 PM, Tuan Pengfei pengfeit...@gmail.com wrote: Hello everyone, i have something worried me, my new sl 6.2 can't reboot or shutdown, ie. can't run into level 0. The screen prints(as i remmeber ...): stopping iptables: error lldpad can't connect to just like this, so i set iptables and ip6tables service off with What setting are you using in iptables ? cat /etc/sysconfig/iptables -Connie Sieh chkconfig, yet it is resolved. it never happens. But it is not a good solution. Anyone here can provide a reason of this problem and a good solution? Thanks. --14dae9340525f877db04c6f82b7b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I am sorry, i forget to give my system info:brLinux localhost.localdomain= 2.6.32-220.23.1.el6.x86_64 #1 SMP Mon Jun 18 09:58:09 CDT 2012 x86_64 x86_= 64 x86_64 GNU/LinuxbrLenovo g430brThis is my first time i use sl. It ru= ns good with rhel 6.0 slackware 13.xx and fedora 1x these years.br brbrdiv class=3Dgmail_quoteOn Sat, Aug 11, 2012 at 3:07 PM, Tuan Pe= ngfei span dir=3Dltrlt;a href=3Dmailto:pengfeit...@gmail.com; target= =3D_blankpengfeit...@gmail.com/agt;/span wrote:brblockquote clas= s=3Dgmail_quote style=3Dmargin:0 0 0 .8ex;border-left:1px #ccc solid;pad= ding-left:1ex Hello everyone, i have something worried me, my new sl 6.2 can#39;t reboot= or shutdown, ie. can#39;t run into level 0. The screen prints(as i remmeb= er ...):brquot;stopping iptables:br=A0error lldpad can#39;t connect t= o br =A0brquot;brjust like this, so i set iptables and ip6tables servic= e off with chkconfig, yet it is resolved. it never happens. But it is not a= good solution.brAnyone here can provide a reason of this problem and a g= ood solution?br Thanks.br /blockquote/divbr --14dae9340525f877db04c6f82b7b--
Scientific Linux 6.3 i386/x86_64 is now available
Thanks to all who helped test the beta/release candidates. - Release Notes for Scientific Linux 6.3 - Major Differences from SL6.2 Added/Changed: OpenAFS Updated to version 1.6.1-112.sl6 External Repositories for yum The yum-conf-rpmfusion has been added by popular request. End users must verify their own eligibility and license compliance before use. yum-conf-sl6x Updated GPG key list, CERN's key is now listed here too redhat-logos Now provides 'linux-logos' xorg-x11-server Changed to remove TUV's support URL sl-indexhtml Updated Swedish translation by Alexander Lindqvist sl-bookmarks Now includes links to useful non-SL provided resources SL_enable_serialconsole Augeas is now used for setting up the initial configuration The rpm now removes the serial configuration when uninstalled Now uses 'conflict' to ensure only one version installed at a time The end result should be identical to the previous script The old configuration script can be found in the %doc folder /usr/share/SL_enable_serialconsole*/OLDSCRIPT revisor Support has been added for the upstream changes in anaconda. The 'beta' release notice can now be turned on or off depending on your needs. sl-revisor-configs The kickstart files provided have been renamed for simplicity. We've also added a script for making an updated disc, containing all the current published errata Removed: libproxy-mozjs Requires an old version of xulrunner, upstream bug 797779. We have removed it for now, when an updated package is released we expect to build it. If you need this package you can pull it from 6.2 libvirt-qpid Requires an old version of qpid-cpp-client, upstream bug 839006 We have removed it for now, when an updated package is released we expect to build it. If you need this package you can pull it from 6.2 sanlock and tboot Upstream only features these packages on x86_64, previously they were in both arches. If upstream returns support for these in the i686 tree, we expect to package them again. Download http://ftp.scientificlinux.org/linux/scientific/6.3/ ftp://ftp.scientificlinux.org/linux/scientific/6.3/ Iso Download area i686: http://ftp.scientificlinux.org/linux/scientific/6.3/i386/iso/ x86_64: http://ftp.scientificlinux.org/linux/scientific/6.3/x86_64/iso/ -Connie Sieh TEXT/html; name=sl-release-notes-6.3.html: Unrecognized
Re: SL 6.3 alphas/betas/rcs?
On Tue, 24 Jul 2012, Nathan wrote: How can I track the progress of and/or download and test out the alpha/beta/rc versions of 6.3 (or future releases in general)? I've been searching around the web site and can't seem to find anything there. ~ Nathan If we do a ALPHA release(do not always do a alpha) it is announced on the scientific-linux-devel mailing list. Beta 1 and Beta 2 are announced on the scientific-linux-devel mailing list. The Release Candidates are announced on both the scientific-linux-devel and the scientific-linux-users mailing lists. -Connie Sieh
Re: Scientific Linux 6.3 Beta 1 Release now available for testing
On Mon, 23 Jul 2012, Martin Flemming wrote: Hi, Pat ! Yep, everything is going well now ! .. of course :-) Sorry, for troubles, but the error messages wasn't familiar for me .. .. usually it will be call install images didn't match with repository .. i've had to use --delete-option for the rsync of the 6rolling-repo :-) Anyway .. Thanks for the great work cheers Martin On Fri, 20 Jul 2012, Pat Riehecky wrote: I've just fired off a pxe boot using the images from http://ftp.scientificlinux.org/linux/scientific/6rolling/i386/os/images/pxeboot/ http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/os/images/pxeboot/ and I was able to get past the partitioning menu and complete the installation. This is a bit odd. The exception you've listed below is some of the code added in 6.3. Can I have you re-download the pxe initrd.img along and try again? Pat On 07/20/2012 07:59 AM, Martin Flemming wrote: Hi ! Is this right, that a test installation only works with DVD/Networkimages ? i want to install via pxe, but after partitioning, the installations breaks with e.g. anaconda exception report Traceback /tmp/updates/yuminstall.py line 596 in readRepoConfig if not BETANAG and (rawhide in repo.id or development in repo.id and NameError : global name 'BETANAG' is not defined Or is my installation enviroment a buggy ? Thanks cheers Martin On Tue, 17 Jul 2012, Connie Sieh wrote: Since there has been interest in the release of SL 6.3 I am forwarding this testing anouncment which normally only goes to scientific-linux-devel . -Connie Sieh - Scientific Linux 6.3 Beta 1 i386/x86_64July 16, 2012 These are notes of the Alpha/Beta releases for Scientific Linux 6.3 . THIS IS NOT FOR PRODUCTION. This is for testing. Please report back any issues to scientific-linux-de...@listserv.fnal.gov . There should be no expectation that a yum upgrade to SL 6.3 will work. A new install is the recommended method to move from sl6rolling(this alpha release) and the released SL 6.3. Items marked with * are changes from the last release DOWNLOAD INFO DVD: http://ftp.scientificlinux.org/linux/scientific/6rolling/i386/iso http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/iso Network Install Images: http://ftp.scientificlinux.org/linux/scientific/6rolling/i386/images/boot.iso http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/images/boot.iso CHANGES WE MADE SINCE PREVIOUS RELEASE *yum-conf-sl6x-1-2 -Updated GPG key list, CERN's key is now listed here too *redhat-logos-60.0.14-2.sl6.5 -Now provides 'linux-logos' *kmod-openafs-1.6.1-112.sl6.71 *openafs-1.6.1-112.sl6 *openafs-authlibs-1.6.1-112.sl6 *openafs-authlibs-devel-1.6.1-112.sl6 *openafs-client-1.6.1-112.sl6 *openafs-compat-1.6.1-112.sl6 *openafs-devel-1.6.1-112.sl6 *openafs-kernel-source-1.6.1-112.sl6 *openafs-kpasswd-1.6.1-112.sl6 *openafs-krb5-1.6.1-112.sl6 *openafs-plumbing-tools-1.6.1-112.sl6 *openafs-server-1.6.1-112.sl6 -Updated to more current version, this is based on OpenAFS 1.6.1 *sl-indexhtml-6-2.sl6.6 -Updated Swedish translation by Alexander Lindqvist *sl-bookmarks-6-2.sl6 -Now includes links to useful non-SL provided resources *sl-release-6.3-0.rolling -Updated to point at 6rolling *SL_enable_serialconsole-4.1-1.el6 *SL_enable_serialconsole-96-4.1-1.el6 *SL_enable_serialconsole-192-4.1-1.el6 *SL_enable_serialconsole-384-4.1-1.el6 *SL_enable_serialconsole-1152-4.1-1.el6 -added '-r' option to script for removal of the configuration -now removes configuration when uninstalled -Switched to augeas based configuration -The old script can be found in the %doc folder -removed support for non-grub bootloaders as none are available for SL6 -a number of SPEC file changes to make things cleaner -Now uses 'conflict' to ensure only one version installed at a time RPMS ADDED IN THIS RELEASE *rpmfusion-free-release-6-1.noarch.rpm *yum-conf-rpmfusion-6-0.1.noarch.rpm -Simplified access to this repository was requested by the community The 'non-free' repository is not included. It is the responsibility of the end user to verify their compliance with the licensing of the rpms in the rpmfusion repository. MAJOR
Scientific Linux 6.3 Beta 2 i386/x86_64 is now available for testing (fwd)
FYI -Connie Sieh -- Forwarded message -- Date: Mon, 23 Jul 2012 17:08:37 -0500 From: Connie Sieh cs...@fnal.gov To: scientific-linux-de...@fnal.gov Subject: Scientific Linux 6.3 Beta 2 i386/x86_64 is now available for testing Scientific Linux 6.3 Beta 2 i386/x86_64July 23, 2012 These are notes of the Alpha/Beta releases for Scientific Linux 6.3 . THIS IS NOT FOR PRODUCTION. This is for testing. Please report back any issues to scientific-linux-de...@listserv.fnal.gov . There should be no expectation that a yum upgrade to SL 6.3 will work. A new install is the recommended method to move from sl6rolling(this alpha release) and the released SL 6.3. Items marked with * are changes from the last release DOWNLOAD INFO DVD: http://ftp.scientificlinux.org/linux/scientific/6rolling/i386/iso http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/iso Network Install Images: http://ftp.scientificlinux.org/linux/scientific/6rolling/i386/images/boot.iso http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/images/boot.iso CHANGES WE MADE SINCE PREVIOUS RELEASE ITEMS MARKED with a ** are changes since last ALPHA/BETA *yum-conf-sl6x-1-2 - Updated GPG key list, CERN's key is now listed here too *redhat-logos-60.0.14-2.sl6.5 - Now provides 'linux-logos' *kmod-openafs-1.6.1-112.sl6.71 *openafs-1.6.1-112.sl6 *openafs-authlibs-1.6.1-112.sl6 *openafs-authlibs-devel-1.6.1-112.sl6 *openafs-client-1.6.1-112.sl6 *openafs-compat-1.6.1-112.sl6 *openafs-devel-1.6.1-112.sl6 *openafs-kernel-source-1.6.1-112.sl6 *openafs-kpasswd-1.6.1-112.sl6 *openafs-krb5-1.6.1-112.sl6 *openafs-plumbing-tools-1.6.1-112.sl6 *openafs-server-1.6.1-112.sl6 - Updated to more current version, this is based on OpenAFS 1.6.1 *sl-indexhtml-6-2.sl6.6 - Updated Swedish translation by Alexander Lindqvist *sl-bookmarks-6-2.sl6 - Now includes links to useful non-SL provided resources *sl-release-6.3-0.rolling - Updated to point at 6rolling *SL_enable_serialconsole-4.1-1.el6 *SL_enable_serialconsole-96-4.1-1.el6 *SL_enable_serialconsole-192-4.1-1.el6 *SL_enable_serialconsole-384-4.1-1.el6 *SL_enable_serialconsole-1152-4.1-1.el6 - added '-r' option to script for removal of the configuration - now removes configuration when uninstalled - Switched to augeas based configuration - The old script can be found in the %doc folder - removed support for non-grub bootloaders as none are available for SL6 - a number of SPEC file changes to make things cleaner - Now uses 'conflict' to ensure only one version installed at a time **sl-release-notes-6.3-1 - Updated for 6.3 - Added technical release notes from TUV **revisor-2.2-3.sl6_3 - Added support for --final feature that was added in anaconda buildinstall **sl-revisor-configs-1-6.3.3 - Renamed kickstart files for simplicity - Added script for making a disc containing published errata - Updated yuminstall.py to latest release RPMS ADDED IN THIS RELEASE *rpmfusion-free-release-6-1.noarch.rpm *yum-conf-rpmfusion-6-0.1.noarch.rpm - Simplified access to this repository was requested by the community The 'non-free' repository is not included. It is the responsibility of the end user to verify their compliance with the licensing of the rpms in the rpmfusion repository. MAJOR CHANGES TUV MADE *libreoffice - openoffice.org has been replaced with libreoffice. The libreoffice packages 'provide' the right packages to maintain compatibility for kickstart and yum installs. *anaconda - Anaconda now alerts users to the beta status of a release when it is tagged appropriately. Upstream has added this functionality and we are taking advantage of it for the beta cycle. POSSIBLE UPGRADE PROBLEMS *libproxy-mozjs - Requires an old version of xulrunner, upstream bug 797779. We have removed it from SL6.3. When an updated package is released we will build it. If you need this package you can pull it from 6.2 *libvirt-qpid
