Hello,
Thanks for reporting this, especially with a solution.
We'll work on getting this fixed.
Thanks
Troy
Yannick Perret wrote:
Hello,
I got some troubles with 'yum' on SL5x 64bit. In some cases (seems to
depend of the order of packages) yum fail to install kernel with a crash
message:
# y
Hello,
In Scientific Linux 5.4 we have updated openafs to version 1.4.11. In
keeping with our OpenAFS strategy, we are going to push this update out
with the first kernel released after the distribution release.
We plan on pushing this openafs update out when we push out the kernel
update.
Hello,
The new security update for SL5 has been built and is currently being
tested. This has an important security fix. But it is also the first
kernel since Update 4 that we plan on pushing out, and as such, we are
being cautious.
We plan on pushing this kernel out on Monday, November 9, 2
November 4, 2009
Scientific Linux 5.4 x86_64 is now officially released and available.
We want to thank everyone who has contributed, tested, and given us
feedback. We say that every time, but we really mean it. Without
everyone's help and testing, this release wouldn't be as good as it is.
There
November 4, 2009
Scientific Linux 5.4 i386 is now officially released and available.
We want to thank everyone who has contributed, tested, and given us
feedback. We say that every time, but we really mean it. Without
everyone's help and testing, this release wouldn't be as good as it is.
There a
Thanks for the help.
> You probably have SL_enable_serialconsole-3.1-4.noarch installed. Try
> removing it,
This solved the problem.
Bill Lutter
Stephan Wiesand wrote:
Hi Troy,
On Nov 4, 2009, at 16:24, Troy Dawson wrote:
Recent RHEL releases?
No, not recent ... all
right. But for SL4 with the latest kernel (-98.0.15), it's just DOS
*if* vm.mmap_min_addr is set to, say, 4096. Which, unfortunately, is
not the default. SL5 with SEL
For what it is worth,
I do have the 50-udev.permissions line as suggested by the other SL response.
I had checked this yesterday before sending email to SL group although I did
not report it.
ttyS*:root:uucp:0660
ON SL4.4
powering on the serial device will switch from root:uucp 0660 to root:roo
Hi Troy,
On Nov 4, 2009, at 16:24, Troy Dawson wrote:
Recent RHEL releases?
No, not recent ... all
right. But for SL4 with the latest kernel (-98.0.15), it's just DOS
*if* vm.mmap_min_addr is set to, say, 4096. Which, unfortunately, is
not the default. SL5 with SELinux *dis*abled is safe
Hi all,
I'd like to know if I can install a Sun fire x4170 machine with SL4.6
or SL5.3.
does anybody know about it?
We are using Sun Fire x4150 machine and there is not a problem, but
x4170 is not tested.
thanks for all.
Juanjo
--
===
On Wed, Nov 4, 2009 at 1:14 AM, Faye Gibbins
wrote:
> Hi,
>
> Any comment from the SL5 distro maintainers on this exploit apparently in
> recent RHEL releases?
The vulnerability has been there for a long time. It has only just
been found by someone who works on the kernel. The finders comments
Recent RHEL releases?
No, not recent ... all
We already have the kernels all built, and are working on the dependencies.
Troy
Faye Gibbins wrote:
Hi,
Any comment from the SL5 distro maintainers on this exploit
apparently in recent RHEL releases?
http://www.theregister.co.uk/2009/11/03/l
Email from Troy yesterday indicated that SL will have this patch available
soon, within the next couple of days.
Steve
On Wed, 4 Nov 2009, Faye Gibbins wrote:
Hi,
Any comment from the SL5 distro maintainers on this exploit apparently in
recent RHEL releases?
http://www.theregister.co.uk/
John Rowe wrote:
On Wed, 2009-11-04 at 11:01 +, Mark Whidby wrote:
John Rowe wrote:
Nov 4 10:36:31 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b
Nov 4 10:36:31 terra kernel: end_request: I/O error, dev sdq, sector 5858973568
Nov 4 10:36:31 terra kernel: printk: 16 messag
On Wed, 2009-11-04 at 11:01 +, Mark Whidby wrote:
> John Rowe wrote:
> >> Nov 4 10:36:31 terra kernel: sd 5:0:0:1: SCSI error: return code =
> >> 0x000b
> >> Nov 4 10:36:31 terra kernel: end_request: I/O error, dev sdq, sector
> >> 5858973568
> >> Nov 4 10:36:31 terra kernel: printk: 1
John Rowe wrote:
Nov 4 10:36:31 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b
Nov 4 10:36:31 terra kernel: end_request: I/O error, dev sdq, sector 5858973568
Nov 4 10:36:31 terra kernel: printk: 16 messages suppressed.
Nov 4 10:36:31 terra kernel: Buffer I/O error on device s
> Nov 4 10:36:31 terra kernel: sd 5:0:0:1: SCSI error: return code = 0x000b
> Nov 4 10:36:31 terra kernel: end_request: I/O error, dev sdq, sector
> 5858973568
> Nov 4 10:36:31 terra kernel: printk: 16 messages suppressed.
> Nov 4 10:36:31 terra kernel: Buffer I/O error on device sdq, logi
Hi,
I'm trying to configure a RAID box with 12 x 1 Tb disks on an SL 5.0 system
running kernel 2.6.18-8.1.8.el5 through this controller:
04:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X
Fusion-MPT Dual Ultra320 SCSI (rev 08)
However, whenever I configure more than 3 of t
Hi,
Any comment from the SL5 distro maintainers on this exploit
apparently in recent RHEL releases?
http://www.theregister.co.uk/2009/11/03/linux_kernel_vulnerability/
Faye
--
-
Faye Gibbins, Computing Officer (Infrastructure Services
19 matches
Mail list logo