Mailinglist Archive: opensuse (4570 mails)

[Joseph Loo <jloo@xxxxxxx>]

There is an option on the /etc/fstab that does the mounting 
automtaically. It has to do with the last 2 numbers on the list. I 
suggest you add 1 n where n is the order of mounting. If you have 0 in 
the first number, it will not automatically moun the partition.

By the way I love useing automount.. I use it only on a few machines. at 
home. To me it just offers a lot of flexibility with a small performance 
penalty. Also the /net feature allows me to easily access other machins 
exported file system without using root.

Jonathan Brooks wrote:
> Joseph Loo wrote:
>   
> > In SUSE 10.0 they finally got the /net working right again. Why don't
> > you turn on the atuofs, setup, auto.master, and auto.net. Then as a
> > standard user say the machine is crab, you can then do a cd
> > /net/crab/to-your_exported_directory. It requires no root command. If
> > you turn on the timeout, if you are not using it, it will even unmount
> > the file without any problem.
> >
> > Jonathan Brooks wrote:
> >     
> > > Hi,
> > >
> > > I'm also having a few problems with NFS on SuSE 10. I am trying to mount
> > > resources from a SLES 9 machine, presumably set up for nfsvers 3???
> > >
> > > Each boot time, I get the error message that the "server reports TCP
> > > unavailable, resorting to UDP". I also occasionally see error messages
> > > to the effect of "server reports nfsvers 4 not available, switching to
> > > version 3".
> > >
> > > All in all, it means that each time I reboot my SuSE 10 machine, I have
> > > to log in as root and issue the command: mount -vat nfs, and more often
> > > than not this will pick up the nfs drives that aren't being mounted at
> > > boot time.
> > >
> > > FYI, here's the lines from /etc/fstab:
> > >
> > > 163.1.82.28:/home       /home   nfs
> > > rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0
> > > 163.1.82.28:/home1      /home1  nfs
> > > rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0
> > > 163.1.82.28:/home2      /home2  nfs
> > > rsize=8192,wsize=8192,intr,bg,nfsvers=3 0 0
> > >
> > > What are the implications of using UDP and nfsvers=2 on
> > > security/performance etc.????
> > >
> > > Anyone know what's going on? I have another AMD64 machine (SuSE 9.3),
> > > which has exactly the same problem.
> > >
> > > Best wishes,
> > >
> > > Jon.
> > >
> > > Roger Oberholtzer wrote:
> > >  
> > >       
> > > > On Sun, 2005-11-06 at 15:21 -0500, Dan Nash wrote:
> > > >    
> > > >         
> > > > > I have an Apple OS X 10.4.3 that was successfully connected to Suse 
> > > > > Linux 9.2 NFS server. I upgraded to Suse 10.0 and now the Apple 
> > > > > cannot find the Linux server. It can successfully ping the Linux IP 
> > > > > address. What settings do I need when starting the Linux NFS 
> > > > > services? There must be some differences between 9.2 and 10.0 that 
> > > > > I'm missing.
> > > > >       
> > > > >           
> > > > Probably the same thing I went through with OS-9 (Microware, not Apple)
> > > > connectivity. The 2.6 kernel (where NFS now lives) uses a newer version
> > > > of NFS by default. It also uses udp instead of tcp.
> > > >
> > > > Can you mount an export from OS/X on SUSE 10.0?
> > > >
> > > > When mounting on SUSE 10.0, I needed to add this to the fstab options:
> > > >
> > > >     udp,nfsvers=2
> > > >
> > > > I do not know how you specify this when exporting. Or even if you can.
> > > > But maybe this will get you started in the right direction.
> > > >
> > > > Hope this helps.
> > > >  
> > > >     
> > > >         
> > >   
> > >       
> Hi Joseph,
>
> Thanks for the info, but rather than using automounting, I would like to
> be able to use NFS options in /etc/fstab. I would dearly like to know
> why our AMD64 machines have so much trouble connecting to our SLES
> server to mount NFS drives at boot time.
>
> Automounting is a great system, but I don't need it here. There are only
> a few machines to administer, and fstab is just easier.
>
> Best wishes,
>
> Jon.
>   

--
Joseph Loo
jloo@xxxxxxx