Contents |
We're still defining the scope of the problem. What are the common uses of syscall() out there?
The "syscall" function is the #1 most-needed function in glibc not in the LSB. Unfortunately, the kernel community (for good reason) is extremely nervous about exposing syscall to the wide world.
We need to decide whether we should export it, or whether there are other workarounds to syscall usage.
A rough proposed schedule for this project. When we anticipate that we will reach certain milestones. Also, if the project has an absolutely-must-be-completed-by date, mention it here.
| Milestone | Plan Date | Outlook | Comments |
|---|---|---|---|
| Identify the common uses of syscall. | |||
| Produce a document reflecting that usage, along with recommended actions. | |||
| Implement those actions. |
No resources are dedicated to this project.
No hardware is dedicated to this project.
List of people who are working on the project and their roles.
| Name | Role |
|---|---|
| Jeff Licquia | Project Owner |
Tasks will map many-to-one to milestones. Tasks are specific actionable work items that need to be completed in order to reach a milestone
| Task | Owner | Status | Outlook |
|---|
| Task | Owner | Status | Outlook |
|---|
Tasks that can't be scheduled yet because they are waiting on some other task or external entity
| Task | Owner | Status | Outlook |
|---|
No comments yet.