Mount error - works with Slackware 14.2, does not work with Slackware -current
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 works with Slackware 14.2, has for a very long time. With Slackware current, I get this:
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
dmesg shows:
CIFS: Unknown mount option "symfollow"
But I'm not using symfollow.
UPDATE: Apparently this is a known bug in utils-linux 2.36.1, fixed in 2.36.2. Slackware-current seems to be using 2.36.1. Is there a way for me to update my install to 2.36.2 without waiting for slackware-current to update?
Background - one of our suppliers is updating their SSH Ciphers to AES, discontinuing SHA*. Slackware 14.2 apparently does not support this, hence the update to slackware-current.
UPDATE: Apparently this is a known bug in utils-linux 2.36.1, fixed in 2.36.2. Slackware-current seems to be using 2.36.1. Is there a way for me to update my install to 2.36.2 without waiting for slackware-current to update?
Background - one of our suppliers is updating their SSH Ciphers to AES, discontinuing SHA*. Slackware 14.2 apparently does not support this, hence the update to slackware-current.
Most likely you'd just need to grab the util-linux source tarball for 2.36.2 and drop it in the directory with the util-linux.SlackBuild script and all the patches and then run the SlackBuild and install the resulting package.
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Original Poster
Rep:
Huh...never thought of that. The SlackBuild script looks for whatever version of the file is there, instead of hard coding it. Nice. Downloaded the master from github. repackaged it to util-linux-2.36.2-x86_64-1.txz cause it comes as a zip file. Plop into build directory. Building...done...and...omg it works. That was too easy. I think I owe you a beer...and maybe a pizza, I was starting to sweat.....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.