Re: Scientific Linux "SL 5.9" for x86_64 RC2 is now available for testing
On Mon, Feb 4, 2013 at 1:49 AM, Connie Sieh wrote: > We will release this RC2 as released on Feb 5, 2013 unless we hear > about a important issue. I'd noticed it showing up in the mirrors. Looks good, I've been testing some of the more interesting published components and am quite happy with it. It is *definitely* time for most of us to be using SL 6.x. for stability and compatibility with modern free or open source components. In fact, I've got some tweaked configurations for the "mock" software builder that are suitable for SL releases. Any suggestions on the best way to get them into the "contrib" packages, as "mock-sl" to augment the CentOS based configurations normally built into "mock"?
Re: Update > kernel panic -
On 2 февраля 2013 15:50:17 Bob Goodwin - Zuni, Virginia, USA wrote: > I did a yum update via ssh on an SL6 server the other day, > noticed that it never indicated complete? Yesterday I began to > have odd problems and after rebooting the server, it wouldn't, > it complains of a kernel panic. Using SL-Live I've installed > another hard drive and transferred file to that, now unless > someone can tell me a better way all I know is to re-install and > start over. That server has been running for a year or more > without a problem, usually it's just there, only shut down in a > power outage and then always restarted without a problem.. > > > box7 Scientific Linux 6.3 I'm using SL5.8 After a short shutdown today the machine came up with kernel panic (can't find root). -- Best regards, Serge A. Salamanka e-mail: salama...@newman.bas-net.by skype: serge.salamanka National Grid Infrastructure for Scientific Research Minsk, Belarus
Re: Update > kernel panic -
On 02/04/2013 08:45 AM, Serge A. Salamanka wrote: On 2 февраля 2013 15:50:17 Bob Goodwin - Zuni, Virginia, USA wrote: I did a yum update via ssh on an SL6 server the other day, noticed that it never indicated complete? Yesterday I began to have odd problems and after rebooting the server, it wouldn't, it complains of a kernel panic. Using SL-Live I've installed another hard drive and transferred file to that, now unless someone can tell me a better way all I know is to re-install and start over. That server has been running for a year or more without a problem, usually it's just there, only shut down in a power outage and then always restarted without a problem.. box7 Scientific Linux 6.3 I'm using SL5.8 After a short shutdown today the machine came up with kernel panic (can't find root). It turned out my kernel panic was self inflicted. Apparently I shut down before an update finished. To add to the confusion the opening screen does not show the alternate kernels you may boot to. Once I figured that out I was able to boot to an earlier version and remove and replace the damaged kernel, all is well now. I did notice that the yum install of the kernel seemed to take longer than usual but it did complete eventually? Bob -- http://www.qrz.com/db/W2BOD box7 Scientific Linux 6.3
Re: Update > kernel panic -
В Пнд, 04/02/2013 в 16:45 +0300, Serge A. Salamanka пишет: > On 2 февраля 2013 15:50:17 Bob Goodwin - Zuni, Virginia, USA wrote: > > I did a yum update via ssh on an SL6 server the other day, > > noticed that it never indicated complete? Yesterday I began to > > have odd problems and after rebooting the server, it wouldn't, > > it complains of a kernel panic. Using SL-Live I've installed > > another hard drive and transferred file to that, now unless > > someone can tell me a better way all I know is to re-install and > > start over. That server has been running for a year or more > > without a problem, usually it's just there, only shut down in a > > power outage and then always restarted without a problem.. > > > > > > box7 Scientific Linux 6.3 > > I'm using SL5.8 > After a short shutdown today the machine came up with kernel panic (can't > find > root). It's may be consequence of file system damaging or grub misconfiguration. But we found & fix some NULL-pointer references in sound subsystem of last 5x kernel updates: http://listserv.fnal.gov/scripts/wa.exe?A2=ind1302&L=scientific-linux-devel&T=0&P=348
Re: Update > kernel panic -
That link gives links to "bug-fixed" packages, but the Bugzilla is still open. Who generated the patches? On Mon, Feb 4, 2013 at 9:33 AM, Oleg Sadov wrote: > В Пнд, 04/02/2013 в 16:45 +0300, Serge A. Salamanka пишет: > > On 2 февраля 2013 15:50:17 Bob Goodwin - Zuni, Virginia, USA wrote: > > > I did a yum update via ssh on an SL6 server the other day, > > > noticed that it never indicated complete? Yesterday I began to > > > have odd problems and after rebooting the server, it wouldn't, > > > it complains of a kernel panic. Using SL-Live I've installed > > > another hard drive and transferred file to that, now unless > > > someone can tell me a better way all I know is to re-install > and > > > start over. That server has been running for a year or more > > > without a problem, usually it's just there, only shut down in a > > > power outage and then always restarted without a problem.. > > > > > > > > > box7 Scientific Linux 6.3 > > > > I'm using SL5.8 > > After a short shutdown today the machine came up with kernel panic > (can't find > > root). > > It's may be consequence of file system damaging or grub > misconfiguration. > > But we found & fix some NULL-pointer references in sound subsystem of > last 5x kernel updates: > > > http://listserv.fnal.gov/scripts/wa.exe?A2=ind1302&L=scientific-linux-devel&T=0&P=348 > -- Thanks, Jamie Duncan @jamieeduncan
Re: Update > kernel panic -
That's our patch around modprobe snd-hda-intel kernel crashing. It placed to RH BugZilla, but is not approved by Red Hat at this time. В Пнд, 04/02/2013 в 10:46 -0500, Jamie Duncan пишет: > That link gives links to "bug-fixed" packages, but the Bugzilla is > still open. Who generated the patches? > > > On Mon, Feb 4, 2013 at 9:33 AM, Oleg Sadov wrote: > В Пнд, 04/02/2013 в 16:45 +0300, Serge A. Salamanka пишет: > > On 2 февраля 2013 15:50:17 Bob Goodwin - Zuni, Virginia, USA > wrote: > > > I did a yum update via ssh on an SL6 server the > other day, > > > noticed that it never indicated complete? > Yesterday I began to > > > have odd problems and after rebooting the server, > it wouldn't, > > > it complains of a kernel panic. Using SL-Live I've > installed > > > another hard drive and transferred file to that, > now unless > > > someone can tell me a better way all I know is to > re-install and > > > start over. That server has been running for a > year or more > > > without a problem, usually it's just there, only > shut down in a > > > power outage and then always restarted without a > problem.. > > > > > > > > > box7 Scientific Linux 6.3 > > > > I'm using SL5.8 > > After a short shutdown today the machine came up with > kernel panic (can't find > > root). > > > It's may be consequence of file system damaging or grub > misconfiguration. > > But we found & fix some NULL-pointer references in sound > subsystem of > last 5x kernel updates: > > > http://listserv.fnal.gov/scripts/wa.exe?A2=ind1302&L=scientific-linux-devel&T=0&P=348 > > > > > -- > Thanks, > > Jamie Duncan > @jamieeduncan > >
Re: Update > kernel panic -
I just wasn't aware that SL split that way. RH hasn't accepted it, which (I'm assuming) means it hasn't been accepted upstream, either. Are these maintained indefinitely if they are rejected for some reason? On Mon, Feb 4, 2013 at 11:33 AM, Oleg Sadov wrote: > That's our patch around modprobe snd-hda-intel kernel crashing. It > placed to RH BugZilla, but is not approved by Red Hat at this time. > > В Пнд, 04/02/2013 в 10:46 -0500, Jamie Duncan пишет: > > That link gives links to "bug-fixed" packages, but the Bugzilla is > > still open. Who generated the patches? > > > > > > On Mon, Feb 4, 2013 at 9:33 AM, Oleg Sadov wrote: > > В Пнд, 04/02/2013 в 16:45 +0300, Serge A. Salamanka пишет: > > > On 2 февраля 2013 15:50:17 Bob Goodwin - Zuni, Virginia, USA > > wrote: > > > > I did a yum update via ssh on an SL6 server the > > other day, > > > > noticed that it never indicated complete? > > Yesterday I began to > > > > have odd problems and after rebooting the server, > > it wouldn't, > > > > it complains of a kernel panic. Using SL-Live I've > > installed > > > > another hard drive and transferred file to that, > > now unless > > > > someone can tell me a better way all I know is to > > re-install and > > > > start over. That server has been running for a > > year or more > > > > without a problem, usually it's just there, only > > shut down in a > > > > power outage and then always restarted without a > > problem.. > > > > > > > > > > > > box7 Scientific Linux 6.3 > > > > > > I'm using SL5.8 > > > After a short shutdown today the machine came up with > > kernel panic (can't find > > > root). > > > > > > It's may be consequence of file system damaging or grub > > misconfiguration. > > > > But we found & fix some NULL-pointer references in sound > > subsystem of > > last 5x kernel updates: > > > > > http://listserv.fnal.gov/scripts/wa.exe?A2=ind1302&L=scientific-linux-devel&T=0&P=348 > > > > > > > > > > -- > > Thanks, > > > > Jamie Duncan > > @jamieeduncan > > > > > -- Thanks, Jamie Duncan @jamieeduncan
Re: Update > kernel panic -
On Feb 4, 2013, at 5:36 PM, Jamie Duncan wrote: > I just wasn't aware that SL split that way. Please check the URL that Oleg provided in his first post. It points to a repository in russia. I don't think this is a SL endorsed patch. Matthias > > RH hasn't accepted it, which (I'm assuming) means it hasn't been accepted > upstream, either. > > Are these maintained indefinitely if they are rejected for some reason? > > > On Mon, Feb 4, 2013 at 11:33 AM, Oleg Sadov wrote: > That's our patch around modprobe snd-hda-intel kernel crashing. It > placed to RH BugZilla, but is not approved by Red Hat at this time. > > В Пнд, 04/02/2013 в 10:46 -0500, Jamie Duncan пишет: > > That link gives links to "bug-fixed" packages, but the Bugzilla is > > still open. Who generated the patches? > > > > > > On Mon, Feb 4, 2013 at 9:33 AM, Oleg Sadov wrote: > > В Пнд, 04/02/2013 в 16:45 +0300, Serge A. Salamanka пишет: > > > On 2 февраля 2013 15:50:17 Bob Goodwin - Zuni, Virginia, USA > > wrote: > > > > I did a yum update via ssh on an SL6 server the > > other day, > > > > noticed that it never indicated complete? > > Yesterday I began to > > > > have odd problems and after rebooting the server, > > it wouldn't, > > > > it complains of a kernel panic. Using SL-Live I've > > installed > > > > another hard drive and transferred file to that, > > now unless > > > > someone can tell me a better way all I know is to > > re-install and > > > > start over. That server has been running for a > > year or more > > > > without a problem, usually it's just there, only > > shut down in a > > > > power outage and then always restarted without a > > problem.. > > > > > > > > > > > > box7 Scientific Linux 6.3 > > > > > > I'm using SL5.8 > > > After a short shutdown today the machine came up with > > kernel panic (can't find > > > root). > > > > > > It's may be consequence of file system damaging or grub > > misconfiguration. > > > > But we found & fix some NULL-pointer references in sound > > subsystem of > > last 5x kernel updates: > > > > > > http://listserv.fnal.gov/scripts/wa.exe?A2=ind1302&L=scientific-linux-devel&T=0&P=348 > > > > > > > > > > -- > > Thanks, > > > > Jamie Duncan > > @jamieeduncan > > > > > > > > -- > Thanks, > > Jamie Duncan > @jamieeduncan > smime.p7s Description: S/MIME cryptographic signature
Re: Update > kernel panic -
Ah. hadn't noticed that. Does SL submit directly to upstream projects, or exclusively to RH? On Mon, Feb 4, 2013 at 12:00 PM, Matthias Schroeder < matthias.schro...@cern.ch> wrote: > > On Feb 4, 2013, at 5:36 PM, Jamie Duncan wrote: > > I just wasn't aware that SL split that way. > > > Please check the URL that Oleg provided in his first post. It points to a > repository in russia. I don't think this is a SL endorsed patch. > > Matthias > > > RH hasn't accepted it, which (I'm assuming) means it hasn't been accepted > upstream, either. > > Are these maintained indefinitely if they are rejected for some reason? > > > On Mon, Feb 4, 2013 at 11:33 AM, Oleg Sadov wrote: > >> That's our patch around modprobe snd-hda-intel kernel crashing. It >> placed to RH BugZilla, but is not approved by Red Hat at this time. >> >> В Пнд, 04/02/2013 в 10:46 -0500, Jamie Duncan пишет: >> > That link gives links to "bug-fixed" packages, but the Bugzilla is >> > still open. Who generated the patches? >> > >> > >> > On Mon, Feb 4, 2013 at 9:33 AM, Oleg Sadov wrote: >> > В Пнд, 04/02/2013 в 16:45 +0300, Serge A. Salamanka пишет: >> > > On 2 февраля 2013 15:50:17 Bob Goodwin - Zuni, Virginia, USA >> > wrote: >> > > > I did a yum update via ssh on an SL6 server the >> > other day, >> > > > noticed that it never indicated complete? >> > Yesterday I began to >> > > > have odd problems and after rebooting the server, >> > it wouldn't, >> > > > it complains of a kernel panic. Using SL-Live I've >> > installed >> > > > another hard drive and transferred file to that, >> > now unless >> > > > someone can tell me a better way all I know is to >> > re-install and >> > > > start over. That server has been running for a >> > year or more >> > > > without a problem, usually it's just there, only >> > shut down in a >> > > > power outage and then always restarted without a >> > problem.. >> > > > >> > > > >> > > > box7 Scientific Linux 6.3 >> > > >> > > I'm using SL5.8 >> > > After a short shutdown today the machine came up with >> > kernel panic (can't find >> > > root). >> > >> > >> > It's may be consequence of file system damaging or grub >> > misconfiguration. >> > >> > But we found & fix some NULL-pointer references in sound >> > subsystem of >> > last 5x kernel updates: >> > >> > >> http://listserv.fnal.gov/scripts/wa.exe?A2=ind1302&L=scientific-linux-devel&T=0&P=348 >> > >> > >> > >> > >> > -- >> > Thanks, >> > >> > Jamie Duncan >> > @jamieeduncan >> > >> > >> > > > > -- > Thanks, > > Jamie Duncan > @jamieeduncan > > > -- Thanks, Jamie Duncan @jamieeduncan
Re: Update > kernel panic -
Exactly! It's not SL split -- currently it's just a test package for concrete problem fix from Linux Ink dev. team reported to RH BZ and placed to testing repository of Scientific Linux Cyrillic Edition project for solution checking by our users with a such problem -- not more, not less. В Пнд, 04/02/2013 в 12:01 -0500, Jamie Duncan пишет: > Ah. hadn't noticed that. > > > > Does SL submit directly to upstream projects, or exclusively to RH? > > > On Mon, Feb 4, 2013 at 12:00 PM, Matthias Schroeder > wrote: > > On Feb 4, 2013, at 5:36 PM, Jamie Duncan > wrote: > > > I just wasn't aware that SL split that way. > > > Please check the URL that Oleg provided in his first post. It > points to a repository in russia. I don't think this is a SL > endorsed patch. > > > Matthias > > > > > > > > RH hasn't accepted it, which (I'm assuming) means it hasn't > > been accepted upstream, either. > > > > > > Are these maintained indefinitely if they are rejected for > > some reason? > > > > > > On Mon, Feb 4, 2013 at 11:33 AM, Oleg Sadov > > wrote: > > That's our patch around modprobe snd-hda-intel > > kernel crashing. It > > placed to RH BugZilla, but is not approved by Red > > Hat at this time. > > > > В Пнд, 04/02/2013 в 10:46 -0500, Jamie Duncan пишет: > > > That link gives links to "bug-fixed" packages, but > > the Bugzilla is > > > still open. Who generated the patches? > > > > > > > > > On Mon, Feb 4, 2013 at 9:33 AM, Oleg Sadov > > wrote: > > > В Пнд, 04/02/2013 в 16:45 +0300, Serge A. > > Salamanka пишет: > > > > On 2 февраля 2013 15:50:17 Bob Goodwin - > > Zuni, Virginia, USA > > > wrote: > > > > > I did a yum update via ssh on > > an SL6 server the > > > other day, > > > > > noticed that it never > > indicated complete? > > > Yesterday I began to > > > > > have odd problems and after > > rebooting the server, > > > it wouldn't, > > > > > it complains of a kernel > > panic. Using SL-Live I've > > > installed > > > > > another hard drive and > > transferred file to that, > > > now unless > > > > > someone can tell me a better > > way all I know is to > > > re-install and > > > > > start over. That server has > > been running for a > > > year or more > > > > > without a problem, usually > > it's just there, only > > > shut down in a > > > > > power outage and then always > > restarted without a > > > problem.. > > > > > > > > > > > > > > > box7 Scientific Linux 6.3 > > > > > > > > I'm using SL5.8 > > > > After a short shutdown today the > > machine came up with > > > kernel panic (can't find > > > > root). > > > > > > > > > It's may be consequence of file system > > damaging or grub > > > misconfiguration. > > > > > > But we found & fix some NULL-pointer > > references in sound > > > subsystem of > > > last 5x kernel updates: > > > > > > > > > http://listserv.fnal.gov/scripts/wa.exe?A2=ind1302&L=scientific-linux-devel&T=0&P=348 > > > > > > > > > > > > > > > -- > > > Thanks, > > > > > > Jamie Duncan > > > @jamieeduncan > > > > > > > > > > > > > > > > > > -- > > Thanks, > > > > Jamie Duncan > > @jamieeduncan >
lynx browser in SL6.3
Is anybody else out there trying to use lynx in SL6.3? When I bring it up, the text for url links comes up as yellow on a white background, and is pretty much invisible. This wasn't the case in SL5.5. I know how to fix the problem for my own use, but lynx shouldn't come up unusable by default. Before I try reporting it as a bug to the packagers, I want to be sure it happens to other people too, and isn't due to some idiosyncracy of my own setup. Anyone? Stephen Isard
Re: lynx browser in SL6.3
Change your terminal settings.The background color is the default background color of your terminal.It sucks if you are on a default white background xterm but works well if you are on a black background terminal.that you are experiencing is a software color philosophy difference. I personally hate white backgrounds because they hurt my eyes over time but the default color coded scheme for the terminal is impossible to read with a black background. In addition every admin I've ever worked with and the hundreds of people I've talked with in user groups who don't run X11 on their servers hate it too. Do what every one else does change it to your liking and deploy the changes to all if your hosts.-- Sent from my HP Pre3On Feb 4, 2013 3:18 PM, Stephen Isard <7p03xy...@sneakemail.com> wrote: Is anybody else out there trying to use lynx in SL6.3? When I bring it up, the text for url links comes up as yellow on a white background, and is pretty much invisible. This wasn't the case in SL5.5. I know how to fix the problem for my own use, but lynx shouldn't come up unusable by default. Before I try reporting it as a bug to the packagers, I want to be sure it happens to other people too, and isn't due to some idiosyncracy of my own setup. Anyone? Stephen Isard
Re: lynx browser in SL6.3
On 02/05/2013 01:05 PM, Paul Robert Marino wrote: On Feb 4, 2013 3:18 PM, Stephen Isard <7p03xy...@sneakemail.com> wrote: Is anybody else out there trying to use lynx in SL6.3? When I bring it up, the text for url links comes up as yellow on a white background, and is pretty much invisible. This wasn't the case in SL5.5. I know how to fix the problem for my own use, but lynx shouldn't come up unusable by default. Before I try reporting it as a bug to the packagers, I want to be sure it happens to other people too, and isn't due to some idiosyncracy of my own setup. Anyone? Change your terminal settings. The background color is the default background color of your terminal. It sucks if you are on a default white background xterm but works well if you are on a black background terminal. that you are experiencing is a software color philosophy difference. I personally hate white backgrounds because they hurt my eyes over time but the default color coded scheme for the terminal is impossible to read with a black background. In addition every admin I've ever worked with and the hundreds of people I've talked with in user groups who don't run X11 on their servers hate it too. Do what every one else does change it to your liking and deploy the changes to all if your hosts. The default Lynx color scheme is designed for a dark background. Since at least the mid 90's people have been complaining about that on the Lynx dev list. Those users are invariably users of an X-based window manager that has a windowed terminal program that defaults to a light background. This idea has always been rejected. Making Lynx friendly to terminal emulators at the expense of breaking Lynx in its primary use case (runlevels 1-3) is unacceptable. In particular, system administrators trying to get X (or anything else) back up need Lynx to work correctly on a dark background, because that's all they've got to work with in many cases. Setting the X terminal emulators to actually emulate the way real terminals work, on the other hand, sounds like a good idea (to me). I don't know anyone who leaves terminal programs with the default light background scheme, but maybe some do. Anyway, that can be considered a distro-level issue since a distro could decide to set their own defaults for Gnome Terminal and Kterm instead of just going along with the embedded X aversion to dark backgrounds. (In the early 80's "dark" meant "old fashioned", so it wasn't politically acceptable within that particular dev tribe. Today I don't think anyone cares.)
