🐺 LupineOS (WolfPack v0.1)

██╗     ██╗   ██╗██████╗ ██╗███╗   ██╗███████╗ ██████╗ ███████╗
██║     ██║   ██║██╔══██╗██║████╗  ██║██╔════╝██╔═══██╗██╔════╝
██║     ██║   ██║██████╔╝██║██╔██╗ ██║█████╗  ██║   ██║███████╗
██║     ██║   ██║██╔═══╝ ██║██║╚██╗██║██╔══╝  ██║   ██║╚════██║
███████╗╚██████╔╝██║     ██║██║ ╚████║███████╗╚██████╔╝███████║
╚══════╝ ╚═════╝ ╚═╝     ╚═╝╚═╝  ╚═══╝╚══════╝ ╚═════╝ ╚══════╝

Version: 0.1.0 (Alpha) Codename: WolfPack Host OS: Fedora Atomic (COSMIC Desktop) Hardware Target: Dell XPS 9570 (i7-8750H / 32GB RAM / GTX 1050 Ti)

---

🚀 Installation

Option A: Download Official Release

1. Go to GitHub Releases.
2. Download ISO: Grab the latest lupineos-41.iso from GitHub Releases.
3. Install:
   • Boot the USB.
   • Install Fedora to disk.
   • Reboot into your new system.
4. Initialize Environment (Important): Open a terminal and run the bootstrap script to set up your dotfiles and containers:

   git clone https://github.com/TheExiled/LupineOS.git ~/LupineOS
   cd ~/LupineOS && ./install.sh

Option B: Build from Source (Native)

We use a Native Containerized Build process to ensure reproducibility while using native Fedora tools (lorax, mkksiso).

Prerequisites:

• Linux Host (Fedora Recommended)
• podman installed
• sudo privileges (required for loop device creation)

Build Command:

./generate-iso-native.sh

What this does:

1. Spins up a privileged Fedora 41 container.
2. Manually creates loop devices (essential for lorax).
3. Installs lorax, ostree, and mkksiso.
4. Phase 1: Builds a raw boot.iso using lorax.
5. Phase 2: Injects our custom Kickstart capability using mkksiso.
6. Outputs lupineos-41.iso and generates a SHA256 checksum.

Output:

• lupineos-41.iso: The bootable installer.
• docs/checksum.txt: Hash for verification.

---

🛠 Manual Bootstrap (Legacy)

For existing Fedora Atomic users who just want the dotfiles.

1. Clone Repo: git clone https://github.com/TheExiled/LupineOS.git ~/LupineOS
2. Run Script: cd ~/LupineOS && ./install.sh

1. Core Philosophy

"Many parts, one instinct." LupineOS follows a strict Atomic/Container architecture to separate concerns while functioning as a unified whole.

1. Immutable Host: The base OS is read-only.
2. The Pack (Containers): Distinct, specialized environments (dev, admin, sec) that hunt together.
3. Unified Senses: All environments share the same shell (zsh), prompt (starship), and editor (helix) config via the shared /home directory.

---

2. The Host Environment

These tools are installed on the host to ensure fast access to the filesystem and hardware.

2.1. Native Binaries

Installed manually to ~/.local/bin to bypass rpm-ostree layering.

• eza: Modern ls replacement (Rust).
• ripgrep (rg): Recursive search respecting .gitignore (Rust).
• bat: cat with syntax highlighting (Rust).
• zoxide: Smart directory jumping (Rust).

2.2. Gaming & GUI Stack (Flatpaks)

Gaming runs isolated from the dev environment using Flatpaks.

• Launchers: Steam, Heroic (Epic/GOG), Lutris.
• Utils: ProtonUp-Qt, MangoHud, GOverlay.
• Communication: Vesktop (Discord with Wayland screen share).
• Management: Flatseal (Permissions), Warehouse (Cleanup).

---

3. The Pack (Container Ecosystem)

We maintain three distinct environments managed via Distrobox.

📦 Container A: dev (The Alpha)

• Base: Fedora
• Purpose: Rust Development, Python Scripting, AI Interaction.
• Key Tools:
  • Languages: Rust (via rustup), Python 3.
  • Editors: Helix (hx), Neovim.
  • Git: lazygit (TUI), gh (GitHub CLI).

📦 Container B: admin (The Beta)

• Base: Ubuntu
• Purpose: DevOps, Cloud Infrastructure, Server Management.
• Key Tools:
  • IaC: Ansible, Terraform.
  • Cloud: AWS CLI.
  • Network: dig, whois, traceroute.

📦 Container C: sec (The Omega)

• Base: Kali Linux Rolling
• Purpose: Cybersecurity, Penetration Testing.
• Key Tools:
  • Recon: Nmap, Masscan.
  • Web: Burp Suite, SQLMap.
  • Attack: Metasploit, Hydra.

📦 Container D: `data` (The Lab)

• Base: Fedora
• Purpose: Data Science, Database Administration, Local LLM Testing.
• Key Tools: JupyterLab, Pandas, NumPy, PostgreSQL Client, SQLite.

📦 Container E: `arch` (The Sandbox)

• Base: Arch Linux
• Purpose: Access to the AUR (Arch User Repository) and bleeding-edge packages.
• Key Tools: yay (AUR Helper), pacman.
• Note: Built via setup_sandbox.sh to auto-compile yay.---

4. Automation & Structure

• configs/: Shared dotfiles (Zellij, Helix, Starship).
• assets/: Branding and Wallpapers.
• generate-iso-native.sh: The official ISO build script (Native Fedora 41 Container).
  • install.sh: Dotfile bootstrap script.