You are not logged in.
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...
after a casual review of all posts at:
https://dev1galaxy.org/search.php?action=show_user_posts&user_id=7554
...smells ...fishy ...ai/bot ...?
my thoughts echo a previous reply:
when i used Evolution i remember the "Save/Restore Evolution Data" function having a duration in direct proportion to the total number of emails in the client.
to make the duration more tolerable we moved as much as possible to cold-storage/verified-backups to eliminate the "Save/Restore Evolution Data" workload.
keep us posted on your progress!
grabbed my old chimaera drive since i was using evolution on it.
wanted to confirm that evolution does have its own backup function(so if you don't have a current one then make a couple backups, preferrably on different media)
also evolution has a "remove duplicate messages" function as well(you mentioned "repeating mails" but i suppose that isn't the same as "duplicates" so that probably won't work for you)
i was able to create a new directory/folder and i was able to select and move emails out of the trash folder and into a "normal" folder(the trash folder appears to not allow as many operations/options?)
i was also able to create duplicate emails and then use the "remove duplicate messages" function to get rid of them.
keep us posted on your progress!
at the moment i am not near my notes but i might get that way fairly soon.
in the meantime be careful what you do as i seem to remember some email clients choking/failing/corrupting-data/etc when attempting processes on a very large number of emails.
how many are in your trash directory/folder?
if you don't already have a _proven_working_backup_ for your whole email archive(s) you should do and confirm that as a first step.
keep us posted!
after reading this thread it is appropriate to introduce/mention/promote/reference/support/etc the ever-awesome(imhho) Cory Doctorow!
https://en.wikipedia.org/wiki/Cory_Doctorow
see also his very successful kickstarters:
https://www.kickstarter.com/profile/doctorow/created
fyi, no affiliation other than to buy, read, and support all his many varied global efforts.
mostly for the convenience of future thread visitors:
more carry_on/pile_on...same song was sung 18 months ago:
reading this post reminded me of: