#include <hallo.h>
* Micah Anderson [Fri, Feb 25 2005, 06:33:19PM]:
> > What was wrong with that answer?!
>
> Look, if you run module-assistant, a dialog front-end comes up. It
> suggests I run UPDATE before I continue, I run UPDATE. Apparantly the
> next step is to run PREPARE, I do that, it installs some packages that
> are apparantly needed, then says "Done!", then I guess the most
> logical next step is to pick the module I want to install. So I pick
> loop-aes.
Sounds okay.
> Then I am presented with a menu of confusing options, I can list
> binary packages (binary packages of what?),
Should I rename that? To what? Suggestions welcome.
"Installable module packages" maybe?
> I can SEARCH (search for what?),
Search in the apt-pool for pre-built package, shipped by Debian.
Suggest a better description.
> I can GET (get what? I try it and it gets some loop-aes
> things, not what I would call intuitive, but ok),
That is the download/installation of the source package. Should I rename
that? Into what exactly?
> I can BUILD (I assume loop-aes, since that is selected).
Yup
> So I try BUILD and it says
> "The source package may not to be installed. Would you"
Hm. This is a longer line and should have been broken by the dialog
tool? Is the dialog package installed?
Anyways, I could force the line break.
> Thats it... My brain has a PARSE ERROR because I dont understand the
> first sentence "the source package may not to be installed" what does
> that mean? The second sentence which is only "Would you" doesn't
> really ask me anything that I understand because it is not complete.
> If I choose YES it fails, if I choose NO, it fails.
In this state, it is not possible to verify whether the source has been
completely unpacked or not.
So in theory, m-a could unpack that always. However, some people patch
the module source manually so they would not like that action. And it
needs some time, after all.
If you know better wording, please tell me.
> I try to make my window huge, I still don't get all of the message.
Sounds like whiptail problems. Can you scroll with the cursor buttons?
> It fails to build a module if you follow its instructions. If you want
It fails especially because you need a complete source tree. I added
something to warn the user about the suspicous module, but it will need
some time to find its way into the archive.
And the fakesource function should work better know. It should create a
provisoric kernel source directory which is similar to the one used by
the kernel team.
> me to do something different, then make it clear, I cannot intuit what
> your meaning is behind the purpose of faking the source tree. Why
That is why you need to RTFM. That is simply not realistic to expect m-a
to perform magic.
> doesn't the curses GUI do this for you? What the message is that I am
It could... but it would be like a stupid MS wizard ("Should I do a?
Press ok." and then it extracts 300mb in the background but shows the
users a progress bar. aaaargh)
> If I follow the HOWO instructions or what I can read in the dialog
> box, you end up with a failure. Either the instructions need to be
> fixed so you do what you are supposed to do, or the GUI which leads
> you to believe that this is how you do things should be fixed.
>
> Perhaps I am using module-assistant incorrectly, but what does "You
> can fake the source tree with "m-a fakesource", though." mean? Why
> would I want to do that? Why isn't this obvious or documented
> somewhere how to use the tool?
The new warning says:
Warning: the selected module source is known to require a complete
kernel source structure in order to be built correctly. However, only
a reduced version of the source (kernel-headers) has been found, so
the build process will probably fail.
In order to get a full kernel source, you have the following options:
- fake the source directory - create one that may look very similar
to the one that has been used to build your kernel (based on its
configuration and fresh source archive). The results are uncertain,
but it should work in most cases.
Call \"module-assistant fakesource\" to automate this.
- use a custom kernel built from scratch (custom configuration,
custom source, custom kernel package installed). Please read the
Kernel HOWTO and/or make-kpkg documentation for the further steps.
Is that clear enough?
Regards,
Eduard.
--
Immerhin meint die Filmf�rderungsanstalt, im Jahr 2002 seien 59
Millionen CD-Rohlinge von 5,9 Millionen Nutzern mit Filmen bespielt
worden, im Durchschnitt also zw�lf Rohlinge pro Anwender.
-- <http://www.heise.de/newsticker/data/see-08.04.03-000/>
