Util-Linux package development
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@gnu.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux-ng <util-linux-ng@vger.kernel.org>
Subject: [RFC PATCH 0/3] mkfs.minix: add v3 support
Date: Thu, 31 Mar 2011 11:59:24 -0300	[thread overview]
Message-ID: <1301583564.2159.14.camel@offworld> (raw)

Hi,

The following patches add support for the minix3 filesystem in
mkfs.minix. I have been able to successfully try this out on different
disks, loading different types of files (images, text, video, etc.). I
have also verified that stat(2) works fine on this and the regression
tests for util-linux pass. Since I am not a fs expert please try this
out thoroughly and let me know your opinion. Despite the ugliness of the
code (for years now), I tried not to be too invasive and not rewrite
large parts of it.

With this new version we can
* have up to 60 characters for filenames.
* specify the block size to be used.

Additionally, four options were added:
* -1, -2, -3 to specify what version of the fs to create
* -B to specify the block size

Thanks,
Davidlohr 


                 reply	other threads:[~2011-03-31 15:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1301583564.2159.14.camel@offworld \
    --to=dave@gnu.org \
    --cc=kzak@redhat.com \
    --cc=util-linux-ng@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