netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: netdev@oss.sgi.com
Subject: Fw: [Bugme-new] [Bug 3777] New: tun driver fails to open when built in, must be modular
Date: Fri, 19 Nov 2004 15:08:08 -0800	[thread overview]
Message-ID: <20041119150808.578154d3.akpm@osdl.org> (raw)



Begin forwarded message:

Date: Fri, 19 Nov 2004 14:19:35 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 3777] New: tun driver fails to open when built in, must be modular


http://bugme.osdl.org/show_bug.cgi?id=3777

           Summary: tun driver fails to open when built in, must be modular
    Kernel Version: 2.6.10-rc2
            Status: NEW
          Severity: normal
             Owner: jgarzik@pobox.com
         Submitter: bill@crowellsystems.com


Distribution: slackware/mfxlinux
Hardware Environment:i386
Software Environment:
Problem Description: kernel will not assign/open a tun device when tun.o is
compiled as a built-in. ifconfig gives 'unable to open /dev/net/tun' error.
compiling as a module fixes.

Steps to reproduce:
Compile kernel with tun/tap device driver as a built-in. Run ifconfig to see
error. recompile as a module, modprobe tun and run ifconfig - no error.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

             reply	other threads:[~2004-11-19 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 23:08 Andrew Morton [this message]
2004-11-20  5:27 ` Fw: [Bugme-new] [Bug 3777] New: tun driver fails to open when built in, must be modular Michael Renzmann
2004-11-20  5:32   ` Fw: [Bugme-new] [Bug 3777] New: tun driver fails to open whenbuilt " shemminger

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=20041119150808.578154d3.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).