README.md


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

<h1 align="center"> *NIX suicide kit </h1>
<p align="center">
  <a href="https://github.com/Nam4ik/syskill/actions/workflows/rust.yml">
    <img alt="ci" src="https://img.shields.io/github/actions/workflow/status/Nam4ik/syskill/rust.yml?branch=main&label=ci">
  </a>
  <a href="LICENSE">
    <img alt="License" src="https://img.shields.io/github/license/Nam4ik/syskill">
  </a>
  <img alt="C" src="https://img.shields.io/badge/C-00599C?logo=c&logoColor=white">
  <img alt="Rust" src="https://img.shields.io/badge/Rust-000000?logo=rust&logoColor=white">
  <a href="https://github.com/Nam4ik/syskill/issues">
    <img alt="Issues" src="https://img.shields.io/github/issues/Nam4ik/syskill">
  </a>
  <a href="https://github.com/Nam4ik/syskill/stargazers">
    <img alt="Stars" src="https://img.shields.io/github/stars/Nam4ik/syskill">
  </a>
  <br> 
</p>

___________________________

<div align="center">
  <img src="./README/sample.gif" width="460" height="450">

____________________________
**A utility that will help you beautifully deal with your UNIX system.**
> [!WARNING]
> To get working `kmod-panic` you need to build project itself. 

</div>


> [!WARNING] 
> DONT USE THIS ON PRODUCTION OR REAL PC, SOME FUNCTIONS MAY CAUSE YOUR SYSTEM TO BECOME COMPLETELY UNSTABLE.
> But when calling a function located in `src/non-critical/`, all the consequences will go away after a reboot.

This package provides a CLI utility with a set of functions for mocking your operating system, both critical and non-critical. From the already familiar fork bombs `:(){ :|:& };:` or something more critical like `sudo rm -rf /* --no-preserve-root` before rendering graphic artifacts by interfering with the frame buffer.

I also neglected optimization in this project. Seriously, what kind of optimization and code cleanliness are you talking about in a project that's literally designed to consolidate all possible ways to abuse or kill your system into one?

Most of the functions have been rewritten to suit the features of different UNIX-like systems (FreeBSD, OpenBSD, linux, etc...).
In the future, an addition to the project is planned in the form of similar abilities but for `win32`
About compatability with mos *NIX system you can read [here](https://github.com/Nam4ik/syskill/blob/main/NIXES_COMPATABILITY.md)

P.S. I don't use AI in my main work, only for spot-checking and debugging.