add xfs support as a module?

add other sound cards and NIC card modules

should this build a normal vmlinuz or bzImage kernel?

should this use LINUX_VERSION or PKGVERSION in PLIST?

make sure ownership of modules is root (see makefile for -r switch)

why were modules/2.4.22/modules.usbmap
modules/2.4.22/modules.generic_string
modules/2.4.22/modules.parportmap
modules/2.4.22/modules.pnpbiosmap
modules/2.4.22/modules.isapnpmap
modules/2.4.22/modules.dep
modules/2.4.22/modules.ieee1394map
modules/2.4.22/modules.pcimap
files touched too? (2.4.22 files touch on a 2.6.x install)

if [ -r System.map ]; then /usr/sbin/depmod -ae -F System.map  2.6.3; fidepmod: *** Unresolved symbols in /lib/modules/2.6.3/kernel/drivers/message/i2o/i2o_config.ko

depmod:         i2o_post_this
depmod: *** Unresolved symbols in /lib/modules/2.6.3/kernel/drivers/net/ppp_generic.ko
depmod:         slhc_init

FATAL: ldconfig must be used with "||${TRUE}".
(that is bug in pkglint.)

make sure gcc exists (see very bottom of Makefile)

thread about missing stdarg.h
 http://www.ussg.iu.edu/hypermail/linux/kernel/0209.3/1015.html
For time being I run kernel make like this:
   GCC_EXEC_PREFIX=/usr/app/gcc/lib/gcc-lib/ make

make package for linux-kernel-headers too
 ${MAKE} include/linux/version.h
glibc provides its own <net/*> and <scsi/*> header files to replace them
so just include/asm and include/linux

message to suggest running lilo if using LILO

maybe dynamically figure out modules for PLIST

LOCALBASE should be / for PLIST to be right
(need to use LOCLABASE for the install part too.)

should install .config file too; for example:
Knoppix kernel-headers-2.4.22-xfs_10.00.Custom_i386.deb
ar p ../kernel-headers-2.4.22-xfs_10.00.Custom_i386.deb data.tar.gz | tar zxf -
and found usr/src/kernel-headers-2.4.22-xfs/.config

try to just install headers with make config followed by make include/linux/version.h

copy certain directories from include to /usr/include

look at default /boot/config-2.2.20-idepci

# cp -i arch/i386/boot/bzImage /bzImage.-- with kernel-version- or other name
#   maybe copy to boot directory (as lilo also knows it)

- This package has known vulnerabilities, please investigate and fix
  if possible. (see: CVE-2008-1375, CVE-2008-1675, CVE-2008-1669,
  CVE-2008-1615, CVE-2008-1375, CVE-2008-0007, CVE-2007-6282,
  CVE-2005-0504, CVE-2008-1673, CVE-2008-2750, CVE-2008-2812,
  CVE-2008-3077, CVE-2008-3247, CVE-2008-3276, CVE-2008-3686,
  CVE-2008-1514, CVE-2008-3831, CVE-2008-5025, CVE-2009-0029,
  http://secunia.com/advisories/30258/, CVE-2008-3272, CVE-2008-3275,
  CVE-2008-3534, CVE-2008-4410, CVE-2008-4933, CVE-2008-4934,
  CVE-2008-5029, CVE-2008-5134, CVE-2008-3528, CVE-2008-4395,
  CVE-2008-5079, CVE-2008-5300, CVE-2008-5395, CVE-2009-0031,
  CVE-2009-0834, CVE-2009-0835, CVE-2009-1184, CVE-2009-1192,
  CVE-2009-1265, CVE-2009-1337, CVE-2009-1385, CVE-2009-1439,
  CVE-2009-1633, CVE-2009-1895, CVE-2009-1897, CVE-2009-2287,
  CVE-2009-2692, CVE-2009-3002, http://secunia.com/advisories/33656/,
  http://secunia.com/advisories/33938/,
  http://secunia.com/advisories/34033/,
  http://secunia.com/advisories/33977/,
  http://secunia.com/advisories/35127/,
  http://bugzilla.kernel.org/show_bug.cgi?id=12430, SA36200, SA35985,
  SA36136, SA35983, SA36617, SA36891, SA36707, CVE-2009-3547,
  CVE-2009-1298, CVE-2009-4131, CVE-2009-4308, CVE-2009-4307,
  CVE-2009-3939, CVE-2009-4020, CVE-2009-4141, CVE-2010-0006,
  CVE-2010-0007, SA38718, SA38594, SA39297, SA39344, CVE-2010-2524,
  CVE-2010-2954, CVE-2010-2955, CVE-2010-2960, CVE-2010-2962
  CVE-2010-3081, CVE-2010-3301, SA41440, SA42354, SA42365, CVE-2011-1083,
  CVE-2011-1180, CVE-2017-6874).
  --- I say there are now too many to enumerate... how about we save
  --- time and say this package needs to be updated to a known current
  --- secure version of the linux kernel and stop adding to this list?