Blog

Watt'n ditte?

Keine Ahnung, es fing als Blog bzw. Newsfeed an und wurde vom groben Unfug übernommen. Zwischendrin selten mal Ernsthaftes, aber ich wüsste nicht wie das irgendjemand auseinander halten soll.
Was hier so steht regt dich furchtbar auf? Dann rasch weiter zum Beschwerde-Formular, deine Meinung interessiert mich ganz doll!
Sofern nicht anders angegeben, stehen alle Bilder unter: CC BY 4.0 und wurden vollständig mit Inkscape erstellt.

Archiv: 2021 2020 2019 2018 2017 2016 2015 | Gallery |

11.06.2021 - Grub 2.06 does NOT add LUKS2-support

If you read IT-newssites these days you may have had read these:

GRUB 2.06 [...] LUKS2 encrypted volume support (Phoronix)

Grub 2.06 [...] versteht sich mit LUKS2 verschlüsselten Partitionen (linux-magazin)

Grub 2.06: Die Software unterstützt nun Boot-Partitionen, die mit LUKS2 verschlüsselt sind (heise)

Just another examples of journalists not caring about their work and spreading bullshit.
In detail Grub 2.06 adds support for reading LUKS2-headers, but not Argon2 key derivation support. So if you convert your LUKS-header, password-hashes are still in PBKDF2 as long as you don't update them. If you do, tools will by default use Argon2 and on next boot it will fail.
Or as the guy in the phoronix comments wrote: "LUKS2 without Argon2 is a nonsense."
You can't call that LUKS2-support.
(No offense to the Grub-devs, if have read the mailing list and comprehend this decision.)

  • [1] https://www.phoronix.com/scan.php?page=news_item&px=GRUB-2.06-Released
  • [2] https://www.heise.de/news/Bootloader-Grub-2-06-verbessert-Sicherheit-6068231.html
  • [3] https://www.linux-magazin.de/news/grub-2-06-unterstuetzt-luks2-verschluesselung/

01.06.2021 - Processmanaging and youuu (Linproman's taskfile-format)

Well hellu there little Jimmy, today you're learning about the Linproman tasksystem and how to survive a nuclear holocaust by a time traveling dictator.

The task's GUI: An unshiny reminder of being stuck in traffic :c

Creating a taskfile to tell Linproman what to do when a condition gets true, is as easy as customize config- or good ol' inifiles:
Just create a textfile, place it with ending .task into the folder you defined in Options»General and after application-startup or Taskform's contextmenuentry "reload tasks" it will be loaded and checked.

You have a program which should be run batches, but crashes from time to time? Well, you could report a bug and of course it will be fixed, like all the other issues not rotting in bugtrackers at all. Or you create a task which starts the batch-program again after it crashed.

Another program freaks out for some reason and starts eating up all your RAM? Create another task for shoting down that little bugger.

You're running 2 or more programs, but you want to shutdown your PC when they're all done? Create... you got the idea!

The full documentation about the Linproman's taskfile-format you'll find here. Feel free to bookmark it, it'll will be up-to-date for future releases (unlike this article).


The currently possible conditions

You can put processconditions into a taskfile, which will be checked against the process (for example how much CPU-percent the process uses) and (also) systemconditions which will be check against the whole system (for example how much of the CPUs are in use or how much RAM is available).
ActionExplanation
truealways true
falsealways false
alivetrue if process exists
jstrue if process just started (Xticks will be ignored because it makes no sense here)
deadtrue if the process was brutally murdered
cpu>true if cpu-use is above X percent
cpu<true if cpu-use is below X percent
hddr>true if devicereaddelta is above X bytes per tick
hddr<true if devicereaddelta is below X bytes per tick
hddw>true if devicewrittendelta is above X bytes per tick
hddw<true if devicewrittendelta is below X bytes per tick
netr>true if networkreceiceddelta is above X bytes per tick
netr<true if networkreceiveddelta is below X bytes per tick
nets>true if networkwrittendelta is above X bytes per tick
nets<true if networkwrittendelta is below X bytes per tick
ram>true if ramuse above X bytes
ram%>true if ramuse above X percent
swap>true if swapuse above X bytes
swap%>true if swapuse above X percent
Systemconditions only:
cputtrue if CPU is below throttle-speed (Options»General)
batctrue if one of the bats is charging (or BATID)
batdtrue if one of the bats is discharging (or BATID)
batftrue if one all the bats are full (or BATID)
bat%>true if average level of all the bats are above X percent (or BATID)
bat%<true if average level of all the bats are below X percent (or BATID)
batmodetrue if Commissioner Gordon needs help your device is running on battery (not yet implemented)

Examples

Move mediainfo-gui and g-earth (which spawning always on monitor 1 to monitor 2):
[main] name=Move wrong spawning windows description=because they're programmed by Pakled scriptpathname=/home/lilstinky/scripts/linproman/move_pid_2_mainmonitor.sh enabled=1 conditionconnection=1 [processcondition0] ByName=mediainfo-gui condition=js [processcondition1] ByName=googleearth-bin condition=js script_parameters=googleearth
Kill Thunar if it is using to much cpu: [main] name=Stuck thunar description=Thunar using all cpu: https://gitlab.xfce.org/xfce/thunar/-/issues/510 scriptpathname=/home/lilstinky/scripts/linproman/warn_n_kill.sh enabled=1 [processcondition0] ByName=thunar condition=cpu> XTicks=120 resettrueticksafterwards=1 value=10 script_parameters=thunar
Shut down or stand-by a system when CPU and network-traffic is below a value: [main] name=Stand-by lazy system description=Sleep now! scriptpathname=/home/lilstinky/scripts/linproman/standby.sh enabled=1 disableafterfiring=1 [systemcondition0] XTicks=300 condition=cpu< value=10 [systemcondition1] XTicks=300 condition=netr< value=10k [systemcondition2] XTicks=300 condition=nets< value=10k
End the "helper-apps" Evolution leaves in RAM on exit (*-source-registry, *-calendar-factory and *-addressbook-factory): [main] name=Cleanup after Evolution description=End the nasty helper-apps Evolution leaves in RAM after it has ended scriptpathname=/home/lilstinky/scripts/linproman/cleanup_evolutionstuff.sh enabled=1 fired=0 [processcondition0] ByName=evolution ByNameStrict=1 HandleAll=1 resettrueticksafterwards=1 condition=dead XTicks=10

And this is how you survive nukes by duck and cover, little Billy. Now go home, find your parent's lighter and a gas can and burn stuff!

25.04.2021 - Buuugs! 1.4 released

Version 1.4 von Buuugs! ist erschienen, als Quelltext und als x64-Binaries.

Version 1.4 of Buuugs! published, source and x64-binaries are available.

Main-window with bugs, featurerequests and used units of Buuugs! Bug-window with bug's details of Buuugs! Bug-window with bug's solution in a simple RTF-editor of Buuugs! Bug-window with bug's links (to programs, units or reporters/developers) of Buuugs! Featurerequest-window with featurerequests's details and description in a simple RTF-editor of Buuugs! Unit/Class-window with unit's details and description in a simple RTF-editor of Buuugs! Program's window with links to units/classes of Buuugs! Window for doing additional admin-stuff and editing some table of Buuugs! Search-window of Buuugs! The General's choice of options of Buuugs! Autochangelog-window which creates automaticilly a list of changes (new features, fixed stuff, updates) of Buuugs!

06.04.2021 - Linproman 1.0 (Alpha 2)

Version 1.0 (Alpha 2) of Linproman - Linux Process Manager published, source and x64-binaries are available.

Besides a massive performance improvement on icon fetching and bugfixing, I finally started implementing the actual process managing part of Linproman: A small subsystem able to run scripts on process and/or system events. Like run a script when a process is created or dies.
Later, it will be able to react when a process draws to much CPU-time (to kill processes which are stuck in a loop for example) or if your device is on battery.
So far the engine is implemented and some conditions are working (to get some testcases running). To my surprise I got this easy on CPU at first try: 7 testcases with 13 conditions take less than 1 ms to run.

Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot Linproman (Linux Process Manager) Screenshoot

Archiv: 2021 2020 2019 2018 2017 2016 2015 | Gallery |