networking ubuntu and mint and windows

Michael Butash michael at butash.net
Fri Dec 2 15:09:56 MST 2011


NFS is like cifs (windoze file sharing).  On my lan it's way faster to 
use than cifs to my filer, and plays somewhat nice with various unixes. 
  You'll really want nfs AND samba for windoze unless you're going to 
install nfs for windows or run cygwin.

Exports sets allowances and permissions, hosts.allow/deny set network 
port access for services (just define your local network as a whole) 
rest is related to local uid/gid.  These have to match on your unix 
boxen to be effective!

You can run samba for this, Ubuntu, presumably mint, etc have system 
gui's for these things.  You should probably poke around system settings 
for file sharing.

All the init stuff gets setup by apt - don't worry about that much.

When you're done poking at your settings, restart nfs services in init:

sudo service nfs-server restart

(init.d script name may differ - nfs and tab for autocomplete)

-mb


On 12/02/2011 02:35 PM, 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 <http://192.168.0.0/192.168.0.4>
>       lockd : 192.168.0.0/192.168.0.4 <http://192.168.0.0/192.168.0.4>
>       mountd : 192.168.0.0/192.168.0.4 <http://192.168.0.0/192.168.0.4>
>       rquotad : 192.168.0.0/192.168.0.4 <http://192.168.0.0/192.168.0.4>
>       statd : 192.168.0.0/192.168.0.4 <http://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 at fries-biro.com
> <mailto:kevin at 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 at gmail.com
>     <mailto:cryptworks at 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 at usa.net <mailto:danceswithcrows at usa.net>> wrote:
>      > > From: Michael Havens <bmike1 at gmail.com <mailto:bmike1 at 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 at lists.plug.phoenix.az.us
>     <mailto:PLUG-discuss at 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 at lists.plug.phoenix.az.us
>     <mailto:PLUG-discuss at 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 at lists.plug.phoenix.az.us
>     <mailto:PLUG-discuss at 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 at lists.plug.phoenix.az.us
>     <mailto:PLUG-discuss at 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 at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss


More information about the PLUG-discuss mailing list