Guzio/system
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Compare commits

base: Guzio:fa2ee94200c4ea19f558bc21ba887de1e4546166
Branches Tags
Guzio:main
..
compare: Guzio:ebf0b2ff8f6e9abd822eb199dfd67c828c0d5385
Branches Tags
Guzio:main

No commits in common. "fa2ee94200c4ea19f558bc21ba887de1e4546166" and "ebf0b2ff8f6e9abd822eb199dfd67c828c0d5385" have entirely different histories.
fa2ee94200 ... ebf0b2ff8f

3 changed files with 3 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/atama-branding/hook.sh
View file

@ -1,3 +1,3 @@
#!/bin/bash #!/bin/bash
mkdir -p /etc/ mkdir -p /etc/
echo -e "NAME=\"AtamaOS\"\nPRETTY_NAME=\"Arch Linux ― AtamaOS\"\nID=atama\nID_LIKE=\"alg arch blendos android\"\nBUILD_ID=rolling\nANSI_COLOR=\"38;2;23;147;209\"\nHOME_URL=\"\"\nDOCUMENTATION_URL=\"\"\nSUPPORT_URL=\"\"\nBUG_REPORT_URL=\"\"\nPRIVACY_POLICY_URL=\"\"\nLOGO=arch\nIMAGE_ID=alg-xfce\nIMAGE_VERSION=2025.10" > /etc/os-release echo -e "NAME=\"Atama\"\nPRETTY_NAME=\"AtamaOS\"\nID=atama\nID_LIKE=\"alg arch blendos\"\nBUILD_ID=rolling\nANSI_COLOR=\"38;2;23;147;209\"\nHOME_URL=\"\"\nDOCUMENTATION_URL=\"\"\nSUPPORT_URL=\"\"\nBUG_REPORT_URL=\"\"\nPRIVACY_POLICY_URL=\"\"\nLOGO=arch\nIMAGE_ID=alg-xfce\nIMAGE_VERSION=2025.10" > /etc/os-release

2
modules/atama-branding/module.yaml
View file

@ -5,7 +5,7 @@ post_install_hook: "hook.sh"
post_disable_hook: "unhook.sh" #No matter what I tried, I couldn't get this hook to actually trigger, so it seems to be an in-development stub that doesn't work yet (especially given how there was literally 0 documentation on this - I simply spotted it being listed in auto-generated modules). For now, the unhook script has to be run manually if you want to undo the power button setup. Nevertheless, it's listed here, so it should Just Work [TM] when DCli adds support. post_disable_hook: "unhook.sh" #No matter what I tried, I couldn't get this hook to actually trigger, so it seems to be an in-development stub that doesn't work yet (especially given how there was literally 0 documentation on this - I simply spotted it being listed in auto-generated modules). For now, the unhook script has to be run manually if you want to undo the power button setup. Nevertheless, it's listed here, so it should Just Work [TM] when DCli adds support.
hook_behavior: always #...instead of "once" because this lets your config be self-healing (even if you mess something up, next dcli sync will restore it); ...instead of "ask" because I don't like pestering people with RUN THIS HOOK? RUN THIS HOOK? (if anything, that makes it more likely that they will "[S]kip always", thus rendering the „self-healing” non-functional) hook_behavior: always #...instead of "once" because this lets your config be self-healing (even if you mess something up, next dcli sync will restore it); ...instead of "ask" because I don't like pestering people with RUN THIS HOOK? RUN THIS HOOK? (if anything, that makes it more likely that they will "[S]kip always", thus rendering the „self-healing” non-functional)
author: "Guzio" author: "Guzio"
version: "1.0.1" version: "1.0.0"
category: "system" category: "system"
tags: [] tags: []
license: "MIT" license: "MIT"

6
modules/system-packages-GuzioPadV4/sudo.md
View file

@ -14,9 +14,5 @@ Appended at the end:
guzio ALL = (root) NOPASSWD: /home/guzio/.config/hypr/scripts/rootedinit.sh guzio ALL = (root) NOPASSWD: /home/guzio/.config/hypr/scripts/rootedinit.sh
guzio ALL = (root) NOPASSWD: /home/guzio/.config/hypr/scripts/volume-root.sh guzio ALL = (root) NOPASSWD: /home/guzio/.config/hypr/scripts/volume-root.sh
guzio ALL = (root) NOPASSWD: /usr/bin/htop guzio ALL = (root) NOPASSWD: /usr/bin/htop
guzio ALL = (root) NOPASSWD: /home/guzio/.config/hypr/scripts/waydroid-root.sh
``` ```
Those changes WILL NEVER be added to a `dcli` hook-script because editing `/etc/sudoers` requires UTMOST CAUTION (there is a reason it's supposed to be done with `SUDO_EDITOR=/bin/nano visudo`) and Bash scripts doing text edits simply aren't reliable enough for tasks this sensitive. I'll only trust custom C/C++/Rust/Go/other-systems-language code that interacts with `sudo`'s APIs directly. Those changes WILL NEVER be added to a `dcli` hook-script because editing `/etc/sudoers` requires UTMOST CAUTION (there is a reason it's supposed to be done with `SUDO_EDITOR=/bin/nano visudo`) and Bash scripts doing text edits simply aren't reliable enough for tasks this sensitive. I'll only trust custom C/C++/Rust/Go/other-systems-language code that interacts with `sudo`'s APIs directly.
### Also, speaking of appending...
`* soft nofile 524288` at the end of `/etc/security/limits.conf` to let Waydroid be restarted more than once or twice (unrelated to sudo, but I didn't wanna make a new MD doc for a single sentence)