[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081229121423.efde9d06.akpm@linux-foundation.org>
Date: Mon, 29 Dec 2008 12:14:23 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Boaz Harrosh <bharrosh@...asas.com>
Cc: avishay@...il.com, jeff@...zik.org, viro@...IV.linux.org.uk,
linux-fsdevel@...r.kernel.org, osd-dev@...n-osd.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 7/9] exofs: mkexofs
On Tue, 16 Dec 2008 17:33:48 +0200
Boaz Harrosh <bharrosh@...asas.com> wrote:
> We need a mechanism to prepare the file system (mkfs).
> I chose to implement that by means of a couple of
> mount-options. Because there is no user-mode API for committing
> OSD commands. And also, all this stuff is highly internal to
> the file system itself.
>
> - Added two mount options mkfs=0/1,format=capacity_in_meg, so mkfs/format
> can be executed by kernel code just before mount. An mkexofs utility
> can now be implemented by means of a script that mounts and unmount the
> file system with proper options.
Doing mkfs in-kernel is unusual. I don't think the above description
sufficiently helps the uninitiated understand why mkfs cannot be done
in userspace as usual. Please flesh it out a bit.
What are the dependencies for this filesystem code? I assume that it
depends on various block- and scsi-level patches? Which ones, and
what is their status, and is this code even compileable without them?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists