[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
initrd support
From: |
Samuel Thibault |
Subject: |
initrd support |
Date: |
Mon, 5 Sep 2011 03:10:50 +0200 |
User-agent: |
Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) |
Hello,
Back again with the initrd support question. There were several
proposals which at least somebody doesn't like:
- introduce ramdisk devices in Mach. Not considered as hurdish, would
need the addition of a device command to release the memory.
- somehow link the ramdisk into ext2fs itself, or a storeio task. This
makes it harder to tinker with the image, since mounting/unmounting it
is not enough any more, one has to relink.
A hybrid solution could be the following:
module --nounzip /boot/initrd.gz '$(initrd-task=data-task-create)'
module /boot/kernel/ext2fs.static ext2fs ... -T typed gunzip:task:${initrd-task}
data-task-create being a script command which creates a task whose only
content is the initrd content, starting at vaddr 0. ext2fs can then peek
the data from the task, and possibly destroy it if e.g. using taskonce:
instead of task:
What do people think about it?
Samuel
- initrd support,
Samuel Thibault <=