hakurei/system/mkdir.go, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/system/mkdir.go?h=develop2025-11-12T16:17:47Zinternal/system: relocate from system2025-11-12T16:17:47ZOphestracat@gensokyo.uk2025-11-12T16:15:19Zurn:sha1:4e7aab07d5b175345fdf3ea08868dab1e6d90126
These packages are highly specific to hakurei and are difficult to use safely from other pieces of code.
Their exported symbols are made available until v0.4.0 where they will be removed for #24.
Signed-off-by: Ophestra <cat@gensokyo.uk>
container/check: move absolute pathname2025-10-07T11:57:58ZOphestracat@gensokyo.uk2025-10-07T11:06:26Zurn:sha1:0e6c1a50260de141c50bb50fd3f2b2bcf9a3fe64
This allows use of absolute pathname values without importing container.
Signed-off-by: Ophestra <cat@gensokyo.uk>
system: enforce absolute paths2025-10-02T17:26:14ZOphestracat@gensokyo.uk2025-10-02T17:26:14Zurn:sha1:d16da6da8c4880d90dc35fa9006806f7c0395d7f
This is less error-prone, and is quite easy to integrate considering internal/app has already migrated to container.Absolute.
Closes #11.
Signed-off-by: Ophestra <cat@gensokyo.uk>
hst/enablement: move bits from system2025-09-28T21:34:29ZOphestracat@gensokyo.uk2025-09-28T21:32:15Zurn:sha1:44ba7a5f02b7575a706a22aac53c8ac608d18f23
This is part of the hst API, should not be in the implementation package.
Signed-off-by: Ophestra <cat@gensokyo.uk>
container: remove global msg2025-09-28T21:11:47ZOphestracat@gensokyo.uk2025-09-28T17:33:10Zurn:sha1:46cd3a28c83e93b5d66c52d06a8366c11910d5c0
This frees all container instances of side effects.
Signed-off-by: Ophestra <cat@gensokyo.uk>
system/mkdir: use syscall dispatcher2025-09-06T13:30:08ZOphestracat@gensokyo.uk2025-09-06T13:30:08Zurn:sha1:323d132c40a74c5ac7a91731a0c43def2a8be7f1
This enables mkdir op methods to be instrumented.
Signed-off-by: Ophestra <cat@gensokyo.uk>
system: unexport Op implementations2025-09-06T07:16:03ZOphestracat@gensokyo.uk2025-09-06T07:16:03Zurn:sha1:e68db7fbfc367f25ccbaf57ec43f0f4b3c93cba7
None of these are valid with their zero value, and the implementations assume they are created by the builder methods. They are by all means an implementation detail and exporting them makes no sense.
Signed-off-by: Ophestra <cat@gensokyo.uk>
system: improve tests of the I struct2025-09-02T17:16:10ZOphestracat@gensokyo.uk2025-09-02T17:16:10Zurn:sha1:024d2ff7826a81db65eefa1843730b537ebdeef1
This cleans up for the test overhaul of this package.
Signed-off-by: Ophestra <cat@gensokyo.uk>
system: update doc commands and remove mutex2025-09-01T19:54:34ZOphestracat@gensokyo.uk2025-09-01T19:54:34Zurn:sha1:6f719bc3c19d56279d2d76d3bcf8fb66ace2d2fb
The mutex is not really doing anything, none of these methods make sense when called concurrently anyway. The copylocks analysis is still satisfied by the noCopy struct.
Signed-off-by: Ophestra <cat@gensokyo.uk>
system: wrap op errors2025-08-30T13:49:12ZOphestracat@gensokyo.uk2025-08-30T13:49:12Zurn:sha1:f5abce9df5727904a1daa246025a87c4bfe62553
This passes more information allowing for better error handling. This eliminates generic WrapErr from system.
Signed-off-by: Ophestra <cat@gensokyo.uk>