+++ This bug was initially created as a clone of Bug #47994 +++ > I'd like for BadRAM to be included in the list of kernel patches in package sys-kernel/gentoo-dev-sources . > BadRAM's objective is to allow the use of memory that have a few bad bytes safely by preventing programs from allocating the bad adresses. > More details & patch at the given URL. The steps to do it yourself are the straight-forward: 1) Make up a new, local release of your favorite gentoo-sources; 2) Copy genpatches-*.{base,extras}.tar.bz2 in yout distfiles directory to two files showing your new release number; 3) Download the corresponding patch file from the site above; 4) Rename it following the example; 5) Add the patch file to the base tarball; 6) Make a fresh digest of the new ebuild; 7) Emerge & install the patched gentoo-sources.
Created attachment 148464 [details, diff] BadRAM patch for kernel 2.6.18.1 Already included into genpatches-2.6.18-42.base.tar.bz2
Created attachment 148465 [details, diff] Changes in ChangeLog
Created attachment 148469 [details] Ebuild for BadRAM-patched kernel 2.6.18.1 K_GENPATCHES_VER must be set to the new release number!
Created attachment 148470 [details] Tarball with BadRAM-patch included
Created attachment 148471 [details] Original tarball, only renamed
(In reply to comment #0) For newer kernels, you only have to adapt the version numbers (I personally prefer versions optimized to a given hardware and running stable). As an answer to http://bugs.gentoo.org/show_bug.cgi?id=47994#c1, I would say that the older a machine gets the sooner you could find yourself put back in those old days, when the RAM costed more than the PC itself, especially with originally high-end laptops. And folks, believe me, HD and RAM defects *do* happen!
Created attachment 148473 [details] Original tarball, only renamed Sorry, tarball http://bugs.gentoo.org/attachment.cgi?id=148471 was the wrong one.
no chance - get it accepted upstream *** This bug has been marked as a duplicate of bug 47994 ***
