<feed xmlns='http://www.w3.org/2005/Atom'>
<title>hakurei/internal/app/init/early.go, branch develop</title>
<subtitle>low-level userspace tooling for Rosa OS</subtitle>
<id>http://src.rosa.moe/hakurei/atom/internal/app/init/early.go?h=develop</id>
<link rel='self' href='http://src.rosa.moe/hakurei/atom/internal/app/init/early.go?h=develop'/>
<link rel='alternate' type='text/html' href='http://src.rosa.moe/hakurei/'/>
<updated>2025-03-13T12:57:54Z</updated>
<entry>
<title>internal/app: rename init to init0</title>
<updated>2025-03-13T12:57:54Z</updated>
<author>
<name>Ophestra</name>
<email>cat@gensokyo.uk</email>
</author>
<published>2025-03-13T12:57:54Z</published>
<link rel='alternate' type='text/html' href='http://src.rosa.moe/hakurei/commit/?id=4133b555ba8dd38accb272d86c01898ac4b99f95'/>
<id>urn:sha1:4133b555ba8dd38accb272d86c01898ac4b99f95</id>
<content type='text'>
This makes way for the new container init.

Signed-off-by: Ophestra &lt;cat@gensokyo.uk&gt;
</content>
</entry>
<entry>
<title>fmsg: implement suspend in writer</title>
<updated>2025-02-16T09:51:53Z</updated>
<author>
<name>Ophestra</name>
<email>cat@gensokyo.uk</email>
</author>
<published>2025-02-16T08:26:09Z</published>
<link rel='alternate' type='text/html' href='http://src.rosa.moe/hakurei/commit/?id=e599b5583dd821ed26bdfc01f7f67d4a317b9843'/>
<id>urn:sha1:e599b5583dd821ed26bdfc01f7f67d4a317b9843</id>
<content type='text'>
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 &lt;cat@gensokyo.uk&gt;
</content>
</entry>
<entry>
<title>internal: move shim and init into app</title>
<updated>2025-02-16T07:28:46Z</updated>
<author>
<name>Ophestra</name>
<email>cat@gensokyo.uk</email>
</author>
<published>2025-02-16T07:28:46Z</published>
<link rel='alternate' type='text/html' href='http://src.rosa.moe/hakurei/commit/?id=33a4ab11c226c736c0d8b2644fbbe27a5ca045e9'/>
<id>urn:sha1:33a4ab11c226c736c0d8b2644fbbe27a5ca045e9</id>
<content type='text'>
This structure makes more sense, as both processes are part of an app's lifecycle.

Signed-off-by: Ophestra &lt;cat@gensokyo.uk&gt;
</content>
</entry>
</feed>
