[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reiser4 support in GNU GRUB...

From: Yoshinori K. Okuji
Subject: Re: Reiser4 support in GNU GRUB...
Date: Fri, 04 Apr 2003 23:34:39 +0900
User-agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (Unebigoryƍmae) APEL/10.3 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI)

At Thu, 03 Apr 2003 15:10:22 +0400,
Yury Umanets wrote:
> Some time ago I've written the letter to address@hidden about reiser4 
> support in GNU GRUB and adding memory management to it. As I still have 
> not an answer, I write it one more time. And I hope to receive it this time.

I'm sorry. I missed your previous mail.

> Reiser4 team is interested in adding reiser4 support to GNU GRUB. And it 
> can be done by means of using our static libreiser4, built in stand 
> alone mode, that is, without libc, gcc built-ins and without features 
> which are not needed for GRUB like file creating/writing, repair stuff, 
> etc.

Is that easier than modifying our code to support Reiser4?

> And now the problem is that, we cannot use FSYS_BUF for memory manager, 
> because it is used by all fs GRUB supports them and as they are not 
> aware about the memory manager, they work with FSYS_BUF as with 
> dedicated to them raw data array and corrupt it.

Why is it a problem, although GRUB 0.9x doesn't support opening
multiple files at a time? attempt_mount is always called before
opening a file, so you can initialize FSYS_BUF to a known state in a
mount function.

> In boot time everything probably will be okay, as GRUB will use only one 
> fs-implemntation and namely root partition uses it, say reiser4. But as 
> "memory manager tack" exists in GRUB's TODO list, probably it is time to 
> implement it?

It has already been implemented for GRUB 2 (aka PUPA). It will never
be implemented for GRUB 1.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]