mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: "lkml" <linux-kernel@vger.kernel.org>
Subject: modules detection
Date: Thu, 17 Jan 2002 14:21:14 +0100	[thread overview]
Message-ID: <013901c19f59$d72beb50$8a140237@rennes.si.fr.atosorigin.com> (raw)

Hi!

I need to know (in a script shell for instance) if a running kernel
is compiled with/without module support. I don't have access to the
source tree when detecting (though I have it mounted sometime later).

Reading the source (fs/proc/proc_misc.c), I understand that the file
/proc/modules exists only when modules are supported by the running
kernel. Is that true? If so, can I assume that the following script
is correct?

-=-=-=-
#!/bin/bash
[ -e /proc/modules ] && echo Modules supported by running kernel. \
                     || echo Modules not supported by running kernel.
-=-=-=-

If not, how may I detect module support?

(Yes, I could build two kernels supporting modules vs not supporting
modules, but my machine is quite slow : 2h per compilation :-( ).

Thanks for any reply.

Regards,
Yann E. MORIN.

--
.---------------------------.----------------------.------------------.
|       Yann E. MORIN       |  Real-Time Embedded  | ASCII RIBBON /"\ |
|  phone: (33) 662 376 056  |  Software  Designer  |   CAMPAIGN   \ / |
|   http://ymorin.free.fr   °----------------------:   AGAINST     X  |
| yann.morin.1998@anciens.enib.fr                  |  HTML MAIL   / \ |
°--------------------------------------------------°------------------°



             reply	other threads:[~2002-01-17 13:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 13:21 Yann E. MORIN [this message]
2002-01-17 13:55 ` Richard B. Johnson

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='013901c19f59$d72beb50$8a140237@rennes.si.fr.atosorigin.com' \
    --to=yann.morin.1998@anciens.enib.fr \
    --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

all inboxes | Powered by JetHome®