From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: grub nilfs2 module
Date: Thu, 04 Feb 2010 16:54:56 +0900 (JST) [thread overview]
Message-ID: <20100204.165456.217843065.ryusuke@osrg.net> (raw)
In-Reply-To: <20100204.100228.02802641.ryusuke-sG5X7nlA6pw@public.gmane.org>
Hi,
On Thu, 04 Feb 2010 10:02:28 +0900 (JST), Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> wrote:
> Hi,
> On Wed, 03 Feb 2010 21:43:46 +0900, Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org> wrote:
> > Hi,
> >
> > I've written nilfs2 module for grub2 boot loader.
> >
> > Here is the patch and mail I'v sent to grub-devel ML.
> > http://lists.gnu.org/archive/html/grub-devel/2010-02/msg00025.html
>
> Great!
>
> The patch looks fine to me except some work, for instance,
> rollforwarding and checksum based log validation is needed.
>
> But meanwhile, this prototype seems enough to load kernels and
> initrds.
>
> I'd like to try it for my laptop.
>
> > It may not be mature yet, but I was able to boot kernel
> > from nilfs2 partition and mount it as rootfs.
> > So you are able to boot the system that has only nilfs2 partition.
Let me ask you a question.
One thing which is important in NILFS is that every block in the
partition can be moved by the garbage collection (except two super
blocks).
So, we cannot assume that file blocks stay in a locked position even
for unmodified files.
Doesn't this cause problems for the boot sequence of GRUB2 ?
Regards,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-04 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 12:43 grub nilfs2 module Jiro SEKIBA
[not found] ` <87vdeea3r1.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-02-04 1:02 ` Ryusuke Konishi
[not found] ` <20100204.100228.02802641.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-02-04 7:54 ` Ryusuke Konishi [this message]
[not found] ` <20100204.165456.217843065.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-02-04 8:18 ` Jiro SEKIBA
[not found] ` <87d40l9zyb.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-02-04 9:03 ` Ryusuke Konishi
2010-02-04 9:03 ` Jiro SEKIBA
[not found] ` <87bpg59xug.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-02-04 9:21 ` Ryusuke Konishi
[not found] ` <20100204.182139.37565943.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-02-09 11:07 ` Ryusuke Konishi
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=20100204.165456.217843065.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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