[syslinux] [PATCH] 4 Patches for initrd+= and initrdfile= Options

Gert Hulselmans hulselmansgert at gmail.com
Fri Oct 26 13:24:14 PDT 2012


It could be useful that instead of only being able to specify the file
and the path in the initramfs:

  initrdfile=foo@/goes/to/foo

that the initrdfle parameter can also load a text file with:

  initrdfile=<files_to_add_to_initramfs.txt

where the "files_to_add_to_initramfs.txt" file contains entries like:

foo1@/goes/to/foo1
foo2@/goes/to/foo2
foo3@/goes/to/foo3
foo4@/goes/to/foo4

I don't know what the length of the command line is that can be passed
to linux.c32,
but if it is limitted to 4 kiB, like the linux kernel command line, an
approach like this
might be needed when you want to add a rather large list of files to
an initramfs.

- Gert


2012/10/26 Shao Miller <sha0.miller at gmail.com>:
> On 10/26/2012 04:37, Ferenc Wagner wrote:
>>
>> "Shao Miller" <sha0.miller at gmail.com> writes:
>>>
>>> 1. The "initrdfile=" option allows you to specify the target path for the
>>> file that will be encapsulated, using the '@' symbol. Please see commit
>>> messages, way down below.
>>
>> Hi Shao, This is way cool! How do you feel about adding support for
>> recursing into directories?
>
>
> Are you asking about loading an entire directory from the Syslinux boot
> media and passing that directory and its files into Linux' rootfs via the
> initramfs scheme?  If so, while it could be coded, it wouldn't work for
> filesystems that cannot list directory contents, such as PXELINUX' TFTP
> "filesystem."  Is that what you meant?  - Shao
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>



More information about the Syslinux mailing list