Bug#201191: partconf: mkfs should indicate progress

[Gaudenz Steinlin <gaudenz@soziologie.ch>]

On Tue, 2003-11-11 at 15:15, Steinar H. Gunderson wrote:

> > I suggest a simple solution. I think the most important thing is that
> > users don't see a blue screen for several seconds like it's now, but a
> > progress bar. I would only step it forward after one filesystem is
> > created, so we don't have to parse mkfs.* output. A setup with only one
> > root partition and one swap would have two steps:
> > 0% creating filesystem on /dev/...
> > 50% creating swap on /dev/...
> > 100% finished
> 
> It would definitely help compared to what we have today, but it would still
> suck.
Yes, but I don't think it's worth to invest more time in that now. This
would be an easy and acceptable solution.

> 
> > I think one point of having partitioner is, that it does not use
> > libparted for filesystem creation and is therefore more versatile and
> > less prone to errors.
> 
> Why would running mkfs.ext2 be more versatile than using libparted? (Like I
> said, I'd use mkfs.* for JFS etc., but ATM we don't even have that on our
> install disks. :-) )

I don't know how stable parted on i386 is. Last time I tried to format a
partition with parted on my powerbook it just hung forever and did not
format the partition. So I thought parted my be a little bit flaky.
Actually I don't know if the bug is in the frontend or the library.

Gaudenz