public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: f5ibh <f5ibh@db0bm.ampr.org>
To: kaos@ocs.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: msg : cannot create ksymoops/nnnnn.ksyms
Date: Mon, 8 Jan 2001 23:30:12 +0100	[thread overview]
Message-ID: <200101082230.XAA13551@db0bm.ampr.org> (raw)

Hi Keith,
>> NET4: Unix domain sockets 1.0 for Linux NET4.0.
>> insmod: /lib/modules/2.2.19pre6/misc/unix.o: cannot create
> /var/log/ksymoops/20010106112242.ksyms Read-only file system

> man insmod, look for /var/log/ksymoops.  If you define this directory
> then it is expected to be writable when modules are loaded.  Logging
> module data for ksymoops is a user selectable option, you have to
> decide to use it, and you have done so.

Ok, I knew that, the problem is why unix.o is loaded so early ? I've not found
where it is requested / loaded (I've kmod enabled). 

>> insmod:/lib/modules/2.4.0/kernel/net/unix/unix.o : insmod net-pf-1 failed.

> "alias net-pf-1 unix" is a built in alias.  Looks like you did not
> compile for Unix sockets and something in the kernel wants Unix
> sockets.  If you really do not want Unix sockets, "alias net-pf-1 off".

This was a configuration error. I had missed a configuration step. Thank you.

----
Thank you and best regards

		Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-08 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 22:30 f5ibh [this message]
2001-01-08 22:58 ` msg : cannot create ksymoops/nnnnn.ksyms Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-01-06 11:43 f5ibh
2001-01-06 12:37 ` Keith Owens

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=200101082230.XAA13551@db0bm.ampr.org \
    --to=f5ibh@db0bm.ampr.org \
    --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