<braewoods>
Who seriously needs to care about the space limitations of regular CDs? DVDs are quite plentiful these days.
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux-devel
<beerman>
i just want it smaller, i don't give two cents about fitting it on a CD
SiFuh has quit [Quit: leaving]
SiFuh has joined #crux-devel
farkuhar has joined #crux-devel
<stenur>
I do. All external sources (including O-Ss) except git that i track are checked out to a NULL branch which contains only a file that contains the name of the projects real master/main/trunk/etc branch. And the .git/objects is gc'd after updates, and aggressively so "four times a year" (with .keep update once a year for now). This saves tremendous amounts of space, and is good enough for me.
<stenur>
And i love to be able to download ISOs which are small. Not only because of my constrained internet bandwidth.
<stenur>
crux-3.0.iso.zst is 251072132 bytes, 3.6 is 829997436. Bummer.
<farkuhar>
Re: the nghttp2-libs name change, i seem to recall something similar happened with the crux 3.6 release, when mesa3d was renamed to mesa, but setup-helper did not properly rename them during an upgrade. That was fixed in 3.6.1, though.
<jaeger>
There's an oldcrux.nu directory backup in frinnst's homedir that's 29G, I'm going to delete it from crux.nu to free up space. I doubt there's anything interesting or needed in there but I have local backups in case
<jaeger>
also going to remove a 12G backup file from 2017, same thing applies. I have local backups
<jaeger>
need to free up some space in / as well but just mentioning for reference
<beerman>
yep
<jaeger>
I might set up some more aggressive log rotation soon... or possibly do some filesystem reorg since the / partition isn't too large
<beerman>
well, as soon as we ditch flyspray this problem should be nonexistant
<beerman>
IIRC, its that that spams the php fpm log aggressively but i haven't restarted fpm yet to continue, always wanted to be able to have you step in and do a backup if needed just in case or whatever
<jaeger>
For what it's worth there are 3 backups done every day :D
<jaeger>
8 hours apart
<beerman>
lol
<beerman>
yeah
<beerman>
i just don't want to risk/provoke it
<beerman>
:D
<beerman>
it might be easier to pull the content and try a config out locally
<jaeger>
sure, could do that
<jaeger>
Definitely safer
<beerman>
i mean
<beerman>
i dont see a problem in just restarting fpm in place
<beerman>
i just seen it go haywire too much to trust it however :D
<beerman>
we could just do that quickly and if that works i can continue playing with nginx and so on
<beerman>
shouldn't be too much work left to do for it anyway
<beerman>
we just still might need to clean up the host further, apart from logs, i already deleted a lot of old backups etc
<stenur>
wouldn't it be nice if that CRUX logrotate concept would finally be replaced by sysklogd's power? As in "kern.* /var/log/kernel ;rotate=200k:5"
<stenur>
(It now also can "notify /root/bin/syslog-notify.sh