Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 16 Jul 2002 04:22:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 16 Jul 2002 04:22:47 -0400 Received: from pop.gmx.de ([213.165.64.20]:25540 "HELO mail.gmx.net") by vger.kernel.org with SMTP id ; Tue, 16 Jul 2002 04:22:47 -0400 Message-ID: <002c01c22ca2$bb80a6d0$1c6fa8c0@hyper> From: "Christian Ludwig" To: "Tom Oehser" Cc: "Daniel Phillips" , "Ville Herva" , "Linux Kernel Mailinglist" References: Subject: [PATCH] bzip2 compression for kernel 2.4 and ramdisk Date: Tue, 16 Jul 2002 10:28:15 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1678 Lines: 39 Hi, I have released the new version 1.4 of the bzip2 support patch. You can find it at http://chrissicool.piranho.com/linux (sorry for the ads.) This patch consists actually of two independant parts, which do _not_ belong together in any case. The only reason why they cannot be split up is that both are using the same decompression code for bzip2 at the same location. The two parts are: 1. A kernel bzip2 compression support patch. The kernel will be compressed with bzip2, if you choose the appropriate option in the "General options" menu of the kernel configuration. Choosing gzip compression is still possible. You can also choose the compression level in nine steps, from very poor compression (level 1), which is not very memory and speed intensive. A very strong compression (level 9) makes the bzImage smaller, but uses a large amount of RAM for decompression and takes longer. This part is architecture dependent and was implemented for i386 based PCs. 2. A ramdisk bzip2 compression support patch. You can enable gzip or bzip2 compression (or even both) for the ramdisk in the kernel configuration. The ramdisk driver will test the image, which should be loaded. If it recognises a valid (and supported) ramdisk image, it will load and decompress it. The ramdisk compression is optional. You even can turn off compressed ramdisk support at all. If you find bugs, please mail me. Have fun. - Christian Ludwig - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/