mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Jean-Eric Cuendet <jean-eric.cuendet@linkvest.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMB browser
Date: 01 Sep 2002 14:47:47 +0300	[thread overview]
Message-ID: <1030880868.31922.44.camel@gby.benyossef.com> (raw)
In-Reply-To: <3D709AB7.705@linkvest.com>

On Sat, 2002-08-31 at 13:30, Jean-Eric Cuendet wrote:
> Hi,
> I want to develop a filesystem driver. It will be able to access SMB 
> shares without mountnig.
> I'll do a daemon that use libsmbclient from Samba 3.0 that do all the 
> dirty stuff (getting the available domains, authenticating, getting 
> files, etc...) and a device driver that will be a filesystem driver. The 
> driver should communicate with the daemon to ask him about shares, 
> machines, domains, etc...

People who reinvent the wheel usually end up making it square. 


> 
> The idea is:
> - the daemon should be started by "/etc/init.d/browser start" at beginning
> - The daemon loads the driver into the kernel
> - The daemon then mounts the filesystem on /smb using the filesystem 
> provided by the driver
> - The driver waits for file requests on /smb to serve them
> The hierarchy will be :
> 
> /smb --|-- WG1  --|-- Machine1 --|-- Share1
>        |          |              |-- Share2
>        |          |-- Machine2 --|-- Share1
>        |                         |-- Share2
>        |                         |-- Share3
>              |
>        |-- WG2  --|-- Machine3 --|-- Share1
>        |-- DOM1 --|-- Machine4 --|-- etc...
>        |-- DOM2 --|-- Machine5
> 
> Then the user access /smb/WG2/Machine38/Share12/Dir1/File2
> Cool, no?
> 
> The authentication is done externally from the kernel, by a userland 
> process or PAM (a kerberos ticket is gotten from the Domain controller 
> or Samba PDC). Then the daemon uses that info to authenticate in the 
> domain. If no auth info is available, then it's authenticated as Guest.
> 
> My question:
> what is the best/easy way to make a kernel driver communicate with 
> userland? Is it via UNIX socket? Or ioctl? Shared memory? Else?
> 
> Thanks for any idea.
> -jec
> 
> 
> 
> -
> 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/
-- 
Gilad Ben-Yossef <gilad@benyossef.com>
http://benyossef.com

"Money talks, bullshit walks and GNU awks."
  -- Shachar "Sun" Shemesh, debt collector for the GNU/Yakuza


  parent reply	other threads:[~2002-09-01 11:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-31 10:30 Jean-Eric Cuendet
2002-08-31 11:31 ` Lionel Bouton
2002-08-31 19:23   ` Jean-Eric Cuendet
2002-08-31 23:26     ` Daniel Bruce Lynes
     [not found] ` <20020831103928.B140@alexis.itd.umich.edu>
2002-08-31 20:01   ` Jean-Eric Cuendet
2002-09-01 11:47 ` Gilad Ben-Yossef [this message]
2002-09-01 11:49 ` Gilad Ben-Yossef

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=1030880868.31922.44.camel@gby.benyossef.com \
    --to=gilad@benyossef.com \
    --cc=jean-eric.cuendet@linkvest.com \
    --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

all inboxes | Powered by JetHome®