Date: Sun, 4 Aug 2024 12:09:32 -0600 From: Alan Somers <asomers@freebsd.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: A Demo of rust-in-base Message-ID: <CAOtMX2ht0EinR4G56gN6z=gQuJDAHfnE0JPOo7E6hSWC1=dDzA@mail.gmail.com> In-Reply-To: <202408041800.474I0HUM050473@critter.freebsd.dk> References: <CAOtMX2gdt8xYyLR3peYWhov-161-6d7%2B8L6TiHCCyw1NQyspXw@mail.gmail.com> <202408041800.474I0HUM050473@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 4, 2024 at 12:00=E2=80=AFPM Poul-Henning Kamp <phk@phk.freebsd.= dk> wrote: > > -------- > Alan Somers writes: > > Due to all of the recent discussion of using Rust for code in the > > FreeBSD base, I've put together a demo of what it might look like. It > > demonstrates: > > Awesome! > > But to be blunt: Is it worth the effort, relative to concentrating > on a pkg-based distribution of FreeBSD, where these things could > be built with the regular "COTS" Rust ecosystem, without having to > do all this extra work and adding all this extra maintenance load ? If it weren't for my experience with CTL, I would say no. But CTL stuff _cannot_ exist in the ports tree, since the ioctl interface is unstable. Similarly, stuff like the fusefs test suite can't exist in the ports tree, either. It needs to be updated in lock-step with even minor kernel changes. If those are to use Rust, they need to reside in the same git repository as freebsd-src.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2ht0EinR4G56gN6z=gQuJDAHfnE0JPOo7E6hSWC1=dDzA>