Re: kernel and modules compiling

1999-05-14 Thread Jean-Yves BARBIER
Colin Tree wrote:
 
 Hi,
  try
 make xconfig   ormenuconfig
 make dep ; make clean ; make zImage
 mv  --force  /lib/modules/2.x.x  /lib/modules/2.x.x-old ( if recompiling
 the same version )
 make modules ; make modules_install
 edit lilo if necessary  ( new kernel will be /boot/vmlinuz
 old kernel will be
 /boot/vmlinuz.old  ? )
 make install   ( also creates new boot floppy )
 lilo
 reboot
 modconf  ( set up /etc/modules )
 reboot
 

Why so much?

make xconfig   ormenuconfig
make-kpkg kernel_image
mv  --force  /lib/modules/2.x.x  /lib/modules/2.x.x-old (if recompiling the 
same version) OR rm /lib/modules/2.x.x
cd ..
dpkg -i kernel_image-2.x.x-1.00-i386.deb
reboot

Hop! this is it!

Regards,
JY

-- 
Jean-Yves BARBIER   [EMAIL PROTECTED]
Les choses ne sont pas toujours ce que l'on voudrait qu'elles soient qu'elles 
fussent... P. DAC
Boycott Intel, watch: http://www.bigbrotherinside.com
If you need N components to build your board, you'll ALWAYS have N-1 in stock 
Murphy's law


Re: kernel and modules compiling

1999-05-14 Thread Pollywog

On 13-May-99 Jean-Yves BARBIER wrote:
 mv  --force  /lib/modules/2.x.x  /lib/modules/2.x.x-old (if recompiling the
 same version) OR rm /lib/modules/2.x.x

Why this step?  I guess I don't understand the force part.

thanks

--
Andrew

[PGP5.0 Key ID 0x5EE61C37]



Re: kernel and modules compiling

1999-05-13 Thread J Horacio MG
Hi Alexander,

excuse me for going over this again, but I fear something is going
awfully wrong.

Alexander Schwartz dixit:
~ On Wed, 12 May 1999, J Horacio MG wrote:
~ 
~  ~ I also install the kernel using a small shellprogram provided (you will
~  ~ need to switch that to executable using chmod +x)
~  ~ 
~  ~ The last thing I do is that I run lilo. 
~  ~ 
~  ~ make bzImage
~  ~ make modules
~  ~ # rm -rf /lib/modules/2.2.5 # Only if you are very sure about this!

I did this... well, sort of, just in case I did:
...
make modules
# cd /lib/modules
cp -r 2.0.36/ /tmp
rm -r 2.0.36
cd /usr/src/linux
make modules_install

and to my surprise, it only installed modules/fs/ and modules/net ...
what happened to the rest of the modules?  This is not doing much sense,
but just in case you can help me with it, I send you again the .config
file I'm using.

TIA

Horacio
#
# Automatically generated make config: don't edit
#

#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KERNELD=y

#
# General setup
#
# CONFIG_MATH_EMULATION is not set
CONFIG_NET=y
# CONFIG_MAX_16M is not set
CONFIG_PCI=y
# CONFIG_MCA is not set
CONFIG_SYSVIPC=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M686 is not set
# CONFIG_MTRR is not set
# CONFIG_BIGPHYS_AREA is not set

#
# Floppy, IDE, and other block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_IDE_PCMCIA is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_TRITON is not set
CONFIG_IDE_CHIPSETS=y

#
# Note: most of these also require special kernel boot parameters
#
# CONFIG_BLK_DEV_ALI14XX is not set
# CONFIG_BLK_DEV_DTC2278 is not set
# CONFIG_BLK_DEV_HT6560B is not set
# CONFIG_BLK_DEV_QD6580 is not set
# CONFIG_BLK_DEV_UMC8672 is not set

#
# Additional Block Devices
#
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_DEV_HD is not set

#
# Networking options
#
# CONFIG_FIREWALL is not set
# CONFIG_NET_ALIAS is not set
CONFIG_INET=y
# CONFIG_IP_FORWARD is not set
# CONFIG_IP_MULTICAST is not set
CONFIG_SYN_COOKIES=y
# CONFIG_IP_ACCT is not set
# CONFIG_IP_ROUTER is not set
# CONFIG_NET_IPIP is not set

#
# (it is safe to leave these untouched)
#
# CONFIG_INET_PCTCP is not set
# CONFIG_INET_RARP is not set
# CONFIG_NO_PATH_MTU_DISCOVERY is not set
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y

#
#  
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_AX25 is not set
# CONFIG_NETLINK is not set

#
# SCSI support
#
# CONFIG_SCSI is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_EQUALIZER is not set
# CONFIG_PLIP is not set
CONFIG_PPP=y

#
# CCP compressors for PPP are only built as modules.
#
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
# CONFIG_NET_RADIO is not set
# CONFIG_NET_ETHERNET is not set
# CONFIG_TR is not set
# CONFIG_FDDI is not set
# CONFIG_ARCNET is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# CD-ROM drivers (not for SCSI or IDE/ATAPI drives)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Filesystems
#
CONFIG_QUOTA=y
CONFIG_MINIX_FS=y
# CONFIG_EXT_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_XIA_FS is not set
CONFIG_NLS=y
CONFIG_ISO9660_FS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
# CONFIG_NLS_CODEPAGE_874 is not set
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
CONFIG_NLS_ISO8859_5=m
# CONFIG_NLS_ISO8859_6 is not set
CONFIG_NLS_ISO8859_7=m
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_ISO8859_9 is not set
CONFIG_NLS_KOI8_R=m
CONFIG_PROC_FS=y
CONFIG_NFS_FS=m
CONFIG_SMB_FS=m
CONFIG_SMB_WIN95=y
# CONFIG_HPFS_FS is not set
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=y
# CONFIG_BSD_DISKLABEL is not set
CONFIG_SMD_DISKLABEL=y

#
# Character devices
#
CONFIG_SERIAL=y
# CONFIG_DIGI is not set
# CONFIG_CYCLADES is not set
# CONFIG_STALDRV is not set
# CONFIG_RISCOM8 is not set
# CONFIG_PRINTER is not set
# CONFIG_SPECIALIX is not set
# CONFIG_MOUSE is not set
# 

Re: kernel and modules compiling

1999-05-13 Thread Khalid EZZARAOUI
J Horacio MG wrote:

 Hi Alexander,

 and to my surprise, it only installed modules/fs/ and modules/net ...
 what happened to the rest of the modules?  This is not doing much sense,
 but just in case you can help me with it, I send you again the .config
 file I'm using.

 TIA

 Horacio

   

configName: config
  Type: Plain Text (text/plain)

perhaps you set the option in the kernel config that says to not compil modules
that don't change.
(this option set the version of your kernel in modules)


Re: kernel and modules compiling

1999-05-13 Thread Colin Tree
Hi,
 try
make xconfig   ormenuconfig
make dep ; make clean ; make zImage
mv  --force  /lib/modules/2.x.x  /lib/modules/2.x.x-old ( if recompiling
the same version )
make modules ; make modules_install
edit lilo if necessary  ( new kernel will be /boot/vmlinuz
old kernel will be
/boot/vmlinuz.old  ? )
make install   ( also creates new boot floppy )
lilo
reboot
modconf  ( set up /etc/modules )
reboot

 I just recompiled kernel 2.0.36, and everything seems to work fine
 except for the following messages during boot up (same with modprobe).
 pon seems to be working ok so, what does all this mean?

 :~# modprobe ppp.o
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol netif_rx_R88a5d1d7
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol
 unregister_netdev_R83363374
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol dev_close_R314d8913
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol n_tty_ioctl_Rd58a4d14
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol kill_fasync_R1e36b960
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol dev_alloc_skb_Rd29823b6
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol dev_kfree_skb_R13582d30
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol
 tty_register_ldisc_Rc1106c2e
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol
 register_netdev_Re4ba25d3

 If it helps, I include the .config file.

 Another message I used to get with the default kernel (also with the new
 compiled kernel) during bootup is:

 lspci not found so PCI conflict not checked

 I'm afraid I don't quite understand the way modules work.  If I make
 `lsmod' I still see the module pcmcia_core, which I didn't select;
 earlier I had modules bsd_comp, ppp [bsd_comp](1), and slhc [slip ppp],
 whereas now I just have bsd_comp and slhc [slip].

 Is there anything else I should do after:
 make mrproper
 make config
 make dep
 make clean
 make zImage
 make modules
 make modules_install?


--

Cheers,
Colin Tree






Re: kernel and modules compiling

1999-05-12 Thread J Horacio MG
~ I also install the kernel using a small shellprogram provided (you will
~ need to switch that to executable using chmod +x)
~ 
~ The last thing I do is that I run lilo. 
~ 
~ make bzImage
~ make modules
~ # rm -rf /lib/modules/2.2.5 # Only if you are very sure about this!

I wondered whether that could / should be done.  The prob here is that
you won't be able to run any other previous kernel, just the new
compiled one.

~ make modules_install
~ depmod -a 
~ cd arch/i386/boot
~ ./install.sh 2.2.5 bzImage ../../../System.map /

that script is just to copy the image to /boot/vmlinux-x.x.x and
System.map?  or does it also add the lines to lilo.conf?

~ lilo

Horacio


Re: kernel and modules compiling

1999-05-12 Thread Alexander Schwartz
On Wed, 12 May 1999, J Horacio MG wrote:

 ~ I also install the kernel using a small shellprogram provided (you will
 ~ need to switch that to executable using chmod +x)
 ~ 
 ~ The last thing I do is that I run lilo. 
 ~ 
 ~ make bzImage
 ~ make modules
 ~ # rm -rf /lib/modules/2.2.5 # Only if you are very sure about this!
 
 I wondered whether that could / should be done.  The prob here is that
 you won't be able to run any other previous kernel, just the new
 compiled one.

Well, that's probably right if you want to use several versions of one
kernel. I've nevery tried that. I am running only one version of a kernel,
and as a backup I have an older kernel version. My lilo.conf looks like
this:

image=/boot/vmlinuz-2.2.5
  label=Linux2.2.5

image=/boot/vmlinuz-2.2.1
  label=Linux2.2.1

image=/boot/vmlinuz-2.0.34
  label=Linux2.0.34
  append=mem=128M
 
 ~ make modules_install
 ~ depmod -a 
 ~ cd arch/i386/boot
 ~ ./install.sh 2.2.5 bzImage ../../../System.map /
 
 that script is just to copy the image to /boot/vmlinux-x.x.x and
 System.map?  or does it also add the lines to lilo.conf?

Well, actually this script calls only installkernel, see man
installkernel: 

   The  new kernel is installed into /boot/vmlinuz-{version},
   a link is made from /boot/vmlinuz to the new  kernel,  and
   the   previously   installed   kernel   is   available  as
   /boot/vmlinuz.old.  If you use LILO, /etc/lilo.conf should
   contain   entries   for   the   images  /boot/vmlinuz  and
   /boot/vmlinuz.old.  ({version} is the  new  kernel's  verĀ­
   sion.)

Alex.

-- 
Alexander Schwartz ([EMAIL PROTECTED])
http://ourworld.compuserve.com/homepages/alex_schwartz


kernel and modules compiling

1999-05-11 Thread J Horacio MG
I just recompiled kernel 2.0.36, and everything seems to work fine
except for the following messages during boot up (same with modprobe).
pon seems to be working ok so, what does all this mean?

:~# modprobe ppp.o
/lib/modules/2.0.36/net/ppp.o: unresolved symbol netif_rx_R88a5d1d7
/lib/modules/2.0.36/net/ppp.o: unresolved symbol
unregister_netdev_R83363374
/lib/modules/2.0.36/net/ppp.o: unresolved symbol dev_close_R314d8913
/lib/modules/2.0.36/net/ppp.o: unresolved symbol n_tty_ioctl_Rd58a4d14
/lib/modules/2.0.36/net/ppp.o: unresolved symbol kill_fasync_R1e36b960
/lib/modules/2.0.36/net/ppp.o: unresolved symbol dev_alloc_skb_Rd29823b6
/lib/modules/2.0.36/net/ppp.o: unresolved symbol dev_kfree_skb_R13582d30
/lib/modules/2.0.36/net/ppp.o: unresolved symbol
tty_register_ldisc_Rc1106c2e
/lib/modules/2.0.36/net/ppp.o: unresolved symbol
register_netdev_Re4ba25d3


If it helps, I include the .config file.

Another message I used to get with the default kernel (also with the new
compiled kernel) during bootup is:

lspci not found so PCI conflict not checked

I'm afraid I don't quite understand the way modules work.  If I make
`lsmod' I still see the module pcmcia_core, which I didn't select;
earlier I had modules bsd_comp, ppp [bsd_comp](1), and slhc [slip ppp],
whereas now I just have bsd_comp and slhc [slip].

Is there anything else I should do after:
make mrproper
make config
make dep
make clean
make zImage
make modules
make modules_install?

Thank You in Advance

Horacio
#
# Automatically generated make config: don't edit
#

#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KERNELD=y

#
# General setup
#
# CONFIG_MATH_EMULATION is not set
CONFIG_NET=y
# CONFIG_MAX_16M is not set
CONFIG_PCI=y
# CONFIG_MCA is not set
CONFIG_SYSVIPC=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
# CONFIG_M386 is not set
# CONFIG_M486 is not set
CONFIG_M586=y
# CONFIG_M686 is not set
# CONFIG_MTRR is not set
# CONFIG_BIGPHYS_AREA is not set

#
# Floppy, IDE, and other block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=y
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_IDE_PCMCIA is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_TRITON is not set
CONFIG_IDE_CHIPSETS=y

#
# Note: most of these also require special kernel boot parameters
#
# CONFIG_BLK_DEV_ALI14XX is not set
# CONFIG_BLK_DEV_DTC2278 is not set
# CONFIG_BLK_DEV_HT6560B is not set
# CONFIG_BLK_DEV_QD6580 is not set
# CONFIG_BLK_DEV_UMC8672 is not set

#
# Additional Block Devices
#
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_DEV_HD is not set

#
# Networking options
#
# CONFIG_FIREWALL is not set
# CONFIG_NET_ALIAS is not set
CONFIG_INET=y
# CONFIG_IP_FORWARD is not set
# CONFIG_IP_MULTICAST is not set
CONFIG_SYN_COOKIES=y
# CONFIG_IP_ACCT is not set
# CONFIG_IP_ROUTER is not set
# CONFIG_NET_IPIP is not set

#
# (it is safe to leave these untouched)
#
# CONFIG_INET_PCTCP is not set
# CONFIG_INET_RARP is not set
# CONFIG_NO_PATH_MTU_DISCOVERY is not set
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y

#
#  
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_AX25 is not set
# CONFIG_NETLINK is not set

#
# SCSI support
#
# CONFIG_SCSI is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_EQUALIZER is not set
# CONFIG_PLIP is not set
CONFIG_PPP=y

#
# CCP compressors for PPP are only built as modules.
#
CONFIG_SLIP=m
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
# CONFIG_SLIP_MODE_SLIP6 is not set
# CONFIG_NET_RADIO is not set
# CONFIG_NET_ETHERNET is not set
# CONFIG_TR is not set
# CONFIG_FDDI is not set
# CONFIG_ARCNET is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# CD-ROM drivers (not for SCSI or IDE/ATAPI drives)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Filesystems
#
CONFIG_QUOTA=y
CONFIG_MINIX_FS=y
# CONFIG_EXT_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_XIA_FS is not set
CONFIG_NLS=y
CONFIG_ISO9660_FS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
# CONFIG_NLS_CODEPAGE_874 is not set
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
# CONFIG_NLS_ISO8859_3 is not set
# 

Re: kernel and modules compiling

1999-05-11 Thread Alexander Schwartz
Hi Horacio,

I usually clean my module directory before I reinstall the the kernel
modules to get rid of old stuff in there. But beware: If you are using
PCMCIA or VMWARE, you will need to reinstall the PCMCIA and VMWARE
modules.

After I install my modules using make modules_install I run

  depmod -a

This tells modprobe which modules depend on each other.

I also install the kernel using a small shellprogram provided (you will
need to switch that to executable using chmod +x)

The last thing I do is that I run lilo. 

My procedure: 

make bzImage
make modules
# rm -rf /lib/modules/2.2.5 # Only if you are very sure about this!
make modules_install
depmod -a 
cd arch/i386/boot
./install.sh 2.2.5 bzImage ../../../System.map /
lilo
 
Alex.

On Tue, 11 May 1999, J Horacio MG wrote:

 I just recompiled kernel 2.0.36, and everything seems to work fine
 except for the following messages during boot up (same with modprobe).
 pon seems to be working ok so, what does all this mean?
 
 :~# modprobe ppp.o
 /lib/modules/2.0.36/net/ppp.o: unresolved symbol netif_rx_R88a5d1d7
 
 Is there anything else I should do after:
 make mrproper
 make config
 make dep
 make clean
 make zImage
 make modules
 make modules_install?

-- 
Alexander Schwartz ([EMAIL PROTECTED])
http://ourworld.compuserve.com/homepages/alex_schwartz


kernel and modules compiling

1998-10-10 Thread zhaoway
Hello Debian-user,

  20 minutes ago, I did a re-compile of the kernel and modules.
  I'm  new  to debian, have played with Linux for more than
  half a year. Somebody had just talking about kernel compiling
  here in this list: Is this easy enough?

  O.K., my experience:

  Following the instructions of README in /usr/src/linux,
  compiling the kernel is easy. Even with make config,
  since there're lot of '?'s, and my box, except the sound card,
  is very normal, config is not difficult. And make dep; make;
  cp .. /boot/.., all are very straight. Documented very well.

  But then modules. Following modules.txt, make modules, make
  modules_install are ok..

  Then reboot: a lot of unresolved .!
  In fact, I've experienced this, so I went to /lib/modules/...
  did a depmod -a. My question is why this is not documented in
  the modules.txt? It only says depmod -a is need in init script.
  But seems this is not the case in my box.(?) I need do this
  right after modules installed.

  Then reboot: linear and char-major-10 and net-pf-5 trouble!
  I must say I'm an accomplished guesser 8), I went to /etc,
  do a ls, guess on the file names, bingo! vi modules,
  comment linear; vi conf.modules
  Guess again (with help of comments), uncomment net-pf-5,
  add a char-major-10 off. I must say I do not understand
  even one bit of this file. But my guess works! Hehe,
  My question again: why not documented?
  I know this surely's been documented somewhere since it's
  very important. But I'd like to see it in the modules.txt
  or modules.Debian.txt 'cause that's why I will look
  for the answer when compiling kernel and modules and encountering
  problems. I do not think I should read all of the
  man pages and info pages before I could say that I do not want
  that 700k kernel and want a 300k one. At least a link,
  like in the README says when do modules, read modules.txt,
  right?

  It's clear, hence easy, but not enough.

Best regards,
 Zhaoway  mailto:[EMAIL PROTECTED]


Re: kernel and modules compiling

1998-10-10 Thread Dave Swegen
On Sun, Oct 11, 1998 at 01:20 +0800, zhaoway wrote:
   My question again: why not documented?
   I know this surely's been documented somewhere since it's
   very important. But I'd like to see it in the modules.txt
   or modules.Debian.txt 'cause that's why I will look
   for the answer when compiling kernel and modules and encountering
   problems. I do not think I should read all of the
   man pages and info pages before I could say that I do not want
   that 700k kernel and want a 300k one. At least a link,
   like in the README says when do modules, read modules.txt,
   right?
 
   It's clear, hence easy, but not enough.

Well done, you have passed the secret test :) Seriously though, it is a
very valid point - I found out purely by accident what to do. These sort
of blatant omissions are not good...

Cheers
Dave