hakurei/cmd/fpkg/proc.go, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/cmd/fpkg/proc.go?h=develop2025-06-25T11:50:24Zcmd/planterette: remove hsu special case2025-06-25T11:50:24ZOphestracat@gensokyo.uk2025-06-25T11:44:49Zurn:sha1:aa454b158f3713b2ee47162837dcea1efdce0ee6
Remove special case and invoke hakurei out of process.
Signed-off-by: Ophestra <cat@gensokyo.uk>
treewide: rename to hakurei2025-06-24T19:57:41ZOphestracat@gensokyo.uk2025-06-24T18:59:52Zurn:sha1:87e008d56de974947ebb99c2cc40b25d3c2cf43e
Fortify makes little sense for a container tool.
Signed-off-by: Ophestra <cat@gensokyo.uk>
app/instance: wrap internal implementation2025-04-12T04:56:41ZOphestracat@gensokyo.uk2025-04-12T04:56:41Zurn:sha1:6309469e933a31a300fbf16d8e77f48dcee402d3
This reduces the scope of the fst package, which was growing questionably large.
Signed-off-by: Ophestra <cat@gensokyo.uk>
app: rename app implementation package2025-04-12T01:54:24ZOphestracat@gensokyo.uk2025-04-12T01:54:24Zurn:sha1:0d7c1a9a4356614f035225aeb24e66421879a99b
Signed-off-by: Ophestra <cat@gensokyo.uk>
app: improve shim process management2025-04-06T18:55:17ZOphestracat@gensokyo.uk2025-04-05T14:51:39Zurn:sha1:e9a7cd526f4e5f0a8f7b18ad3682d2e3afbcb8ba
This ensures a signal gets delivered to the process instead of relying on parent death behaviour.
SIGCONT was chosen as it is the only signal an unprivileged process is allowed to send to processes with different credentials.
A custom signal handler is installed because the Go runtime does not expose signal information other than which signal was received, and shim must check pid to ensure reasonable behaviour.
Signed-off-by: Ophestra <cat@gensokyo.uk>
app: run in native sandbox2025-03-24T16:52:49ZOphestracat@gensokyo.uk2025-03-24T16:52:49Zurn:sha1:5c4058d5ac7e7944973ca8216c258fc50c194e22
Signed-off-by: Ophestra <cat@gensokyo.uk>
cmd/fpkg: call app in-process2025-02-26T10:51:44ZOphestracat@gensokyo.uk2025-02-26T10:46:43Zurn:sha1:673b648bd35285a1dbfc0348716dd6bdd8064a51
Wrapping fortify is slow, painful and error-prone. Start apps in-process instead.
Signed-off-by: Ophestra <cat@gensokyo.uk>
cmd/fpkg: use fortify path from internal2025-02-26T03:16:35ZOphestracat@gensokyo.uk2025-02-26T03:16:35Zurn:sha1:4fa38d60633d921774ccf2771994e5161c12c4f5
Signed-off-by: Ophestra <cat@gensokyo.uk>
fmsg: implement suspend in writer2025-02-16T09:51:53ZOphestracat@gensokyo.uk2025-02-16T08:26:09Zurn:sha1:e599b5583dd821ed26bdfc01f7f67d4a317b9843
This removes the requirement to call fmsg.Exit on every exit path, and enables direct use of the "log" package. However, fmsg.BeforeExit is still encouraged when possible to catch exit on suspended output.
Signed-off-by: Ophestra <cat@gensokyo.uk>
proc: remove duplicate compile-time fortify reference2025-01-18T02:59:33ZOphestracat@gensokyo.uk2025-01-18T02:59:33Zurn:sha1:7baca66a56f67fa5722b689cbff747eac12b857e
This is no longer needed since shim and init are now part of the main program.
Signed-off-by: Ophestra <cat@gensokyo.uk>