public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: Nico Schottelius <nico-kernel@schottelius.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-net@vger.kernel.org, underley@underley.eu.org
Subject: Re: [BUG] 2.6.0test7 & test4: tun.o (devfs)
Date: Tue, 14 Oct 2003 09:53:24 +0200	[thread overview]
Message-ID: <1066118003.482.5.camel@slurv> (raw)
In-Reply-To: <20031013214835.GA8006@schottelius.org>

On Mon, 2003-10-13 at 23:48, Nico Schottelius wrote:
> Hello!
> 
> When loading tun.o in test7 and test4 it does not create /dev/net/tun.
> I am not familar with the devfs_create_device() call, so I cannot
> currently see what's wrong where. But I think tun.o should create the device..

It creates /dev/misc/net/tun, IIRC.

-- 
Mvh,
André Tomt
andre@tomt.net


  reply	other threads:[~2003-10-14  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 21:48 [BUG] 2.6.0test7 & test4: tun.o (devfs) Nico Schottelius
2003-10-14  7:53 ` Andre Tomt [this message]
2003-10-14  7:57   ` Nico Schottelius

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=1066118003.482.5.camel@slurv \
    --to=andre@tomt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=nico-kernel@schottelius.org \
    --cc=underley@underley.eu.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