hi ya
I don't understand the problem here... but are you guys
trying to get the Network neighborhood to show the linux boxes ??
( guessing not )
linux boxes should easilily be able to see the Windows Boxes
linux# ls -la /smb/Windows_boxes/....
Using some of the examples here, and assuming the Windows have
shares that linux can see...
Mail_Server
/etc/exports
/var/spool/mail *.your_domain.com(rw)
/etc *.your_domain.com(ro)
Home_Server
/etc/exports ( watch out for rootsquash -- add ro,no_root_squash if you dare )
/etc *.your_domain.com(ro)
#
/home/tom tom_machine.your_domain.com(rw)
/home/dick dick_machine.your_domain.com(rw)
/home/harry harry_machine.your_domain.com(rw)
Linux Client:
/etc/smb.conf
#
# configure some path to export to WinNT...
# ( put at the bottom of smb.conf )
#
[Export_to_NT]
path = /usr2/Web_Pages
browseable = yes
; read only = no
writable = yes
/etc/auto.master
/smb /etc/auto.smb
/etc/auto.sbm
mail -fstype=nfs Mail_Server:/var/spool/mail
home -fstype=nfs Home_Server:/home
#
WinNT -fstype=smbfs,login=Administrator,passwd=xxx WinNT:/C
Win98 -fstype=smbfs,login=Administrator,passwd=xxx Win98:/C
Win95 -fstype=smbfs,login=Administrator,passwd=xxx Win95:/C
To see the various mailboxes
linux# ls -la /smb/mail/*
To see the various home dirs
linux# ls -la /smb/home/*
To see the various windows shares..
linux# ls -la /smb/{WinNT,Win98,Win95}/msdos.sys ( aka c:/msdos.sys )
>From the NT side...
------------------
create a network mapped drive...
linux:/Export_to_NT
and reboot..... and when you bring up the filebrowser...you shoudl be able
to see the entire web page tree at linux:/usr2/Web_pages
=
= any NT can see the stuff exported by linux...
=
= any linux can see the stuff exported/shared by the NTs
=
= no new coded is needed ??
=
have fun linuxing
alvin
http://www.Linux-Consulting.com/Amd_AutoFS/autofs-HOWTO.html
>
> On Tue, 9 Nov 1999, H. Peter Anvin wrote:
>
> > Anders Melchiorsen wrote:
> > >
> > > I have to find a medium-sized project (that is, half time work for a
> > > couple of months) to do in University. I want to do something that I
> > > can benefit from personally, and so I thought about an automounter for
> > > Windows shares. (I live in a dorm with lots of Windows machines
> > > sharing things through SMB).
>
> I've been working on the same thing for a while. You can find my
> current (working, but too buggy to be useful yet) perl code at
> ftp://mycroft.jones.rice.edu/pub/roy/autosmb/
>
> ... actually, that port may be firewalled. I'll have it at
> http://www.owlnet.rice.edu/~roystgnr/autosmb/ too.
>
> > > As far as I can tell, autofs does support smbmount, but only on a per
> > > share basis; you need to specify a mount rule for each share on each
> > > server. What I want is dynamic browsing capabilities like Windows
> > > offers.
>
> You can get autofs to automatically mount a SMB share such that
> "cd /smb/server=share" will take you there, or with a little more work
> so that "cd /smb/server/share" will take you there. Unfortunately, I
> haven't been able to figure out how to make "ls /smb" or
> "ls /smb/server" do useful things efficiently. My first attempt has
> to get a complete server/share listing on every scanned subnet at
> once, which is grossly inefficient.
>
> > > I think the main problem is that the virtual file system needs two
> > > levels, the first with the servers and the second with shares on each
> > > server.
>
> Exactly. I've thought of some hacks to do this, but they all involve
> either writing a new autofs module, writing a new vfs driver, or doing
> hideous loopback mounts of small ext2 image files.
>
> > > Is autofs able to do this, perhaps with a few scripts hacked together?
> > > Would it be hard to expand autofs in this direction? Is there some
> > > reason it cannot be done?
>
> What I envisioned: First level: /smb contains a list of symlinks,
> one for each server, to /.autosmb, which is automounted, with a
> program map set up to get a list of shares on that server. When you
> "cd /smb/server" it mounts "the magic filesystem", which is just a
> directory containing a list of symlinks to sharenames, in
> "/.autosmb/server=share" format. The same program map can then mount
> an SMB share for that server and sharename. The question is how to
> create "the impossible filesystem" on demand.
>
> > > If it is not currently possible in autofs, would one be able to do
> > > it with amd (I understand that amd is a bit more powerful, at the
> > > cost of being vastly more complex)?
>
> Is amd still supported? I thought it was being phased out.
>
> > It should be doable by using an autofs nested mount on the first level
> > and a program mount on the second level. Shouldn't be too difficult.
>
> The trick is not browsing any SMB share on demand, but also getting an
> on-demand list of shares that are browsable.
>
> Oh, yeah, and there's still a nasty parsing bug in autofs that makes it
> impossible to mount shares that have whitespace in their server name
> or share name.
>
> Plus the whole "smbmount" thing is shaky at best. I advise giving up
> on the smbfs specific support in autofs, and simply making sure your
> system is configured so that "mount -t smb" and "mount -t smbfs" work
> as expected.
>
> HPA: that's the second time I've hit reply and sent something to you
> only accidentally... sorry!
> ---
> Roy Stogner
>
