```text
==================================================
antiX 19.5  Debian Archive and Text Archaeology
==================================================

Purpose
-------

antiX 19.5 is based on Debian 10 (Buster).

Both antiX 19.5 and Debian Buster are now end-of-life, so their
original package repositories are no longer part of the normal
Debian mirror network.

The system can still be useful as a lightweight terminal machine,
provided that its package sources are handled carefully.

The intended use of this installation is:

- terminal-based Internet access
- BBS and Telnet systems
- Gopher and Gemini
- text-oriented web browsing
- Internet and software archaeology
- local archival work
- SSH access
- lightweight Unix tools

The important principle is:

    Use the archive to obtain individual packages when needed.
    Do not treat an archived system as a normal upgrade target.


--------------------------------------------------
1. Inspect the Existing APT Configuration
--------------------------------------------------

Check the main APT directory:

    ls -l /etc/apt/

Check whether a traditional sources.list exists:

    cat /etc/apt/sources.list

Inspect additional repository definitions:

    ls -l /etc/apt/sources.list.d/

Display all configured sources:

    for f in /etc/apt/sources.list.d/*; do
        echo "===== $f ====="
        cat "$f"
    done

On older antiX installations, repositories may be distributed
across several files instead of a single /etc/apt/sources.list.


--------------------------------------------------
2. Back Up the Existing Repository Configuration
--------------------------------------------------

Before changing anything:

    sudo mkdir -p /root/apt-backup
    sudo cp -a /etc/apt/sources.list.d /root/apt-backup/

This provides a local recovery copy of the original repository
configuration.

To restore it later:

    sudo rm -rf /etc/apt/sources.list.d
    sudo cp -a /root/apt-backup/sources.list.d /etc/apt/


--------------------------------------------------
3. Disable Obsolete Repositories
--------------------------------------------------

Old antiX and Debian Buster mirror entries may no longer work.

Disable obsolete entries rather than deleting them immediately.

For example:

    sudo nano /etc/apt/sources.list.d/antix.list
    sudo nano /etc/apt/sources.list.d/debian.list
    sudo nano /etc/apt/sources.list.d/debian-stable-updates.list

Comment out active repository lines by placing '#' at the beginning.

Keep the original files intact whenever possible.

This makes the configuration easier to reconstruct later.


--------------------------------------------------
4. Add the Debian Buster Archive
--------------------------------------------------

Create a dedicated archive source:

    sudo nano /etc/apt/sources.list.d/debian-archive.list

Add:

    deb http://archive.debian.org/debian buster main contrib non-free

The archive contains the package indexes for the retired Debian
Buster release.

Do not enable Testing, Sid, or another current Debian release on
this installation simply to obtain newer software.

Mixing releases is considerably more dangerous than using an old
but internally consistent package set.


--------------------------------------------------
5. Disable Release-Date Expiration
--------------------------------------------------

Archived Debian repositories contain Release metadata from the
past.

APT may reject this metadata because the repository is no longer
considered current.

Create:

    sudo nano /etc/apt/apt.conf.d/99no-check-valid-until

Add:

    Acquire::Check-Valid-Until "false";

This setting is appropriate when deliberately using a historical
repository archive.

It should not be copied blindly to a normal, current Debian system.


--------------------------------------------------
6. Refresh the Package Lists
--------------------------------------------------

Clean the local package cache:

    sudo apt clean

Update the package indexes:

    sudo apt update

A successful update should retrieve the Buster package indexes
from archive.debian.org.

Verify that packages are visible:

    apt search mc

or:

    apt show mc


--------------------------------------------------
7. Important: Do Not Perform a Blind System Upgrade
--------------------------------------------------

An archived Buster installation is not a normal supported system.

Avoid:

    sudo apt upgrade

and especially:

    sudo apt full-upgrade

unless the complete dependency situation has been inspected and
a deliberate upgrade is actually required.

The preferred operating model is:

    install what is needed
    keep the existing system stable
    avoid unnecessary dependency changes


--------------------------------------------------
8. Install Packages Individually
--------------------------------------------------

For this installation, packages are installed according to need.

Useful basic tools include:

    mc
    htop
    tmux
    nano
    vim
    less
    tree

Install individually or in small groups:

    sudo apt install mc
    sudo apt install htop
    sudo apt install tmux

This makes it easier to identify dependency problems and observe
the effect of each installation.


==================================================
TEXT-ORIENTED INTERNET TOOLKIT
==================================================

The machine is intended to operate primarily through the terminal.

The following tools form the basic working environment.


--------------------------------------------------
9. Text Web Browsers
--------------------------------------------------

Installed clients:

    lynx
    elinks
    links
    w3m

Examples:

    lynx http://example.com
    elinks https://example.com
    links http://example.com
    w3m http://example.com

These clients are useful for sites whose content remains accessible
without a modern graphical browser.

HTTPS support depends on the version and TLS libraries available in
the installed client.

Protocol matters:

    http://
    https://
    gopher://
    gemini://

are different protocols and should not be treated interchangeably.


--------------------------------------------------
10. Gopher
--------------------------------------------------

Gopher is one of the most useful protocols for Internet archaeology.

Use a Gopher-capable client where available.

Example:

    w3m gopher://gopher.floodgap.com

Gopher servers often provide:

- text archives
- menus
- documentation
- software indexes
- historical material
- links to other text resources


--------------------------------------------------
11. Gemini
--------------------------------------------------

Gemini provides a deliberately lightweight text-oriented protocol.

A Gemini-capable client can be used with:

    gemini://

The protocol is particularly useful when exploring modern
text-oriented communities and minimalist Internet services.


--------------------------------------------------
12. BBS and Telnet
--------------------------------------------------

Traditional BBS systems may still be accessible through Telnet.

Example:

    telnet host.example 23

Telnet is intentionally unencrypted.

Use it for public BBS services and other systems that explicitly
provide Telnet access.

For administrative access to Unix systems, prefer SSH.


--------------------------------------------------
13. SSH
--------------------------------------------------

OpenSSH provides encrypted remote access.

Client:

    ssh user@host

Server installation, when required:

    sudo apt install openssh-server

For an archived system, avoid replacing working SSH components
without first checking the available package versions and
dependencies.


--------------------------------------------------
14. Download and Synchronization Tools
--------------------------------------------------

Useful tools for collecting archival material:

    wget
    curl
    rsync

Examples:

    wget http://example.org/file.txt

    curl -O http://example.org/file.txt

    rsync -av source/ archive/

These tools allow the machine to function as a small local
collection point for historical text and software.


--------------------------------------------------
15. Archives and Compression
--------------------------------------------------

Useful archive utilities:

    gzip
    bzip2
    xz-utils
    unzip

Historical software archives frequently contain compressed text,
documentation, source code, disk images, and other material.

The ability to unpack several generations of archive formats is
therefore more useful here than installing large modern desktop
applications.


--------------------------------------------------
16. News and Mail
--------------------------------------------------

Text-oriented clients may include:

    alpine
    mutt
    tin
    slrn

These provide terminal interfaces for mail and NNTP/Usenet-style
services where the relevant servers are still available.

Availability of the underlying service should always be checked
separately from client installation.


--------------------------------------------------
17. IRC
--------------------------------------------------

Traditional IRC remains accessible entirely from the terminal.

Useful clients include:

    irssi
    weechat

These are particularly appropriate for a lightweight, persistent
terminal environment and work well inside tmux.


--------------------------------------------------
18. Network Utilities
--------------------------------------------------

Useful diagnostic tools include:

    net-tools
    traceroute
    nmap
    whois
    dnsutils

Examples:

    ifconfig

    traceroute example.com

    dig example.com

    whois example.com

These tools are useful for understanding the network environment
and locating surviving services.

Use network scanning only against systems you own or are explicitly
authorized to test.


==================================================
WORKING MODEL
==================================================

This machine should be treated as a lightweight archival workstation,
not as a modern general-purpose desktop.

The preferred workflow is:

    SSH
      |
      +-- tmux
            |
            +-- browser
            +-- BBS / Telnet
            +-- Gopher
            +-- Gemini
            +-- IRC
            +-- archive tools
            +-- local notes


--------------------------------------------------
19. Resource Strategy
--------------------------------------------------

The machine has limited RAM and old hardware.

Prefer:

- terminal applications
- small packages
- one task at a time
- tmux sessions
- local text archives
- incremental downloads
- simple Unix utilities

Avoid:

- large desktop applications
- unnecessary graphical stacks
- mixing Debian releases
- indiscriminate upgrades
- replacing working core components without reason


--------------------------------------------------
20. Protocol Map
--------------------------------------------------

    HTTP
        lynx / links / elinks / w3m

    HTTPS
        lynx / links / elinks / w3m
        depending on TLS support

    Gopher
        Gopher-capable clients

    Gemini
        Gemini client

    Telnet
        telnet / BBS clients

    SSH
        OpenSSH client

    IRC
        irssi / weechat

    NNTP
        tin / slrn

    Mail
        mutt / alpine


==================================================
RECOVERY NOTES
==================================================

If the APT configuration needs to be restored:

    sudo rm -rf /etc/apt/sources.list.d
    sudo cp -a /root/apt-backup/sources.list.d /etc/apt/

Then refresh the package lists:

    sudo apt update

If the archive configuration is still required, recreate:

    /etc/apt/sources.list.d/debian-archive.list

with:

    deb http://archive.debian.org/debian buster main contrib non-free

and keep:

    /etc/apt/apt.conf.d/99no-check-valid-until

with:

    Acquire::Check-Valid-Until "false";


==================================================
FINAL PRINCIPLE
==================================================

This installation is not intended to become a newer Debian system.

Its value is precisely the opposite:

    old hardware
        +
    lightweight Unix
        +
    historical package archive
        +
    terminal software
        +
    surviving Internet protocols
        =
    a practical Internet archaeology workstation


The archive is a source of tools, not an invitation to upgrade
the entire machine.

Keep the base system stable.

Add only what is useful.

Preserve working configurations.

And when a useful piece of old Internet turns up:

    download it
    inspect it
    archive it
    document it

==================================================
```