Linux MIPS Architecture development
 help / color / mirror / Atom feed
* initrd support.
@ 2005-01-14  9:17 moreau francis
  2005-01-14 15:41 ` Thiemo Seufer
  0 siblings, 1 reply; 4+ messages in thread
From: moreau francis @ 2005-01-14  9:17 UTC (permalink / raw)
  To: linux-mips

Hi,

I'm going to use initrd to mount my root fs, but I was
wondering what its status...
I have noticed in boot directory addinitrd program
that seems to add an initrd image right after the
kernel.
But there's also a section in kernel/vmlinux.lds.S
called
.initrd that includes initrd image during kernel 
compilation.

Why are there two different ways of using initrd ?
Which one I should use ?

Thanks for your answers.

Francis.


	

	
		
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: initrd support.
  2005-01-14  9:17 initrd support moreau francis
@ 2005-01-14 15:41 ` Thiemo Seufer
  2005-01-14 17:30   ` moreau francis
  2005-01-15  2:04   ` Kumba
  0 siblings, 2 replies; 4+ messages in thread
From: Thiemo Seufer @ 2005-01-14 15:41 UTC (permalink / raw)
  To: moreau francis; +Cc: linux-mips

moreau francis wrote:
> Hi,
> 
> I'm going to use initrd to mount my root fs, but I was
> wondering what its status...
> I have noticed in boot directory addinitrd program
> that seems to add an initrd image right after the
> kernel.
> But there's also a section in kernel/vmlinux.lds.S
> called
> .initrd that includes initrd image during kernel 
> compilation.
> 
> Why are there two different ways of using initrd ?

Actually, there are three:
- the generic initramfs method for compiled in initrds
- the addinitrd method to attach a initrd to a precompiled kernel
  image (which is old, and essentially unmaintained)
- the rd_start/rd_size method, which allows a bootloader to load both
  kernel and initrd images into memory and then tells the kernel via
  the rd_start/rd_size parameters where the initrd is located

> Which one I should use ?

Depends on your machine/bootloader and how much flexibility you want.


Thiemo

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: initrd support.
  2005-01-14 15:41 ` Thiemo Seufer
@ 2005-01-14 17:30   ` moreau francis
  2005-01-15  2:04   ` Kumba
  1 sibling, 0 replies; 4+ messages in thread
From: moreau francis @ 2005-01-14 17:30 UTC (permalink / raw)
  To: Thiemo Seufer; +Cc: linux-mips

 --- Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
a écrit : 
> Actually, there are three:
> - the generic initramfs method for compiled in
> initrds
what's the difference with the rd_start/rd_size method
?

> - the addinitrd method to attach a initrd to a
> precompiled kernel
>   image (which is old, and essentially unmaintained)
why is it still in kernel's tree ? Is it going to be
removed ?

> - the rd_start/rd_size method, which allows a
> bootloader to load both
>   kernel and initrd images into memory and then
> tells the kernel via
>   the rd_start/rd_size parameters where the initrd
> is located
Why do I need to provide rd_start/ rd_size setup
parameters ? It's already provided by vmlinux.lds.S.

thanks,

Francis.



	

	
		
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: initrd support.
  2005-01-14 15:41 ` Thiemo Seufer
  2005-01-14 17:30   ` moreau francis
@ 2005-01-15  2:04   ` Kumba
  1 sibling, 0 replies; 4+ messages in thread
From: Kumba @ 2005-01-15  2:04 UTC (permalink / raw)
  To: linux-mips; +Cc: moreau francis

Thiemo Seufer wrote:
> 
> Actually, there are three:
> - the generic initramfs method for compiled in initrds

Is there any docs for this floating around outside of the blurb on the LMO wiki?

Doing a few tests with this, I was unable to get a kernel to see the ramdisk. 
  Despite there being an initramfs built into the kernel, there were no 
"RAMDISK: Compressed ramdisk found at block 0" messages, or no "checking if 
image is initramfs...it isn't (no cpio magic); looks like an initrd" messages 
that I've commonly seen with built-in ramdisks.

I figure in the end, either the problem is PEBKAC, invalid kernel command line 
params (root=/dev/ram0?), or broken code.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: small 
hands do them because they must, while the eyes of the great are elsewhere." 
--Elrond

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-01-15  1:59 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-01-14  9:17 initrd support moreau francis
2005-01-14 15:41 ` Thiemo Seufer
2005-01-14 17:30   ` moreau francis
2005-01-15  2:04   ` Kumba

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox