<jow>
I think this is caused by ustream-ssl-wolfssl
<jow>
ever since it was made default, luci was not functioning properly
<jow>
there's been no related changes to luci or uhttpd in months
<nyt>
weird, since that doesnt seem to be an ssl related error...
<nyt>
what should I switch it out to?
<jow>
try changing to ustream-ssl-openssl if you have the sapce, see if it improves it
<nyt>
x86, so have all the space in the world
<jow>
afair, the errors above are caused by the ustream-ssl-wolfssl layer mixing up data, or someow returning data in such a way that uhttpd's state machine gets confused
<jow>
that leads to all sorts of issues... timeouts, random 400 errors, even on static ressources etc.
<olmari>
BTW, any improvement over using nginx as webserver? Or is it more of "no one is caring so no coding is done" I'm also fine with any answer, craving for info to determine future actions =)
<nyt>
luci-ssl-nginx or luci-ssl-openssl ?
<jow>
nyt: luci-ssl-openssl
<nyt>
[nyt@cc:~/archive/openwrt/x86]: make -j30
<olmari>
(heh, timing of our questions 😀 )
<jow>
olmari: I personally don't care for nginx and I keep receiving bug reports about it handling things differently in subtle ways
<jow>
so it likely has hidden issues with LuCI as well
<olmari>
mm
<nyt>
make -r world: build failed.
<nyt>
ew
<nyt>
that failed after package/install
<jow>
nyt: might be that you need to manually deselect conflicitng stuff
<guidosarducci>
jow: howdy, wondering if you had time to look at the fw3 dscp/mark fixes I posted?
<jow>
guidosarducci: briefly, looks okay
<olmari>
jow: Would have made one of mine bigger router nice lil RP and webserver for things, but we'll manage other ways :)
<olmari>
I can fully see your point in openwrt context in general tho
malwar3hun73r has quit [Ping timeout: 256 seconds]
{Nico} has quit [Ping timeout: 256 seconds]
plntyk has quit [Ping timeout: 256 seconds]
yanosz has quit [Ping timeout: 256 seconds]
Neighbor11111113 has quit [Ping timeout: 256 seconds]
migy has quit [Ping timeout: 256 seconds]
nbd_ has quit [Ping timeout: 256 seconds]
LoopHoldYoaBrown has quit [Ping timeout: 256 seconds]
yuvadm has quit [Ping timeout: 256 seconds]
skolev_ has quit [Ping timeout: 256 seconds]
feriman has joined #openwrt-devel
nyt- has joined #openwrt-devel
nyt has quit [Ping timeout: 256 seconds]
cp- has quit [Quit: Disappeared in a puff of smoke]
skolev has joined #openwrt-devel
cp- has joined #openwrt-devel
LoopHoldYoaBrown has joined #openwrt-devel
malwar3hun73r has joined #openwrt-devel
<karlp>
have you figured out how to get me a cert that is respected yet?
<karlp>
otherwise I'm certainlyagainst this going into 21.02,
<karlp>
I thought the pint was thebranch so you go and do this sort of hacking in master, instead of backdooring it back into stable
Neighbor11111113 has joined #openwrt-devel
poljar has quit [Remote host closed the connection]
poljar1 has joined #openwrt-devel
Tapper has quit [Ping timeout: 245 seconds]
Acinonyx has joined #openwrt-devel
<ynezz>
uh?
<ynezz>
It's about SSL opt-in, making it more visible to the users
<karlp>
yeah, but we're still at this, "ok, you get ssl, just accept this self signed cert warning, hope you aren't being mitm'd" right?
<ynezz>
ssl is disabled by default, after first login you'll get a notice, that "HTTPS is available, make router management more secure with HTTPS. Please read https://openwrt.org/docs/guide-user/luci/luci.secure first"
nyt- is now known as nyt
<rsalvaterra>
ynezz: So, uh… this interest in getting LuCI working over HTTPS is because suddenly we stopped trusting the LAN? :P
<nyt>
openwrt2020 looks kind of not so great
<nyt>
:(
<karlp>
but we trust it enought to accepet self signed certs from it....
<karlp>
magic security!
<stintel>
pffft, http or gtfo :P
<rsalvaterra>
Sounds a bit pointless to insist in HTTPS, to be honest…
<ynezz>
rsalvaterra: yeah, you can use telnet if you want
<nyt>
... if youre being mitm'd on your own network after you just setup and connected to your router, maybe there's an issue
<rsalvaterra>
ynezz: Only from the WAN, over WireGuard, thank you. XD
<nyt>
also i just disabled ssl for testing
<ynezz>
karlp: this PR is about promotion of optional HTTPS, no intention to fix your self-signed issue
<nyt>
was getting weird login issues and 403 without it
<ynezz>
nyt: that's issue with cookie
<nyt>
ah
<karlp>
except that by turning it, you're _giveing_ self signed, and thereby encouraging the behaviour of "just accept the warning"
<olmari>
TBH, Acme client in owrt is easy enough, and even more so uhttpd/luci-openssl has awesome defaults too :)
<karlp>
and I strongly feel that's NOT OK.
<ynezz>
karlp: you can create/improve that wiki page and make it OK
<karlp>
but hey, this is the same coversation as last time.
<nyt>
eh, how are you going to actually get a signed cert for your router with no fqdn
<nyt>
not gonna happen
<olmari>
on organizational stuff you'd obviously have your own CA to sign certs with and company computer policies would include that in cert trust store ;)
<ynezz>
nyt: you don't need one, you can have your own PKI and trusted CA, so just upload your own cert
<ynezz>
nobody forces you to use self-signed certificate generated on a router with crappy entropy
<karlp>
ynezz: so, seeing as it's the same discussion as las titme, and it's a lost cause,can we at least leave it out of 20-branch? it certainly seems like new functionality, and was highly controversial at the itme,
<karlp>
slamming it in now sounds like backdooring it
<nyt>
ynezz, and if youre going to go through that trouble, you can just specify the certs?
<ynezz>
it says
<nyt>
i dont see the issue
<ynezz>
karlp: "ynezz wants to merge 6 commits into openwrt:master"
<karlp>
you _can_ upload your own cert, but is that the "click here to turn on https! magic!" is doing?
<ynezz>
where do you see 21.02?
<olmari>
the main point is to have trusted certificate, either by public CA, or by yourself, or as last resort, accept it in browser =)
<karlp>
13:04:17 ynezz | would be nice to get it into 21.02
<karlp>
that's what I'm against.
<ynezz>
would be, yes
Ultrasauce_ is now known as Ultrasauce
<karlp>
let it play out in master, fine, I'm never going ot be able to stop progress anyway :)
<rsalvaterra>
Hey, in alternative we could move LuCI to a 802.1AE secured management VLAN…
* rsalvaterra
runs
<olmari>
well... nothing in https relates to how you would run stuff on local network, nor VLANning methods =)
<rsalvaterra>
… or, you know… just keeping untrusted devices in an isolated VLAN (or not keeping them at all).
<olmari>
mhm, "management VLAN" alone is an good practice, while nothing stops to use non-ssl stuff at local network perioid... all within decisions of network owner
<grift>
no my field but i would argue that ssl by default would make some sense if luci would have a default password set so that it doesnt go into the plain, but luci has no default password set either.. so that argument doesnt fly
<grift>
s/no/not/
<rsalvaterra>
olmari: Yeah, but I'm not seeing OpenWrt configured out of the box with a management VLAN. That would scare the s**t out of Joe User.
<ynezz>
well, you should first configure your device before plugging it into your network
<ynezz>
so just your device and your laptop
<grift>
does that not imply setting up any ssl then?
<rsalvaterra>
ynezz: Then why insist on HTTPS out of the box? :)
<olmari>
Having PW and being able to sniff data is separate things
<ynezz>
cool, at least someone understands
<grift>
yes i dont mind eitherway. i guess theres some worthy "data to sniff"
<ynezz>
root password?
<grift>
but its not set?
<ynezz>
with ssh password login by default
<grift>
yes but then you manually set up ssl?
<grift>
using ssh
<grift>
anyhow ill drop it, i am fine with it
<grift>
https "breaks" things even with a valid certificate
<grift>
so ce'st la vie
damex has quit [Quit: damex]
damex has joined #openwrt-devel
cp- has quit [Quit: Disappeared in a puff of smoke]
cp- has joined #openwrt-devel
decke has quit [Quit: Leaving.]
damex has quit [Read error: Connection reset by peer]
Slimey has joined #openwrt-devel
damex has joined #openwrt-devel
whyz has quit [Quit: bbl]
damex has quit [Read error: Connection reset by peer]
damex has joined #openwrt-devel
<grift>
i generally admire a pro-active approach, but there could be back lash. try allowing sites with self-signed certificates in some chrome browsers on android phone. you need a PhD for it
<grift>
in my selinux policy i dont try to do things like this (i use to)
<grift>
i basicly assume that device owners know what they are doing
<grift>
have to trust someone ...
damex has quit [Read error: Connection reset by peer]
damex has joined #openwrt-devel
<ynezz>
it's opt-in, so you can just ignore it, but those who get it have it one click away
<grift>
and you know i was going to say but you cannot compare selinux with ssl in openwrt but you actually cal
<grift>
because selinux is opt-in as well
<grift>
so you can argue that if someone has to knowledge to enable selinux then you can expect that someone to know what that might mean
shibboleth has quit [Ping timeout: 268 seconds]
<ynezz>
well, you need kernel for that, so you can't opkg install selinux
<grift>
and i guess the same applies for ssl since thats not a deffault either
<grift>
thats true
<ynezz>
but SSL libs are already there, in every image
<grift>
but there are some similarities
<grift>
yes
<ynezz>
and I can't imagine selinux on most of the targets
<grift>
thats not the point though
<ynezz>
like for example currently cheap/popular mt7621/ath79
<grift>
the point is should we be treating our audience like little children?
<rsalvaterra>
ynezz: There's a lot of pending stuff I can't imagine for ath79 and friends… :P
<ynezz>
grift: BTW it was me who has made that SSL optional, as it was always on by default in commit 0cf3c5dd7257dff1c87b61c5e53e5b1787ab7015
<Q_>
How would you get a valid certificate for it? Or would you create a self-signed certificate?
<ynezz>
so actually I don't know why the people are complaining :p
<Q_>
Either you trust your network not to do an MITM attack, or you use ssh.
<grift>
i am not complaining for the record (i just find it an interesting topic and i am bored)
<nyt>
you mean ssh
<nyt>
with a self generated key
<nyt>
....
<nyt>
that you have to accept the first time
<nyt>
lol
damex has quit [Read error: Connection reset by peer]
damex has joined #openwrt-devel
<ynezz>
yes, that's exactly the same issue as with HTTPS, but people don't care, because SSH clients just make it easy to accept the MITM key
<ynezz>
who checks the fingerprints, right
<grift>
the thing is that accepting a self signed certificate is not easy with modern web browsers
<grift>
i tried it a while ago on my phone
<olmari>
for sane ciphers etc it is mostly easy.. for broken ciphers etc its almost impossible
<rsalvaterra>
Shamelessly hijacking the topic, what we *really* need is zstd compression support for jffs2.
<karlp>
tofu is not the same as how brwosers do it.
<karlp>
you don't get the "HOST KEY HAS CHANGED!" warning rom a browser, you just get a "new" "trust unknown?"
<rsalvaterra>
Right now, zstd is the perfect jack-of-all-trades of compression. We can use it for zram, overlay compression and whatever other compression needs which might arise. And having a single compressor for everything saves space.
<rsalvaterra>
I have patches in my trees (core and fstools) enabling zstd overlay compression in ubifs, but unfortunately jffs2 doesn't support zstd.
<grift>
dunno what to say rsalvaterra any suggestions?
<rsalvaterra>
Well, obviously we need zstd compression in jffs2. I started reading the zstd API, in order to do it myself, but I still don't understand it completely (and jffs2 is stuck in 2005, or so, as it doesn't use the crypto API). And there are possible locking issues to solve too…
<grift>
are there no possible replacements for jffs2? (excuse my ignorance, just showing interest)
<stintel>
btrfs
* stintel
hides
<grift>
2005 is a long time
<rsalvaterra>
grift: Not for small NOR flash (up to 16 MiB, or so).
<rsalvaterra>
For larger filesystems, ubifs scales better, but has higher (space) overhead.
<grift>
i guess that say's something ....
<grift>
about nor flash upto 16 MiB i mean
<rsalvaterra>
grift: That's probably the vast majority of the devices supported by OpenWrt. ;)
nitroshift has quit [Ping timeout: 272 seconds]
* grift
avoids a trap
<rsalvaterra>
I have three 8 MiB devices (ath79), one 128 MiB NAND device (RM2100) and The Beast which is the Omnia.
<grift>
i guess the status quo it is
<rsalvaterra>
And I still wonder why the Omnia's eMMC isn't socketed… missed opportunity, I believe.
<rsalvaterra>
stintel: I won't touch btrfs with a two meter pole. :P
<stintel>
until bcachefs goes upstream there's no alternative ;)
<rsalvaterra>
stintel: I thought I was the only one looking forward to it! :)
<stintel>
rsalvaterra: testing bcachefs in production for 3 years
<rsalvaterra>
stintel: You wrote "testing" and "production" in the same sentence.
<stintel>
best testing happens in production
<stintel>
prove me wrong :)
<rsalvaterra>
stintel: I can't. I'm a programmer. :P
<rsalvaterra>
But it still feels wrong… ;)
<stintel>
well it's home/home office production, but it's still production
<stintel>
my home automation runs on it, it holds VM images exposed via iSCSI that I'm using for my day job, etc
<stintel>
it's been a bumpy road, but still, I like it a lot
<stintel>
had to wipe and restore twice because fubar
Borromini has joined #openwrt-devel
<stintel>
but using even the most robust fs is no substitute for backups, so I have those anyway
<rsalvaterra>
Heh… I fail to recount the number of times btrfs ate my data.
Borromin1 has quit [Ping timeout: 260 seconds]
black_ant has quit [Killed (orwell.freenode.net (Nickname regained by services))]
black_an- has joined #openwrt-devel
Tapper has joined #openwrt-devel
<zorun>
stintel: hi, do you have news of your HiFive Unmatched board? I just heard from a colleague that they cannot ship to Europe for now (something about missing CE compliance)
zjason has joined #openwrt-devel
<Borromini>
isn't CE just China Export? :P
* Borromini
ducks
<stintel>
zorun: delayed
<stintel>
08|19:30:25< stintel> estimated shipping date of the hifive unmatched has changed from 11/03 to somewhere june :(
<zorun>
aw, ok :(
<stintel>
zorun: reminds me of my order of a macchiatobin double shot being canceled because missing US re-export authorization
<stintel>
nitroshift suggested to try via Romania but I never tried anymore
<stintel>
zorun: mouser website now also displays shipping alert: Due to government regulations, Mouser is unable to sell this product in your country.
rmilecki has quit [Ping timeout: 260 seconds]
shibboleth has joined #openwrt-devel
feriman has quit [Quit: WeeChat 3.1]
<zorun>
stintel: ah, right
blb4393 has joined #openwrt-devel
<stintel>
zorun: I requested more info from them
<rsalvaterra>
dwmw2: ping. Quick question, since you're one of the authors… is jffs2 compression single-threaded? :)
<rsalvaterra>
It looks like it, but I'm not sure yet.
shibboleth has quit [Quit: shibboleth]
blb4393 has quit [Quit: ChatZilla 0.9.93 [Waterfox 56.3/MOZ_BUILDID]]
<rsalvaterra>
I think I'm going to test this on the AirGrid. Easier to recover when things go south (and they will, I'm messing with the guts of a filesystem).
<Grommish_>
rsalvaterra: Make sure you play appropriate jaunty/adventerous music while you do it.. The Indiana Jones theme is nice
<rsalvaterra>
Let's see if I can kill the abomination that is 530-jffs2_make_lzma_available.patch…
luke-jr has quit [Ping timeout: 246 seconds]
linzst has quit [Quit: Leaving]
<pkgadd>
Borromini: about nlbwmon vs IPv6, did you try to "/etc/init.d/nlbwmon restart" and check if it manages to count properly then? I have a feeling that nlbwmon might have a race condition with wan6 coming up
<pkgadd>
did you just add the ULA prefix or the global one?
owrt-snap-builds has joined #openwrt-devel
owrt-2102-builds has joined #openwrt-devel
owrt-1907-builds has joined #openwrt-devel
<Borromini>
i didn't add any
<Borromini>
when nlbwmon restarts it looks like it adds both though.
jmv09 has quit [Ping timeout: 240 seconds]
<Borromini>
so now there's 2 PRs for 5.10... lol.
<rsalvaterra>
Borromini: Too many people found out that update_kernel.sh exists… :P
<Borromini>
:P
<rsalvaterra>
Actually, why aren't those scripts part of the core…?
valku has quit [Quit: valku]
<Borromini>
no idea
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
<Grommish_>
rsalvaterra: Oh, That is a very catchy tune
<rsalvaterra>
I want that playing in my funeral. B)
<Grommish_>
hahah
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
<Grommish_>
Denis Leary's I'm an Asshole was the top of my lists.. but, this is strong contender
<Grommish_>
for funeral music
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
Borromini has quit [Quit: leaving]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
KGB-1 has joined #openwrt-devel
KGB-1 has quit [Excess Flood]
<stintel>
sigh
KGB-1 has joined #openwrt-devel
KGB-1 was banned on #openwrt-devel by stintel [*!*kgb@camembert.tina.pm]
KGB-1 has quit [Excess Flood]
<stintel>
I dunno who maintains camembert bot but seriously fix the damn excess flood
* stintel
grabs some brie from the fridge
<olmari>
camembert bot?
<stintel>
11|23:24:25 -!- KGB-1 [~kgb@camembert.tina.pm] has quit [Excess Flood]
<olmari>
ah
jottr_ has joined #openwrt-devel
jottr has quit [Ping timeout: 264 seconds]
plntyk has quit [Ping timeout: 245 seconds]
plntyk has joined #openwrt-devel
jottr_ has quit [Client Quit]
<rsalvaterra>
Cheesy bot…
<stintel>
=)
<stintel>
I'd say cheeky but hey
<olmari>
ain't KGB always cheesy? ;P
<rsalvaterra>
Building an image to test jffs2 zstd compression… I'm still worried about the locking, though… It doesn't *seem* to be needed, but I may be completely wrong. And I'll be testing on a single CPU device…
<rsalvaterra>
OMFG
<rsalvaterra>
/dev/mtdblock5 on /overlay type jffs2 (rw,noatime,compr=zstd)
<olmari>
rsalvaterra: either the world became rainbow coloured unicorno or everything just died ;D
<stintel>
is work? o_O
<rsalvaterra>
stintel: It seems so. No stack traces.
<stintel>
amazeballs
<rsalvaterra>
But I had to manually mount it. I probably need to teach a couple of things to fstools.
<stintel>
sounds plausible
<rsalvaterra>
Let me just push this somewhere, so I can show you guys… :)
<rsalvaterra>
(I actually developed in the Linux kernel tree, then generated a patch to apply in OpenWrt.)
<stintel>
rsalvaterra: planning to send upstream ?
<olmari>
zstd is awesome in zfs relating stuff, and I can very well see the awesomeness in jffs2 and owrt standpoint too
<rsalvaterra>
stintel: After fixing the mounting in fstools and retest, for sure!
<rsalvaterra>
The fact this compiled and ran without issues *the first time* scares me. Nothing works the first time.
<stintel>
maybe it's silently eating your data ;)
<stintel>
like btrfs
<stintel>
SCNR
Dracos-Carazza has quit [Ping timeout: 260 seconds]
Dracos-Carazza has joined #openwrt-devel
<rsalvaterra>
stintel: Edited a file with vi, adding some rubbish. Saved, exited, synced. All fine.
<stintel>
that's what btrfs promised 😂
<rsalvaterra>
stintel: I don't think jffs2 is as complex as btrfs, thankfully… :P
<stintel>
yeah don't mind me really, I'm mostly talking bs again
<olmari>
I was curious about btrfs back in.. like... well 15 years ago or something alike that... and it still is kinda... well.. not there =D
<olmari>
all the licensing quirks aside, then came zfs and never looked back =) in computer side of things
<olmari>
for most router stuff I tend to install openwrt then, even when I'm thrown gazillion beefy xeon "do us router" =)
<stintel>
I have this conspiracy theory that oracle paid some developers to make btrfs so fundamentally flawed in order to lure people to slowaris/zfs
<olmari>
fortunately zfs was made good enough by Sun time, and then when oracle came into play, now oracle has their zfs and rest of the work uses openzfs =)
<olmari>
world*
<olmari>
though work isvery suitable word there too, by acident =D
<stintel>
is Eneas U de Queiroz on IRC ?
<rsalvaterra>
Why does Oracle kill everything it touches? ¬_¬
<stintel>
CEO is evil. I remember him openly saying he wants to kill open source
<stintel>
unfortunately that's what money does with most people
<rsalvaterra>
Pfft… I hope he lives to see PostgreSQL kill Oracle. :P
<stintel>
amen
<rsalvaterra>
Hmm… can't see what's wrong in fstools, should be mounting with compr=zstd…
<rsalvaterra>
Oh, well… I probably just need to get some sleep-
<olmari>
Amen
<guidosarducci>
rsalvaterra: FYI I didn't want to wait and upstreamed a limits.h patch, with you as reporter. If two people had related problems, probably a safe bet.
<rsalvaterra>
guidosarducci: Great! Thanks! :)
<stintel>
upstream is imo always the best place to get feedback, so even if the patch is wrong/incomplete/imperfect/..., it never hurts sending it upstream
<guidosarducci>
stintel: I've found upstream quite helpful and open to thoughtful fixes and discussion, unlike <ahem>...
<rsalvaterra>
Wait! It mounted correctly!! I probably hadn't noticed at first boot. XD
<rsalvaterra>
Sweeeeeeeet!
<rsalvaterra>
I love problems which fix themselves without a single line of code. :P
<guidosarducci>
stintel: also often easier to get something backported from upstream than accepted first downstream
<stintel>
guidosarducci: well upstream has much more manpower usually
<stintel>
I simply completely ignore stuff that is over my head / outside my comfortzone, which effectively means I barely accept stuff at all, as I'm a system engineer for living, barely touch any real code at work
<rsalvaterra>
In this case, I'm testing on OpenWrt because this is jffs2 and it's easier to test here. But I'm *not* sending this to OpenWrt before being accepted upstream.
black_an- has quit [Ping timeout: 246 seconds]
<guidosarducci>
stintel: yup, very true. The "maintainer" role is also clearer there. And FWIW, the context that comes from a systems mindset is key but often undervalued.
<stintel>
guidosarducci: it's probably why I'm always complaining in here ;)