All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Umanets <umka@namesys.com>
To: Steve Pratt <slpratt@us.ibm.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>,
	Andrew Clausen <clausen@gnu.org>
Subject: Re: EVMS Reiser FSIM
Date: Wed, 29 May 2002 18:17:43 +0400	[thread overview]
Message-ID: <3CF4E307.1010805@namesys.com> (raw)
In-Reply-To: OFB49DCA39.27F715F1-ON85256BC8.004B436D@pok.ibm.com

Steve Pratt wrote:

>Thanks for all the help answering questions about the reiser utilities.  I
>have released the  ReiserFS FSIM into the EVMS CVS tree to be included in
>our upcoming 1.1 release.   Check it out if you get a chance and feel free
>to give me comments.  Also let me know if you think more options are
>required on mkfs and fsck.  I only did the basics and avoided non-standard
>journals since the kernel file system code is not readily available yet.
>When it is, I can go back and add that support.
>  
>
I thing you have released an incorrect reiserfs FSIM in theory. On my 
own you should add extra parameters
support into GNU Parted (quite simple task). And then you might be using 
it as central component of FSIM
for *ALL* filesystems. Not just for reiserfs.

Or you might be using some library (from reiserfsprogs package or from 
progsreiserfs package).

The way you have selected, might be used by an propriatary software, 
that wanted to use GPL project, not other GPL project.

BTW, I have almost done smart resizing (from partition start) in 
libreiserfs. But you can't using the libraries of third pesons, so you 
will haven't smart resizing and other features in your FSIM :))

Yet another issue. One man almost done JFS support for GNU Parted. Are 
you going to add it to EVMS too? I think yes. And probably you will do 
it in maner like ReiserFS (forking and piping).

Yury Umanets



  reply	other threads:[~2002-05-29 14:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 13:46 EVMS Reiser FSIM Steve Pratt
2002-05-29 14:17 ` Yury Umanets [this message]
2002-05-30  5:09 ` Oleg Drokin
2002-05-30  5:32   ` Adrian Phillips
2002-05-30  5:54     ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29 16:28 Steve Pratt
2002-05-30  7:37 ` Yury Umanets
2002-05-30  9:53 ` Andrew Clausen
2002-05-30 12:56   ` Hans Reiser
2002-05-30 23:50     ` Andrew Clausen
2002-05-30 17:14 Steve Pratt
2002-05-31  9:26 ` Oleg Drokin
2002-05-30 19:02 Steve Pratt
2002-05-31 13:43 ` Andrew Clausen
2002-05-31 17:03 Steve Pratt
2002-05-31 17:28 ` Oleg Drokin
2002-06-03 16:00 ` Oleg Drokin
2002-05-31 17:40 Steve Pratt
2002-06-01  1:35 ` Andrew Clausen
2002-06-03 19:04 Steve Pratt
2002-06-03 19:36 ` Oleg Drokin
2002-06-03 21:03 Steve Pratt
2002-06-04  6:09 ` Oleg Drokin
2002-06-03 23:34 Steve Pratt
2002-06-04 15:02 Steve Pratt
2002-06-04 15:10 ` Oleg Drokin
2002-06-04 16:45 Steve Pratt

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=3CF4E307.1010805@namesys.com \
    --to=umka@namesys.com \
    --cc=clausen@gnu.org \
    --cc=reiserfs-list@namesys.com \
    --cc=slpratt@us.ibm.com \
    /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.