LinuxQuestions.org - Requests for -current (14.2-->15.0)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Requests for -current (14.2-->15.0) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/)

Quote:

Originally Posted by cgorac (Post 5802289)

It is equally annoying to have to read these statements "current is development, not a rolling release, blah, blah" over and over again, written by same group of persons that are just regular users like the rest of us, and not part of Slackware team.

Then, what do do when someone who obviously misuses -current asks for help? Just don't answer?

Hi,

As NEWUSER pointed out earlier, leave this thread for the intended use.

--
Best regards,
Andrzej Telszewski

May I suggest setting CONFIG_SND_HDA_INPUT_BEEP=y in the kernel config.
My laptop needs it in order to generate a beep.

You can set CONFIG_SND_HDA_INPUT_BEEP_MODE=0 to leave it disabled by default so as not to annoy people who have old-school beepers on their motherboards.

I use to be on -current, but found I didn't have the skills or time (and downtime) to troubleshoot some issues experienced. I reverted to stable and have had stability and success even integrating NVIDIA then moving back to nouvea since my card is now nearly fully supported. I heeded the official slackware.com and doc.slackware.com recommendations to install "stable" and not -current because:

"Do not track the Current branch on production systems as it is a test-bed for upcoming releases. It is recommended that you use the latest stable release with the security updates instead."

Plus we have all LQ senior contributor advice to only use -current "if you are willing to accept breakage AND have the ability to suggest fixes" which paraphases our BDFL recommendation. So when people complain about -currrent breaking something and how to fix it I'd suggest simply leaving the message unanswered or only reply with "have you tried this on stable". The reply would be consistent with requests for "help should only be made for stable", and "-current is a testing branch and should only be used if you are able to accept breakage and are able to resolve the problem yourself."

The only other solution to removing these time wasting rants is to make -current hidden until it is a release candidate.

With the current openness of letting us have access to -current and the occasional -current user frustration rant... Sometimes it is better to let the person grieve in silence and simply be there to help them after they realize that stable is where they belong.

Cheers

hdparm-9.53:

- Read Drive Capacity fixes from Iestyn Walters.
- SET MAX ADDRESS fixes from Tom Yan <tom.ty89@gmail.com>.
- added --security-prompt-for-password to --security-help output.
- fwdownload changes from Jihoon Lee.
https://freefr.dl.sourceforge.net/pr...rm-9.53.tar.gz

When you are too lazy to use the commandline to setup an encrypted lvm , maybe one day add that option in the installation (ncurses) ...... Would be nice.

Hi,

Quote:

Originally Posted by gmgf (Post 5802781)

rust-1.23.0:

https://github.com/rust-lang/rust/bl...er/RELEASES.md
https://static.rust-lang.org/dist/ru...3.0-src.tar.gz

This update breaks (not for the first time) building mozilla-firefox-57.0.4 on my 14.2 box.
With rust-1.22.1, FF builds fine.

--
Best regards,
Andrzej Telszewski

Quote:

Originally Posted by Alien Bob (Post 5801687)

No, it is not that we think it's your system. It's the way you seem to be looking at slackware-current, expecting updates to be fully tested against everything that is NOT part of Slackware itself.
That is not how it works. The development cycle between two stable releases (14.2 and 15.0 for instance) is called "slackware-current" and if you use that development version you are a tester. Period.
You can expect that on release of Slackware 15.0, it probably contains a kernel that is supported by the Nvidia drivers, but even that compatibility will not be tested by Pat or the Slackware team.
And if it is tested and it's proven that Nvidia drivers are not compatible, that's still not a reason to delay updates. Slackware-current is always the bleeding edge and sometimes, it bleeds until 3rd parties get their act together.

You, the user/admin, are responsible for keeping a Slackware-current system functional. If you distrust -current updates because of potential incompatibilities (Nvidia for instance) but you want to run slackware-current regardless, then the best advice is to NOT immediately apply updates. Rather, you wait a day, check this LinuxQuestions.org forum for any reported issues, and eventually you update your computer when you are confident that there is no major breakage.

And a final advice. In case of kernel upgrades, ALWAYS keep a working kernel installed. NEVER use "upgradepkg" or "slackpkg upgrade-all" to upgrade from your working kernel to the next one. If you use slackpkg, make sure to blacklist "kernel-generic", "kernel-huge" and "kernel-modules".
My boot menu always contains at least two kernel choices. If the new kernel does not work or creates issues, you can safely go back to your previous kernel.

I do not understand why you were so pissed at Slackware and Pat. It was unwarranted.

OK Eric your always right. We all spend time making this shi easy.
as I see the website finally updated NVIDA Vaseline givers repo and my automatic script that builds the NVIDIA stupid blob that uses json to read.h my script DOES NOT looks for any xorg changes and kernel changes.
and then uninstalls nvidia then does a slack update . the sed goes and looks at the latest up loads to the site. The changelog had nothing in xorg. the nvidia blob was set with out uploading to that version to nvidia. And Pat did not write a NVidia fail for current. Current is not testing. This is a serious slack.
if any one want to ;look at Nvida server upload log ask them. I already. as far as slackbuilds and Nvidia. Get with it.
your always right the customer is stupid teach them. that a changelog is what

https://github.com/Drakeo/update-nvi...commits/master

Slackware 15.0 missing tools

Dear All,

I am using 64x and 32x 14.2, sendmail is used as a server connected to my provider (BatchMail facility).
All the mail of our domain is send to our version of sendmail, which includes a lot of protection. We have our own rc.firewall and rc.firewall_ipv6 plus a static ipv6 gateway,
which looks good.
Now sendmail get less attention, and the tools imapd-(2.20) are missing completely
in 15.0. Still such a version is needed, especially ipop3d (pop3s).
The latter one uses a self-signed certificate (related to the sendmail certs.
We use seamonkey on a few PCs to get our mail from our mail server.
We spend a lot of years from very early slackware version on to build a save configuration.

PLEASE do not skip all those earlier utilities which made Slackware a save reliable tool,

I do not use dovecot, nor postfix, but only sendmail, imapd-2.20, an iptable firewall
which block any intruder. Further on we run DNSSEC, might be improved.

I am an old man (73) working from the 1980 with Unix and slackware, subject mainly language research, I don't want to start all over again,

Thank you,

Jaap (@) talo

So all of sendmail as in the previous release, and imapd-2-20 and maybe some other things,

I could do better but this is not my normal business.

It is what it is. The UW imap and pop3 servers have been replaced with dovecot and you will have to plan a migration. This is what sometimes happens to old tools.
Perhaps if you could share your configurations and let other people in this community share their thoughts.

Note that you do not *have* to upgrade to Slackware 15.9 when that is released. You can enjoy Slackware 14.2 for the years to come.

Also, read this https://wiki2.dovecot.org/Migration

Quote:

Originally Posted by Drakeo (Post 5802969)

OK Eric your always right. We all spend time making this shi easy.

After a4z you are the second one in a day telling me that I am on a high horse.
That is a pity since in both cases, you are angry users of Slackware. Where a4z feels misunderstood and underrated and you are pissed because Slackware developers do not test whether 3rd party software breaks or not. Hogwash.
I am no longer taking part in this discussion, after this post.

Quote:

Current is not testing. This is a serious slack.

If you are still thinking that running slackware-current guarantees a stable experience then you need to start realizing what slackware-current is, because it is something else entirely. It is the publicly shared Slackware development tree, here to let people test these updates and give feedback before the next stable release. It's the bleeding edge. If it breaks, you were warned in advance. Fixes are usually fast if the issue is with the Slackware packages.
In your case it is an issue with a provider of commercial closed-source software who is lagging behind, but even that takes a day or so to solve.

If you are not able to wait these few days to let teams sow the seams together again, then you should not use slackware-current. Consider reverting to Slackware 14.2 please.

I have repeated myself more than I should have. If the message does not get through, then too bad for you all who mistake Slackware for a rolling-release distro.