• Re: It's official, slashdot enters phase of "slow days"

    From Mike Small@smallm@panix.com to alt.os.linux.slackware on Thu Mar 5 09:22:18 2026
    From Newsgroup: alt.os.linux.slackware

    Popping Mad <rainbow@colition.gov> writes:

    On 2/23/26 10:54 AM, jayjwa wrote:
    Slashdot used to be the place back in the day. Now it's just sad and
    needs to close. What little tech they write about is old and the rest is
    just propaganda. I stopped visiting long ago. Even The Reg got bad. Many
    such cases.


    because facebook is much better... or instagram... NOT

    It is actually funny to read this on usenet.

    Soylentnews is still going, it looks like. To me it's a significant
    improvement over what Slashdot has become. And its gmane/gwene bridge
    is up to date.



    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From mummycullen@mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) to alt.os.linux.slackware on Thu Mar 5 11:27:46 2026
    From Newsgroup: alt.os.linux.slackware

    jayjwa wrote:
    mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) writes:


    Did you receive a reply? This is a response to the post seen at:
    http://www.jlaforums.com/viewtopic.php?p=701801931#701801931


    Page doesn't load. It says I'm "rate limited" despite never having
    visited before.

    --
    PGP Key ID: 781C A3E2 C6ED 70A6 B356 7AF5 B510 542E D460 5CAE
    "The Internet should always be the Wild West!"





    Not sure, I tried from multiple places and no issue with the exception of one VPN I used which required solving captcha


    This is a response to the post seen at: http://www.jlaforums.com/viewtopic.php?p=701801931#701801931
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Joseph Rosevear@Mail@JoesLife.org to alt.os.linux.slackware on Wed Apr 22 20:13:28 2026
    From Newsgroup: alt.os.linux.slackware

    On Thu, 26 Feb 2026 20:03:40 -0500, MummyChunk wrote:

    Joseph Rosevear wrote:
    On Thu, 26 Feb 2026 14:00:48 -0500, MummyChunk wrote:


    Did you receive a reply?

    This is a response to the post seen at:
    http://www.jlaforums.com/viewtopic.php?p=701801931#701801931



    My post did appear on jlaforums.com, but yours was the only reply.
    Appreciate you bridging the threads! I'm thinking twice about the name
    "ZombieSlack". Have you tried anything similar with persistent
    Slackware installs, or got any thoughts on the Zombie approach? Happy
    to chat more if interested.




    Thanks for the update. Grok's warning makes sense: having "Slackware" in
    the project name can look like endorsement, even if that isn't your
    intent. Renaming the toolkit to something like SAM.Zombie and describing
    it as "for Slackware 15.0" or "works with Slackware" feels safer.

    The idea itself is interesting, especially the part about converting a running LiveSlak into a persistent setup without a full reinstall.
    What's your persistence approach under the hood, and how easy is it to
    roll back if someone changes their mind?

    Thanks for the interest, and sorry for the delay in answering!

    I'm working on a release of "Zombie Silas" as part of the SAM.Zombie
    library. Perhaps even I will produce actual, bootable Zombie Silas flashdrives for distribution as well.

    Under the hood, the tweaks to a running LiveSlak are very much like the
    tweaks to an rsynced copy of a Slackware reference installation (a
    "Basis"). Both are performed by the same script, aptly called "bite".
    The two processes are a little different, yet very much the same. This similarity is accomplished by using chroot for the Slackware tweaks and
    root to perform the LiveSlak tweaks.

    The LiveSlak tweaks are temporary and must be performed as root at each
    boot of LiveSlak. This is a serious nuisance, but a great benefit at the
    same time. After all, it provides real persistence and custom
    modifications to the environment and system, including KDE.


    This is a response to the post seen at: http://www.jlaforums.com/viewtopic.php?p=701801931#701801931

    --- Synchronet 3.21f-Linux NewsLink 1.2