On Sat, May 23 2009, Bob Skaroff wrote:

> I don't find the explanation in the man page for make-kpkg adequate.

        Then this is an excellent opportunity to improve the
 documentation for all users. Improvements gratefully accepted.

> I'm afraid that I don't know all the details of package installation
> and unless there is a significant value add to do so, I probably won't
> learn them all.

        This is fine. Perhaps there is some value in learning how to
 tailor kernel image installations to your liking?

> The man page needs to be more specific.

        In what way, exactly?

> You should understand that that there are debian users that don't want
> an ubuntu experience, but don't have the desire to learn chapter and
> verse on every technical topic.  Not everyone is a debian developer.
> I've been a debian user since 3.0.

        Sure. But since I do not fit that demographic, I am perhaps not
 the best person to attempt to enhance the documentation in that manner.

> I need to know what are the names of the hook scripts and the
> post-installation maintainer scripts and what changes must be made to
> them to convey that an initrd is needed.

        Well, it depends. There are a slew of post install example
 scripts shipped i the package (and not  all can be installed
 simultaneously, since some of them do the same job, and often
 incompatibly -- like the yaird and inintramfs-tools compatible
 scripts). 

        Or you can write your own, based on the examples. All my scripta
 are called manoj-<somethihng>, for instance.

> not "arrange to convey".

        Well, I thought I had covered this in the README.gz file, but
 perhaps you can suggest improvements.

        manoj
-- 
Each new user of a new system uncovers a new class of bugs. Kernighan
Manoj Srivastava <[email protected]> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C



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

Reply via email to