Re: [Evms] Questions about portability

[Christoph Hellwig]

On Mon, Nov 13, 2000 at 05:15:04PM -0200, Andrew Clausen wrote:
> > > Could similar arguments be made about this stuff?  (the programs
> > > aren't really independent - it doesn't make sense (in MOST cases) to
> > > run these programs on their own?)
> > 
> > No.  I often run e.g. lvextend on my own.
> 
> Why, BTW?

Usually because it is a raw device.  Sometimes because I create a
new filesystem on it and need an other size.

> > I don't know sane filesystems (e.g. ext2) and sane partitioning schemes
> > (e.g. LVM) should know of each other...
> > And I'm interested in LVM and not all that DOS legacy crap.
> > You want it in parted - but I don't want to see such things in a LVM
> > enviroment.
> 
> Obviously, the file system code is going to be shared between partition
> and LVM environments, so the code is going to be there, but it doesn't
> need to appear in the LVM interface.

True.  What about

        ext2resize.c            --> core ext2fs resizing code
        ext2resize_parted.c     --> glue for libparted (incl partition stuff)
        ext2resize_stand.c      --> standalone glue ?

> In which case, it should be possible to specify this (convieniently).
> This would be a big debate, and I don't think this is the appropriate
> place, hehe...
> 
> Maybe I should ask for address@hidden  :p

Why? I really like

   --i-really-want-to-ignore-that-stupid-bloody-error

;\

> > Actually I wouldn't - but lots of others would...
> 
> So, I win?  :p
> 
> I guess not, because you'd rather print out the [translated] error
> messages
> to stderr, and be done with it.  Not sure how this works for GUIs.  (log
> window?)

It doesn't even have to be a log window, just grep all the [translated]
messages and put them into the log widget (which can have it's own window,
but doesn't have to).

        Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.