@dequbed

It doesn't really matter who is using the llm anyway, systemd as a project went on to bet on llms' full "potential", as indicated by https://slopscan.ava.pet/repo/https%3A%2F%2Fgithub%2Ecom%2Fsystemd%2Fsystemd
It's just a matter of time until more LLM-tainted commits make it to systemd

If we're focusing on Lennart, I would say he's pretty accepting of llms and so is likely to make use of them in other projects: https://github.com/systemd/systemd/issues/41085#issuecomment-4053443496

Regardless, Chimera Linux's author did a good resumé of everything that ppl like me find wrong with systemd on its own: https://chimera-linux.org/docs/faq#what-is-the-projects-take-on-systemd

#issuecomment #what

Was er meint sind Optimierungen in der Serverkonfiguration des MariaDB SQL Servers.

Die in deinem Fall vermutlich nicht notwendig sind da es ja auch so mit wenig RAM bedarf läuft.

Das ist zum Beispiel was im Friendica Matrix Channel angepinnt/empfohlen ist:

max_connections = 256
# thread-cache set equal to max connections
thread_cache_size = 256
table_cache = 2048
# Enable the old query optimizer setting (cf. https://github.com/friendica/friendica/issues/11465#issuecomment-1222720339)
optimizer_use_condition_selectivity = 1
optimizer_switch = 'rowid_filter=off'
# Cf. https://gist.github.com/fevangelou/0da9941e67a9c9bb2596
join_buffer_size = 2M
table_definition_cache = 1200
table_open_cache = 1200
# Use up to 70-80% of RAM
innodb_buffer_pool_size = 4G
# Use 25% of the innodb_buffer_pool_size value
innodb_log_file_size = 1G
innodb_file_per_table = 1
innodb_default_row_format = dynamic
# increased values to avoid too frequent checkpointing
innodb_log_buffer_size = 128M
# disk speed settings optimized for NVMe SSD
innodb_flush_neighbors = 0
innodb_io_capacity = 1000
innodb_io_capacity_max = 2000
wait_timeout = 28800
interactive_timeout = 28800
low_priority_updates = 1
# 0 = NEVER, 1 = AUTO, 2 = ALWAYS
concurrent_insert = 2
Solange du nicht in Probleme läufts, würde ich aber bei der Standardkonfig bleiben.

CC: @[email protected] @[email protected]

https://codeberg.org/librewolf/issues/issues/1919#issuecomment-4988409

This is what I found, from about a year ago, where they vaguely say "we remove it because it's unwanted feature creep, not because it's AI" which is, ehhhhhhh, but not nearly as strong a stance as Waterfox and Zen. That's why I am not recc'ing Librewolf personally at this time

#issuecomment