7 replies
May 2023

tqh Developer

Very nice writeup, and amazing work!
Process unique identifiers with area_id’s sounds a bit hacky, is that just for .net tests?
Perhaps a better solution should exist in Haiku?

1 reply
May 2023

nielx Developer

For my Rust cross-compiler builder, I have cobbled together a pkgman tool (in Python) that is designed to work on top of a cross-compiler docker image, and is able to connect to a remote repo, and install packages by name. It does not do any fancy stuff like resolving dependencies, but it is good enough to dynamically download packages from HaikuPorts based on a package name, without having to maintain a list of URLs with the latest versions.

I might be interested, if this is a tool that works for you too, to harden the code a bit more and then add it to the cross-compiler image.

1 reply
May 2023

steveh2022

Hack or no hack, they should give you all the kernel support you need to get your dotnet port done. You’re doing an awesome job.

May 2023

anevilyak Developer

Regarding enumerating mount points, you may want to look at src/bin/df.cpp. It uses BVolume to retrieve all the info needed from a dev_t using the published APIs, which may be simpler than your current approach.

1 reply
May 2023 ▶ tqh

trungnt2910

Sorry for the late reply, but yes, I’ve recently made a change to Haiku allowing processes to retrieve the process start time. The area_id hack is now removed.

I will document that in an upcoming blog.