1 |
On Mon, Dec 24, 2012 at 08:38:30PM -0600, Dale wrote: |
2 |
> Bruce Hill wrote: |
3 |
> > On Mon, Dec 24, 2012 at 06:29:07PM -0600, »Q« wrote: |
4 |
> >> On Mon, 24 Dec 2012 17:04:13 -0600 |
5 |
> >> Bruce Hill <daddy@×××××××××××××××××××××.com> wrote: |
6 |
> >> |
7 |
> >>> Gentoo had mkinitrd once upon a time, but it's now in attic. |
8 |
> >>> Somewhere, sometime, for some reason, initramfs (inital ram |
9 |
> >>> filesystem) became vogue for the Gentoo camp, rather than initrd |
10 |
> >>> (initial ram disk image), and mkinitrd got retired. |
11 |
> >> Is there Gentoo documentation for creating initramfs without using |
12 |
> >> dracut? I could only find documentation for doing it *with* dracut, |
13 |
> >> and that procedure required using genkernel. Surely Gentoo must have |
14 |
> >> an initramfs guide for non-genkernel users, but I couldn't find one. |
15 |
> > Do you understand that initrd.gz and initramfs are *not* the same thing? |
16 |
> |
17 |
> |
18 |
> Don't they sort of *do* the same thing? Different method but still a |
19 |
> boot up helper thingy. This is why I started calling them init thingy. |
20 |
> There are a few init thingys and I just lump them all together since |
21 |
> they sort of serve the same function but in a different way. |
22 |
> |
23 |
> Feel free to set me straight tho. As long as you don't tell me my |
24 |
> system is broken and has not been able to boot for the last 9 years |
25 |
> without one of those things. ROFL |
26 |
> |
27 |
> Dale |
28 |
|
29 |
It's explained well here: |
30 |
|
31 |
http://en.wikipedia.org/wiki/Initrd |
32 |
|
33 |
There are many things reported by the Gentoo Community, especially by #gentoo |
34 |
on FreeNode, such that you would think the entire world is governed that way; |
35 |
however, most of it is Just Not True (TM). |
36 |
|
37 |
You will read in that link that initial ramdisk images (initrd) became popular |
38 |
for kitchen sink (distro) kernels, so that "make allmodconfig" kernel images, |
39 |
with even more modules added on some distros (Slackware, for one example), |
40 |
could boot on virtually anyone's hardware. |
41 |
|
42 |
That's a basic kernel presupposition -- the binary distros ship a kernel that, |
43 |
hopefully, will work on any and all comps. Gentoo, on the other hand, doesn't |
44 |
ship a kernel at all, and expects you to build your own. I wasn't on the |
45 |
Gentoo ship when genkernel came along, but would suspect it was originally |
46 |
written to help those poor souls who were "trying Gentoo" and could not build |
47 |
a kernel on their own (since that seems to be the audience using it now). |
48 |
|
49 |
This thread has wandered so far off track that it isn't coming back. Wish I |
50 |
could figure out how to /ignore a thread in Mutt. :( |
51 |
-- |
52 |
Happy Penguin Computers >') |
53 |
126 Fenco Drive ( \ |
54 |
Tupelo, MS 38801 ^^ |
55 |
support@×××××××××××××××××××××.com |
56 |
662-269-2706 662-205-6424 |
57 |
http://happypenguincomputers.com/ |
58 |
|
59 |
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting |