Newer versions of Slackware should boot fine with just dd'ing the iso to a USB stick. From the 14.1 release notes:

> Slackware ISO images (both the ones available online as well as the discs sent out from the Slackware store) have been processed using isohybrid. This allows them to be written to a USB stick, which can then be booted and used as the install source. This works on machines running both regular BIOS as well as UEFI.

So, the "w3m" SlackBuild includes w3mimg (or w3m-img) by default. While not a separate executable, assuming you have "Display Inline Images" turned on, and your terminal emulator supports it (which are you using?), it should work out of the box.

I just used sbopkg to install w3m, and while MATE Terminal didn't show images, xterm did just fine. So the good news is that the package is already installed for you. The bad is something else is getting in the way.

Important to note: on the SlackBuild page for w3m, it mentions that it requires imlib2. Did you install imlib2 via SlackBuild? If not, grab that and give it another try.

Also, should you be interested: generally, if you run into software XYZ and there's not package nor SlackBuild for it, here's my typical go-to:

1.) Find the source for the software. In the case of w3m, it's at https://sourceforge.net/projects/w3m/. 2.) Download the source and untar/unzip it. 3.) In the resulting folder, as another user noted, run the following:

./config make make install (the last one might require sudo/root)

Assuming you have the needed dependencies, you should be good to go. And if not, it'll error during the build and you can go from there.

Hopefully this helps out, and props for sticking with it. Let me/us know if you need anything else. :)

There's a bug in iwlist: too many access points can overflow its internal buffer.

wicd uses iwlist; networkmanager doesn't. The easy workround is to use networkmanager.

Alternatively there's a patch here: http://www.linuxfromscratch.org/patches/blfs/svn/wireless_tools-29-fix_iwlist_scanning-1.patch

> Hey there, how many members the slackware development team is composed of?

Checking the release notes for 14.2 is probably the best way to find out who's working on Slackware.

> How to become a slackware developer?

Gain Patrick's trust, mostly likely by helping Slackware from the outside for a number of years. But Pat is the ultimate decision maker on who qualifies.

14.2 is the last stable release. It gets patches and fixes, but not updates just for the sake of doing updates.

For example, Slackware-current is running kernel 4.14.61. Slackware 14.2 is on 4.4.144.

Look at the changelog for -current and the changelog for 14.2. Pretty much everything in -stable is a security fix. Current gets new versions of packages just because.

I did this several years back on a 2009 MBP. I used refit to get it to work.

As much as I like Slackware, the Arch documentation is usually where I find the best answers. You have to work around their Arch-only bits, but they're thorough and well written.

You should ALWAYS upgrade your kernel in Slackware manually. Don't use slackpkg update/upgrade-all to upgrade kernels. It's NOT a good idea. You should blacklist the kernel in slackpkg. Others may blow this off and poo-poo it, but this is experience talking here. Pay attention. :)

​

There have definitely been MANY upgrades to the kernel in 14.2 since 2016, that's for sure. You can see them all here -> http://www.slackware.com/security/. My Slack64-14.2 is currently running 4.4.240.

It's a risk. I download some compiled software from sources I trust. Including the browser I am using right now. This post provides documentation and a download point for some of the machines running slackware that I support, if nothing else. Anyone is free to do their own compile and check it.

The compile required about 2 hours on my machine. Someone may be looking to save some time, but as you say it's a risk. In some ways, the open source movement is to avoid relying on others for binaries. Of course, linux from scratch is an example of bootstrapping from source only.

Keep in mind! Steam uses 32-bit, so if you're on Slack x64 you'll have to install the Slackware multilib.

Not sure if the slackbuild does this for you or not.

It depends how far away Current is from the Stable release. Right now Current is very close to Stable, so you could look at the Current changelog and try to replace those packages with the versions from 14.2. pkgtools doesn't care about software dependencies, so you shouldn't run into any issues where it won't let you delete/install packages (although there could be other issues).

I do a full install of every Stable release (without formatting /home) and then restore my custom configurations (/etc). But my installations always end up as a mix of Stable and Current because I compile+install the Current version of some software on my Stable PC.

http://www.slackware.com/~msimons/slackware/grfx/shared/bluepiSW.jpg

http://cache.desktopnexus.com/cropped-wallpapers/8/8201-1920x1080-%5BDesktopNexus.com%5D.jpg?st=fEJLMdU8zXIKXND8jQL-9g&e=1448827306

Hahaa, that is true. Both logo's I think look very beautiful.

Slackware "keep-it-simple" approach allows to customize it to any specific needs. If you are interested in games, here, for example, Eric Hameleers' (AlienBOB) Linux client for the Steam gaming platform or you can also try steam.SlackBuild from SlackBuild.org Performance in 3D games would primarily depend on how well your graphic card is supported by Nvidia/ Linux driver , see e.g., Anyone using a GTX 960? What's it like with Linux? Slackware currently offers recent mesa-11.0.4 and xorg-server-1.17.4 and good modern selection of desktop environments not filled with the bloatware...

I would like to point out some work has been done to allow PAM to work with slackware. vbatts@ did a lot of the leg work, and his stuff can be found at the following:

• http://www.slackware.com/~vbatts/pam/
• http://www.hashbangbash.com/downloads/pam/

This should help your efforts.

From http://www.slackware.com/releasenotes/15.0.php

> On the 32-bit side, there are both SMP (multiple processor capable) and non-SMP (single processor) kernels. The non-SMP kernel is mostly intended for machines that can't run the SMP kernel, which is anything older than a Pentium III, and some models of the Pentium M that don't support PAE (although it seems that these might support PAE but just lack the CPU flags to advertise it -- try booting with the "forcepae" kernel option).

If those games work with Steam and Proton on another Linux distribution they should work on Slackware. Most 3rd-Party software is done with SlackBuilds build scripts(see slackbuilds.org). There seems to be a SlackBuild available for vscode(of course GCC and Clang are present for your C language endeavors). I haven't used VirtualBox yet on Slackware, but I have used Qemu and virtmanager. There are also 3rd Party repositories for pre-built packages. The Minecraft launcher will certainly work if you install the JDK/JRE. You can use one of the many tools such as sbopkg and slackpkg+ to manage these packages. For Steam you need to use AlienBob's multilib 32bit compatibility packages(see http://www.slackware.com/~alien/multilib/). There is an effort to keep SlackBuilds scripts working on slackware64-current located on GitHub, and you will likely need to use this until the SlackBuilds repository moves to Slackware 15.0. SlackDocs(http://docs.slackware.com) and the text files that cover installation found in the Slackware file tree are a great help. The Slackware forum over at LinuxQuestions.org is a great place to post if you have other questions.

I don't use Steam but here's a post discussing installing it on Slackware

https://www.reddit.com/r/slackware/comments/4vzzp2/how_to_install_steam_client_on_slackware_142/

My favourite tool for handling cloud storage is rclone

Recently, they've added a web page option to it.

See https://rclone.org/gui/

If you still feel the urge to compile things, I'd recommend sbopkg, which I use to handle compiling & installing packages.

Oh, also, slackpkg handles keeping things up-to-date for security patches, etc.

Come on in, the water's fine!

http://www.slax.org/documentation.php

"Thanks to it, Slax runs on computers with as low as 48MB of RAM (in text mode)."

You could try X with the xfce window manager (it's included but KDE is the default). Slax does use compressed swap technology which would be advantageous in such a situation but there's no way you're going to run the default graphical environment.

Let me know if you need any help with it, I know Slax fairly well as I've customized versions of the Slax bundles you'll see under the /slax directory (.sb extension) to include such things as ~~kernel modules~~ firmware for my TV Tuner card.

Windows copies itself to the place I specified in my earlier post, which is probably want Linux distros should do too. Slackware just doesn't do it because, well, it's Slackware. You're expected to know about this beforehand and do it yourself because the distro generally takes that approach. Windows also has extra help because a lot of boards are just programmed to look for Windows, even though it's against spec

If you want to prevent this from happening in the future, you can either manually copy elilo (and the conf, kernel, and initrd) to \efi\boot\bootx64.efi or you can install something like rEFInd there. I prefer the second option because it's useful for other things

> leaving sudo off by default

It's so hard to add a new user to wheel (not even necessary, I think) and to make one-line edits to two files in /etc...

> PS in case you live in a rock

The bug has been fixed, says the changelog.

Once it comes out, yes it should be possible with a few caveats. You can read the -current changelog to see if any package upgrades affect your system.

If you want to get a feel for what it may be like, set up a VM or a spare computer with 14.2, update it with slackpkg, then change the slackpkg mirror list to point at a -current mirror. Do

# slackpkg update # slackpkg install-new

Note any changed or new config files, then

# slackpkg upgrade-all

And again take care of any changed/new configs. Reboot and you should in theory be fine. Any hangups, issues, or gotchas present during this operation will possibly appear when upgrading to 15.0 after its release, so keep that in mind.

>Pentium 4 2.2ghz and 2gb RAM

Ouch. You'll truly test your patience compiling LO on that hardware. How many days can you afford? :-)

If you only want the LO package, there is a slackbuild to convert the upstream RPM to a tgz package.

Another option is to use a pre-built from Alien Bob. You can download the binary package or use his build script.

slackpkg clean-system

• uncheck all but the vlc that you just installed

Now go to Alien Bob's repos and download/install his vlc .txz file.

http://www.slackware.com/~alien/slackbuilds/vlc/

Luck!

AlienBOB's version of Steam works fantastically as well, for those who aren't using sbopkg: AlienBOB's Slackbuilds

For any new folks reading this, however, don't forget to modify your /etc/slackpkg/blacklist after installing Slackbuilds and the multilib by adding the following lines:

[0-9]+_SBo

(For Slackbuilds from Slackbuilds.org)

[0-9]+alien

(For AlienBOB's Slackbuilds)

[0-9]+compat32

(for AlienBOB's multilib... this one's especially important because, if you don't add it, your multilib absolutely WILL get messed up by standard slackpkg updates)

Sorry for the late reply.

I'm probably being lazy/impatient but I don't know where the source is. I'm looking at the build folder and I don't see a source, maybe it was removed. The link is removed too for slackbuilds.org link for 32bit.

I've just been booting up Linux Mint through a flashdrive at the moment, unfortunately I did not set up one of those partition things that allows you to save on a live USB.

This is only a problem when I'm trying to stream movies on this little computer so whatever... YouTube works (HTML5 right?)

Yeah maybe I'm just being weak and giving up. I've looked around for a 32bit source for Chromium, unless it's included in Slackware 14.1? I did a full install.

Thanks for the warning! I use command-line utilities for handling compressed files, anyway :)

curl -O http://www.slackware.com/~alien/slackbuilds/p7zip/pkg64/14.1/p7zip-15.09-x86_64-1alien.tgz sudo installpkg p7zip-15.09-x86_64-1alien.tgz man p7zip

This was just added to Slackware-current. From the changelog:

> ap/sudo-1.8.15-x86_64-1.txz: Upgraded. > New options: --with-insults --with-all-insults --with-pc-insults. > Sorry about this, I know it's a bit silly. ;-) > Thanks to chytraeus for the suggestion.

OK, so in the interest of internet friendliness, I've re-booted my PC from a LiveSlax CD.

Having done that, yes, iso2usb.sh is available.

I am now slowly downloading a Slackware ISO to test this script.

Meanwhile, my VMs and video streams to the rest of the house are down, so I fully expect annoyed daughters to appear any minute now coz I don't have money to buy a real server. Hint, hint.

Running the command

iso2usb -I slackware64-14.2-install-dvd.iso -o /dev/sdh -c 1.3G -w 15 -v

gives output

Required program (s) not found in root's PATH mkdosfs Exiting

I downloaded package dosfstools-3.0.28-i586-1.txz from a Slackware mirror and ran

installpkg dosfstools-3.0.28-i586-1.txz

to install it.

This is onto the running Slackware image booted off my CD. Your USB booted image may have other files missing like you indicated.

The programs sgdisk & gdisk are in the package gptfdisk-1.0.1-x86_64.txz.

I couldn't find the program extlinux, so you might have to download & compile that from source.

https://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-6.03.tar.xz

Now, I found that to compile this, you need libunistring & nasm installed, so head back to your Slackware mirror, download & installpkg them before running make in your syslinux folder.

I've been using intel's pstate stuff exclusively for around 6 months now, I think (albeit on Gentoo).

I honestly like it quite a lot and think it does as good as if not much better than the ondemand governor.

If you are worried about extending your battery life further you could play with the performance tuning options. I haven't messed with them, though.

max_perf_pct: limits the maximum P state that will be requested by the driver stated as a percentage of the available performance. The available (P states) performance may be reduced by the no_turbo setting described below.

min_perf_pct: limits the minimum P state that will be requested by the driver stated as a percentage of the max (non-turbo) performance level.

no_turbo: limits the driver to selecting P states below the turbo frequency range.

see: https://www.kernel.org/doc/Documentation/cpu-freq/intel-pstate.txt