0.18.0 --- the atoms of openkal 0.17, the stop word given back, and a start without execveat by Sunrisepeak · Pull Request #38 · mcpplibs/openkal-linux

0.18.0 --- the atoms of openkal 0.17, the stop word given back, and a start without execveat

Sunrisepeak

and

speak-agent

committed

a92da11

SIGPIPE ignored for this program's own writes is not passed on: a started program begins with the disposition this one was started with

Sunrisepeak

and

speak-agent

committed

2d8aaef

the SIGPIPE test starts both cases itself, independent of what its harness was started with

Sunrisepeak

and

speak-agent

committed

5e1f914

kal_env_loader: a program built for its environment has no loader to name (openkal 0.17)

Sunrisepeak

and

speak-agent

committed

94d468c

a name held open is removed at once where the volume claims KAL_FS_PROP_REMOVE_OPEN (openkal 0.17, clause 7.14)

Sunrisepeak

and

speak-agent

committed

3b914ea

a program in a pid namespace whose /proc is the system's is named as /proc names it, and one the kernel gives no descriptor for is observed through its entry

Sunrisepeak

and

speak-agent

committed

7086951

the vectors are read from environ wherever the C library publishes it, and from the registers only where it does not: a static program over musl passed the check with what its registers held

Sunrisepeak

and

speak-agent

committed

ea4f39e

openkal 0.17.0, by version

Sunrisepeak

and

speak-agent

committed

55497ef

Navigation Menu

Repository navigation

0.18.0 --- the atoms of openkal 0.17, the stop word given back, and a start without execveat - #38

0.18.0 --- the atoms of openkal 0.17, the stop word given back, and a start without execveat#38
Sunrisepeak merged 8 commits into
mainfrom
openkal-0.17.0

Commits on Oct 26, 2026

0.18.0 --- the atoms of openkal 0.17, the stop word given back, and a start without execveat

SIGPIPE ignored for this program's own writes is not passed on: a started program begins with the disposition this one was started with

the SIGPIPE test starts both cases itself, independent of what its harness was started with

kal_env_loader: a program built for its environment has no loader to name (openkal 0.17)

a name held open is removed at once where the volume claims KAL_FS_PROP_REMOVE_OPEN (openkal 0.17, clause 7.14)

a program in a pid namespace whose /proc is the system's is named as /proc names it, and one the kernel gives no descriptor for is observed through its entry

the vectors are read from environ wherever the C library publishes it, and from the registers only where it does not: a static program over musl passed the check with what its registers held

openkal 0.17.0, by version