Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Jan 2002 18:29:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Jan 2002 18:29:36 -0500 Received: from sphinx.mythic-beasts.com ([195.82.107.246]:56333 "EHLO sphinx.mythic-beasts.com") by vger.kernel.org with ESMTP id ; Wed, 9 Jan 2002 18:29:31 -0500 Date: Wed, 9 Jan 2002 23:29:29 +0000 (GMT) From: Matthew Kirkwood X-X-Sender: To: "Eric S. Raymond" cc: Subject: Re: initramfs programs (was [RFC] klibc requirements) In-Reply-To: <20020109174637.A1742@thyrsus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 9 Jan 2002, Eric S. Raymond wrote: > > > The underlying problem is that dmidecode needs access to kmem, and I > > > can't assume that the person running my configurator will be root. > > > > But you can "su -c" (also sudo, I suppose). If that person > > doesn't have root, then building a kernel isn't going to do > > them much good. > > We've been over this already. No, the configurator user should *not* > have to su at any point before actual kernel installation. Bad > practice, no doughnut. Why bad practice? Anyway, you can: if [ /proc/ -nt /var/run/dmidecode ]; then echo We need to run some code as root. echo -n Enter root\'s\ su -c 'dmidecode > /var/run/dmidecode' fi Which provides at least a way to have your config tool work without having to bloat the initramfs. Matthew. - 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/