All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Fanning <christopher.fanning@gmail.com>
To: autofs@linux.kernel.org
Subject: autofs and terminal networks woes.
Date: Thu, 17 Feb 2005 11:33:25 +0100	[thread overview]
Message-ID: <215ff441050217023378003e72@mail.gmail.com> (raw)

Hello all,

I am working with terminal networks. I have been using PXES
(http://pxes.sourceforge.net/) as the thinclient and freeNX
(http://developer.berlios.de/projects/freenx/) as the X protocol.

All users run their session on the central terminal server. Each pc,
where the users sits, is running X (PXES). Problems start when the
user wants to access the floppy because /mnt/floppy is the floppy
drive on the server, when in reality, the user is not phisically at
the server. By clicking on his floppy icon, the user expects to access
the drive on his thinclient.

PXES (the thinclient) runs a samba server just for this reason.
Therefore, the user can browse smb://thinclient/fd or
smb://thinclient/cdrom to access his local drives because he is
physically @thinclient.
I have managed to setup floppy and cdrom icons on the desktop at
login. By using the freeNX code, we can know the ip of the thinclient.

So, we have varios users running individual sessions on the server
simultaneously. Each user is sitting at a client with its own ip. Each
user can access their floppy via smb://thinclient_ip/fd

I feel this is a limited solution. When the user goes to konqueror o
nautilus and accesses /mnt/floppy, he reads the floppy on the server
(bad becaue he is not physically there). All system-wide references to
the floppy or cdrom or usb are wrong. Only the icons
(smb://thinclient/..) made explicitly are correct.

Considering this limitation, I thought something might be able to be
done with autofs 

It does seem possible to do something like this.
/var/autofs/terminales/a_thinclient_ip/floppy
/var/autofs/terminales/a_thinclientl_ip/cdrom

So I setup the samba server on the thinclient to accept guest without password
(I read somewhere that this was necessary for autofs).

more /etc/auto.terminals
floppy  -fstype=smbfs,guest,fmask=666,dmask=777        ://a_thinclient_ip/fd
and it works!

However, I think I need to use an external script (you call that a
map?) that produces this output
a_thinclient_ip   -fstype=smbfs,guest,fmask=666,dmask=777      
/floppy thinclient_ip:/fd

I have manually added this to auto.smb to test it and it doesn't work.

So my question here is why?
floppy  -fstype=smbfs,guest,fmask=666,dmask=777       
://a_thinclient_ip/fd  (this mounts)
a_thinclient_ip   -fstype=smbfs,guest,fmask=666,dmask=777      
/floppy thinclient_ip:/fd   (this doesn't)

What am I overlooking?

Thanks in advance
Chris.

             reply	other threads:[~2005-02-17 10:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17 10:33 Chris Fanning [this message]
2005-02-17 13:39 ` autofs and terminal networks woes raven
2005-02-17 14:06   ` Chris Fanning
2005-02-17 14:10     ` raven
2005-02-17 15:15       ` Chris Fanning
2005-02-17 16:09         ` Jonathan Loran
2005-02-20 19:38           ` Chris Fanning
2005-02-21  4:39             ` Ian Kent
2005-03-08 11:36               ` Chris Fanning
2005-03-08 13:39                 ` raven
2005-02-20 21:59     ` Steinar H. Gunderson

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=215ff441050217023378003e72@mail.gmail.com \
    --to=christopher.fanning@gmail.com \
    --cc=autofs@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.