Re: [Gbootroot-devel] Verbosity Logging

[Jonathan R. <mtt...@ac...>]

On Thu, 24 Aug 2000, Cristian Ionescu-Idbohrn wrote:

> 
> First off: my toes are to big for this keyboard :-)
> What I thought was WARN showed up as WARM :-(

Well the next time, just say:

perl -e '$trans = "WARM", $trans =~ tr/M/N/, print $trans;' 
 
:)

> 
> [snip]
> 
> 
> Let me explain what I thought of when I suggested WARN as a separate error
> level.
> 
> We know what we're be going to do (at the beginning of the script). We
> have a plan. We also know we can't do things with our bare hands. We need
> some system tools. We know what system tools we need. Let's make sure we
> have access to those tools (sanity checks in an init phase right from the
> beginning, like: the program is there and is executable). Any problems
> that arise, report them as WARN (warnings) to the user.

I see what you are talking about, Yard does this.  This is generally a
good thing to do, I was hoping people who make packages for distributions
would fill in the blanks, for instance, by making gBootRoot dependent on
binutils, but that is assuming too much.  Sanity checks for some things
will be optional.  For instance, if it isn't necessary for stripping to be
done by objcopy (which belongs to binutils), there is no sense in
requiring it.  

I'll be adding stripping soon to make gBootRoot useable on 1440 devices in
distributions which don't strip libraries.  This situation created a very
large initrd.  You wouldn't happen to be running a distribution with
unstripped libraries or binaries would you?

One cool thing, you can use the 1722 setting on most 1440 floppy devices
without any problems.  This is a trick of Tom's rtbt.  This creates a lot
of extra room for both the Boot and Root disk.  :)  This is something I
will put in the FAQ.