Subject: kernel-packages_2.00 uploaded to master

From: Manoj Srivastava <[email-masked]>
Date: 02 Jul 1996 22:12:04 -0400

Hi guys,

	This is a major change in the user interface, and though I
 have tried to test this out, I'd appreciate it if you were careful
 while trying this out.  Since this is so new, I'd let it stay
 experimental, and release 2.01 as a real release (and announce that
 on debian-changes).

	Look below for details of changes. I'd appreciate comments.

	manoj

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

Date: 01 Jul 96 06:15 UT
Format: 1.6
Distribution: unstable
Urgency: Low
Maintainer: Manoj Srivastava <[email-masked]>
Source: kernel-package
Version: 2.00
Binary:  kernel-package
Architecture: all source
Description: 
 kernel-package: Debian Linux kernel package build scripts.
Changes: 
 * Make image.postinst test the lilo configuration, and warn about errors.
 * The kernel-package package unpacks into /usr/lib/kernel-package
 * /usr/sbin/make-kpkg is the recommended front-end wrapper script for
   kernel-package, this runs the right debian.rules
 * Test to ensure that the kernel targets are executed in the kernel source
   directory. (make-kpkg also does this test)
 * The kernel-package will work with files in ./debian/*, (needed for
   the case when the package is bundled in with kernel-source-X.XX.XX),
   as well as a standalone package.
 * Split debian.rules into debian/kernel.rules and debian/package.rules,
   one of which will be copied to debian.rules at package build time
   depending on whether this is a kernel-source package or a kernel-package
   package (yes, we have an identity crisis, thank you).
 * Added a site override file /etc/kernel-pkg.conf (this is a conffile)
 * Added kernel-packageconfig in /usr/sbin to help configure the conffile
 * Added a postinst file to kernel package (which runs kernel-packageconfig)
 * support auxiliary modules in /usr/src/modules
 * Made all targets for modules conform to what Brian Mays uses in pcmcia
 .
Files:
 1ce3ffb40fce12a6f95b7b58a371e6a9  30038  experimental  -  kernel-package_2.00.tar.gz
 1def2d7aff2e338ce3107da904f9ca1a  37544  experimental  optional  kernel-package_2.00_all.deb

-- 
 On our campus the UNIX system has proved to be not only an effective
 software tool, but an agent of technical and social change within the
 University. John Lions (U. of Toronto (?))
Manoj Srivastava               Systems Research Programmer, Project Pilgrim,
Phone: (413) 545-3918                A143B Lederle Graduate Research Center,
Fax:   (413) 545-1249         University of Massachusetts, Amherst, MA 01003
<[email-masked]> <URL:http://www.pilgrim.umass.edu/%7Esrivasta/>

---

From: Michael Alan Dorman <[email-masked]>
Date: Wed, 03 Jul 1996 16:41:21 -0400

I like the idea, but I'm having a heck of a time getting it to work.

I unzipped virgin 2.0 sources in /var/tmp/linux, and then patched to
2.01.  I copied my config from its usual resting place to
/var/tmp/linux/.config, and ran make config for good measure.

I installed the new kernel-package.  I read the README, which seems
terribly out of sync with what the make-kpkg script really wants.  I
tried running 'make-kpkg binary', and it churned and whirred and
eventually came up with,

"sed: can't read debian/image.postinst: No such file or directory"

Which makes sense, since there's no /var/tmp/linux/debian directory.

Also, make-kpkg kernel_image (which is all I'm really interested in)
tells me this isn't a valid target.

So did I do something wrong?  I haven't found the docs to be
sufficiently in sync to say.

Once it works, though, I think it'll be even nicer than the previous
kernel-package, of which I am a big fan.

Mike.
--
"Don't let me make you unhappy by failing to be contrary enough...."

---

From: Rob Browning <[email-masked]>
Date: 04 Jul 1996 10:59:33 -0500

> /var/tmp/linux/.config, and ran make config for good measure.

You may already know this, but...

I'd be careful about doing this stuff in /tmp or /var/tmp.  If any of
the files are too old when the cleaning scripts fire, they're
history.

Someone recently told me about a nasty experience when he mounted a
friends drive (main partition with a big (un-backed up) project on it)
on /tmp to do some work on it.  He was working late, and sooner or
later the cleaning scripts fired.  Most of the files on the drive were
lost...

--
Rob

---

From: Lars Wirzenius <[email-masked]>
Date: Fri, 05 Jul 1996 10:08:28 +0300

[ NB: I read the list.  Don't CC replies to me.  I pay for my PPP.  Thanks ]

> later the cleaning scripts fired.  Most of the files on the drive were

I'd classify that as a bug.  I wouldn't mount anything in /tmp or
/var/tmp, but I don't think /etc/cron.daily/standard should go across
mount points anyway.

Does anyone else think it is a bug?  Tell me, and I'll send in a bug
report.

---

From: Miquel van Smoorenburg <[email-masked]>
Date: Sat, 6 Jul 1996 10:37:25 +0200 (MET DST)

> /var/tmp, but I don't think /etc/cron.daily/standard should go across

Well if you mount a drive *on* /tmp, then it _is_ /tmp for the
system for any and all purposes. If you mount it under /tmp, for
example on /tmp/mnt, then the cleanup scripts should leave it alone.

Just my $.02

Mike.
-- 
  Miquel van    | Cistron Internet Services   --    Alphen aan den Rijn.
  Smoorenburg,  | mailto:[email-masked]          http://www.cistron.nl/
[email-masked] | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)

---

From: Rob Browning <[email-masked]>
Date: 06 Jul 1996 00:53:17 -0500

> Does anyone else think it is a bug?  Tell me, and I'll send in a bug

We should probably check that this actually happens on a Debian
system, because it just dawned on me that this guy might have been
using some other distribution.

--
Rob