[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: samba and NFS support (was: Re: from Corel: may we help?)
From:       aleXXX <alexander.neundorf () rz ! tu-ilmenau ! de>
Date:       1999-11-26 12:51:10
[Download RAW message or body]

On Fr, 26 Nov 1999, Nicolas Brodu wrote:
> aleXXX wrote:

> Hmmm, smb and NFS are not the same. I used to access the same host using both
> protocols, with different shares.

Yes, of course, I don't see the problem.
I took the name of the samba shares as they are, and for the NFS exports
I took the path of the export and replaced the '/' with a special sign (I used
a '+'), cause '/' in filenames only cause problems.

so a samba share "public" would become
~/network/host/public
a NFS-export /public would become
~/network/host/+public 

> For smb, at present the solution for transparency is to consider everything
> as directories (wheter workgroup, share lists, or real directories).
> ex: smb://workgroup will return the members
> smb://[workgroup/]host will return the shares (workgroup optional)
> smb://[workgroup/]host/share/dir/file gets the file

Yes, me too.

I thouhgt something like this:
LAN:// returns the workgoups, or maybe nothing, looks a bit strange
LAN://workgroup returns the members
LAN://workgroup/host returns the shares, exports, volumes
LAN://workgroup/host/share mounts the
(samba-share|NFS-export|Novell-volume|whatever) and returns the contents of the
mounted directory.

> That could just be the solution for NFS, but for SMB I think this introduces too
> much overhead. In this case, sending different packet types to the different
> servers will give you those informations. Then, they are cached in memory
> instead of a temporary tree on disk.

I don' t understand what you mean exactly with overhead.
Mounting wouldn't take space on disk and makes it accessible for every app,
let's say Xemacs or Xv or xmms or StarOffice or ....

> > Should I stay this way or do it the other way (then I must switch to smblib)
> 
> As libsmb author, my point of view might not be objective. What I think, though,
> is that if you have a better solution than libsmb then you can 
> either:
> . Put it into KDE directly. This would be better for the users.
> .. Merge our works.

Yes.

This is what my stuff can do:

Find hosts:
-----------
-in "normal" LAN's (what is normal ?)
-in NT-domains
-in LAN's without samba/windows
-in LAN's with different workgroups
-in LAN's without working DNS
-in LAN's with DHCP
-in LAN's with different DNS/WINS-names (or am I mixing up the names, I think
you know what I mean)
-maybe NovellNetware servers (never tested, but source included)


Find shares:
---------
-if configured and used correctly in all of the above cases with samba<2.0.6
(samba shares, NFS if user==root, maybe Novell volumes)


Mounting shares:
------------
-as above


Problems:
-------
-smbmount only exists for linux, 
maybe mounting for linux and your stuff on other systems ?

-at the moment I can't detect if smbmount/smbclient asks for a
password, so the user must know before he does something wether a password is
required. Yesterday I got a good hint from the author of kdesu, so this
will be solved.

-depends on the syntax of the samba tools, maybe
smbclient/smbmount -h could be parsed in a _very_ clever way ?
For kNetmon this is not so important (it is not so hard to update), but if it
is an ioslave it must be relyable (or would it be possible to update a single
ioslave in KDE 2 ?) 

-configuration is a bit complicated


What I would like to have:
------------------
-some code to find the master of a workgroup
-some code to find the workgroups
-some code to check if a password is required
-some code to check if it is a NT-domain

Please mail me what your stuff can do.
Is it for KDE 1.x or 2 ?

> Problem for me is that I have great difficulty to access SMB networks from 
> here. I'm no longer in the environment where I started to code the lib, and
> cannot work on KDE2 directly (have to transfer everything on floppy and compile
> at home, offline).

Hmm, me too.
At the moment I am at a practical training (Praktikum) at the DLR
(http://www.dlr.de) for one term, and here I have access to a LAN from Solaris
2.6 with KDE 1.1.2 (I convinced them :-) ) and samba 1.9.18.
So here I definitely won't be able to try KDE 2 -stuff.
The thing with the floppies is the same for me.
In december I will update to egcs, then I can install Krash, and from april I
will have access to a LAN at home.
So it is a bit difficult for me at the moment too.

What I could do at the moment is try to make a KDE-ioslave from my code, at
first for KDE 1.x, only to see how it works at all.

Bye
Alex

[prev in list] [next in list] [prev in thread] [next in thread]