On Fri, Dec 2, 2011 at 3:02 PM, Kevin Fries <kevin@fries-biro.com> wrote:

NFS is file sharing, like mounting a server directory in Windows. In
the Windows platform, there are two programs that are installed as part
of the standard Windows: Server, and Workstation.

Server is what creates shares on your system that others can see through
network neighborhood (or whatever MS is calling it this week, Network
Places?)

Workstation is the software that makes the link and makes it available
to the current machine.

Linux can install SMB to connect, or share its folders using the Windows
protocol, called CIFS (old references will still call it SMB, which is
its predecessor)

Linux also has support for the old Unix equivalent, NFS, or Network File
System. In NFS, the Server portion is handled by a daemon, and you
create your shares though the /etc/exports file. The client side is
handled via the standard mount command. But it is just a second
protocol to handle the same task.

Windows systems can also mount NFS drives, but you have to find, and
install, the software separately. Mac's btw act exactly like Linux
machine's in this case, and therefore can mount NFS natively, or you can
in stall the Samba to talk CIFS.

What I thought you were talking about earlier was remote desktop access.
This is a completely different topic.

Remote desktop means that you will see machine-a's desktop on
machine-b's screen. This allows you to run a program on machine-a while
being currently logged into machine-b. For that, I recommended Free-NX.

Again, you have the Windows technology, and the one everyone else uses.

Windows natively has a program called Terminal Services. You can
connect as a client to a server at any time. Every version since XP has
had this software installed, but you are limited to 1-2 connections
depending on your version of Windows. Ubuntu has a client for Terminal
Server also.

Linux and Mac machines generally use a program called VNC for remote
desktop. It is included with every version I have ever seen of Linux
(or is in the repositories). VNC has no security in it by default, so
many tools have been built to secure the connection. The simplest is
generally to tunnel it though a SSH connection.

When I recommended Free-NX for remote desktop, It was due to the fact
that you are obviously new to all of this, and wanted to point you to
the easiest way to install the software. Free-NX will require you to
have SSH setup between the machines (easy enough), and it will tunnel
between the machine a VNC session. It hides all of this tough a very
straightforward GUI, so it is fairly easy for a nubie.

But Free-NX will not share files, it only let you see the desktop on the
other side.

NFS will not let you see the other side, or run programs on the remote
machine, it will only share files.

Personally, I am not a fan of NFS. If I want files on another machine,
I open Nautulus (desktop file browser in Ubuntu), and type:

ssh://myothermachine

I now have a windows that I can drag and drop files to and from. And if
I want to run something on that machine, I will use Free-NX. And it can
use the same SSH tunnel to do both.

Good Luck

Kevin

On Fri, 2011-12-02 at 14:35 -0700, Michael Havens wrote:
> I am confused..... what exactly does NFS do? Maybe we should do both!
> Below is the /etc/exports file i created for the computer I decided to
> make the server
>
> # /etc/exports: the access control list for filesystems which may
> be exported
> / 192.168.0.0(ro) 192.168.0.1(ro) 192.168.0.4(rw,sync)
> /home 192.168.0.2(ro,sync)
>
> (computers)
>
> (192.168.0.0) I don't know where this device is. I figure it has
> to do with the router.
> (192.168.0.1) Is the address to the router
> (192.168.0.2) is the address to the windows box
> (192.168.0.3) is the address to the designated server
> (192.168.0.4) Is the address to the laptop wifi
>
> This is /etc/hosts.deny:
>
> portmap : all
> lockd : all
> mountd : all
> rquotad : all
> statd : all
>
> this is /etc/allow:
>
> portmap 192.168.0.0/192.168.0.4
> lockd : 192.168.0.0/192.168.0.4
> mountd : 192.168.0.0/192.168.0.4
> rquotad : 192.168.0.0/192.168.0.4
> statd : 192.168.0.0/192.168.0.4
>
> this being completed the next step in my guide tells me that these
> daemons need to be started:
> rpc.portmap
> rpc.mountd,
> rpc.nfsd
> rpc.statd,
> rpc.lockd (if necessary), and
> rpc.rquotad
>
> google says that startup scrips are in /etc/init.d but in that directory the only rpc is rpcbind-boot which is a link to /lib/init/upstart-job
> which is a script... one of the lines in it says:
>
>
>
> # Symlink target for initscripts that have been converted to Upstart.
>
> I'm a little lost! How do I get these scripts and add them to init.d or where should I put them?
>
>
> On Fri, Dec 2, 2011 at 1:36 PM, Kevin Fries <kevin@fries-biro.com>
> wrote:
> Sorry I was slow to jump in on this one...
>
> NX rocks. I disagree that it is a pain to set up. It uses
> VNC and SSH
> to remote the desktop. Ubuntu .deb packages exist on their
> site, so
> install is pretty simple. And, it is as secure as anything
> short of
> full scale enterprise class application.
>
> HTH
> Kevin
>
> On Fri, 2011-12-02 at 12:53 -0700, Michael Havens wrote:
> > which way do you think is best for the learning experience?
> >
> > On Fri, Dec 2, 2011 at 11:35 AM, Stephen
> <cryptworks@gmail.com> wrote:
> > you can use rlogin via ssh, and then xming and putty
> to do the
> > same
> > from windows to Linux boxes.
> >
> > these will maintain the most open options. I have
> use the
> > xming/putty
> > combination and its pretty nice. and as secure as
> your ssh
> > session :-)
> >
> > On Fri, Dec 2, 2011 at 11:32 AM, Matt Graham
> > <danceswithcrows@usa.net> wrote:
> > > From: Michael Havens <bmike1@gmail.com>
> > >> No MAC. Two Linux boxes and 1 Windows XP box. Is
> there a
> > way to
> > >> make it so that I can have the desktop of the
> other
> > computer on
> > >> another or else is this all text?
> > > [snip]
> > >
> > > That's a bit of a different question, and has
> nothing to do
> > with NFS. This is
> > > more like "remote access". There are a bunch of
> ways; here
> > are the most
> > > popular:
> > >
> > > VNC/TightVNC : Totally cross-platform, tested,
> stable,
> > etcetera. On 'Doze,
> > > TightVNC Server will, if run, make the 'Doze
> desktop
> > available to clients. On
> > > Linux, you want x11vncserver or its
> GUIfied/friendly
> > counterparts KDE Desktop
> > > Sharing or the GNOME equivalent (vino?). Many
> clients
> > exist. Pick your
> > > favorite; they usually have "vnc" in their name
> somewhere.
> > NOTE: vncserver
> > > and tightvncserver create a virtual Display
> instead of
> > sharing an
> > > already-existing Display.
> > >
> > > Windows Desktop Sharing : A 'Doze box can share
> its desktop
> > to remote clients.
> > > There's a Linux client called rdesktop that works
> pretty
> > well. Last I
> > > checked, there was a proof-of-concept Linux server
> that
> > didn't work all that
> > > well, so this is pretty much one-way only.
> > >
> > > NXServer : Proprietary free as in beer, but quite
> fast over
> > low-bandwidth
> > > links. It's a bit of a pain to set up. It works
> well once
> > it's been set up.
> > >
> > > X11 : Can be used, usually isn't, since most
> modern X
> > servers are started with
> > > -nolisten tcp , and GTK+ apps tend to behave badly
> when not
> > able to connect to
> > > a local X socket.
> > >
> > > sshing to a Linux box is usually much faster than
> dragging a
> > GUI around. But
> > > there are ways if you really need them. Don't
> forget that
> > you can "ssh -Y
> > > remotehost xclient" to ssh to remotehost, then
> tunnel X over
> > ssh, so that
> > > xclient is running on remotehost, but displaying
> on your
> > local Display, which
> > > may be useful in some cases.
> > >
> > > --
> > > Matt G / Dances With Crows
> > > The Crow202 Blog: http://crow202.org/wordpress/
> > > There is no Darkness in Eternity/But only Light
> too dim for
> > us to see
> > >
> > >
> ---------------------------------------------------
> > > PLUG-discuss mailing list -
> > PLUG-discuss@lists.plug.phoenix.az.us
> > > To subscribe, unsubscribe, or to change your mail
> settings:
> > >
> >
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> >
> >
> >
> > --
> > A mouse trap, placed on top of your alarm clock,
> will prevent
> > you from
> > rolling over and going back to sleep after you hit
> the snooze
> > button.
> >
> > Stephen
> >
> > ---------------------------------------------------
> > PLUG-discuss mailing list -
> > PLUG-discuss@lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail
> settings:
> >
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> >
> >
> >
> > --
> > :-)~MIKE~(-:
> > ---------------------------------------------------
> > PLUG-discuss mailing list -
> PLUG-discuss@lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail settings:
> >
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list -
> PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
>
>
> --
> :-)~MIKE~(-:
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss