Commits

Commit:
4753f0691a01a52bd5aa6b650832fbc3fba9218e
From:
rsc <devnull@localhost>
Date:
more exits
diff | patch | tree
Commit:
a0a331aad99bbca5a13fa4b69593061f29dc3a29
From:
rsc <devnull@localhost>
Date:
add _procwakeupandunlock to help ease locking contention on Linux 2.4.
diff | patch | tree
Commit:
815552b9ed41df2f20892f6467dd47f91f93aca1
From:
rsc <devnull@localhost>
Date:
go back to 1000 scheds
diff | patch | tree
Commit:
a620761c92f49d2738f99fab206a4c61a89394cf
From:
rsc <devnull@localhost>
Date:
add some annoying lock loop prints -- let's see if they ever fire. also fix race in delaystack. it was actually happening! that just goes to show that while i can reason very well about what can and cannot happen, i have no intuition at all for how likely they are.
diff | patch | tree
Commit:
1d2533d0101fd1721ab26837485c0b094205c3bd
From:
rsc <devnull@localhost>
Date:
restore old plan 9 property that when the last thread exits the main proc, the remaining program ends up in the background and the program appears to have exited.
diff | patch | tree
Commit:
d54ead7fb922cfa661c7b7f0d0b2ba1251cdea7f
From:
rsc <devnull@localhost>
Date:
more freebsd work
diff | patch | tree
Commit:
93eb807ac2b7c23cae2b0999957532b5b666f437
From:
rsc <devnull@localhost>
Date:
remove debugging
diff | patch | tree
Commit:
2c87dda8f89e84082523b03b62c5d47d55c13341
From:
rsc <devnull@localhost>
Date:
add threaddaemonize(), more bug fixes
diff | patch | tree
Commit:
8cbd854a8ab2c4f8c738c5bea5263217cb892a77
From:
rsc <devnull@localhost>
Date:
better exec handling
diff | patch | tree
Commit:
955a2ca78d7efc2787864e38a3d902df16fc2541
From:
rsc <devnull@localhost>
Date:
starting to work on Linux
diff | patch | tree
Commit:
f1e8706de85f43523a789f4411b5727ed5211ec3
From:
rsc <devnull@localhost>
Date:
linux pre-2.6 implementation
diff | patch | tree