From nobody Sun Jan 21 03:30:55 2024 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4THf5V2yPqz5884N for ; Sun, 21 Jan 2024 03:31:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4THf5V0djKz4PY0 for ; Sun, 21 Jan 2024 03:31:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-40e86a9fc4bso27091345e9.2 for ; Sat, 20 Jan 2024 19:31:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1705807867; x=1706412667; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=cCxrEOaKv/lDs3/gg58OCxyiPik5Tcb+Ftrduy7BA48=; b=wD1bW0PSc090Zf+h53BM7Mq41gFr7P3ftWEGK2R6Sp/CRvOto4dqhSuxGCN8js+c4H 62CNRFzv6iOuZIEIHR5vCMSRZQlUILxRR7EhOlSC+UH4Dtt6hs43giJJuidi5eG+0sN+ YjypUwIByt/rJFN1I/lBuZQROFjau8BDIgLHV1e4OF/J8pRrxc0wleMaUPodZNunc6wB kC5LROuv5r931avwGWJkAzytbTGJlprgtxasyOHNM1nn5hS6VvU+78m/ml5Q4VePnejP 3dNYCXuIPqtqL56GMjdKplF22pvmMVyOskQLDSlgDDIcFBJb6bDYXh+Anw4qKmNDHdzg GyDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705807867; x=1706412667; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=cCxrEOaKv/lDs3/gg58OCxyiPik5Tcb+Ftrduy7BA48=; b=cAtZsiFrVDatg9cKDt+7Hk2wwm1NirT3CqIlzrsmGaT3OY0jh0tdPT0riLTDjX9UpK T5Mzg6iviEXvB0OdFoiEe/ItMm8Tqwvu8xpZP2rt3TrSmHmAB94oLn5mGmU1ZpkkvXOt Psxe7I3ewIFN17aXpr8wOGruZ0v5hebJvWIzKcRSYFYON8vplTCD8yXdTiVOobYWQJtK r0aXm0bdiRkJF4TApQSQOIZ7ct5tFodKnIOP34IVgVoIlXa/QXaTm5+AWdqbSc/vQQke M5MUSxk/32RFQfZ4lf/Q9N0E/Ci8SlhEfO1cj8XiNWPzhZrl2PoeURrkRIDarUkwFXBx 85Zg== X-Gm-Message-State: AOJu0YyqgCl0Dg50UZUDoMs1YoUqGxpHhaFy1e36d3q6VKoOSz8WjYrH AgwM4sXX+E1rzgzt1PD5KBQ/D2n85KSz0prxPeGuQQ05CR5QHT6TTlmKUiWXCI4IM1OW3OXYPjb Q9y9ENYpnoteEjJ1JVSGJMgjEh1iQbHMwt2L+og== X-Google-Smtp-Source: AGHT+IFMYY+YxmSsboiToxa5Nl5IPMYkgZ9PibNMa9HxXOltc0vg4f/1eBYRSH5vIUb7mwU4OtJ9D1QSAUZu1op55Gk= X-Received: by 2002:a05:600c:5253:b0:40e:6087:89b7 with SMTP id fc19-20020a05600c525300b0040e608789b7mr1092977wmb.107.1705807867175; Sat, 20 Jan 2024 19:31:07 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <1673801705774097@mail.yandex.ru> <20240121110611.af567b0ac3a8fd8593ffcb7f@dec.sakura.ne.jp> In-Reply-To: <20240121110611.af567b0ac3a8fd8593ffcb7f@dec.sakura.ne.jp> From: Warner Losh Date: Sat, 20 Jan 2024 20:30:55 -0700 Message-ID: Subject: Re: The Case for Rust (in the base system) To: Tomoaki AOKI Cc: Aleksandr Fedorov , Alan Somers , FreeBSD Hackers , Scott Long , "Goran Meki??" Content-Type: multipart/alternative; boundary="000000000000fa7706060f6c5723" X-Rspamd-Queue-Id: 4THf5V0djKz4PY0 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --000000000000fa7706060f6c5723 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jan 20, 2024, 7:06=E2=80=AFPM Tomoaki AOKI wrote: > On Sat, 20 Jan 2024 15:31:23 -0700 > Warner Losh wrote: > > > On Sat, Jan 20, 2024 at 11:45=E2=80=AFAM Aleksandr Fedorov > > > wrote: > > > > > What about external dependencies? > > > > > > > https://github.com/Axcient/freebsd-nfs-exporter/blob/master/Cargo.toml#L1= 9 > > > https://github.com/asomers/gstat-rs/blob/master/gstat/src/main.rs#L20 > > > > > > Is there any plan for which crates we should take into the base syste= m? > > > > > > We have had C++ in base for many years, but I don=E2=80=99t see any g= ood > libraries > > > for CLI, logging, JSON, etc. > > > > > > > > > > https://doc.rust-lang.org/rustc/platform-support.html#tier-1-with-host-to= ols > > > > > > Where is the support for Freebsd as a primary platform? ARM, RISC-V, > > > Power? Should we rewrite devd? > > > > > > I think we need to start by providing official repositories (e.g > > > git.FreeBSD.org/rust.git or git.FreeBSD.org/go.git) > > > for different languages that include stable bindings to the system AP= I: > > > - sysctl > > > - libgeom > > > - libifconfig > > > - netgraph > > > - jail > > > - etc. > > > > > > So that it=E2=80=99s not just some anonymous on crates.io that repres= ents > these > > > bindings, but our community. > > > Officially, with support for a stable ABI for releases, security > patches, > > > etc. > > > > > > After this, it will be possible to think about which components to > include > > > in the base system. > > > > > > I would be glad to see a more modern language than C in the database, > but > > > I=E2=80=99m afraid that it will be like with C++, > > > that we will get a couple of daemons and utilities and that=E2=80=99s= all. > > > > > > > These are all good questions that need good answers, though necessarily > to > > get started. > > > > But the other question that occured to me after my last posting was "Wh= at > > about build integration?" > > How much of the rust automation do we take in vs how much do we drive > from > > a future bsd.rust.mk. > > I can sketch out bsd.rust.mk (to pick an arbitrary name, we'd likely > need > > one for what we traditionally > > think of as libraries (which may or may not map 1:1 onto crates: we cou= ld > > have c callable libraries > > written in rust in the future, for example) and one for binaries. > > Initially, though, if we go with the > > 'make rust tests possible' then we'd likely need the appropriate packag= es > > installed for whatever > > dependencies we'd have in the tests. This would give us a taste for wha= t > > we'd need to do for > > base, I'd think. Once we had that notion, I can easily see there needin= g > to > > be some sort of > > rust bindings for ATF/kyua as one of the first libraries / crates that > > would test that aspect of > > the build system. That all would be up to the people writing the tests = in > > rust, I'd imagine. > > > > While I could jot out the basics of this integration (so one could just > add > > the rust > > tools to a subdir or subdirs, include the bsd.rust.mk or whatever and > then > > it would build > > if rust is enabled, and would emit a warning it was skipped because rus= t > > was disabled). > > We'd find out if this is workable or not and iterate from there. But th= at > > would also require > > active participation from the rust advocates to make it a reality: I ca= n > > put together the > > build infrastructure for the disabled case, but likely can't on my own = do > > the rust enabled > > case. I'd be happy to work with someone to do that, but I'm not going t= o > be > > able to do > > that myself: my need for rust is slight, my knowledge of rust is weak, > etc. > > Working with > > someone (or ideally several someones), though it could become reality. = So > > please contact > > me if you'd like to work on this. > > > > Warner > > One way to go could be moving programs rewritten with rust to ports. > There are some programs (not in rust, though) moved to ports, like rcs. > Yes. And a number of programs have been made available as ports, but not too many replace c programs. Currently, it would not be so realistic, but once we completely switch > to pkgbase, IIUC, programs in base can sanely depemd on ports programs, > excluding kernel and fundamental libraries. Possible, but I'd wager not for quite some time for fundamental things. I could be wrong on this timeline... As non-rust consumers of graphics/librsvg2-rust can sanely link with > it, I assume kmods in ports written in rust can kldload'ed sanely. > This could be a good starting point. > Kernel modules are far off om the horizon at this point. There was a proof of concept done years ago, but much has changed so an effort is needed to get back to that basic point. And would be not all, but test for rust libraries could be implemented > with C/C++ or any other language suitable, if the rust libraries can > sanely linked with test codes. > That's not a given... ABIs are hard enough without a C to rust layer sneaking in. Warner Am I wrong? > > > > > 20.01.2024, 19:51, "Alan Somers" : > > > > > > In a recent thread on src-committers, we discussed the costs and > > > benefits of including Rust code in the FreeBSD base system. To > > > summarize, the cost is that it would double our build times. imp > > > suggested adding an additional step after buildworld for stuff that > > > requires an external toolchain. That would ease the build time pain. > > > The benefit is that some tools would become easier to write, or even > > > become possible. Here is a list of actual and potential Rust projects > > > that could benefit from being in-tree. If anybody else has items to > > > add, I suggest moving this into the project wiki: > > > > > > Stuff that could only be written in Rust if it were in base > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > * ctl-exporter (I started this, but discovered that the CTL stats API > is > > > unstable, so it can't live in ports. Instead, I had to do it in C). > > > > > > > https://github.com/freebsd/freebsd-src/commit/1a7f22d9c211f504f6c48a86401= 469181a67ec34 > > > > > > * fusefs tests. Absolutely impossible to do in C. I considered Rust, > but > > > went > > > with C++ so they could live in base. They are too closely coupled t= o > > > fusefs(5) to live out-of-tree. > > > https://github.com/freebsd/freebsd-src/tree/main/tests/sys/fs/fusef= s > > > > > > * devd. Currently C++, but imp suggested a rewrite. > > > https://github.com/freebsd/freebsd-src/tree/main/sbin/devd > > > > > > * zfsd. Currently C++, but I've long pondered a rewrite. Using Rust > would > > > make it more testable. > > > https://github.com/freebsd/freebsd-src/tree/main/cddl/usr.sbin/zfsd > > > > > > * nscd. Currently C, but confusing and with no test coverage. I've > > > contemplated a rewrite myself, but I don't want to do it in C. > > > https://github.com/freebsd/freebsd-src/tree/main/usr.sbin/nscd > > > > > > * The userland portion of the 802.11ac and Lightning stacks. scottl > > > suggested > > > that these were good candidates for Rust. > > > > > > * freebsd-kpi-r14-0 . https://crates.io/crates/freebsd-kpi-r14-0 > > > > > > Stuff that can live in ports, but would be nicer in base > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D > > > > > > * gstat-rs https://crates.io/crates/gstat > > > > > > * geom-exporter (I've started this, but haven't published it) > > > > > > * nfs-exporter https://crates.io/crates/freebsd-nfs-exporter > > > > > > * virtiofsd-rs . Nobody has yet tried to port it to FreeBSD. But if t= he > > > connection to bhyve(8) is too intimate, it might be hard to do in > ports. > > > https://gitlab.com/virtio-fs/virtiofsd > > > > > > * jail-exporter https://crates.io/crates/jail_exporter > > > > > > * Various jail managers have been attempted in Rust. I think these ar= e > > > fine in > > > ports, but others like Goran Mekic have opined that they should be > moved > > > to > > > base instead. > > > > > > * musikid's pjdfstest rewrite. I think it would be great to start usi= ng > > > this > > > to test the base system's file systems. If the tests themselves > lived in > > > base, they would be easier to sync with file system development. > > > https://github.com/musikid/pjdfstest > > > > > > * pf-rs. I suspect that the API isn't very stable. > > > https://crates.io/crates/pf-rs > > > > > > * benchpmc. The pmc counter names changes between releases. > > > https://crates.io/crates/benchpmc > > > > > > FreeBSD-related applications that are just fine in ports > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > * fsx-rs. Unlike pjdfstest, this only tests datapath APIs. Those are > > > usually > > > more stable than control path APIs, so I think there's little to be > > > gained by > > > moving this into base. https://crates.io/crates/fsx > > > > > > * ztop. It uses ZFS's kstats sysctl interface, which is pretty stable= . > > > https://crates.io/crates/ztop > > > > > > * iocage-provision https://crates.io/crates/iocage-provision > > > > > > * rsblk https://crates.io/crates/rsblk > > > > > > * xfuse https://github.com/KhaledEmaraDev/xfuse > > > > > > Other FreeBSD-related libraries in Rust > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > Just see the list at https://crates.io/keywords/freebsd > > > -- > Tomoaki AOKI > --000000000000fa7706060f6c5723 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Jan 20, 2024, 7:06=E2=80=AFPM Tomoaki AOKI <= ;junchoon@dec.sakura.ne.jp= > wrote:
On Sat, 20 Jan 2024 15:= 31:23 -0700
Warner Losh <imp@bsdimp.com> wrote:

> On Sat, Jan 20, 2024 at 11:45=E2=80=AFAM Aleksandr Fedorov <wigne= ddoom@yandex.ru>
> wrote:
>
> > What about external dependencies?
> >
> > https= ://github.com/Axcient/freebsd-nfs-exporter/blob/master/Cargo.toml#L19 > > https://gi= thub.com/asomers/gstat-rs/blob/master/gstat/src/main.rs#L20
> >
> > Is there any plan for which crates we should take into the base s= ystem?
> >
> > We have had C++ in base for many years, but I don=E2=80=99t see a= ny good libraries
> > for CLI, logging, JSON, etc.
> >
> >
> > htt= ps://doc.rust-lang.org/rustc/platform-support.html#tier-1-with-host-tools
> >
> > Where is the support for Freebsd as a primary platform? ARM, RISC= -V,
> > Power? Should we rewrite devd?
> >
> > I think we need to start by providing official repositories (e.g<= br> > > git.FreeBSD.org/rust.git or g= it.FreeBSD.org/go.git)
> > for different languages that include stable bindings to the syste= m API:
> > - sysctl
> > - libgeom
> > - libifconfig
> > - netgraph
> > - jail
> > - etc.
> >
> > So that it=E2=80=99s not just some anonymous on crates.io t= hat represents these
> > bindings, but our community.
> > Officially, with support for a stable ABI for releases, security = patches,
> > etc.
> >
> > After this, it will be possible to think about which components t= o include
> > in the base system.
> >
> > I would be glad to see a more modern language than C in the datab= ase, but
> > I=E2=80=99m afraid that it will be like with C++,
> > that we will get a couple of daemons and utilities and that=E2=80= =99s all.
> >
>
> These are all good questions that need good answers, though necessaril= y to
> get started.
>
> But the other question that occured to me after my last posting was &q= uot;What
> about build integration?"
> How much of the rust automation do we take in vs how much do we drive = from
> a future bsd.rust.mk.
> I can sketch out bsd.rust.mk (to pick an arbitrary name, we= 9;d likely need
> one for what we traditionally
> think of as libraries (which may or may not map 1:1 onto crates: we co= uld
> have c callable libraries
> written in rust in the future, for example) and one for binaries.
> Initially, though, if we go with the
> 'make rust tests possible' then we'd likely need the appro= priate packages
> installed for whatever
> dependencies we'd have in the tests. This would give us a taste fo= r what
> we'd need to do for
> base, I'd think. Once we had that notion, I can easily see there n= eeding to
> be some sort of
> rust bindings for ATF/kyua as one of the first libraries / crates that=
> would test that aspect of
> the build system. That all would be up to the people writing the tests= in
> rust, I'd imagine.
>
> While I could jot out the basics of this integration (so one could jus= t add
> the rust
> tools to a subdir or subdirs, include the bsd.rust.mk or whate= ver and then
> it would build
> if rust is enabled, and would emit a warning it was skipped because ru= st
> was disabled).
> We'd find out if this is workable or not and iterate from there. B= ut that
> would also require
> active participation from the rust advocates to make it a reality: I c= an
> put together the
> build infrastructure for the disabled case, but likely can't on my= own do
> the rust enabled
> case. I'd be happy to work with someone to do that, but I'm no= t going to be
> able to do
> that myself: my need for rust is slight, my knowledge of rust is weak,= etc.
> Working with
> someone (or ideally several someones), though it could become reality.= So
> please contact
> me if you'd like to work on this.
>
> Warner

One way to go could be moving programs rewritten with rust to ports.
There are some programs (not in rust, though) moved to ports, like rcs.
=

Yes.= And a number of programs have been made available as ports, but not too ma= ny replace c programs.

<= div class=3D"gmail_quote">
Currently, it would not be so realistic, but once we completely switch
to pkgbase, IIUC, programs in base can sanely depemd on ports programs,
excluding kernel and fundamental libraries.

Possible, but I'd wager not for = quite some time for fundamental things. I could be wrong on this timeline..= .

As non-rust consumers of graphics/librsvg2-rust can sanely link with
it, I assume kmods in ports written in rust can kldload'ed sanely.
This could be a good starting point.

Kernel modules are far off om the hor= izon at this point. There was a proof of concept done years ago, but much h= as changed so an effort is needed to get back to that basic point.

And would be not all, but test for rust libraries could be implemented
with C/C++ or any other language suitable, if the rust libraries can
sanely linked with test codes.

That's not a given... ABIs are hard enoug= h without a C to rust layer sneaking in.

<= div dir=3D"auto">Warner

=
Am I wrong?


> > 20.01.2024, 19:51, "Alan Somers" <asomers@freebsd.o= rg>:
> >
> > In a recent thread on src-committers, we discussed the costs and<= br> > > benefits of including Rust code in the FreeBSD base system. To > > summarize, the cost is that it would double our build times. imp<= br> > > suggested adding an additional step after buildworld for stuff th= at
> > requires an external toolchain. That would ease the build time pa= in.
> > The benefit is that some tools would become easier to write, or e= ven
> > become possible. Here is a list of actual and potential Rust proj= ects
> > that could benefit from being in-tree. If anybody else has items = to
> > add, I suggest moving this into the project wiki:
> >
> > Stuff that could only be written in Rust if it were in base
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > * ctl-exporter (I started this, but discovered that the CTL stats= API is
> >=C2=A0 =C2=A0unstable, so it can't live in ports. Instead, I h= ad to do it in C).
> >
> > https://github.com/freebsd/freebsd-src/commit/1a7f22d9c211f504f6c48a= 86401469181a67ec34
> >
> > * fusefs tests. Absolutely impossible to do in C. I considered Ru= st, but
> > went
> >=C2=A0 =C2=A0with C++ so they could live in base. They are too clo= sely coupled to
> >=C2=A0 =C2=A0fusefs(5) to live out-of-tree.
> >=C2=A0 =C2=A0https://github.com/freebsd/freebsd-src/tree/main/tests/sys/fs/fusefs > >
> > * devd. Currently C++, but imp suggested a rewrite.
> >=C2=A0 =C2=A0https://g= ithub.com/freebsd/freebsd-src/tree/main/sbin/devd
> >
> > * zfsd. Currently C++, but I've long pondered a rewrite. Usin= g Rust would
> >=C2=A0 =C2=A0make it more testable.
> >=C2=A0 =C2=A0= https://github.com/freebsd/freebsd-src/tree/main/cddl/usr.sbin/zfsd
> >
> > * nscd. Currently C, but confusing and with no test coverage. I&#= 39;ve
> >=C2=A0 =C2=A0contemplated a rewrite myself, but I don't want t= o do it in C.
> >=C2=A0 =C2=A0https= ://github.com/freebsd/freebsd-src/tree/main/usr.sbin/nscd
> >
> > * The userland portion of the 802.11ac and Lightning stacks. scot= tl
> > suggested
> >=C2=A0 =C2=A0that these were good candidates for Rust.
> >
> > * freebsd-kpi-r14-0 . https://crates.= io/crates/freebsd-kpi-r14-0
> >
> > Stuff that can live in ports, but would be nicer in base
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > * gstat-rs https://crates.io/crates/gstat
> >
> > * geom-exporter (I've started this, but haven't published= it)
> >
> > * nfs-exporter https://crates.io/c= rates/freebsd-nfs-exporter
> >
> > * virtiofsd-rs . Nobody has yet tried to port it to FreeBSD. But = if the
> >=C2=A0 =C2=A0connection to bhyve(8) is too intimate, it might be h= ard to do in ports.
> >=C2=A0 =C2=A0https://gitlab.com/virtio-fs/= virtiofsd
> >
> > * jail-exporter https://crates.io/crates/= jail_exporter
> >
> > * Various jail managers have been attempted in Rust. I think thes= e are
> > fine in
> >=C2=A0 =C2=A0ports, but others like Goran Mekic have opined that t= hey should be moved
> > to
> >=C2=A0 =C2=A0base instead.
> >
> > * musikid's pjdfstest rewrite. I think it would be great to s= tart using
> > this
> >=C2=A0 =C2=A0to test the base system's file systems. If the te= sts themselves lived in
> >=C2=A0 =C2=A0base, they would be easier to sync with file system d= evelopment.
> >=C2=A0 =C2=A0https://github.com/musikid/pjd= fstest
> >
> > * pf-rs. I suspect that the API isn't very stable.
> >=C2=A0 =C2=A0https://crates.io/crates/pf-rs > >
> > * benchpmc. The pmc counter names changes between releases.
> >=C2=A0 =C2=A0https://crates.io/crates/benchpmc<= /a>
> >
> > FreeBSD-related applications that are just fine in ports
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > * fsx-rs. Unlike pjdfstest, this only tests datapath APIs. Those = are
> > usually
> >=C2=A0 =C2=A0more stable than control path APIs, so I think there&= #39;s little to be
> > gained by
> >=C2=A0 =C2=A0moving this into base. https://crates.i= o/crates/fsx
> >
> > * ztop. It uses ZFS's kstats sysctl interface, which is prett= y stable.
> >=C2=A0 =C2=A0https://crates.io/crates/ztop
> >
> > * iocage-provision https://crates.io/c= rates/iocage-provision
> >
> > * rsblk https://crates.io/crates/rsblk
> >
> > * xfuse https://github.com/KhaledEmara= Dev/xfuse
> >
> > Other FreeBSD-related libraries in Rust
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > Just see the list at https://crates.io/keywor= ds/freebsd


--
Tomoaki AOKI=C2=A0 =C2=A0 <junchoon@dec.sakura.ne.jp>
--000000000000fa7706060f6c5723--