public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marvin Stodolsky <stodolsk@rcn.com>
To: kaos@ocs.com.au, linux-kernel@vger.kernel.org
Subject: build -->/usr/src/linux
Date: Sun, 08 Apr 2001 09:47:06 -0500	[thread overview]
Message-ID: <3AD079EA.50DA97F3@rcn.com> (raw)

MODULE SUPPORT [GENERAL], KMOD
P:      Keith Owens
M:      kaos@ocs.com.au
L:      linux-kernel@vger.kernel.org
============================================

Though I've done some rational searching through the Documetation,
an explanation hasn't manifested, as to why there has appeared in the
2.4.nn   ??????:


# ls -l /lib/modules/2.4.3/
total 24
lrwxrwxrwx    1 root     root  ???????   20 Apr  2 17:00 build ->
/usr/src/linux-2.4.3
drwxr-xr-x    6 root     root         1024 Apr  2 17:00 kernel
-rw-r--r--    1 root     root         4725 Apr  8 08:06 modules.dep
-rw-r--r--    1 root     root           31 Apr  8 08:06
modules.generic_string
-rw-r--r--    1 root     root         4388 Apr  8 08:06
modules.isapnpmap
-rw-r--r--    1 root     root           29 Apr  8 08:06
modules.parportmap
-rw-r--r--    1 root     root         8723 Apr  8 08:06 modules.pcimap
-rw-r--r--    1 root     root         1317 Apr  8 08:06 modules.usbmap
lrwxrwxrwx    1 root     root           35 Apr  2 17:05 pcmcia ->
/lib/modules/2.4.3-oldpcmcia/pcmcia

-----------
Could someone enlighten me?  What is it necessary for?

It's presence has required some gymnastics, per below, during module
installation for the Winmodem driver, ltmodem.o requiring a subsequent
"depmod -a"

MarvS
===========================================================
from the module install script  ./ltinst

# To avoid non-relevant complaint noise that would be generated during
#    depmod -a   within update-modules
# under 2.4.nn kernels due to the symbolic Link
#   /lib/modules/2.4.nn/build --> /usr/src/linux
# if kernel-source "make clean" is run betweem build_module & 
#   ltinst (install ltmodem.o in the /lib/modules/  tree)
# The Link is moved to  /tmp and after "update-modules" is  restored.
if [ -L /lib/modules/$SYS/build ]; then
mv /lib/modules/$SYS/build /tmp
fi

# Updating module dependancies
if [ -f /etc/modutils/aliases ]; then
update-modules
else
depmod -a
fi

# Restoring build link if any
if [ -L /tmp/build ]; then
mv /tmp/build /lib/modules/$SYS/
fi

             reply	other threads:[~2001-04-08 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9aqmgo$8f6ol$1@fido.engr.sgi.com>
2001-04-08 14:47 ` Marvin Stodolsky [this message]
2001-04-08 15:16   ` build -->/usr/src/linux Russell King
2001-04-08 17:30     ` Marvin Stodolsky
2001-04-08 21:49       ` Miquel van Smoorenburg
2001-04-08 23:01         ` Jamie Lokier
2001-04-09 11:29           ` Miquel van Smoorenburg
2001-04-09 15:02             ` Jamie Lokier
2001-04-09 23:01       ` richard offer
2001-04-10 14:08         ` Jamie Lokier
2001-04-10 16:36           ` richard offer
2001-04-10 16:42             ` Jamie Lokier
2001-04-10 16:52               ` richard offer
2001-04-10 17:04                 ` Jamie Lokier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AD079EA.50DA97F3@rcn.com \
    --to=stodolsk@rcn.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox