Skip to content
Snippets Groups Projects
  1. Sep 06, 2006
  2. Sep 03, 2006
  3. Aug 24, 2006
  4. Aug 23, 2006
  5. Aug 22, 2006
    • kaashoek's avatar
      i/o redirection in sh · 8b58e810
      kaashoek authored
      better parsing of sh commands (copied from jos sh)
      cat: read from 1 if no args
      sbrk system call, but untested
      getpid system call
      moved locks in keyboard intr, but why do we get intr w. null characters from keyboard?
      8b58e810
  6. Aug 19, 2006
  7. Aug 14, 2006
    • kaashoek's avatar
      user-level programs: mkdir and rm · d7b3b802
      kaashoek authored
      shell parses arguments (very simplistic)
      readme version of README (sh doesn't deal with capital characters)
      printf recognizes %c
      nicer output format for ls
      d7b3b802
  8. Aug 13, 2006
  9. Aug 12, 2006
    • kaashoek's avatar
      zero freed blocks · c372e8dc
      kaashoek authored
      multi-block directories
      track size of directory (size = number entries in use)
      should namei (and other code that scans through directories) scan through all blocks of a directory and not use size?
      c372e8dc
  10. Aug 11, 2006
  11. Aug 09, 2006
  12. Aug 08, 2006
  13. Jul 29, 2006
    • rtm's avatar
      open() · 32630628
      rtm authored
      32630628
  14. Jul 28, 2006
  15. Jul 27, 2006
  16. Jul 16, 2006
    • rsc's avatar
      nitpicks · c54c7926
      rsc authored
      c54c7926
    • rsc's avatar
      · 9b37d1bf
      rsc authored
      Add user.h for prototypes.
      Add cons_puts for cleaner output.
      9b37d1bf
  17. Jul 10, 2006
    • rsc's avatar
      Changes to allow use of native x86 ELF compilers, which on my · 5ce9751c
      rsc authored
      Linux 2.4 box using gcc 3.4.6 don't seem to follow the same
      conventions as the i386-jos-elf-gcc compilers.
      Can run make 'TOOLPREFIX=' or edit the Makefile.
      
      curproc[cpu()] can now be NULL, indicating that no proc is running.
      This seemed safer to me than having curproc[0] and curproc[1]
      both pointing at proc[0] potentially.
      
      The old implementation of swtch depended on the stack frame layout
      used inside swtch being okay to return from on the other stack
      (exactly the V6 you are not expected to understand this).
      It also could be called in two contexts: at boot time, to schedule
      the very first process, and later, on behalf of a process, to sleep
      or schedule some other process.
      
      I split this into two functions: scheduler and swtch.
      
      The scheduler is now a separate never-returning function, invoked
      by each cpu once set up.  The scheduler looks like:
      
      	scheduler() {
      		setjmp(cpu.context);
      
      		pick proc to schedule
      		blah blah blah
      
      		longjmp(proc.context)
      	}
      
      The new swtch is intended to be called only when curproc[cpu()] is not NULL,
      that is, only on behalf of a user proc.  It does:
      
      	swtch() {
      		if(setjmp(proc.context) == 0)
      			longjmp(cpu.context)
      	}
      
      to save the current proc context and then jump over to the scheduler,
      running on the cpu stack.
      
      Similarly the system call stubs are now in assembly in usys.S to avoid
      needing to know the details of stack frame layout used by the compiler.
      
      Also various changes in the debugging prints.
      5ce9751c
    • kaashoek's avatar
      oops · 084f2143
      kaashoek authored
      084f2143
Loading