If the above "double ssh" command works, then we've established that our assumptions about ports (that the default port 22 is being used everywhere) and firewalls (that R2 and PC1 are allowing incoming on port 22) are correct.

To achieve SFTP via port forwarding, you have to tell R1 to take incoming traffic on port 22 and forward it to R2. Then you have to tell R2 to take incoming traffic on port 22 and forward it to PC1. I think that should do it.

@contrast - The best place to share this AppImage with a larger community would be at https://www.appimagehub.com but unfortunately the requirements for submitting an AppImage there are too strict (the application needs to be compiled on a machine with very ancient glibc, for instance). It's just too much of a hassle.

Hopefully people who want an AppImage of gimp 2.8 will find this thread. I'll leave my tweaked, final version of the AppImage at this link indefinitely:
http://files.dantas.airpost.net/public/ … 4.AppImage

Cheers!

I figured it out. Gimp cannot find the plugins inside the AppImage. I came up with a quick fix, which involves two changes:

1. At root of AppDir there is gimp.desktop. Change its Exec line from this:

Exec=gimp-2.8 %U

To this:

Exec=gimp-2.8-wrapper %U

2. Create (and mark as executable) AppDir/usr/bin/gimp-2.8-wrapper with this in it:

#!/bin/sh

dir=/tmp/gimp2.8-plugins

if [ ! -d "$dir" ]; then
	mkdir -p "$dir"
	HERE="$(dirname "$(readlink -f "${0}")")"
	cp -r "$HERE"/../lib/gimp/2.0/plug-ins "$dir"
fi

export GIMP2_PLUGINDIR="$dir" 
exec gimp-2.8 "$@"

Create AppImage from the tweaked AppDir. Now the AppImage works perfectly. Thanks again, Tatwi!

EDIT: I cleaned up the wrapper script a bit.

Hi, Tatwi. I use an AppImage of GIMP 2.10.8 but, like you, I'm unhappy with the recent changes.
Can you please share your AppImage of GIMP 2.8.x for 64-bit?

If proficient UNIX/Linux usage is a craft, then the shell is the craftsman's workbench. I think having a solid grasp of bash--and knowing how it's different from other shells--is key. You can't go wrong by starting with the shell because it's essential no matter what your specific needs are. Where you go from there depends on your specific needs and interests.

- best bash tutorial anywhere: http://tldp.org/LDP/abs/html/
- compilation of bash pitfalls: https://mywiki.wooledge.org/BashPitfalls
- learn to recognize bashisms: https://mywiki.wooledge.org/Bashism

Write as many shell scripts as you can. After a script is working, make it correct. After it's correct, make it beautiful. Here is a tool to help you improve your existing shell scripts: https://github.com/koalaman/shellcheck

I hope that helps

The official Tiny Core Linux wiki is down. Developers are aware and working on it. In the meantime, wiki can be accessed via this mirror:
https://www.linuxsecrets.com/tinycoreli … start.html

Their forum is alive and well:
http://forum.tinycorelinux.net

Main reason to strip binaries is to make them smaller (I've sometimes seen them shrink to 50-75% of original size). TCL packages contain stripped binaries in the interest of keeping everything as tiny as possible.

Asking people to pitch in computing power but they refuse to show the source code? That's lopsided and creepy.

I'll be happy to contribute and spread the word when they make the source code available.

That's not correct. The output of the hwclock command is your local time, and what comes after the final + or - is your timezone's offset from UTC. +00:00 would only be correct for users who live in Greenwich

Please go over the steps above in my longer post. If you still have questions after that, let me know and I'll try to help.

No resolution. Also, I don't know if this is peculiar to T400 or all laptops.
Note that the ExpressCard came with a power cable, but I don't use it because I don't want to carry around an extra cable.

So here is what I've discovered:

- ExpressCard never works on battery power.

- ExpressCard works if laptop was on AC when it booted and has been on AC continuously up to and including when I use the ExpressCard.

- If laptop was on battery power when it booted and later I switch to AC power, I need to eject and re-insert the ExpressCard in order for it to work.

Hope this helps.

Ron,

I don't think the fact that your friend's email client is proprietary has anything to do with it. Also, uni2ascii is unlikely to help. It sounds like an encoding issue.

The emoji in question is the "slightly smiling face" (formal Unicode notation: U+1F642, details about it here: https://www.iemoji.com/view/emoji/1112/ … ling-face). Here are the relevant details:
UTF-8 encoding: 0xf09f9982
UTF-16 encoding: 0xd83dde42 (notice this matches the "D83D "DE42" in your original post)

How are you viewing your friend's emails? In a web browser? If so, take a look at that emoji here:
https://unicode.org/emoji/charts/full-e … html#1f602

If you can see the "slightly smiling face" emoji there under the "Browser" column, we'll know it's not a browser or font issue on your end.

My best guess is that your friend's email client is using UTF-16 encoding, while your email client is expecting UTF-8 encoding. Different encodings agree on how to represent 7-bit ASCII characters but differ on how they represent wider characters such as emojis.

Have your friend check their outgoing mail encoding and change it to UTF-8 if it's currently something else.

Forking the OpenBSD kernel in order to avoid systemd and/or other linuxland woes makes no sense. By virtue of not being Linux, OpenBSD (as-is) does not suffer from linuxland woes.

With extensions/packages. I don't think it would be appropriate to take up space on Devuan's servers to go into great detail here. If you decide to try it and need help, start a thread on forum.tinycorelinux.net or send me a personal message there (my user name is GNUser there, too).

Everything you need to know to get started is in the gratis e-book "Into the Core":
http://www.tinycorelinux.net/corebook.pdf