From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "R. Engür Pişirici" <engur@bilkent.edu.tr>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: a specific question...
Date: Sun, 16 Dec 2018 10:32:42 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1812161031370.22396@localhost.localdomain> (raw)
In-Reply-To: <c11d97374ccecb92e9c7291810c3d449@bilkent.edu.tr>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Sun, 16 Dec 2018, R. Engür Pişirici wrote:
> Hello All,
>
> Before starting to ask my question, I would like to apologize about
> asking a silly question. Mostly, i always try to find answers by
> reading, searching, digging, etc. However, i really couldnt find a
> proper answer for my question.
>
> My question is about l2tp/pptp drivers in kernel. pptp driver is in
> /drivers/net. But, l2tp driver is in /net I want to know why they
> reside in different paths? What did i miss?
typically, what you find under /net is code for general networking
*protocols*, while drivers/net contains actual device drivers for
physical devices. sometimes, the split is not perfect.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-12-16 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9d7f9b8b02ac6b219403bb448a53a950@bilkent.edu.tr>
2018-12-16 15:24 ` a specific question R. Engür Pişirici
2018-12-16 15:32 ` Robert P. J. Day [this message]
2018-12-17 8:59 ` Ozgur
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=alpine.LFD.2.21.1812161031370.22396@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=engur@bilkent.edu.tr \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).