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 E4ADD13827E for ; Mon, 9 Dec 2013 15:28:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BE730E0BEA; Mon, 9 Dec 2013 15:28:29 +0000 (UTC) Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C8562E0BCA for ; Mon, 9 Dec 2013 15:28:28 +0000 (UTC) Received: by mail-vc0-f181.google.com with SMTP id ks9so3493204vcb.12 for ; Mon, 09 Dec 2013 07:28:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=GagSFj/rRidDy2gQZKgQTSxtYZjhUen0UFM7O9br45U=; b=Ye7Ir5kutwLCSIrjRu45yCo5CQalusL0pxfVru1Skc4+zhnX0CJQo516nZulJwyu8r 9LcegvSTS9EmlC6L3evZhV2S2Fyk13K7WmUivJ70v06nFCiPZJDe43HHrE5MHyrXP0Hh 39i/8TbjqW0xHjupeH21YNQezk4/5JOkqfxQiui0wbJxUq4MBCFSZ2ITXpvypQBm3lx1 V9KMGCRvsj00sEF+mPljuvgVcVYmCil2qfsU97Nr1MCyb3ldc47Qc2oOpeFXAWcwRFaz i8toaYIf33rJRFKyEF1+RBlT+67Lt0rD/jUul8LrErA68c2Y2zXD6KEgtuPam906idQx 2auA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.52.191.98 with SMTP id gx2mr825788vdc.71.1386602907912; Mon, 09 Dec 2013 07:28:27 -0800 (PST) Sender: freemanrich@gmail.com Received: by 10.52.112.99 with HTTP; Mon, 9 Dec 2013 07:28:27 -0800 (PST) In-Reply-To: <52A5D89A.4080506@gentoo.org> References: <20131201102015.GA1219@egeo> <20131202202845.GA8574@linux1> <529CF973.2020008@gentoo.org> <529CFAA1.7080608@gentoo.org> <20131203211130.GA31972@linux1> <52A2B788.3040409@gentoo.org> <20131208222552.GA22567@linux1> <52A5D89A.4080506@gentoo.org> Date: Mon, 9 Dec 2013 10:28:27 -0500 X-Google-Sender-Auth: EQC9WVbRbYNSso7BcAT1czcWXSg Message-ID: Subject: Re: [gentoo-dev] openrc 0.12 - netifrc/newnet mix-up From: Rich Freeman To: gentoo-dev Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 061fb7b3-1ffc-48f8-a075-b3c7e1687d61 X-Archives-Hash: 6dee8fd46912b091f9277aab116bc9af On Mon, Dec 9, 2013 at 9:50 AM, Rick "Zero_Chaos" Farina wrote: > I can honestly say most of the time when setup my arm systems I'm > unpacking the arm stage3 on an amd64 and then booting the arm device > with the base stage3 and fixing things from there. I suppose it is > possible to use qemu to install things, as long as I don't mind > pretending it's 1999 due to the slow emulation speeds... Yeah, I really > don't see an improvement here. It works fine for "I'm an amd64 user and > that's all I'll ever use" but when you start talking about smaller > arches it really starts to become a hassle imho. Ok, now the concern is becoming more clear. You're intending to boot directly to the stage3 and not chroot into it, and so you want the stage3 to be a fully-functional userspace, though you don't actually need it to contain a kernel/bootloader. How do you even log into the stage3? Do we not disable the root password by default? Can you boot off of the minimal install image instead? Not sure if we have one of those for ARM. Actually, any boot image that sets up a network and supports chroot would work fine for your purposes. I do realize that many (all?) ARM platforms don't have a flexible bootloader like x86 typically does - so I'll let you speak to what makes sense here. Following the handbook, the network is established by the boot CD and all you do before chrooting is copy over your resolv.conf. In that environment there is no need to have a networking system pre-installed on the stage3. Oh, and if I'm not mistaken the stage3 is based on the system set which is established by the profile, so if it made sense to keep networking around for ARM that would be an option. Rich