All of lore.kernel.org
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Recommended partition scheme for nilfs2
Date: Wed, 6 Jul 2011 19:19:37 +0200	[thread overview]
Message-ID: <201107061919.38253.dexen.devries@gmail.com> (raw)
In-Reply-To: <a6cda77328d5712a296a687a0e05e298.squirrel-aEpbUQpJQqXlKS8GlytQkw@public.gmane.org>

On Wednesday 06 July 2011 18:05:29 you wrote:
> Just one more thing.
> 
> For btrfs and other file systems, it is customary to have a separate boot
> partition, so that at a minimum, you have 3 partitions - /boot, Swap, and
> /. Would that be a problem for nilfs2?
> 
> If it is ok to have a separate boot partition, does it make sense to use
> nilfs2 on it? Or is it better to use a non-journaling file system, like
> Linux Native (ext2) on the boot partition, and nilfs2 on /.


for reference, my setup at home and at work:
two harddrives, one for / and /boot, the other for /home.

both / and /home are NILFS2, while /boot is ext3.

i wanted a very reliable journaling FS on /boot to lessen risk of foobar, and 
also I'm using lilo, which is not supported by NILFS2 yet -- lack of fibmap 
syscall.


-- 
dexen deVries

> (...) I never use more than 800Mb of RAM. I am running Linux,
> a browser and a terminal.
rjbond3rd in http://news.ycombinator.com/item?id=2692529
--
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

  parent reply	other threads:[~2011-07-06 17:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04 19:28 Recommended partition scheme for nilfs2 LinuxBSDos.com
     [not found] ` <4c09eb01174eecf704c751d7bf1b4bb2.squirrel-aEpbUQpJQqXlKS8GlytQkw@public.gmane.org>
2011-07-06  4:35   ` Ryusuke Konishi
     [not found]     ` <20110706.133558.186520806.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-07-06 12:29       ` LinuxBSDos.com
     [not found]         ` <59b61d7de047661eb7c2a1cf42df08f1.squirrel-aEpbUQpJQqXlKS8GlytQkw@public.gmane.org>
2011-07-06 15:43           ` Ryusuke Konishi
     [not found]             ` <20110707.004339.125911682.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-07-06 15:56               ` LinuxBSDos.com
     [not found]                 ` <3414843e1dfde171b9a9da8db1d295a6.squirrel-aEpbUQpJQqXlKS8GlytQkw@public.gmane.org>
2011-07-06 16:05                   ` LinuxBSDos.com
     [not found]                     ` <a6cda77328d5712a296a687a0e05e298.squirrel-aEpbUQpJQqXlKS8GlytQkw@public.gmane.org>
2011-07-06 17:19                       ` dexen deVries [this message]
     [not found]                         ` <201107061919.38253.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-07-07  3:21                           ` Ryusuke Konishi
     [not found]                             ` <20110707.122142.41457972.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-07-07  3:56                               ` LinuxBSDos.com
2011-07-07  4:04                               ` Ryusuke Konishi
     [not found]                                 ` <20110707.130423.56377867.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-07-07  9:13                                   ` dexen deVries
     [not found]                                     ` <201107071113.49938.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-07-07 16:31                                       ` Ryusuke Konishi
2011-07-07  3:55                           ` LinuxBSDos.com

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=201107061919.38253.dexen.devries@gmail.com \
    --to=dexen.devries-re5jqeeqqe8avxtiumwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.