| 27 Mar 2022 |
 Anderson Torres | I am interested in porting Nix to Haiku (the open source BeOS replacement).
I have asked a thing or two in their Telegram channel, and I have received some feedback:
| 18:27:14 |
| Anderson Torres |
be warned, you SHOULD know a bit about Haiku before you can start to use nix on it. Basically / on Haiku is not the same as on unixes. Nix will try to store its data in /nix folder structure, and while it is possible to create that folder, you cannot create files in it, because / is a virtual folder, not the root node of the disk.
You have to redefine the nix store to somewhere else.
Also nix uses hardlinks for some things, which is not supported on BFS.
It seems it fails at fallocate, maybe it is something else then; commenting out the code here solved the problem: https://github.com/NixOS/nix/blob/master/src/libutil/archive.cc#L331
| 18:28:34 |
| Anderson Torres | The other possible problem is that Haiku supports 32-bit operating systems. Maybe it would limit the possibility of porting a "haiku-nixpkgs" to it? | 18:29:54 |
 7c6f434c | Well, Wine on x86_64-linux is dependent on 32-bit libraries | 18:47:03 |
| 7c6f434c | So basic 32-bit stuff breaking would be a problem for a (the) Tier-1 platform | 18:47:56 |
| 7c6f434c | Does BeOS support anything like bind-mounts? Because /nix holding no files itself and just serving as a mountpoint sounds good to me | 18:49:00 |
| 7c6f434c | On the other hand, which parts of the sandbox can be approximated is a complicated question… Bind mounts + chroot (or a clear replacement) would be nice to have… | 18:50:19 |
| Anderson Torres | Maybe bind-mounting can be accomplished. Here is a message from their mailing list (completely out of context, but whatever):
https://www.freelists.org/post/haiku-development/Question-about-system-and-bootsystem,14
| 18:56:25 |
