From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 7F4641381F3 for ; Mon, 26 Nov 2012 01:24:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9579A21C040; Mon, 26 Nov 2012 01:24:27 +0000 (UTC) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.182]) by pigeon.gentoo.org (Postfix) with ESMTP id C5AC521C02A for ; Mon, 26 Nov 2012 01:23:16 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgsKAG6Zu0/O+LLF/2dsb2JhbABEsnYDgRiBCIIWAQU6HDMLEiISFCUQJ4gOC6V5lAEEiwhahABiA4hChHyHXIVfiDqBWIMH X-IronPort-AV: E=Sophos;i="4.75,637,1330923600"; d="scan'208";a="208466346" Received: from 206-248-178-197.dsl.teksavvy.com (HELO waltdnes.org) ([206.248.178.197]) by ironport2-out.teksavvy.com with SMTP; 25 Nov 2012 20:23:15 -0500 Received: by waltdnes.org (sSMTP sendmail emulation); Sun, 25 Nov 2012 20:23:08 -0500 From: "Walter Dnes" Date: Sun, 25 Nov 2012 20:23:08 -0500 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] easy Gentoo tricks Message-ID: <20121126012307.GA19556@waltdnes.org> References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 1104efce-c6c2-4f04-93b8-a93f6ca2cbde X-Archives-Hash: 20e6d369b87cba772462d1026f206f43 On Sun, Nov 25, 2012 at 01:53:22PM -0800, Grant wrote > What are your favorite easy Gentoo tricks? Stuff that makes your system a > lot better in some way with only a minimal amount of effort. I just > discovered one for xfce4: > > emerge tumbler > > No other config. Really cool result. In general, emerging an add-on for an environment will pull in the environment as a dependancy. Similar to your setup, back when I used blackbox, emerging bbkeys would pull in blackbox as a dependancy. My setup takes a little a little setting up, but saves a lot of work when setting up a new kernel. I run with 2 kernels available... 1) Production 2) Experimental Sometimes they're identical. Here's a simplified version of my /etc/lilo.conf with the comment lines stripped out ######################################################## lba32 boot = /dev/sda map = /boot/.map install = /boot/boot-menu.b menu-scheme=Wb prompt timeout=150 delay = 50 image = /boot/kernel-3.0-production root = /dev/sda5 label = Production read-only # read-only for checking append = "noexec32=on" image = /boot/kernel-3.0-experimental root = /dev/sda5 label = Experimental read-only # read-only for checking append = "noexec32=on" ######################################################## This gives me a boot menu with "Production" and "Experimental" kernels to boot from. There are also 2 small scripts... /usr/src/makeover ***IMPORTANT*** The arch/x86 directory is specific to 32-bit i686 kernels. Adjust accordingly if you use a different architecture. ######################################################## #!/bin/bash make && \ make modules_install && \ cp arch/x86/boot/bzImage /boot/kernel-3.0-experimental && \ cp System.map /boot/System.map-3.0-experimental && \ cp .config /boot/config-3.0-experimental && \ lilo ######################################################## /usr/src/promote ######################################################## #!/bin/bash cp /boot/System.map-3.0-experimental /boot/System.map-3.0-production cp /boot/config-3.0-experimental /boot/config-3.0-production cp /boot/kernel-3.0-experimental /boot/kernel-3.0-production lilo ######################################################## I build a new kernel by running "../makeover" from /usr/src/linux. It does the make and overwrites the previous "Experimental" kernel, and runs lilo. It does not touch "Production". After the "Experimental" kernel has been running trouble-free for a while, I promote it to "Production", by running "../promote" from /usr/src/linux. This copies the experimental kernel over the production kernel. At this point, they are identical. Having a previous working kernel to fall back to has saved me on a few occasions. Note; on a brand new install, lilo will come back with an error on the very first run of ../makeover, because there is no Production kernel found. The first time you run ../makeover, run ../promote immediately afterwards. This copies the Experimental kernel to Production, and satisfies lilo. -- Walter Dnes We are apparently better off trying to avoid udev like the plague. Linus Torvalds; 2012/10/03 https://lkml.org/lkml/2012/10/3/349