reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <doiggl@velocitynet.com.au>
To: reiserfs-devel@vger.kernel.org
Subject: Re: reiser4 and grub2
Date: Thu, 21 Oct 2010 00:33:36 +1100	[thread overview]
Message-ID: <33d69d2b913d7597730de74df6c5c3eb@mail.velocitynet.com.au> (raw)
In-Reply-To: <4CBC37E3.3050301@gmail.com>

On Mon, 18 Oct 2010 14:04:51 +0200, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> sannikov wrote:
>> Good day.
>>   
> 
> Hello.
> 
>> I want to ask you about reiser4 and grub-2.
>>
>> I am try to write to Yuriy Umanets but his mailboxes are inactive...
>> Some few days ago I findes his request about this.
>> (http://lists.gnu.org/archive/html/grub-devel/2008-02/msg00263.html)
>>
>> If it is possible, can you describe current state of Raiser4 support in
>> Grub2.
>>   
> 
> Unsupported.
> 
>> As I know this task yet  placed in Grub's TODO list.
>> I hope this idea yet alive.
>>   
> 
> I didn't look at grub2/fs interface yet, but believe that it
> is better then grub1's one.
> 
> There is a patch for reiser4 support in grub1. I don't
> think it will be a big problem to adjust this one for grub2:
> the sources are quite understandable.
> 
> The only thing I am unhappy with is that it can not boot
> reiser4 via module stage1_5 (it is too big and can not
> fit in 62 sectors), It means that user will need to re-install
> grub every time after defragmentation (currently
> unsupported, but upcoming). So it would be nice to resolve
> this problem in grub2 somehow.
> 
> Btrfs stage1_5 module with multi-device support
> successfully fits in 62 sectors. Why reiser4 can not?
> I think we need to get rid of the mini-library with a lot
> of unneeded functions and put everything in one file
> (as other file systems do).
> 
> Thanks,
> Edward.
> 
Looks like some others have had a go at compiling grub2 ,see:

http://download.opensuse.org/repositories/home:/reinauer/openSUSE_11.2/i586/grub2-1.98-18.1.i586.rpm

http://download.opensuse.org/repositories/home:/reinauer/openSUSE_11.2/src/grub2-1.98-18.1.src.rpm

http://download.opensuse.org/repositories/home:/reinauer/openSUSE_11.3/i586/grub2-1.98-18.1.i586.rpm

http://download.opensuse.org/repositories/home:/reinauer/openSUSE_11.3/src/grub2-1.98-18.1.src.rpm

http://download.opensuse.org/repositories/home:/reinauer/openSUSE_11.3/x86_64/grub2-1.98-18.1.x86_64.rpm

http://download.opensuse.org/repositories/home:/reinauer/openSUSE_Factory/i586/grub2-1.98-18.1.i586.rpm

http://download.opensuse.org/repositories/home:/reinauer/openSUSE_Factory/src/grub2-1.98-18.1.src.rpm

http://download.opensuse.org/repositories/home:/reinauer/openSUSE_Factory/x86_64/grub2-1.98-18.1.x86_64.rpm

Glenn

  reply	other threads:[~2010-10-20 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18  9:18 reiser4 and grub2 sannikov
2010-10-18 12:04 ` Edward Shishkin
2010-10-20 13:33   ` doiggl [this message]
2010-10-20 19:10     ` sannikov
2010-10-20 23:35       ` Christian Stroetmann
2010-10-21  8:24       ` doiggl
2011-03-05  4:12   ` doiggl

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=33d69d2b913d7597730de74df6c5c3eb@mail.velocitynet.com.au \
    --to=doiggl@velocitynet.com.au \
    --cc=reiserfs-devel@vger.kernel.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).