[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: viewing/editing files at SMB locations



> Thanks for the info. I guess it's just me then ;)

Well - we all start out knowing little to nothing ;)  Anyway, I guess if you
expected everything to look like it does in windows, I can see why you might
get a little confused.

> I am not familiar with SMB or Samba at all. Could you possibly
> give me the guidelines for setting up an smbmount? I am not sure
> how the whole process works ...

Easiest way is: man smbmount
If you already know how to use a windows share without using smbmount (ie.
using smbclient) then it's not much of a difference. Actually, you could
mount using "mount" instead of smbmount, but smbmount makes it easy to do
non-root mounts of shares. But it doesn't prevent you from using /etc/fstab
to specify permanent smb mount points.

If you don't use PDC functionality, and just have public accessible shares,
smbmount is straight forward: smbmount //server/share /mnt/point.
However, if you need to specify usernames etc. you solve that either using
smbusers or using the -o parameters (which you'll find in the man page).

Best Regards
  Peter Larsen

> On Thu, 2003-10-16 at 20:32, Peter Larsen wrote:
> > > It seems as though the various programs I use to view/edit
> > > files, such as Gedit or Vi, are not able to view or access files
> > > at SMB locations. Can anyone recommend a good editor that can
> > > both view and edit text files and RTF files at SMB locations?
> >
> > Hmmm - I access several windows networks from several of my linux boxes,
and
> > never saw that problem?  What I do is smbmount the shares I need, and
from
> > then on, I never think of the data/files being on a windows network,
linux
> > or anything else. It's just a cd away, and all my programs sees the
files as
> > "usual".
> >
> > Only windows (to my knowledge) has the idea of you needing to specify
the
> > physical aspect of a resource location. I like the way Unix has done
this
> > from the get-go - you don't care if your data is on one huge disk,
several
> > small ones, networked, memory based etc. - they are all part of the same
> > logical structure. It's up to the drivers to find out what to do - not
the
> > application developer/user.
> >
> > Best Regards
> >   Peter Larsen




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]