SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This should be handled by the below entry in rc.M, which occurs directly after running rc.inet2:
Is there a reason the command in rc.M that is ran after rc.inet2 doesn't cover your situation?
While there is a `mount all unmounted` in rc.M, in my slackware 15 installation, nfs3 shares was mounted automatically but not for nfs4. So my guess is, nfs3 got mounted because there is a mount -t nfs line in rc.inet2 and no line for mount -t nfs4.
While there is a `mount all unmounted` in rc.M, in my slackware 15 installation, nfs3 shares was mounted automatically but not for nfs4. So my guess is, nfs3 got mounted because there is a mount -t nfs line in rc.inet2 and no line for mount -t nfs4.
Maybe there is something else than the lack of a mount command in the startup scripts that causes your nfs4 mounts to fail. Are you able to mount them manually? Did it work better for you after adding a line in rc.inet2?
Maybe there is something else than the lack of a mount command in the startup scripts that causes your nfs4 mounts to fail. Are you able to mount them manually? Did it work better for you after adding a line in rc.inet2?
While there is a `mount all unmounted` in rc.M, in my slackware 15 installation, nfs3 shares was mounted automatically but not for nfs4. So my guess is, nfs3 got mounted because there is a mount -t nfs line in rc.inet2 and no line for mount -t nfs4.
I think something is amiss with your system. The command in rc.M is essentially just verbose mount -a, followed by taking that output and showing the mount command for each mount that wasn't mounted prior.
Does just mount -a mount nfs4 shares? I just checked on my 15.0 VM and mount -a mounts my NFS4 entry in fstab and I rebooted and it was automatically mounted when booted up.
What is your fstab entry for your nfs4 mount(s)? Mine was really basic:
Code:
10.0.0.152:/share /mnt/hd nfs4 defaults 0 0
And it mounted:
Code:
jbhansen@slack15:~$ mount -t nfs4
10.0.0.152:/share/movies on /mnt/hd type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.0.101,local_lock=none,addr=10.0.0.152)
Ya I got a AMD Radeon RX 5500 (navi14, LLVM 13.0.0, DRM 3.46, 5.18.7)
I needed to update my Mesa to atleast Mesa 22.1.2 or Mesa 22.2.0-devel as well as libdrm-2.4.110 and this is on Slackware 15.0
All of that was just to play a DirectX12 game called Halo Infinite, Having the new Mesa 22 version at least in extra or testing would be a good thing to do, doesn't mean Mesa Amber has to be deprecated just give us the option thats all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
