kevans91

13 ms·

31.
by kevans91 5y ago
Minor nit that we mostly hadn't moved to GPL3 stuff, and now we're working on replacing the remainder of the GPL2 stuff.
32.
by kevans91 5y ago
I interpreted it as a missing 'if'... > Even [if] I was interested before, ... after reading this?
33.
by kevans91 5y ago
I personally don't see the need, pfSense is rock-solid for my uses.
34.
by kevans91 5y ago
pkgbase? We split base up into packages and deploy binary updates via our package manager, pkg(8), instead of with patches distributed via freebsd-update(8). We have a lot of build knobs that can make some parts optional, and some of those
35.
by kevans91 5y ago
Pretty much anything that would need to come from Broadcom, really The docs that most recently bit us are pcie/ethernet on the RPi4; I got in touch with Broadcom, who is now in a multi-year effort to figure out how to disperse usable d
36.
by kevans91 6y ago
I speak as a FreeBSD developer who has dabbled with RPi, having tested and shuffled in a lot of the initial RPi4 patches and did some not-insignificant hacking to get a single RPi image to actually support RPi3 + RPi4.
37.
by kevans91 6y ago
Speaking from personal experience, it's an absolute pain -- they're already an odd duck (w.r.t. booting, for instance), add on that the documentation is incredibly lacking compared to competitors and you've got a platform tha
38.
by kevans91 6y ago
This is pretty unlikely, unfortunately. We're generally looking out for a Pi maintainer because it doesn't really have one -- it's not the most desirable platform to hack on, from a developer POV.
39.
by kevans91 6y ago
That's just 2021- check back at 2020 and you'll find a couple more.
40.
by kevans91 6y ago
Yeah, sorry, I'm mostly lamenting that there's not a more objective overview. This whole situation is pretty tiring at this point, so it's unlikely that one will surface except as a post-mortem down the road.
41.
by kevans91 6y ago
FWIW, "good review" is pretty debatable (source: was involved) -- it provides a decent overview, but you should read it with the thought in mind that the author did some pretty heavy cherry-picking to support their arguments. Also
42.
by kevans91 6y ago
I was linked back to your reply because it seems that I've not really communicated this very well- there's nothing wrong specifically with how you represented the situation, and I'm sorry if I came across as angry about you s
43.
by kevans91 6y ago
I've been trying to stay quiet here because I just want to part ways, but the last sentences here got to me. This wasn't a "mission to fix if_wg," at least it didn't start that way, and I think that it's import
44.
by kevans91 6y ago
Personal project: > This is a personal project, not backed by the author's employer.
45.
by kevans91 6y ago
Note that there's additional follow-up available here: https://lists.freebsd.org/pipermail/freebsd-hackers/2021-Mar...
46.
by kevans91 6y ago
Oh man, this brings me back to writing Redvex plugins long ago... looks like it's gone far, far away.
47.
by kevans91 6y ago
I think someone reported the latest firmware or something pulling some shenanigans if there's no display connected, whether we use it or not. I don't recall the specifics at the moment, though.
48.
by kevans91 6y ago
FWIW, RPi 4 is fraught with peril on FreeBSD < 13.0 -- and even if you could have gotten it to boot, you'd find neither ethernet nor USB. FreeBSD >= 13.0 has an aarch64 RPI image that should boot OOTB for both RPi3/RPi4 -- t
49.
by kevans91 6y ago
This is outdated; the RPI3 image has been removed for 13.0/14.0-CURRENT with a new RPI image that should serve all (~both) aarch64 Pi.
50.
by kevans91 6y ago
Sorry, a bit late; the ARM64 "RPI" image should work out of the box and recognize all of your RAM.
51.
by kevans91 6y ago
> However, BSD's do not guarantee that their userlands will work with a mismatched kernel. Sure, it often does work, hence why jails only give a warning on mismatch rather than refuse to run at all. FWIW, FreeBSD tends to go to pret
52.
by kevans91 6y ago
Ugh, that's unfortunate. =\ After looking at this repo more closely, this really is pretty suboptimal. build.sh is incredibly flexible, but yeah- no documentation on what you'd need to build a non-pfsense branded product. That&#x2
53.
by kevans91 6y ago
I haven't tried it, but this doesn't seem to be the case anymore. Notably, [0] is clearly a pretty up-to-date copy of the stable/12 that they're almost certainly running given some of the recent direct commit references
54.
by kevans91 6y ago
Huh, cool! Are all Prosody modules pure-lua, or can/do some have a C/binary component to them? I note that the API documentation describes only lua bits, at least.
55.
by kevans91 6y ago
I can't speak for anyone else, but from my perspective (and I suspect others are similar): I like the idea of a jail-backed OCI runtime, but it's not interesting enough to my personal use to overtake any of the other OS-adjacent p
56.
by kevans91 6y ago
A little late to the party, but- MacOS has actually beaten FreeBSD to the punch by shipping with bsdgrep as grep for years at this point. FreeBSD should be able to switch before 13.0, but the bsdgrep developer is a slacker. It's only m
57.
by kevans91 6y ago
I see no reason not to also provide the compatible long option on FreeBSD: https://svnweb.freebsd.org/changeset/base/365954
58.
by kevans91 6y ago
Note that we haven't yet introduced .lua configuration capabilities (that's a project branch off to the side), but it does certainly make modifying menu entries and other fun stuff a lot more palatable in my experience.
59.
by kevans91 6y ago
Yeah, this... though it'd be awesome if they updated their setup for working ZFS boot environments OOTB. Last I checked they were setting vfs.root.mountfrom explicitly in /boot/loader.conf.local, which is not stellar. =-(
60.
by kevans91 6y ago
Generally- so far, flua only drives the generation of the various files we derive from syscalls.master. There's been some WIP to also use it for some pkgbase stuff, as well as an ldconfig lua script for use in post-install scripts now

More ›