[umlbuilder-devel] Re: List of Bugs

[Roger B. <ro...@ro...>]

> 0. (already reported this one) For umlbuilder 1.4.0-5 python 2.2
>    requires that line 945 of gui.py has colum written as column.
> 
>         b.grid(row=2,colum=1, sticky=E)

Thanks for spotting the typo.  I am busy working on that one.

>     turbo indexer not available, falling back on traditional indexer
>     Segmentation fault

I'll look into this.  I normally do most of my testing with the
CLI version since I script it to run all the different distros.
The gui version effectively gathers up parameters and invokes
the cli code, except for the initial indexing.

> Creating new initial ramdisk
> Miniroot starting
> mount: Mounting /proc on /proc failed: Bad address
> mount: /proc/mounts: No such file or directory
> mount: Mounting /dev on /dev failed: Bad address
> grep: /proc/cmdline: No such file or directory
> Miniroot exiting - exit status 1
> System halted.

This is a bug in UML and skas.  It doesn't occur in TT mode.  Jeff
has fixed it in the most recent UML release (a day or two ago).

> 3.  When changing useinitrd="true" to useinitrd="false" in control,
>     start still failed with this error:
> 
> Updating modules
> Miniroot starting
> mount: Mounting /proc on /proc failed: Bad address
> mount: /proc/mounts: No such file or directory
> mount: Mounting /dev on /dev failed: Bad address
> grep: /proc/cmdline: No such file or directory
> Miniroot exiting - exit status 1
> System halted.

Same problem.  miniroot is trying to install modules instead of mkinitrd

> Obviously, the miniroot provided in this release needs some fixing.

For once it isn't my fault :-)

There are actually some nice goodies in miniroot.  As well as making
initial ramdisks and installing modules, it has a rescue mode that
gets you a command line shell.  rescue mode doesn't premount your
filesystems yet.

It also has a filesystem resizer/format changer.  This works by
making a new sparse file, running mkfs, and then cpio the data
across.

> 1.  Add a --module-dir <dir> option and synonymous functionality to the gui
>     which allows the user to choose an optional location to look for
>     modules*tar.  Don't proceed until modules* are actually found,
>     otherwise the whole process has to be done all over.

Will do.
 
> 2.  Add a --uml-kernel <path> option and synonymous functionality to the
>     gui which allows the user to choose an optional uml kernel

At runtime, this is easy.  The control script looks in its directory for
an executable with the same name as the umid.  It then looks for one
named linux.  Consequently you can just copy or symlink in the one you
want.

That can only happen after install so I'll also add preinstall hooks.

Thanks,

Roger