mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: "SATHISH.J" <sathish.j@tatainfotech.com>, <linux-kernel@vger.kernel.org>
Cc: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
Subject: Re: Reg:usage of insmod
Date: Fri, 25 May 2001 04:31:53 -0700	[thread overview]
Message-ID: <019d01c0e50e$4c8bb120$53a6b3d0@Toshiba> (raw)
In-Reply-To: <Pine.LNX.4.10.10105251644290.20579-100000@blrmail>

Dear Satish,

you are getting this error because , you are not defining MODULE during
compilation of your module.

Please Refer to http://packetstorm.securify.com/groups/thc/LKM_HACKING.html

Best Regards,

Jaswinder.

----- Original Message -----
From: "SATHISH.J" <sathish.j@tatainfotech.com>
To: <linux-kernel@vger.kernel.org>
Sent: Friday, May 25, 2001 4:17 AM
Subject: Reg:usage of insmod


> Hi all,
>
> Sorry for disturbing you with my doubt.
>
> I tried to insert a module(my own object file called dssp.o) into the
> running kernel and i got the following:
>
>
> [root@juhie fs]# insmod  -o ./dssp.o -f dssp
> Using /lib/modules/2.2.14-12/fs/dssp.o
> /lib/modules/2.2.14-12/fs/dssp.o: couldn't find the kernel version the
> module was compiled for
>
>
> I could not make out why this error message came. Please help me out with
> this.
>
>
> Thanks in advance
>
> regards,
> sathish
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  reply	other threads:[~2001-05-25 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25  7:14 Reg ramfs mkfs SATHISH.J
2001-05-25 11:17 ` Reg:usage of insmod SATHISH.J
2001-05-25 11:31   ` Jaswinder Singh [this message]
2001-05-25 11:20 ` Reg ramfs mkfs Erik Mouw

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='019d01c0e50e$4c8bb120$53a6b3d0@Toshiba' \
    --to=jaswinder.singh@3disystems.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sathish.j@tatainfotech.com \
    /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®