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.
Hmmm... my Windows 7 was installed once and has run since day one without hick-ups or re-installs and is as stable as day one. Same as the systems I've installed for others over the decades. Problems were few and far apart...
Nobody got their Windows systems to learn how their OS works. They had work to do...
Not that I want to defend Microsoft, but the bashing gets a bit tiresome...
The numbers speaks. 96% Microsoft, 2.5% MacOS and 1.5% Linux/others.
Back to normal thread.
1 members found this post helpful.
Click here to see the post LQ members have rated as the most helpful post in this thread.
And that's a good thing. Because the main reason Windows is such a target of riff-raff and scammery is because of its popularity. It gives the malcontents "more bang for their buck". We who use GNU/Linux definitely do NOT want that big target on the back of our favorite OS.
And while I can't stand Windows these days. There was a time when I was quite enamored with Win 98 and 98SE; not so much XP, though. Actually, excessive "service pack" crash & burns with XP was the main motivation for me going with Slackware as my main OS on all my machines since 2006. Win 7 was OK. I currently have a crippled (Networking disabled) Win 10 on my system primarily for gaming, which I haven't done much of lately. I can't remember the last time I booted that Win 10.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,125
Rep:
Quote:
Originally Posted by vtel57
.........
And while I can't stand Windows these days. There was a time when I was quite enamored with Win 98 and 98SE; not so much XP, though. Actually, excessive "service pack" crash & burns with XP was the main motivation for me going with Slackware.......
I had already been using Linux and Slackware for a few years (since '95 or '96) by the time Xp was released, but, actually, by service pack 3, XP was pretty good, IMO. I still run it to this day in VirtualBox since the original HP Xp drivers for my old flatbed scanner do a much better job than any Linux software I've tried. Before anyone says, "Have you tried "Vuescan?," it doesn't support this particular model.
Last edited by cwizardone; 01-05-2023 at 03:56 PM.
Reason: Typo.
I had already been using Linux and Slackware for a few years (since '95 or '96) by the time Xp was released, but, actually, by service pack 3, XP was pretty good, IMO. I still run it to this day in VirtualBox since the original HP Xp drivers for my old flatbed scanner do a much better job than any Linux software I've tried. Before anyone says, "Have you tried "Vuescan?," it doesn't support this particular model.
I'm just carefull to ever buy devices clearly supported by Linux...
What do you know, i get an used Xerox 3055 3in1 copier and printer that has zero support - but since it was free - I really couldn't say no to the bargain
Short story long, it's sitting there doing it all with Cups and some odd ball downloads across the net (github or some of the ever more scarce side-sources of obsolete binary drivers), and for every in a while i need it to do a scan it can (as in standalone) dump it on a thumb drive in jpeg format... It also is a great photo copier in situ...
FWIW for any real scanning i use the Cannon LIDE 110 instead. Just works.
Yeah, Windows was good for what it ought to do (make money and keep M$ at the front) but I so much better like where I'm now with Slackware...
For some time now, the slakfinder.org website has been offline. The domain still exists, but the web site just does not respond. Matteo Rossini (zerouno) needed a break from computers, so it is likely that the site won’t return on short notice.
The effect of the site’s unavailability becomes quite obvious if you use the slackpkg+ extension for slackpkg to manage the packages you installed from 3rd-party community repositories. The “/etc/slackpkg/slackpkgplus.conf” configuration file contains these lines:
?# use this to keep the slackpkg+ package updated to the latest stable release MIRRORPLUS['slackpkgplus']=https://slakfinder.org/slackpkg+15/ … and that causes a problem every time you run “slackpkg update“. There will be a timeout querying slakfinder.org and a subsequent error. After that, slackpkg will function as usual, you just won’t be able to check on updates for slackpkg+. But the error is annoying.
Luckily I am mirroring the repository for a long while now, so this is easy to fix. Replace the MIRRORPLUS URL above with the following line and run a “slackpkg update“, which will solve the timeout issue:
MIRRORPLUS['slackpkgplus']=https://slackware.nl/slackpkgplus15/
Please check Eric's blog for complete details.
Hope this helps!
I have been wondering lately as to the overall Slackware usage in the Gnu/Linux community. With all the hold you hand distributions, I wondered why. Only thing I can conclude is that ease of use for a hand hold distro. Sure Slackware does require a user to understand and have the means to work with Slackware. I think it does boil down to basic laziness and not contributing time to understand something. Slackware has a lot of users that are willing to help people to solve an issue with Slackware at this forum. Plus we do have; Slackware Doc Project to help new & old users.
I do not want to come across as judgemental but I'm old school and always have been curious and inquisitive about how to solve things. I would always dive into my challenges to see what could be done to service that situation. While I was still at the University, I did a lot of research and it was a benefit to have this attitude along with the means to solve therefore bring things to a conclusion.
I am proud of our Slackware community and the contributions made by it's members.
Yes, interesting thread, but I really would like to see some newbees contribute to it. Us "old timers" know why we like it, but without "new blood" I fear for Slackware's future.
So, if you are a new user of Slackware, please contribute to that tread knowing you, more than people like me, will keep the disto active in the long term
You’ll have noticed – as indicated earlier, the Chromium packages for Slackware 14.2 are no longer being updated.
Today I made available the Slackware packages available for Chromium 111.0.5563.64, and they are accompanied by the un-googled version. This latest release squashes a massive 40 vulnerabilities, none labeled critical, but it’s wise to keep your systems uptodate nevertheless.
These new packages are targeting Slackware 15.0 and newer.
Enjoy! Eric
I'm still running Slackware 14.2, so can't use the newest Ungoogled from Alien. However, just yesterday d-loaded and upgraded using his most recent (and final) Ungoogled Chromium for 14.2. All's well.
Thank you, @onebuck for the announcement above and Thank you, @AlienBob (Eric H.) for ALL you do!
I'm still running Slackware 14.2, so can't use the newest Ungoogled from Alien. However, just yesterday d-loaded and upgraded using his most recent (and final) Ungoogled Chromium for 14.2. All's well.
Thank you, @onebuck for the announcement above and Thank you, @AlienBob (Eric H.) for ALL you do!
I have uploaded the packages for Google Chromium 110.0.5481.77 as well as its un-googled version. The sources for this new major release were available since a week ago, but as it often happens when Chromium updates its major version number, I get to find ways around the breakage that seems to be specific for the unusual Slackware target, and create fixes and patches to make the sources compile into a package for Slackware.
It took me so long to come up with packages this time, that Google already released a newer update (110.0.5481.96) today…
You won’t get that update now, hopefully soon though. Get the 110.0.5481.77 release from my server (chromium or chromium-ungoogled) or its US mirror (chromium or chromium-ungoogled).
The new packages are targeting Slackware 14.2 and newer. As announced last year and repeated a couple of times, I am going to drop support for Slackware 14.2 on the first anniversary of Slackware 15.0, which is February 22nd, 2023.
Ergo, the final version of Chromium you’ll get from me for Slackware 14.2 will be this “110” release because Chromium 111 will see the light on March 1st.
It would be wise to upgrade to Slackware 15.0 anyway if you are still on 14.2.
Enjoy! Eric
I was pretty sure i posted to "This is my Slackware desktop" thread, but i see this here?
Not sure if i posted this already:
(workshop work station).
Nothing fancy, it's a custom built PC with IGP only (HD4000) and a single cooling fan (LED PSU --> pico PSU => 0dB).
Its a 16GB ram 1155 FPGA socket intel mini-ITX motherboard with a H61 chipset and 2.5" spinning HDD.
It gets the work done
Last edited by SCerovec; 03-19-2023 at 07:18 AM.
Reason: Oddity
A few weeks ago, Valve‘s official Linux binaries for its steamclient got an update. The 1.0.0.76 version is built using an updated Steam client:
Client timestamp 1676336721 (2023-02-14)
Steam Runtime version 0.20221019.0
The steamclient package which I create from this release tarball is meant to bootstrap the installation of Valve’s Steam gaming platform on your Slackware computer. The package installs a couple of scripts and a 32-bit Linux runtime based on Ubuntu, and adds a desktop menu entry so that you can easily start Steam.
When you first start ‘steam’ from the menu or from the X terminal command-line, the client scripts will download a larger set of runtime libraries, including 64-bit support. From then on, the steamclient will keep its runtime libraries up-to-date automatically, every time it starts up and connects to the Steam servers.
The Slackware package has a couple of tweaks because we obviously do not have all the expected Ubuntu tools on board. With the help of these tweaks, Steam works out of the box on Slackware – both 32bit and 64-bit with multilib!
If you are using Steam for gaming, be sure to check out its Slackware community. It’s not really chatty in there but last time I checked, the group listed over 400 Slackware users and there’s always a few online and playing.
Enjoy!
Eric
The Wine developers released version 8.4 last week. There’s lots of bugfixes of course, but the announcement also mentions that the work has started on a Wayland graphics driver. Note that in the previous 8.3 release for which I did not create packages, Smart Card support was added, using PCSC-Lite for which I also have a package.
I have created and uploaded fresh Slackware packages (targeting 15.0 and -current) for pure 32bit Wine as well as a 64bit Wine which also contains the 32bit WoW64 (Wine on Wine64) binaries. Both packages have the ‘staging‘ patches applied and contain Gecko (the Wine implementation of Internet Explorer) and Mono (the open-source and cross-platform implementation of the .NET Framework).
The external dependencies for this package remain the same: FAudio and vkd3d are required.
On 64bit Slackware you need to have multilib installed (read the docs). In addition to a standard multilib package set, in addition you need to convert the 32bit versions of the FAudio and vkd3d packages to ‘compat32’ packages and install those.
Note: the MinGW-w64 compiler suite is used to generate the native Windows DLLs in my wine package. This compiler is not needed when you just want to run wine. If you want to compile your own wine, you can install MinGW-w64 from my repository.
Have a good weekend!
Eric
You can always get help from Slackware - Installation. Be sure to post any request with information about your problem. Please be sure to use code tags when posting logs or command results so it is cleaner therefore easier to read and follow. You can use LQ FAQ and How to ask questions the smart way to give you guidelines for posting(s). I hope you enjoy the endeavor with Slackware and sharing through the community.
Hope this helps!
Have fun & enjoy Slackware!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
