Subject: kernel-package_2.02 uploaded to master

From: Manoj Srivastava <[email-masked]>
Date: 25 Jul 1996 16:39:18 -0400

Hi folks,
	
	This should be much easier package to deal with than it has
 been in the past, in fact, I have asked the powers that be to move
 the package out of the experimental projects directory.

	I was supposed to have released this earlier this week, but I
 held it back and tested it with a brand new Linux 2.0.8 kernel
 sources.  I have tested it with all the options I could on my box,
 and It Works For Me(tm).

	I'd appreciate it if people tried this version out, cause I
 probably have time to work on one more version before handing it over
 to someone else, at least for the next couple of months.

	manoj

-----BEGIN PGP SIGNED MESSAGE-----

Date: 25 Jul 96 07:06 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Manoj Srivastava <[email-masked]>
Source: kernel-package
Version: 2.02
Binary:  kernel-package
Architecture: all source
Description: 
 kernel-package: Debian Linux kernel package build scripts.
Changes: 
 * Made image.postinst more polite.
 * Also enabled kernel-{source,image,headers} targets in kernel.rules
 * Changed make-kpkg to also accept the new targets.
 * Fixed typo in man page.
 * The man page says it is an adminstrators man page rather than a
   programmers man page.
 * Recommended libc-dev for kernel-source and kernel-package
 * source suggests ncurses3.0-dev, tk40-dev and the description explains
   you could use make menuconfig rather than plain old make config if you
   had these packages.
 * Fixed typo in the rules for modules in /usr/src/modules/ directory
 * Made the rules for such modules ignore errors (since they are not really
   a part of this package, error there should not halt this build (or so
   people seem to want it)
 * Look for modules in the kernel config file (or the default config file
   if the user has not supplied a config file), and only make modules and
   install them if modules have been configured in the config file. This
   could be tested better.
 * Fixed the make-kpkg.8 man page so that it now does not seem to mandate
   a source and diff file for additional modules installed under the
   directory /usr/src/modules/ (whether these files are produced is at the
   discretion of the maintainer of that modules package.
 * Make configure depend on stamp-configure which in turn depends on .config
   Hopefully, this will remake the image atrget if one changes the config file
   Hopefully, this will not cause the image target to build needlessly.
 .
Files:
 f794ceaf44f99b861cfcae315705c80a  33076  misc  -  kernel-package_2.02.tar.gz
 94dbc309d85684656d8e2b0120c273cc  40620  misc  optional  kernel-package_2.02_all.deb

-- 
 A gen'ral sets his army in array In vain, unless he fight and win the
 day.  -- Denham
Manoj Srivastava               Systems Research Programmer, Project Pilgrim,
Phone: (413) 545-3918               A143B Lederle Graduate Research Center,
Fax:   (413) 545-3203         University of Massachusetts, Amherst, MA 01003
<[email-masked]> <URL:http://www.pilgrim.umass.edu/%7Esrivasta/>

---

From: Alexander Goldstein <[email-masked]>
Date: Fri, 26 Jul 1996 13:13:27 -0500 (CDT)

I though you may want to know this.  Either I or you are cofused about pgp. 
(it could well be me, since I just started using pgp few days ago, but here
it goes.)  When I fignered you at [email-masked], here are first
few lines I got.

---- cut here ----
[pilgrim.umass.edu] 
Login name: srivasta                    In real life: Manoj Srivastava
Office: 143B LGRC, (413) 545-3918               Home phone: (413) 549-4708
Directory: /users/pilgrim_staff/srivasta        Shell: /bin/bash
Last login Thu Jul 25 21:14 on ttyp0 from nscs27p7.remote.e
Plan:
Type Bits/KeyID    Date       User ID
sec  1024/D01B0D83 1993/08/28 Manoj Srivastava <[email-masked]>
                              Manoj Srivastava <[email-masked]>

-----BEGIN PGP SECRET KEY BLOCK-----
Version: 2.6.3a
Comment: Requires PGP version 2.6 or later.

lQHgAyx+rIQAAAEEALmVKaxyBrxFTWMdgNVMlL9gFWYSk2uHPvg1YuhEnC/VOOpT
VNCLYNumGD5bvHu8+mTwUx9TSsNeBQiPtC5lr9tECLmweN18hgOjj9B7Ald0O98I

---- ..... ----

Any way the point is that you have to keep you private/secret keys private,
so I guess you would have to issue KRC for your key and get a new one.

Good Luck,
Alex

---

From: Alexander Goldstein <[email-masked]>
Date: Fri, 26 Jul 1996 14:06:11 -0500 (CDT)

Sorry, that was supposed to go private.