serpente has quit [Remote host closed the connection]
aardo has quit [Ping timeout: 252 seconds]
ardo has joined #crux
DaViruz has quit [Ping timeout: 268 seconds]
hermit_crab has joined #crux
<hermit_crab>
Hello, someone know of a repo with pre-compiled core packages up-to-date? I can't compile binutils;cmake;gcc;python3 on my poor raspi 3b+
lavaball has joined #crux
<hermit_crab>
sorry english mistakes.
<cruxbridge>
<tim> hermit_crab: you are looking for #crux-arm
<hermit_crab>
oh, sorry. DUH!
<hermit_crab>
thanks anyway.
hermit_crab has quit [Quit: hermit_crab]
<cruxbot>
[core/3.8]: util-linux: updated to version 2.41.1
ivandi has quit [Quit: WeeChat 4.6.3]
ivandi has joined #crux
<ivandi>
util-linux does not build with bash-completion installed
SiFuh_ has quit [Remote host closed the connection]
SiFuh_ has joined #crux
<cruxbot>
[core/3.8]: util-linux: fixed build if bash-completion is installed
ivandi has quit [Quit: WeeChat 4.6.3]
ivandi has joined #crux
GazL has joined #crux
<GazL>
Afternoon all.
<GazL>
pkgmk is report a bunch of /usr/share/man/man3/* files missing for the new util-linux build. Have they been intentionally left out and the footprint is wrong, or should they be being installed.
jue has joined #crux
<cruxbot>
[core/3.8]: util-linux: fixed footprint
<jue>
sorry for the mess with util-linux, not my day, it seems ;)
<jue>
and thanks for the reports, of course
<jue>
ivandi: will look at rc tomorrow
<jue>
GazL: to answer your question, the footprint was wrong, I mistakenly had installed asciidoctor
<braewoods_>
jue, the one doctor you don't want a house call from ;)
<jue>
lol
<GazL>
jue: ok. thanks.
lavaball has quit [Remote host closed the connection]
<frinnst>
wtf, meson downloads stuff when building mesa? not very well it seems:
<frinnst>
tcp SYN-SENT
<frinnst>
i hate modern computing
<cruxbridge>
<tim> frinnst: i can't see that happening over here, can you post your log?
<frinnst>
not much, meson tries to connect to something:
<frinnst>
Checking for function "dladdr" with dependency : YES
<frinnst>
Checking for function "dl_iterate_phdr" : YES
<frinnst>
Checking for function "clock_gettime" : YES
<frinnst>
that's those are the 4 last lines, then it just sits and waits for it to timeout i guess
<cruxbridge>
<tim> this is not the port core/meson but some other port?
<frinnst>
im building mesa
<cruxbridge>
<tim> ah.. mh, it shouldn't if its not rust crates for rust stuff
<cruxbridge>
<tim> ivandi: what exactly do you mean when you say that rc does not handle swap?
<frinnst>
I guess that's the reason why. to be honest i cant be arsed to bother with it. I just like to vent. You'd better put me on /ignore :-)
<frinnst>
<frinnst> i hate modern computing
<cruxbridge>
<tim> lol, who doesn't? wanna play buzzword bingo?
<cruxbridge>
<tim> i seen meson do that when it pulls subprojects which should be dependencies and/or guarded with isinst steps, but this usually depends on git also
<farkuhar_>
tim: according to ivandi's patch, swapon should have been placed *after* /bin/mount -a -O no_netdev (during startup), and swapoff should have been placed *before* /bin/umount -a -d -r -t nosysfs,noproc,notmpfs,nodevtmpfs (during shutdown/reboot).
<farkuhar_>
The sequencing of those commands got mixed up, when rc was being refactored to modularize the colour feature.
<cruxbridge>
<tim> right, thank you
<frinnst>
oh wow, went to take a piss and its actually progressing
<frinnst>
sorry i'll pipe my anger to /dev/null now
frinnst has quit [Quit: welcome to IRC: where the men are men, the women are men, and the little girls are FBI agents]
<farkuhar_>
rc 2.35 commented out the lines that handled RNG seeding, but according to random(4) the seed file needs to be "saved across reboots" for cryptographic security. That recommendation applies even if we implement stenur's FS#1921 ("better algorithm to seed /dev/urandom" https://git.zx2c4.com/seedrng )
farkuhar_ has quit [Quit: leaving]
farkuhar has joined #crux
<jue>
farkuhar: I've pushed the changes to rc we've talked about today, please have a look if we need other additions/modifications
<farkuhar>
jue: Thanks. Two fixes have already been pointed out, but there might be others. 1, the placement of swapon and swapoff, with respect to `mount -a` and `umount -a`. 2, saving and restoring the random seed across reboots, as recommended by random(4).
<farkuhar>
SiFuh has been working on a binary rc, https://gitlab.com/SiFuh/Documentation/-/blob/master/Other/rc-20250527.tgz?ref_type=heads , which is the example I followed when commenting out the /dev/urandom manipulations. But after further reading, I agree with restoring those commands as in the latest commit 3a9610ff3ccadbe8ae23fe4c53c6e8ceea55c507.
<GazL>
Perhaps making the writing to /dev/random dependent on /proc/sys/kernel/random/entropy_avail < 256 would be an idea, Unless your in a vm or some imbedded platform with limitied entropy gathering I'm not sure its worth carrying data over. AIUI the crng will reseed every 60 seconds or so anyway.
<GazL>
... or maybe make it dependent on a PARANOID=yes in rc.conf! ;)