You are not logged in.
went to "Lunduke's Projects" on main webpage:
and was curious about:
https://github.com/BryanLunduke/Wikipedia-Donation-Destroyer
direct readme url:
https://github.com/BryanLunduke/Wikipedia-Donation-Destroyer/blob/master/README.md
thought-provoking at the very least...
thread is marked "solved" but cannot figure out which post provides the "solution"?
OP, please update OP to utilize code block. tia.
had this link handy so providing it here for present and future thread visitors:
can the title of this thread be changed to include FRAMEWORK as the manufacturer so that people searching titles for hardware can be aware that they might not want to mess with framework given this thread and others like it across the interwebs.
re: AI
https://craphound.com/news/2026/09/20/technopolitics/
imhho, if everyone read everything Cory Doctorow ever wrote and/or spoke, the world would be much better off.
and, along those lines:
https://craphound.com/news/2026/07/12/12659/
ymmv.
re: slackware
have found these rss feeds handy:
http://www.slackware.com/~alien/slackbuilds/ChangeLog.rss
https://mirrors.slackware.com/feeds/slackware64-15.0.rss
been using Void Linux for about three years and has been ok for the most part
to update i just ctl-alt-t, sudo su, xbps-install -Su, exit from root and do a quick xcheckrestart
then one needs to manually empty everything in /var/cache/xbps/ with a quick sudo rm *.sig* *.xbp*
(if you don't do this then at some point in the future you will potentially run low on free space and all that that entails)
(and i also save the cli session as a text file for later review if necessary)
as always, your mileage may vary
in any case, keep us posted
huge thanks and kudos for keeping us posted and especially your success!
semi-random _food_for_thoughts_ regarding creating an external-data-device capable of booting on both older-bios-booting and newer-uefi-booting hardwares:
as always, ymmv.
edited to add the below.
also see: https://askubuntu.com/users/43926/c-s-cameron for additional articles/commentary/etc.
@ralph.ronnquist, thanks for taking the time and effort to explain why Ventoy causes/creates issues/problems/failures for _some_but_not_all_ folks!
(imhho, your post deserves a "sticky" somewhere it can be easily found)
yt-dlp definitely has a learning curve no matter how you install and set it up.
there is a reason why the main webpage is a very very long slog:
pulled this snippet out of OP OP OT(original-poster_original-post_original-topic)referenced url:
https://windowsforum.com/threads/chrome-150-patch-for-cve-2026-13933-passwords-policy-fix-after-renderer-compromise.433930/
The Bigger Chrome 150 Story Is Attack Surface Sprawl
Chrome 150’s 433 security fixes are striking not only because of the count, but because of their spread. The release notes cover graphics layers, device APIs, extensions, remote access, browser UI, rendering libraries, and platform-specific components. A browser is now closer to a miniature operating system than a document viewer.
That sprawl changes how defenders should think. There is no single “browser vulnerability” category anymore. There are GPU bugs, WebUSB bugs, extension bugs, password bugs, AI-surface bugs, media bugs, and policy bugs, each with different exploitability and enterprise impact.
CVE-2026-13933 sits in the policy category, and policy bugs are easy to underappreciate. Memory corruption sounds dramatic. Policy enforcement sounds bureaucratic. But many of the most consequential security failures are cases where code does exactly what it was written to do — just for an actor that should never have been allowed to ask.
That is why the phrase policy enforcement deserves attention. It is the security model made executable. When it fails, the browser’s internal contract between trusted and untrusted components begins to fray.
regardless of which OS and/or _browser_ one is using, the whole commentary is worth reading when the time is available for such.
may or may-not help but still good information on raid at:
https://dev1galaxy.org/viewtopic.php?id=7213
and also perhaps:
concur with @steve_v regarding installers.
is it just me or does anyone else get hot under the collar when installers refuse to install if the hardware is airgapped/offline/etc?
_just_
_NO_
_wtf_
...ahem...cough...sigh...
mostly out of curiosity as to the quality and format of offline materials...
went to link @chomwitt provided:
https://debian-beginners-handbook.arpinux.org/index-en.html
and then further:
https://debian-beginners-handbook.arpinux.org/trixie-en/index.html
and downloaded the 17MB 267page pdf(warning: direct link to pdf download)
*ttps://debian-beginners-handbook.arpinux.org/trixie-en/download/the_beginners_handbook.pdf
fun read so far.
ymmv.
more re: 486
(also that processor photo is awesome in and of itself, ha!)
doubtful that a 486 system would have enough ram for _any_ Devuan.
wikipedia
https://en.wikipedia.org/wiki/The_Story_of_Mel
and at this current post time, the first link in the "further reading" sub-section contains an image containing Mel Kaye
current working link:
thanks for the update and the solution!
thinking about automount always reminds me of that time my kid stuffed toast loaded with cream cheese into the vhs slot...smh...