From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-143789-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 97E0C13944C
for <garchives@archives.gentoo.org>; Tue, 25 Dec 2012 16:03:26 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id E64CD21C09E;
Tue, 25 Dec 2012 16:03:05 +0000 (UTC)
Received: from mail-ye0-f169.google.com (mail-ye0-f169.google.com [209.85.213.169])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 6FE0821C097
for <gentoo-user@lists.gentoo.org>; Tue, 25 Dec 2012 16:01:24 +0000 (UTC)
Received: by mail-ye0-f169.google.com with SMTP id l13so1346462yen.0
for <gentoo-user@lists.gentoo.org>; Tue, 25 Dec 2012 08:01:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=x-received:message-id:date:from:user-agent:mime-version:to:subject
:references:in-reply-to:x-enigmail-version:content-type
:content-transfer-encoding;
bh=/xzFtm2WHE+p0OnvkuKThu7L6swoSGaMocIOkrnJcDs=;
b=QvVmpkawJKsop+jAWqiudhATzQ++dYQNYudNzvb6AxsVhsIKcrxiXg831gPzg0OIzu
1it4LJAZrhnc1LpfY/CWSjcTDGzP1m/I7su9XhDGuQxEkpbA7qZN78zue7DK2SkQuOCS
Qc4mFj7CKzh0T0q1csIBSQm4Y8pjPtYD6te3wxBMcpDrW2pDxyBnwX5OiLRBA8YtKA1F
E+bfQNImYzMhF6t8bCf7+z9QcICTy5Yc2vWegm15EHUQIVOsQNoESqoX8bJu8BNXidtM
r3to4+YvLZGU1Lh4AHAMrjozKpPLciKwKJID2BhT26pATAYV6oxKD3SA2oo40CFCblHM
gAsQ==
X-Received: by 10.236.59.98 with SMTP id r62mr23217729yhc.130.1356451283603;
Tue, 25 Dec 2012 08:01:23 -0800 (PST)
Received: from [192.168.2.5] (adsl-65-0-94-18.jan.bellsouth.net. [65.0.94.18])
by mx.google.com with ESMTPS id y9sm19326792anh.20.2012.12.25.08.01.21
(version=SSLv3 cipher=OTHER);
Tue, 25 Dec 2012 08:01:22 -0800 (PST)
Message-ID: <50D9CDD0.9020400@gmail.com>
Date: Tue, 25 Dec 2012 10:01:20 -0600
From: Dale <rdalek1967@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0 SeaMonkey/2.14.1
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Anyone switched to eudev yet?
References: <87bodk7lb6.fsf@ist.utl.pt> <20121224085528.56f535ec@khamul.example.com> <50D85167.9060309@gmail.com> <20121224204817.335033c6@khamul.example.com> <50D8B467.4080100@gmail.com> <CAK2H+efOgw=gjMd-7b5ftH9KtgehBXcHRiAm4w1x6p5-vry4uQ@mail.gmail.com> <20121224230413.GL26547@server> <20121224182907.2bf6d3d6@fuchsia.remarqs.net> <20121225020301.GP26547@server> <50D911A6.6070500@gmail.com> <20121225125821.GS26547@server>
In-Reply-To: <20121225125821.GS26547@server>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Archives-Salt: bc112a89-2ebe-4d75-a2f7-015f99e04a24
X-Archives-Hash: c1ac28e98912b6b14721bcf5da4f2419
Bruce Hill wrote:
> On Mon, Dec 24, 2012 at 08:38:30PM -0600, Dale wrote:
>> Bruce Hill wrote:
>>> On Mon, Dec 24, 2012 at 06:29:07PM -0600, »Q« wrote:
>>>> On Mon, 24 Dec 2012 17:04:13 -0600
>>>> Bruce Hill <daddy@happypenguincomputers.com> wrote:
>>>>
>>>>> Gentoo had mkinitrd once upon a time, but it's now in attic.
>>>>> Somewhere, sometime, for some reason, initramfs (inital ram
>>>>> filesystem) became vogue for the Gentoo camp, rather than initrd
>>>>> (initial ram disk image), and mkinitrd got retired.
>>>> Is there Gentoo documentation for creating initramfs without using
>>>> dracut? I could only find documentation for doing it *with* dracut,
>>>> and that procedure required using genkernel. Surely Gentoo must have
>>>> an initramfs guide for non-genkernel users, but I couldn't find one.
>>> Do you understand that initrd.gz and initramfs are *not* the same thing?
>>
>> Don't they sort of *do* the same thing? Different method but still a
>> boot up helper thingy. This is why I started calling them init thingy.
>> There are a few init thingys and I just lump them all together since
>> they sort of serve the same function but in a different way.
>>
>> Feel free to set me straight tho. As long as you don't tell me my
>> system is broken and has not been able to boot for the last 9 years
>> without one of those things. ROFL
>>
>> Dale
> It's explained well here:
>
> http://en.wikipedia.org/wiki/Initrd
>
> There are many things reported by the Gentoo Community, especially by #gentoo
> on FreeNode, such that you would think the entire world is governed that way;
> however, most of it is Just Not True (TM).
>
> You will read in that link that initial ramdisk images (initrd) became popular
> for kitchen sink (distro) kernels, so that "make allmodconfig" kernel images,
> with even more modules added on some distros (Slackware, for one example),
> could boot on virtually anyone's hardware.
>
> That's a basic kernel presupposition -- the binary distros ship a kernel that,
> hopefully, will work on any and all comps. Gentoo, on the other hand, doesn't
> ship a kernel at all, and expects you to build your own. I wasn't on the
> Gentoo ship when genkernel came along, but would suspect it was originally
> written to help those poor souls who were "trying Gentoo" and could not build
> a kernel on their own (since that seems to be the audience using it now).
>
> This thread has wandered so far off track that it isn't coming back. Wish I
> could figure out how to /ignore a thread in Mutt. :(
That is what I thought. It even says they are two different things but
give the same results. So, me calling them init thingys works fine.
"In computing, initrd (initial ramdisk) is a scheme for loading a
temporary root file system into memory in the boot process of the Linux
kernel. initrd and initramfs refer to two different methods of achieving
this. Both are commonly used to make preparations before the real root
file system can be mounted."
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!