2011/9/5 Samuel Thibault
> 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 o
On Mon, Sep 5, 2011 at 3:10 AM, Samuel Thibault wrote:
> 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}
>
> (...)
> What do people think about it?
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 e
olafbuddenha...@gmx.net, le Mon 09 Aug 2010 22:57:32 +0200, a écrit :
> > If I remember correctly they're actually kindof related, because I needed
> > those
> > for the ramdisk message to be displayed correctly.
>
> In that case, you should make an extra patch, and make it part of a
> patch seri
Hi,
On Tue, Aug 03, 2010 at 07:16:25PM -0400, Jeremie Koenig wrote:
> On Sat, Jul 31, 2010 at 04:49:08PM +0200, Samuel Thibault wrote:
> > Jérémie Koenig, le Sat 12 Jun 2010 19:05:20 +0200, a écrit :
> > > @@ -128,7 +129,7 @@
> > > }
> > >else
> > > {
> > > - int i, losers, max
Hi,
On Sat, Jul 31, 2010 at 04:49:08PM +0200, Samuel Thibault wrote:
> Jérémie Koenig, le Sat 12 Jun 2010 19:05:20 +0200, a écrit :
> > @@ -128,7 +129,7 @@
> > }
> >else
> > {
> > - int i, losers, maxlen;
> > + int i, losers;
> >
> >/* Initialize boot script varia
Jérémie Koenig, le Sat 12 Jun 2010 19:05:20 +0200, a écrit :
> @@ -128,7 +129,7 @@
> }
>else
> {
> - int i, losers, maxlen;
> + int i, losers;
>
>/* Initialize boot script variables. We leak these send rights. */
>losers = boot_script_set_variable
> @@ -2
this in my thesis
report.)
The initrd support we are talking about here is *only* for the
Debian-Installer -- not because we consider it a superior solution, but
simply to keep the changes minimal...
-antrik-
Hi,
On Mon, Jun 14, 2010 at 10:31:00AM +0200, Samuel Thibault wrote:
> olafbuddenha...@gmx.net, le Mon 14 Jun 2010 09:00:05 +0200, a écrit :
> > > or that modifying Mach for this purpose is misguided and should be
> > > avoided (for instance by embedding the initrd in a dedicated
> > > section of
Da Zheng, le Mon 14 Jun 2010 17:27:12 +0800, a écrit :
> On 10-6-14 下午3:00, olafbuddenha...@gmx.net wrote:
> > Also, having the initrd implementation in a userspace process will
> > require some changes in the bootstrap process... OTOH, these will be
> > necessary for userspace drivers anyways.
> I
On 10-6-14 下午3:00, olafbuddenha...@gmx.net wrote:
>> or that modifying Mach for this purpose is misguided and should be
>> avoided (for instance by embedding the initrd in a dedicated section
>> of an elf module).
>
> Hm... I don't remember this variont actually being mentioned on IRC --
> but I t
On Mon, Jun 14, 2010 at 10:49:42AM +0200, Samuel Thibault wrote:
> Carl Fredrik Hammar, le Mon 14 Jun 2010 10:47:15 +0200, a écrit :
> >
> > Is there such a thing as a task ID though? I thought tasks can only
> > referenced by ports?
>
> Replace "task id" with "port ID" in my sentence then. Wha
Carl Fredrik Hammar, le Mon 14 Jun 2010 10:47:15 +0200, a écrit :
> On Mon, Jun 14, 2010 at 10:33:49AM +0200, Samuel Thibault wrote:
> > Carl Fredrik Hammar, le Mon 14 Jun 2010 10:22:26 +0200, a écrit :
> > > (For instance, it might be possible to make Mach create a task without
> > > thread if it
On Mon, Jun 14, 2010 at 10:33:49AM +0200, Samuel Thibault wrote:
> Carl Fredrik Hammar, le Mon 14 Jun 2010 10:22:26 +0200, a écrit :
> > (For instance, it might be possible to make Mach create a task without
> > thread if it can't execute the image, then you could just read this task
> > with the t
Carl Fredrik Hammar, le Mon 14 Jun 2010 10:22:26 +0200, a écrit :
> (For instance, it might be possible to make Mach create a task without
> thread if it can't execute the image, then you could just read this task
> with the task store if you know its PID.)
Looks odd, but should be possible. Not l
olafbuddenha...@gmx.net, le Mon 14 Jun 2010 09:00:05 +0200, a écrit :
> > The current version of my d-i images use this as the root filesystem,
> > with grub loading an ext2 filesystem image from the boot CD. Which is
> > not that good considering that the required free space on / will
> > likely v
Hi,
On Mon, Jun 14, 2010 at 09:00:05AM +0200, olafbuddenha...@gmx.net wrote:
> > or that modifying Mach for this purpose is misguided and should be
> > avoided (for instance by embedding the initrd in a dedicated section
> > of an elf module).
>
> Hm... I don't remember this variont actually bein
Hi,
On Fri, Jun 11, 2010 at 03:16:04PM +0200, Jérémie Koenig wrote:
> As part of my debian-installer project[1] I have been working on
> initrd support for GNU Mach.
[...]
> The current version of my d-i images use this as the root filesystem,
> with grub loading an ext2 filesyste
2010/6/11 Jérémie Koenig :
> I'm going to move on to the other parts of my project for now unless
> some critical problem with the attached patch shows up.
Such as its author forgetting about enabling ramdisk_write() in
RAMDISK_DEV_OPS, and hence testing it :-/
I attach the corrected patch.
--
J
Hello,
As part of my debian-installer project[1] I have been working on
initrd support for GNU Mach. The new boot script command
$(devname=ramdisk-create) causes the contents of the module to be
copied into newly allocated memory which is made available to user
space through the device ${devname
20 matches
Mail list logo
