From: Richard <richard_siegfried@systemli.org>
To: kernelnewbies@kernelnewbies.org
Subject: Re: How is the size of init ram disk determined when initramfs is used?
Date: Sun, 1 Jan 2023 17:54:52 +0100 [thread overview]
Message-ID: <bd8b8232-d0ed-b8ba-baff-35937d1365b1@systemli.org> (raw)
In-Reply-To: <072001d8d9f5$0fb3dbd0$2f1b9370$@etri.re.kr>
Hi,
I don't exactly how and where the size is determined, but
On 07/10/2022 04:32, Chan Kim wrote:
> Hello all,
>
> I'm using initramfs.cpio.gz for initial file system image.
> I embed it in the kernel Image file.
> After linux boots, when I'm in the shell, I can create files.
> But I'm curious how much the file system can grow.
> I remember somewhere reading that the initramdisk is made and the initramfs
> archive is extracted in the ramdisk.
> Then how is the ramdisk size determined? During the build usig Kconfig
this is extremly unlikely. For example when you do "apt upgrade" on
debian and there gets a new kernel installed (or I think even when it is
only about specific new kernel modules), sometimes a new initramfs is
built. This includes (as far as I know) also some modules and
configuration specific to your computer. This way they can ship a
generic kernel but it still works custom for you since the initramfs is
custom.
This customization means the intitramfs' size will vary. But since the
kernel is built independently and beforehand it can not know that size.
Also, why should the filesize be that important? Can't it just be stored
in some file header when it's generated ? Maybe I'm missing something here
-- Richard
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2023-01-01 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 2:32 How is the size of init ram disk determined when initramfs is used? Chan Kim
2023-01-01 16:54 ` Richard [this message]
2023-01-01 17:32 ` Bernd Petrovitsch
2023-01-01 19:23 ` Nicholas Mc Guire
2023-01-02 2:37 ` Chan Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd8b8232-d0ed-b8ba-baff-35937d1365b1@systemli.org \
--to=richard_siegfried@systemli.org \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).