On Mon, Jul 15, 2002 at 01:32:08PM +0200, Robert Millan wrote:
> On Mon, Jul 15, 2002 at 06:34:53PM +0200, Guillem Jover wrote:
> > Yes, when i saw James proposal i tought about it, and i think
> > that rewriting or modifing it to be a libparted frontend is
> > the way to go beacuse the current src is a mess. It can also
> > be used by Linux.
> > 
> > If you want we can work on this.
> 
> Well i'm very busy atm, and i'm novice at C so i was thinking
> on learning about it as i go.. If you want to write that
> frontend i could rather disturb you, so feel free to go at it :)

No hurry, and i'll have to learn libparted, so we can take this with
calm :).

> btw, is the UI code from fdisk usable?

The most desirable to be reused is the one from cfdisk (ncurses),
the UIs from fdisk and sfdisk are minimal. But until a deeper look
at libparted is taken won't know if the modifications are one to one,
or imply modifing also the UI.

> > I've got all what is not really Linux specific to compile under the Hurd.
> > And yes quite unportable, 100k of patch :P. I'm testing and polishing
> > last details, but in few days it will be finished.
> 
> could you list what you have? as said before it'd be good to put it on
> respective GNU packages.

I have finished the port, and will send it to the bts this night if
nobody objects.

from bsdutils:

        script
        logger
        renice
        wall
        replay

from util-linux:

        arch
        more
        fsck.minix
        mkfs
        mkfs.minix
        mkswap
        ipcs
        ipcrm
        setsid
        namei
        setterm
        mcookie
        whereis
        ddate
        getopt
        rev
        chkdupexe
        
        # Hurd limitation -> no large file support
        #   work fine on images < 2 GiB
        #   should work on images >= 2 GiB w/ dos partition tables
        #     w/o extended partitions.
        cfdisk
        fdisk
        sfdisk

        # not included -> conflicts with hurd.deb
        getty

regards,
guillem


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Reply via email to