Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • redox redox
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 227
    • Issues 227
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • redox-os
  • redoxredox
  • Issues
  • #739

Closed
Open
Created Nov 04, 2016 by Jeremy Soller@jackpot51Owner0 of 35 tasks completed0/35 tasks

Document default schemes

For every scheme a fully running kernel has, the following functions need to be documented, if implemented. In addition, the Scheme and SchemeMut traits should be documented with usage and the default operation.

Documentation should include usage, what access restrictions there are, what paths and dup arguments are valid, and what errors may be returned.

Path Operations

  • open
  • mkdir
  • rmdir
  • unlink

File Operations

  • dup
  • read
  • write
  • seek
  • fevent
  • fmap
  • fpath
  • fstat
  • fsync
  • ftruncate
  • close

Schemes

  • debug
  • disk
  • display
  • env
  • ethernet
  • event
  • file
  • initfs
  • ip
  • irq
  • network
  • null
  • orbital
  • pipe
  • pty
  • rand
  • sys
  • tcp
  • udp
  • zero
Assignee
Assign to
Time tracking