Re: 7.5?
A possible solution -- creating of your own respin and support the parallel branches of packages that you corrected, before fixing them by the TUV. For example, in our SL respin -- NauLinux we supported our own branches of kernel and Evolution (corresponded to upstream updates) about half a year until TUV repaired the bugs which we described in RH bugzilla, just because it was important for our users. 2017-07-12 21:44 GMT+03:00 ToddAndMargo: > Hi All, > > On a previous post, I was asked why I was always asking about releases. > I responded that Red Hat would fix my bugs, but slate them for future > editions. Here is an example: > > https://bugzilla.redhat.com/show_bug.cgi?id=1356288#c14 > > "It's currently planned for 7.5." > > It was reported under 7.2. They have fixed it, but won't > release it until 7.5. > > I do sincerely appreciate them fixing bugs, but the delays involved > are something to behold. > > When I asked them if there was some workaround till them, > there response was: > > "The best way would be to contact your support > representative, who'll then guide you through the > possible options." > > And I clearly stated I was coming from the community. > > The "double edged sword" of EL Linux can be a real pain > in the neck at times: stability by freezing packing > versus aggravation for not fixing bugs in those > frozen packages. EL Linux defeats the purpose of > Kaizen (continual improvement). > > EL Linux is still a good package though, despite its > aggravations. > > -T
Re: Connie Sieh, founder of Scientific Linux, retires from Fermilab
Connie, good luck in new stage of your life! I hope for your help to further development of Scientific Linux. Sincerely, --Oleg 2017-02-25 0:52 GMT+03:00 Bonnie King: > Friends, > > The Scientific Linux team is at once happy and sad to announce Connie Sieh's > retirement after 23 years. Today is her last full-time day at Fermilab. > > Connie Sieh founded the Fermi Linux and Scientific Linux projects and has > worked on them continuously. She has sometimes preferred to toil behind the > scenes and leave public announcements to others, but has always been a > driving force behind the projects. > > The Scientific Linux story started in the late 1990s when Connie's group > explored using commodity PC hardware and Linux as an alternative to > commercial servers with proprietary UNIX operating systems. From the > distributions available at the time, Red Hat Linux was chosen. > > In 1998, Connie announced Fermi Linux at HEPiX, a semi-annual meeting of > High Energy Physics IT staff. Fermi Linux was a customized and re-branded > version of Red Hat Linux with some tweaks for integration with the Fermilab > environment. It also introduced an installer modification called Workgroups, > a framework to customize package sets for use at different sites and for > different purposes. The Workgroups concept lives on today in the form of > Contexts for SL7. > > In October 2003 TUV changed their product model and introduced Red Hat > Enterprise Linux. Enterprise Linux was no longer freely distributed in > binary form, but sources remained available. > > Connie and her colleagues started building from these sources, creating one > of the first Enterprise Linux rebuilds. A preview, dubbed HEPL, was > presented at spring HEPiX 2004. In May 2004, the rebuild was released as > Scientific Linux. The name was chosen to reflect the goals and user base of > the product. > > Our colleagues at CERN collaborated, customizing and using Scientific Linux > as Scientific Linux CERN (SLC). SL became a standard OS for Scientific > Computing in High Energy Physics at Fermilab, CERN and beyond. > > SL is freely available to the general public, and is a popular Enterprise > Linux rebuild. As a result, it has built a community outside of Fermilab and > HEP. > > With gratitude, the Scientific Linux team would like to recognize Connie's > many years of service and her immense contribution to the project she > founded. > > Connie's outstanding technical and non-technical judgement are the > foundation of Scientific Linux. Her legacy will continue to inform the way > we run SL and we hope she'll remain as a collaborator. > > All the best to Connie in her well-earned retirement. She will be dearly > missed! > > -- > Bonnie King > Group Leader > Scientific Linux & Architecture Management > > Fermi National Accelerator Laboratory > www.fnal.gov
Re: many ip addresses seems banned by scientific linux servers
List of SL mirrors: http://www.scientificlinux.org/downloads/sl-mirrors/ 2015-08-03 5:58 GMT+03:00 d tbsky tbs...@gmail.com: 2015-08-03 2:39 GMT+08:00 Stephen John Smoogen smo...@gmail.com: On 2 August 2015 at 09:32, d tbsky tbs...@gmail.com wrote: hi: we notice some ip address can not access scientific linux servers (web or ftp). I don't know why. for example default sl7.repo list content below: baseurl=http://ftp.scientificlinux.org/linux/scientific/$slreleasever/$basearch/os/ http://ftp1.scientificlinux.org/linux/scientific/$slreleasever/$basearch/os/ http://ftp2.scientificlinux.org/linux/scientific/$slreleasever/$basearch/os/ ftp://ftp.scientificlinux.org/linux/scientific/$slreleasever/$basearch/os/ but they resolve to only 1 ip address: 131.225.105.11 so some of our servers can not get yum update working with the default configuration. this happen about a year ago. and it seems more and more ip are banned.. You need to provide what ip address you are trying to reach the server from for anyone to help on this. There could be two reasons for this: The Scientific Linux distribution is sponsored by a United States Department of Energy National Lab, Fermi Laboratory. That does mean that it has to abide by certain restrictions on what countries are allowed to connect to the server (countries like North Korea and some others). Various foreign governments block access to United States government servers for various reasons at various times. This can cause problems for other people if your access 'transits' that countries routers. Not much can be done about this other than trying to find a mirror that is allowed access in the country and then pointing your yum.repos.d/*.repo files to that mirror. -- Stephen J Smoogen. thanks for the information. may I ask whom to contact so I can give him/her the ip addresses? but since these ip may be blocked again in the future, I don't know if the default sl7.repo can list more repository other than 131.225.105.11? thanks again for kindly help!! Regards, tbskyd
Re: xterm and clipboard
Look at man xterm -- for example, by this way: xterm -xrm '*VT100*translations: #override \n Shift Ctrl KeyC: select-end(CLIPBOARD, CUT_BUFFER0) \n Shift Ctrl KeyV: insert-selection(PRIMARY, CUT_BUFFER0)' Shift Ctrl KeyC actually is not need -- mouse selection placed to clipboard atomatcally. Cutting by shiftCtrlX seems irrealizable -- we don't have direct access to terminal buffer and you need realize complex text editors logic for such things. Most simple way for realizing of such functionality -- emacs shell mode with customized keys binding. --Oleg On Sun, Jun 22, 2014 at 8:07 AM, ToddAndMargo toddandma...@zoho.com wrote: On 06/21/2014 01:28 PM, Tom H wrote: On Fri, Jun 20, 2014 at 8:30 PM, ToddAndMargo toddandma...@zoho.com wrote: Anyone know if there is a way to get copy shiftCtrlC, past shiftCtrlV, and cut shiftCtrlX keystrokes into an xterm? Define copy-selection(CLIPBOARD) and insert-selection(CLIPBOARD) in XTerm*VT100.translations in .Xresources. Hi Tom, Is there a way to put it into the command line that calls the xterm? Many thanks, -T
Re: blue griffon current production successfully built
Python 2.7 may be installed from Software Collections 1.0 for SL6: http://listserv.fnal.gov/scripts/wa.exe?A2=ind1309L=scientific-linux-develT=0P=501 On Tue, Oct 15, 2013 at 10:03 PM, Yasha Karant ykar...@csusb.edu wrote: From a terminal application within gnome, my default Python is: [ykarant@jb344 ~]$ python Python 2.6.6 (r266:84292, Feb 21 2013, 19:26:11) [GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2 Type help, copyright, credits or license for more information. despite having to install whatever the BlueGriffon build required. A number of the responses concerning the build of BlueGriffon further underscore the general lack of polymorphism and encapsulation in the Linux environment as distributed. In a proper modern OS environment, an application that requires non-system versions of applications (other than the core libraries required by the OS itself, a more daunting problem) would have only these in the path of both the building steps and during the execution of the built application, preferably still allowing a dynamic rather than a static image of the built application. Yasha Karant On 10/15/2013 12:06 AM, Steven J. Yellin wrote: Python2.7 can be installed in, say, /usr/local/..., while leaving 2.6 (or for SL5, 2.4) as the default version. When you then need to use version 2.7 there may be some pain with libraries, but perhaps not too much to endure. Steven Yellin On Mon, 14 Oct 2013, Nico Kadel-Garcia wrote: I took a look a thte Fedora SRPM's, which unfortunately ended about 3 years ago with a very out of date release. The current release requires Python 2.7, which is begging for pain to install on an SL 6 system. SL 7 should be much more compatible with current releases. On Mon, Oct 14, 2013 at 9:42 PM, Yasha Karant ykar...@csusb.edu wrote: On 10/14/2013 04:20 PM, ToddAndMargo wrote: On 10/14/2013 04:18 PM, Yasha Karant wrote: I now have built from source BlueGriffon for X86-64 SL6x, version 1.7.2.99.20130729, Build 20131013142156, Codename 'Cla-de-Lue' I can provide detailed instructions or just a copy of both the mozconfig file used for the build and the typescript of the building. I have had to add a few RPMs to SL6x from other distributions. There was a query on a different thread (same general topic, but a different subject line) as to why I used a 5x CentOS RPM for one of the dependencies of the build. I could not find a 6x EL version. The application was not a systems application that would overwrite/override other files, and seemed to be constrained with a unique identifier. My experience is that many EL 5 and even EL 4 applications still work with EL 6, as did this. Presumably, if the EL 6 version is available, that too would work. Yasha Karant Do you have a place to download the RPM? I have the full directory as well as the built files -- but the source code did not come with any obvious configuration/script software to build a RPM. Moreover, I do not have the personnel resources to support this application for future updates, although I expect that the steps that I did will work for such updates. I have not built this for the IA-32 platform, only X86-64. Is anyone with an IA-32 SL6x development system willing to repeat the exercise to produce an IA-32 platform version? Can you supply the necessary information to build a RPM as well as properly specify dependencies? Yasha Karant