[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Evms] Questions about portability

From: Andrew Clausen
Subject: Re: [Evms] Questions about portability
Date: Mon, 13 Nov 2000 17:44:40 -0200

Christoph Hellwig wrote:
> 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.

Interesting.  I guess this is more common with LVs than partitions,
because LVs can have a more complicated (i.e. more painful to
reproduce) layout.

> > 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 ?

The stand-alone stuff shouldn't need a file-system-specific front end,
if it conforms to a common interface, right?

> > 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).

How do you know what to grep for?  What if you have incomplete
(so parts of it come out in another language)

(BTW: I really meant log widget instead of log window...)

Andrew Clausen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]