Lumin Etherlight

Lumin Etherlight, welcome to this humble home of mine, a small haven in the vast wired. A pleasure to meet you, friend. Enjoy the calm, while you’re here. If you wish, perhaps, to learn more about me, go ahead[1], feel free to ask about anything[2], or say hello, if you so wish; I enjoy hearing other voices from beyond the network. If you’re here to explore, then allow me to point you towards some landmarks. But the rest, is on you, traveler. Follow the flows of the hyperlinks, see where they may take you.

If you are here for Etherlight consultation services, please proceed to the Etherlight[3] website, and send us a message at our official contact email address.

This website is where I write, on writing[4] sometimes, if that is of any interest to you, but also on whatever other things that capture my own interest for the day. A list of software[5] tools and packages I frequently use is somewhere around here, so is a list of packages[6] I maintain for Slackware[7]. I will stop rambling, for now, but you can always check this site’s RSS feed[8] to be informed of any new and improved rambles I may put out into the world.

Sometimes, I hea^@)^]\214^\9\213Q^?\200\0\0\0\0

DREAMLINK CONNECTION LOST...

CORE DATA CORRUPTION DETECTED...

SITE RECONSTRUCTION IN PROGRESS...

[1]	[^1]	/c/2C2606/mdv48
[4]	[^1]	/c/2C2606/QoIWB
[5]	[^1]	/c/2C2606/18o8E
[6]	[^1]	/c/2C2606/MuecF
[7]	[^1]	/c/2C2606/kTAdo
[8]	[^1]	/feed.xml
[2]	[^1]	mailto:lumin@etherlight.link
[3]	[^1]	https://www.etherlight.link/

In silence, I hone my Craft; in its perfection, I take pride. The might of a written Word. The power of Language. Order, Chaos, Emergence. Direct solutions, and minimalism, over grandiose dreams of over-engineering. To work on something that would help humanity; that would move us all, if one step forward.

Seeking those who may think the same.

Back References:

/c/2C2606/MkT2d Lumin Etherlight, welcome to this humble home of mine, a small haven in the vast wired. A pleasure to meet you, friend. Enjoy the calm,…

Lightmark, a markup language for the pure of word. You will, perhaps, notice that this entire site is made of plain words[1] and hyperlinks. In pursuing their ultimate purity, I have developed the Lightmark, a tool for writing, that prohibits the use of textual formatting, and multimedia. It enforces focus on paragraphs of pure prose, and the weaving of hyperlinks. The foundational thesis of Lightmark, is that symbols, and the links in-between, are all you will ever need.

[1]

[^1]

/c/2C2606/QoIWB

Back References:

/c/2C2606/QoIWB The word, our true ancient magic, in writing it travels through time and place. Thoughts in my mind, in my place, in my now, will be thoughts in…

The word, our true ancient magic, in writing it travels through time and place. Thoughts in my mind, in my place, in my now, will be thoughts in your own mind, your place, and your now. I will probably never even know... Or even know you. I inscribe my thoughts and words in lightmark[1], my hand-made markup language. I manage most of my writings as redcore[2] sites. I will further expand on my methods as time goes on, as I see more, and learn more, but for now, I have other words to attend to.

[1]	[^1]	/c/2C2606/2lalc
[2]	[^1]	/c/2C2606/87KC2

Back References:

/c/2C2606/MkT2d Lumin Etherlight, welcome to this humble home of mine, a small haven in the vast wired. A pleasure to meet you, friend. Enjoy the calm,…

/c/2C2606/2lalc Lightmark, a markup language for the pure of word. You will, perhaps, notice that this entire site is made of plain words and hyperlinks. In pu…

Red Core, is a system of thought. Technically, it is an integrated collection of a few thousand lines of POSIX shell scripts, Emacs plugins, and small C applications and utilities, all written by me for my personal work-flows. Red Core is loosely inspired by the Zettelkasten, GTD, various database management engines, disk drive file-systems, and some methods for managing and indexing libraries of physical paper documents. I will write more about it later, as time permits, and perhaps publish some source code.

Back References:

/c/2C2606/QoIWB The word, our true ancient magic, in writing it travels through time and place. Thoughts in my mind, in my place, in my now, will be thoughts in…

Software I use, workflows I mold. My preferred operating system is Slackware[1] Linux, for desktop and server alike. Sometimes, I dabble in OpenBSD; I enjoy its simplicity. I spend most of my time inside my Emacs editor, writing prose or code. If I’m feeling a bit meditative, I may drop to ed to do the same. I surf the web with my own heavily modified suckless surf fork, built around the WebKit engine. For the terminal emulator I use st, and for the window manager, dwm. Both are patched and modified by me, but nowhere near as much as surf. As for the system kernel, I configure, compile, and run my own private builds. For communication, mostly email and Usenet, managed with Emacs GNUS, but sometimes also IRC, Signal, and WhatsApp (sadly).

I will expand on each, later, as time permits.

[1]

[^1]

/c/2C2606/kTAdo

Back References:

/c/2C2606/MkT2d Lumin Etherlight, welcome to this humble home of mine, a small haven in the vast wired. A pleasure to meet you, friend. Enjoy the calm,…

Slackware Linux, is my favorite OS, after living for many years with Gentoo, Devuan, Debian, and Arch before that, and dabbling in many others, on desktop and on the server. I have enjoyed the simplicity of Slackware, its stability, and the ease of understanding and modifying it, without it fighting me and breaking my changes all the time. I maintain some Slackware software packages on the SlackBuilds[1] website. If you are facing issues with pre-compiled software demanding newer glibc library versions, you may be interested in looking into how I get Signal[2] binaries to work there by patching their ELF headers to override the dynamic linker and glibc libraries, allowing the usage of more up to date versions of them, without updating the base system defaults.

[1]	[^1]	/c/2C2606/MuecF
[2]	[^1]	/c/2C2606/mf3gC

Back References:

/c/2C2606/MkT2d Lumin Etherlight, welcome to this humble home of mine, a small haven in the vast wired. A pleasure to meet you, friend. Enjoy the calm,…

/c/2C2606/18o8E Software I use, workflows I mold. My preferred operating system is Slackware Linux, for desktop and server alike. Sometimes, I dabble in…

SlackBuilds are scripts to build packages on Slackware. I maintain a few on the SlackBuilds[1] website. Bellow, is a list of the Slackware software packages I’m currently responsible for. Send me an email if you face any issues building or running them. The list may get outdated, so check the SlackBuilds site search[2] for the most current list. You can find the email address to message me at in the ‘*.info’ description file of any of the SlackBuilds I maintain.

busybox, exiftool, feh, grepcidr3,

luanti, nodejs18, optipng, xclip

[1]	[^1]	https://slackbuilds.org/
[2]	[^1]	https://slackbuilds.org/advsearch.php?q=Lumin+Etherlight&stype=maint

Back References:

/c/2C2606/MkT2d Lumin Etherlight, welcome to this humble home of mine, a small haven in the vast wired. A pleasure to meet you, friend. Enjoy the calm,…

/c/2C2606/kTAdo Slackware Linux, is my favorite OS, after living for many years with Gentoo, Devuan, Debian, and Arch before that, and dabbling in many others,…

/c/2C2606/mf3gC Signal, on Slackware 15.0, stopped working a few days ago, as of Jun 4th, 2026, when installing it from SlackBuilds. It requires a newer glibc li…

Signal, on Slackware 15.0, stopped working a few days ago, as of Jun 4th, 2026, when installing it from SlackBuilds[1]. It requires a newer glibc library version than what is provided, by default on Slackware. Some users do fix this by upgrading their glibc library packages to the latest testing ones, from Slackware’s site. This, however, might be risky, and will cause all packages compiled on the upgraded machine to never work on any machines without the upgrade. Thus, you might wish to keep your original Slackware glibc packages, but still want Signal to just work. This hack[2] will allow Signal to use a more up-to-date glibc version, without upgrading the OS base libraries; seems to work for me. First, install the new testing glibc package into a root inside /opt, isolated from the rest of the system, then patch the ELF headers, using patchelf, to update the runtime linker and override the linker library search path for all executable and library files inside the Signal package, to make them use the glibc libraries we installed to /opt, instead of the system-provided ones. If you are interested in this, please check the script[2] for details, and info on how to run it. This is definitely a hacky path, but it is a much narrower intervention than updating glibc for your entire system. It is also well isolated from the rest of the system, so harm is minimized. You can easily revert this hack, if you wish. Do not be alarmed if you see warnings about not finding ‘.interp’ sections, they are harmless, and happen because the dynamic linker in shared libraries can not be updated in the ELF binary itself, but is set instead by the actual executable that requests the shared library dynamically.

At the end of this, Signal should run fine, hopefully :)

[1]	[^1]	/c/2C2606/MuecF
[2]	[^1,^2]	/s/2C2606/saNeW

Back References:

/c/2C2606/kTAdo Slackware Linux, is my favorite OS, after living for many years with Gentoo, Devuan, Debian, and Arch before that, and dabbling in many others,…