Re: [elrepo] How long does kernel release stay in the downloads area?

2012-10-04 Thread Akemi Yagi
On Thu, Oct 4, 2012 at 4:45 AM, Steve Clark scl...@netwolves.com wrote:
 On 10/03/2012 05:57 PM, Antonio Dupont wrote:

 Hello,

 I'm making a build that I will install over and over again and it needs to
 be verified by a 3rd party.

 One of the verification steps is to confirm the location that a piece of
 software was downloaded from.

 How long will a kernel release from El Repo stay in the download area
 (http://elrepo.org/linux/kernel/el6/i386/RPMS/

 kernel-ml-3.5.4-1.el6.elrepo.i686.rpm)?


 It looks like an update replace a previous version and the previous version
 removed.  Is there any place the previous versions are retained?

 Thanks very much for your help in advance.

 Regards,

 Antonio

 Hi Antonio,

 I too would like to see an archive of the kernel-ml kernels.

It will help if we know in what situation older versions of kernel-ml
are desired/needed. As you are all aware, kernel-ml is offered for
testing purposes only. Running it in production may cause security
issues unless it is kept up-to-date.

Technically, we may be able to keep a few versions in the archival
area if requested.

Akemi
___
elrepo mailing list
elrepo@lists.elrepo.org
http://lists.elrepo.org/mailman/listinfo/elrepo


Re: [elrepo] How long does kernel release stay in the downloads area?

2012-10-04 Thread Alan Bartlett
A couple of quick comments from me.

An upstream bug-fix to kernel-ml-3.5.4-1.el6.elrepo, that is
kernel-ml-3.5.5-1.el6.elrepo, is currently in the build-queue and will
be released later today.

The successor to the kernel-ml-3.5.x package,
kernel-ml-3.6.0-1.el6.elrepo is currently being configured, verified,
etc, and, all being well, should be released this week.

Hence the kernel-ml package is one that constantly evolves and
progresses in a forwards direction.

Alan.
___
elrepo mailing list
elrepo@lists.elrepo.org
http://lists.elrepo.org/mailman/listinfo/elrepo


[elrepo] Announcement: EL6 Updated kernel-ml Release [Version 3.5.5-1.el6.elrepo]

2012-10-04 Thread Alan Bartlett
Announcing the release of the kernel-ml-3.5.5-1.el6.elrepo packages
into the EL6 elrepo-kernel repository:

http://elrepo.org/tiki/kernel-ml

The following files are currently syncing to the mirrors:

x86
kernel-ml-3.5.5-1.el6.elrepo.i686.rpm
kernel-ml-devel-3.5.5-1.el6.elrepo.i686.rpm
kernel-ml-doc-3.5.5-1.el6.elrepo.noarch.rpm
kernel-ml-firmware-3.5.5-1.el6.elrepo.noarch.rpm
kernel-ml-headers-3.5.5-1.el6.elrepo.i386.rpm
kernel-ml-NONPAE-3.5.5-1.el6.elrepo.i686.rpm
kernel-ml-NONPAE-devel-3.5.5-1.el6.elrepo.i686.rpm
perf-3.5.5-1.el6.elrepo.i686.rpm

x86_64
kernel-ml-3.5.5-1.el6.elrepo.x86_64.rpm
kernel-ml-devel-3.5.5-1.el6.elrepo.x86_64.rpm
kernel-ml-doc-3.5.5-1.el6.elrepo.noarch.rpm
kernel-ml-firmware-3.5.5-1.el6.elrepo.noarch.rpm
kernel-ml-headers-3.5.5-1.el6.elrepo.x86_64.rpm
perf-3.5.5-1.el6.elrepo.x86_64.rpm

src
kernel-ml-3.5.5-1.el6.elrepo.src.rpm

We provide these kernels for hardware testing in an effort to identify
new/updated drivers which can then be targeted for backporting as kmod
packages. Meanwhile, these kernels may provide interim relief to
people with non-functional hardware. We stress that we consider such
kernels as a last resort for those who are unable to get their
hardware working using the RHEL-6 kernel with supplementary kmod
packages.

These packages are provided As-Is with no implied warranty or
support. Using the kernel-ml may expose your system to security,
performance and/or data corruption issues. Since timely updates may
not be available from the ELRepo Project, the end user has the
ultimate responsibility for deciding whether to continue using the
kernel-ml packages in regular service.

The packages are intentionally named kernel-ml so as not to conflict
with the RHEL-6 kernels and, as such, they may be installed and
updated alongside the regular kernel. The kernel configuration is
based upon a default RHEL-6 configuration with added functionality
enabled as appropriate.

If a bug is found when using these kernels, the end user is encouraged
to report it upstream to the Linux Kernel Bug Tracker [1] and, for our
reference, to the ELRepo bug tracker [2]. By taking such action, the
reporter will be assisting the kernel developers, Red Hat and the Open
Source Community as a whole.

Thank you,

The ELRepo Team.

[1] http://bugzilla.kernel.org/
[2] http://elrepo.org/bugs/
___
elrepo mailing list
elrepo@lists.elrepo.org
http://lists.elrepo.org/mailman/listinfo/elrepo