Linux to Linux

brad.mugleston at comcast.net brad.mugleston at comcast.net
Wed Apr 6 23:27:00 UTC 2005


Rick,

I'll answer at top as it's getting long.

Read  man exports and then played with the exports file.

Tried 192.168.1.103(rw,no_root_squash) and it worked
then tried 192.168.1.0/24(rw,no_root_squash) and it worked.

I tried this as the man file said to use wild cards or full
names.  Don't know why 192.168/16 didn't work but it's working
now.

NOW lets work on the printers..

Brad Mugleston, KI0OT

There are 10 types of people in this world.  Those that
understand binary and those that don't.

On Wed, 6 Apr 2005, Rick Stevens wrote:

> brad.mugleston at comcast.net wrote:
> > Rick,
> >
> > Please see below for my results
> >
> > Brad Mugleston, KI0OT
> >
> > There are 10 types of people in this world.  Those that
> > understand binary and those that don't.
> >
> > On Tue, 8 Mar 2005, Rick Stevens wrote:
> >
> >
> > > brad.mugleston at comcast.net wrote:
> > >
> > > > On Mon, 7 Mar 2005, Rick Stevens wrote:
> > > >
> > > >
> > > >
> > > > > brad.mugleston at comcast.net wrote:
> > > > >
> > > > > Peachy.  Essentially, your /etc/exports file on the server would look
> > > > > like:
> > > > >
> > > > > 	/home/brad	192.168/16(rw,no_root_squash)
> >
> >
> > DONE
> >
> >
> > > > > To manually start the NFS server code:
> > > > >
> > > > > 	/etc/rc.d/init.d/portmap start
> > > > > 	/etc/rc.d/init.d/nfslock start
> > > > > 	/etc/rc.d/init.d/nfs start
> > > > >
> >
> >
> > OK no problems reported
> >
> >
> > > > > On the client, you'd add lines to your /etc/fstab that look like:
> > > > >
> > > > > 	nfsserver:/home/brad	/mountpoint	nfs	rw 0 0
> >
> >
> > Did this replaced nfsserver with my ip 192.168.1.103 and
> > mountpoint with /brads
>
> Fine.
>
> > > > > If you have that in /etc/fstab, the following two commands will start
> > > > > the NFS client code and automatically mount any NFS volumes it finds
> > > > > in /etc/fstab:
> > > > >
> > > > > 	/etc/rc.d/init.d/portmap start
> > > > > 	/etc/rc.d/init.d/netfs start
> >
> >
> > Tried this and got the error:
> > 	mount:192.168.1.103:/home/brad failed, reason given by
> > server: Permission denied
>
> Hmmmm.  On the client, try "showmount -e 192.168.1.103" and verify that
> the server really is exporting the filesystem.  Also check your netmask
> on both the server and client.  If they're 255.255.255.0, then change
> the allowed network in the "/etc/exports" file on the server to
> "192.168.1.0/24".
>
> > > > > If you don't have any entries in /etc/fstab, mount the stuff via:
> > > > >
> > > > > 	mount -t nfs nfsserver:/home/brad /mountpoint
> >
> >
> > Tried this with the same error
>
> As the root user or as a normal user?  This should be done as root.
>
> > I tried changeing the nfsserver to nfsserver and the machine's
> > name but same error
>
> The line should be:
>
> 	mount -t nfs 192.168.1.103:/home/brad /brads
>
> (in fact the "-t nfs" isn't really necessary as the server's export
> is enough to tell mount that it's an NFS mount).
>
> > > > > If you wish to make these permanent (start NFS server processes and
> > > > > mount them on the NFS client), then you can do the following:
> > > > >
> > > > > On the server:
> > > > >
> > > > > 	chkconfig --levels 2345 portmap on
> > > > > 	chkconfig --levels 2345 nfslock on
> > > > > 	chkconfig --levels 2345 nfs on
> > > > >
> >
> >
> > OK no errors
> >
> >
> > > > > On the client:
> > > > >
> > > > > 	chkconfig --levels 2345 portmap on
> > > > > 	chkconfig --levels 2345 netfs on
> >
> >
> >
> > OK no errors
>
> Remember, that doesn't start the processes, it just sets up the stuff
> in /etc/rc.d/rcX.d.
>
> > BTW - I can now ping between the two machines.
>
> You couldn't before?
>
> > Question - if I get this to work I'll need to hard code the IP
> > address - how would this work if the IP was assigned on boot like
> > it is now?
>
> If you can't use fixed IPs on the server end, you'll need to set up
> dynamic DNS and use the DNS name of the server in the mount on the
> client.  Sorry, but DHCP was never meant for server-class machines.
>
> > Still no printer but let's get the first part working
>
> Yes, one problem at a time.
> ----------------------------------------------------------------------
> - Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
> - VitalStream, Inc.                       http://www.vitalstream.com -
> -                                                                    -
> -          Consciousness: that annoying time between naps.           -
> ----------------------------------------------------------------------
>
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list at redhat.com
> https://www.redhat.com/mailman/listinfo/redhat-install-list
> To Unsubscribe Go To ABOVE URL or send a message to:
> redhat-install-list-request at redhat.com
> Subject: unsubscribe
>




More information about the Redhat-install-list mailing list