From: "LinuxBSDos.com" <finid-aEpbUQpJQqXlKS8GlytQkw@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Recommended partition scheme for nilfs2
Date: Wed, 6 Jul 2011 06:29:53 -0600 [thread overview]
Message-ID: <59b61d7de047661eb7c2a1cf42df08f1.squirrel@linuxbsdos.com> (raw)
In-Reply-To: <20110706.133558.186520806.ryusuke-sG5X7nlA6pw@public.gmane.org>
Thank you.
With regards to /home, will there be a negative impact on the way nilfs2
works if /home is on a separate partition?
On Ubuntu and nilfs2, Ubuntu's installer does not have nilfs2 as a file
system option, how did you install Natty N. on nilfs2?
I know these are not dev-related questions, but I'm planning on writing
several nilfs2-related tutorials, and need to know exactly how a disk
should be partitioned for it.
Thanks,
--
Fini D.
> Hi,
> On Mon, 4 Jul 2011 13:28:39 -0600, "LinuxBSDos.com" wrote:
>>
>> Hi,
>>
>> A couple of Linux distributions now have nilfs2 as an optional file
>> system
>> during installation and I just want to find out what the minimum number
>> of
>> partitions required for a nilfs2-based installation is.
>>
>> Is it necessary to create separate partitions for the major file
>> systems,
>> or does nilfs2 require just one root file system directory? Is /home on
>> a
>> separate partition necessary?
>
> nilfs2 can be used as a root filesystem and it is bootable from recent
> grub2. I'm using nilfs2 for the root filesystem on my ubuntu-natty
> laptop.
>
> One restriction is that nilfs2 does not support swap file, so users
> need at least two partitions, swap and root.
>
> /home is not necessary to be a separate partition.
>
>> Lastly, can I encrypt a nilfs2 partition?
>
> nilfs2 itself does not support encryption. Instead, it can be used
> together with ecryptfs or dm-crypt.
>
> Thanks,
> Ryusuke Konishi
>
>> Thanks,
>>
>> --
>> Fini D.
>>
>> --
>> 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
> --
> 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
>
--
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:[~2011-07-06 12:29 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 [this message]
[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
[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=59b61d7de047661eb7c2a1cf42df08f1.squirrel@linuxbsdos.com \
--to=finid-aepbuqpjqqxlks8glytqkw@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@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.