BashCore 2504 (April 2025) is now featured on Oswatch!
We’re proud to announce that the latest release is officially listed!
Built on Debian 12.10 (Bookworm) with kernel 6.1.0-32-amd64, this update brings vim, SMB support, and more.
Thanks for the support, Oswatch!
Download now at https://bashcore.org
Just tried to explain what BashCore is — a minimal, terminal-only OS built for learning and pentesting — and got the same reaction you'd expect if I said a marmot wraps the chocolate.
Not for everyone, but perfect for those who speak fluent shell.
[Post-mortem: BashCore Stress Test Investigation]
Test ended on Day 5.
The system didn’t crash, but I noticed the fan was working overtime. The main suspect?
kworker/0:3+kacpid turns out it was busy with ACPI tasks (power management).
So technically… BashCore held up, but ACPI didn’t like the heat. Literally.
This is a known issue on older hardware with imperfect ACPI/BIOS support.
Takeaway:
BashCore is stable, it’s the laptop that needs therapy 
[Stress Test Interrupted - Day 5]
After almost 5 days of flawless uptime on a 2009 Acer Aspire One, I came back home to find the netbook as warm as a toaster.
The fan was spinning like it was ready for takeoff... main suspect: #kworker.
No crash, but just to be safe, I shut it down. I’ll be away for 3 days.
So, the test ends here…
Scientific conclusion:
BashCore survives, but kworker has more stamina than I do 
[Day 4 – BashCore Stress Test Update]
Running live from an old Acer Aspire One D160 (2009, 2 GB RAM, USB 2.0 boot, no battery).
Uptime: 4d 5h
RAM: 944 MB / 1.91 GB
Load avg: 0.22 0.14 0.25
stress-ng still working at ~23% CPU
msfconsole and NordVPN also running.
No crashes, no slowdowns. Holding strong 
Still 3 days to go!
PSA: VirtualBox 7.0 decided to break NAT Network on me.
Only regular NAT worked… which is useless if your VMs need to talk to each other 
Tried rebooting, reinstalling extensions, sacrificing a goat… nothing worked.
Then I installed VirtualBox 7.1.6 — boom, NAT Network works again!
If you're pulling your hair out like I did, just upgrade. You're welcome
[Day 1 complete – BashCore Uptime Test]
One full day running non-stop from a USB 2.0 stick on an Acer Aspire One D160 (2009, 2 GB RAM, no battery).
RAM: 800 MB / 1.91 GB
Load avg: 0.60 0.70 0.43
Stress-ng still running at ~18% CPU
Zero crashes, zero hangs. Still responsive.
Uptime test continues... 6 days to go!
[Update – 8 hours later]
BashCore still holding strong.
RAM steady at 700 MB
Load average: 0.25 0.18 0.20
No GUI, no disk writes, 6 active terminals
Running from a USB 2.0 stick (8 GB!)
Host: Acer Aspire One D160 (2009, 2 cores, 2 GB RAM, no battery, Wi-Fi only) 
Uptime test continues. 6.5 days to go.
Testing BashCore's stability.
This week, I'm running a continuous 7-day uptime test on BashCore: #noGUI, minimal setup, real usage.
6 terminals, 6 tasks:
- htop
- tshark (live capture)
- ping (via proxychains + Tor)
- msfconsole
- stress loop: while true; do echo ""; sleep 5; done
- stress-ng --cpu 1 --cpu-load 15 --timeout 7d
Running on an old Acer Aspire One (D160) with 2 GB RAM with NordVPN installed.
No disk writes. No frills. Just to see if it holds.
BashCore 2504 is here.
Minimal boot, automatic login, Debian 12.10, kernel 6.1.129-1 (Debian package: 6.1.0-32). No distractions, no GUI. Just raw power and full control — the BashCore way.
user@bashcore:~$
Get it now at https://bashcore.org
BashCore2504 has been published!
Fully updated, polished, and (finally) perfect 
Grab it here: https://sourceforge.net/projects/bashcore/files/
Thinking of suggesting Proton’s free VPN for BashCore users, used via OpenVPN (already included) 
Should work with:
sudo openvpn --config /path/to/file.ovpn
Anyone here using it this way? What do you think?
Working on the latest update of BashCore, codename 2504 (April '25)!
Bugs squashed, tools updated, base upgraded to Debian 12.10, and now includes Vim by default 
Fingers crossed it all works out in the end lmao 
For months, start-stop-daemon and dpkg-divert were throwing warnings during the build, suggesting --no-rename. After countless tests, the fix was simpler than expected: an appropriate hook in LiveBuild did the trick!
Lesson learned: sometimes the solution is right in front of us! 
From day one, TShark has been an essential part of #BashCore. It’s not just a substitute for Wireshark—it’s the same powerful engine, but fully command-line. If you’re serious about network analysis and pentesting, mastering TShark is a must.
It has nothing less than Wireshark, just no GUI. Learn it, and you’ll have full control over packet capture and analysis, even on minimal systems.
Sometimes we don't have the best tools... like the Intel® Atom N450 and Intel® Celeron® N4500. 
Linux Command Library – the perfect CLI reference! 
Try it:
Excited for a workshop on Cyber Security & AI this Friday! Looking forward to learning more and maybe even showcasing BashCore to the speakers and audience. Fingers crossed!
https://www.enacveneto.it/magazine/workshop-cyber-ai-e-big-data-a-feltre
#Kali is for the kids, BashCore is for the real ones!
Forget all the flashy GUIs and unnecessary bloat. Real men (and women) know that raw power comes from the command line. 
Time to level up!
/opt/metasploit-framework/msfconsole
