/slackware/ - Slackware Linux

This is a board for #slackware@irc.rizon.net

That is an IRC Channel hosted by Rizon. You can connect to it with an IRC Client, such as BitchX, HexChat, Pidgin, AdiIRC, WeeChat, Irssi, EPIC or mIRC (Windows).

The IRC Server is Rizon (irc.rizon.net) and the channel is #slackware (once connected, /join #slackware).

There are two sister channels for #slackware, named ##linux (created for all Gnu/Linux distributions) and ##python (created for Python Programmers).

More Rizon Server details here: https://wiki.rizon.net/index.php?title=Servers

P.S.: Many thanks to the 8kun.top administration for fully restoring this board! And not a single thread was lost! :)

Hi there.

https://8kun.top/faq.html#help-my-board-has-been-deleted: "On 8kun, any board may be automatically deleted if it receives no new posts for four (4) weeks."

https://8kun.top/faq.html#i-lost-ownership-of-my-board-what-happened: "You may lose access to your board if you fail to log in for two weeks."

Since this board is very low on traffic, I've created this thread to create dummy posts, so my board isn't deleted.

Compass.

Hi.

User spurthi has made available his Free VPS through his bot "[VM][US]VMDeploy" in ##linux@irc.rizon.net

Type !vm in ##linux@irc.rizon.net to get access or read more at https://vmbot.fsirc.net

Enjoy!

Compass.

This is a late post but better than never!

Slackware 15.0 has been released!

There are no official torrents, but you can easily download them here: https://seedbox.slackware.uk/

Compass.

Hi there.

I've decided to remove all my programs from this thread. It's meaningless to post and update my source code both here and on GitHub. Besides, formatting source code so it's readable in a post is somewhat troublesome and unnecessary work.

Therefore from now on I'll be referencing all my source code in GitHub instead.

Whenever I post a new program on GitHub, I'll advertise it here with a new post in this same thread.

GitHub: https://github.com/compassnet/

Compass.

Here I leave the instructions to install SDK Platform Tools. You'll have adb (android debug bridge) and fastboot available, so depending on the manufacturer you can unlock your bootloader, install recoveries (twrp for example) or flash custom/stock ROMs with these programs.

https://developer.android.com/studio/releases/platform-tools

1. Download SDK Platform Tools from the link above

2. $ unzip platform-tools-latest-linux.zip

3. $ sudo mv platform-tools /usr/local/

4. $ sudo chown -R root:root /usr/local/platform-tools/

5. $ cd /usr/local/bin/

6. $ sudo ln -s /usr/local/platform-tools/adb

7. $ sudo ln -s /usr/local/platform-tools/fastboot

After those commands you'll have adb and fastboot available for all users. If you want to add more binaries, just make the proper symbolic links like above.

Compass.

Ever needed to exchange files between your Android Mobile Device and your PC (for example)?

Then this thread is for you.

Install SimpleSSHD (available from Google's Play Store, F-Droid or from the developers page below). It's very easy to configure and use.

Once you're done, you'll be able to open a secure shell and exchange/sync files to and from your Android devices using ssh/scp/sftp/rsync.

One SimpleSSH is running correctly, just use your LAN/WiFi to transfer files. No more need to plugin cables all the time (less wear on the USB ports too).

Note: You can use ssh-copy-id but there's a catch. Make sure you move the file authorized_keys one directory up so it looks like the following.

From this (wrong): /data/user/0/org.galexander.sshd/files/.ssh/authorized_keys

To this (correct): /data/user/0/org.galexander.sshd/files/authorized_keys

Then you'll be able to connect without a password. It's then safe to delete the folder (/data/user/0/org.galexander.sshd/files/.ssh/). When you use ssh-copy-id the file authorized_keys is saved to a wrong directory. You then have to manually fix it as above.

Downloads: https://play.google.com/store/apps/details?id=org.galexander.sshd & https://f-droid.org/en/packages/org.galexander.sshd/

Download and Instructions: http://www.galexander.org/software/simplesshd/

Compass.

From http://slackware.mirrors.tds.net/slackware/slackware-current/ChangeLog.txt :

Mon Jan 13 00:11:55 UTC 2020

a/elvis-2.2_0-i586-5.txz: Rebuilt.

Don't make /usr/bin/{ex,vi} symlinks.

a/nvi-1.81.6-i586-1.txz: Added.

This is an implementation of the classic ex/vi text editor written by Keith

Bostic. Due to this having UTF8 support which elvis lacks, we'll have it

take over the ex/vi symlinks if they aren't already pointing to a different

choice. Note that the removal of vi/ex symlinks from the elvis and vim

packages might cause your ex/vi symlinks to point to this after all the ex/vi

packages have been upgraded. You can set them to your preferences using

pkgtool -> Setup -> vi-ex.

As you can see, Elvis is being substituted by nvi.

I've done some editing with nvi to see how it goes, and from the little usage I've gotten from it, it's acceptable for simple day to day editing.

Now, if you're writing source code, beware that nvi doesn't have syntax highlighting. All you get are the colours of your terminal/console.

Since I'm learning the basics of Python programming and I make a lot of mistakes, syntax highlighting is very helpful.

Hence enter Vim. It comes standard with a Slackware 14.2 installation, and is the closest you can get to ex/vi along Elvis. Vim has syntax highlighting and is very configurable. Since Elvis seems to be walking out the door, I thought I might as well switch to Vim for coding, and perhaps use nvi for other stuff.

Below is my current $HOME/.vimrc file.

Source: https://gist.githubusercoPost too long. Click here to view the full text.

There are many alternative repositories for Slackware, and here I will post the ones that I currently know of.

https://slackbuilds.org/ (not a repository, but a collection of build scripts)

https://slackware.pkgs.org/

https://packages.slackonly.com/

https://slackware.nl/ - https://alien.slackbook.org/blog/ - http://www.slackware.com/~alien/slackbuilds/

If you ever have the need to run the setup scripts after you're done installing, look in /var/log/setup/.

For example, by running setup.80.make-bootdisk you can make a USB Linux boot stick. Such a boot stick is helpful in some situations, like when you forget to run lilo after updating your linux kernel and the computer won't boot. Of course you can also use the installation media to fix the same issue.

There is important information inside setup.80.make-bootdisk, so make sure to read it. The script will erase the USB stick. You have been warned.

$ less /var/log/setup/setup.80.make-bootdisk

or my favourite

$ most /var/log/setup/setup.80.make-bootdisk

Run them using sudo or root. All of them have prompts, so no changes will be done right away.

Compass.

Elvis is a vi/ex clone and is also Slackware's default vi text editor.

In this thread I won't get into Elvis's commands, but paste my $HOME/.elvisrc instead in the hopes that it's useful for those who use Elvis regularly like I do.

$HOME/.elvisrc is one of the locations where Elvis reads its user configuration file.

You can find the documentation for Elvis online on the internet, or by typing ":help" inside Elvis. This will open the on-line documentation in a new window though. To close the other window, use ctrl+w, w to switch to it, then ":q" to close it.

$ cat .elvisrc

set autoindent

set number

set report=1

set ruler

set scroll=24

set showmatch

set showmode

color normal brightwhite

color lnum yellow

color selection white

color comment lightgreen

color string lightred

color char brown

color number yellow

color function lightcyan

color variable lightmagenta

color link cyan

If you wish to disable "set number" with a file open for example, type ":set nonumber".

Happy text editing!

Compass.

It's possible to test your internet speed using only the command line instead of the web version of speedtest.net.

https://github.com/sivel/speedtest-cli

1. Download speedtest-cli (speedtest-cli works with Python 2.4-3.7):

$ curl -Lo speedtest-cli https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py

2. Move speedtest.py to /usr/local/bin/ and correct the permissions (I'm assuming that's where you want to install it):

$ sudo mv speedtest.py /usr/local/bin/speedtest && sudo chmod 755 /usr/local/bin/speedtest && sudo chown root:root /usr/local/bin/speedtest

3. Read the speedtest-cli help:

$ speedtest -h

If you need to know the specific servers that speedtest.net uses, go to: http://c.speedtest.net/speedtest-servers-static.php

And if you want the ip address of any server, use dig (or nslookup) like this: $ dig speed-server.speedtest.net

Compass.

If you want to block spam hosts from bothering you, one solution is to use a Blocklist combined with /etc/hosts.

Searching around the internet you can find various free Blocklists, but one of the best is https://pgl.yoyo.org/adservers/.

1. Go to https://pgl.yoyo.org/adservers/ with your web browser.

2. In "list ad server hostnames:" select "hosts – in hosts file format" and "view list as plain text:", then click on "go". Save the list (for example spamhosts.txt).

3. Then as root append spamhosts.txt to /etc/hosts:

# cat spamhosts.txt >> /etc/hosts

This command will add spamhosts.txt to the end of your current /etc/hosts, but if you're worried make a backup before you run the command above.

4. There is no need to restart your browser or computer after saving /etc/hosts.

The Blocklist will make requests for the spam hosts to go to localhost (127.0.0.1), which means your computer will translate the host to 127.0.0.1 (just like a DNS Server would). Since 127.0.0.1 is just localhost (your computer with no http server to pull content from), nothing will happen.

Just in case you want to know what my /etc/hosts looks like (I changed the local machine hosts of course), here's a snippet blow:

#
# hosts         This file describes a number of hostname-to-address
#               mappings for the TCP/IP subsystem.  It is mostly
#               used at boot time, when no name servers are running.
#               On small systems, this file can be used instead of a
#               "named" name server.  Just add the names, addresses
#               and any aliases to this file...
#
# By the way, Arnt Gulb

This is the .screenrc I currently use for GNU Screen.

With it you can change windows by using the Function Keys on your keyboard (F1, F2 and so on).

To use it, just place the file in your $HOME and you're set. If you already have a $HOME/.screenrc, make a backup first just in case.

The screenshot differs from the .screenrc by the way.

#
# This is an example for the global screenrc file.
# You may want to install this file as /etc/screenrc.
# Check config.h for the exact location.
#
# Flaws of termcap and standard settings are done here.
#

#startup_message off

#defflow on # will force screen to process ^S/^Q

deflogin on
#autodetach off

#vbell on
#vbell_msg "   Wuff  ----  Wuff!!  "

# all termcap entries are now duplicated as terminfo entries.
# only difference should be the slightly modified syntax, and check for
# terminfo entries, that are already corected in the database.
# 
# G0 	we have a SEMI-GRAPHICS-CHARACTER-MODE
# WS	this sequence resizes our window.
# cs    this sequence changes the scrollregion
# hs@	we have no hardware statusline. screen will only believe that
#       there is a hardware status line if hs,ts,fs,ds are all set.
# ts    to statusline
# fs    from statusline
# ds    delete statusline
# al    add one line
# AL    add multiple lines
# dl    delete one line
# DL    delete multiple lines
# ic    insert one char (space)
# IC    insert multiple chars
# nx    terminal uses xon/xoff

termcap  facit|vt100|xterm LP:G0
terminfo facit|vt100|xterm LP:G0

#the vt100 description does not mention "dl". *sigh*
termcap  vt100 dl=5\E[M
terminfo vt100 dl=5\E[M

#facit's "al" / "dl"  are buggy if the current / last line
#contain attributes...
termcap  facit al=\E[L\E[K:AL@:dl@:DL@:cs=\E[%i%d;%dr:ic@
terminfo facit al=\E[L\E[K:AL@:dl@:DL@:cs=\E[%i%p1%d;%p2%dr:ic@

#make sun termcap/info bette

If you've used my IPTables VPN Killswitch thread together with the Local Caching Name Server thread, you'll likely be unable to connect or reconnect to your VPN Provider Servers.

That's because IPTables will interfere with BIND (basically it won't be able to resolve your VPN's hosts), but there is a fix.

BETWEEN THIS RED TEXT, CONSIDER THIS WORK IN PROGRESS!

$ cat /etc/named.conf

options {

directory "/var/named";

/*

* If there is a firewall between you and nameservers you want

* to talk to, you might need to uncomment the query-source

* directive below. Previous versions of BIND always asked

* questions using port 53, but BIND 8.1 uses an unprivileged

* port by default.

*/

// query-source address * port 53;

So what you need to do is this. And by the way, at this point the VPN Killswitch should be active and OpenVPN inactive (disabled).

1. Stop BIND:

# cd /etc/rc.d/

# ./rc.bind stop (you can use status instead of stop if you want to verify the current state)

2. Uncomment (remove the /'s) from the line "// query-source address * port 53;" in /etc/named.conf, so it looks like this "query-source address * port 53;". You can also leave the original line and just paste an uncommented copy right below like I did (check this threads image).

# vi /etc/named.conf (or use your favourite text editor)

3. Start BIND:

# cd /etc/rc.d/

# ./rc.bind start

4. Start OpenVPN:

# /etc/rc.d/rc.openvpn start /path/tPost too long. Click here to view the full text.