#tyndur · 2010-02-25

66 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen

  1. kwolfMoin
  2. pcmattmanHello kwolf
  3. kwolfHi pcmattman
  4. kwolfHow's it going with the X server? :-P
  5. pcmattmanWell, I found out there's actually alternatives to sysvinit, so I'm investigating those routes at the moment
  6. pcmattmanOS X uses a thing called "launchd" which sounds nice, and isn't a GNU program
  7. pcmattmanThe goal is to have some form of script or something which runs at startup and loads all the drivers necessary for the system (ie, a bunch of modload invocations) to function
  8. pcmattmanThat way the initrd can just contain a tiny subset of modules and drivers and those people want can be loaded later
  9. pcmattmanFor example, the network stack and network drivers should probably be loaded outside of kernel startup, and only if the user says "Yes, enable networking"
  10. kwolfHm, are you going to integrate it with the CDI driver loading stuff that you'll send to the list soon? ;-)
  11. pcmattmanMost likely
  12. kwolfWould be difficult with sysvinit, no?
  13. pcmattmanThe CDI driver loading stuff is an example of loading drivers on-demand (or rather, on device plugin)
  14. kwolfI don't know launchd though, what kind of approach does it use?
  15. pcmattmanlaunchd is basically a mix of cron, inetd, and init
  16. pcmattmanMix of functionality, not code
  17. pcmattmanSo I might have a startup script which runs "modload cdi", and the CDI module is loaded, executed, and a bunch of other drivers are loaded automatically by the loading system I've yet to implement
  18. kwolfSo it's runlevel based like init?
  19. pcmattmanI believe so. I haven't researched it enough yet to be sure
  20. pcmattmanhttp://developer.apple.com/macosx/launchd.html
  21. pcmattmanThe basic idea is to try and really reduce the size of our kernel+initrd and put off loading necessary drivers as late as possible
  22. pcmattman(as well as support running daemon processes such as Apache, if you want to use Pedigree as a web server OS or something ;) )
  23. kwolfWe need a new HTTP status code for Segmentation Fault first ;-)
  24. pcmattman:(
  25. pcmattmanMind you, apache doesn't actually work on Pedigree at the moment because we need to implement writable mmap files
  26. kwolfI thought it was fairly platform independent?
  27. pcmattmanIt is, but we built it with mmap support
  28. kwolfWell, that's your problem then ;-)
  29. pcmattmanHowever, our mmap does not yet support writing to the memory region and having those regions written back to the file
  30. kwolfIf you don't have a working mmap, don't tell Apache to use it
  31. pcmattmanAll we need to do is implement that and it'll work fine
  32. pcmattmanWell, it was mmap or shm
  33. pcmattmanI like keeping my sanity, so I chose mmap ;)
  34. kwolfFair enough ;-)
  35. pcmattmanI might look at lighthttpd though, try and do some stress testing of the TCP code
  36. pcmattmanAnd/or the CDI rtl8139 driver
  37. kwolfThen you need performance, so you need more clever cdi_mem_areas ;-)
  38. pcmattmanHeh, no more quick and easy solution :)
  39. kwolfQuick and easy never works. Except for Hello World.
  40. pcmattmanOr works and then scales terribly
  41. pcmattmanBoth aren't good
  42. pcmattman"server.c:(.text+0x979): undefined reference to `setgroups'" :)
  43. pcmattmanOut of interest, how do you go with tyndur and porting software?
  44. kwolfYou mean just the basic approach?
  45. pcmattmanPretty much
  46. kwolfMaybe you have already seen http://git.tyndur.org/?p=lbuilds.git;a=summary
  47. kwolfIt's basically our build/packaging system for external software
  48. pcmattmanOh, cool
  49. pcmattmanYou put it in a repository
  50. pcmattmanWe put already-built packages in a repository, but not patches, source trees, or any of the tools needed to create ports
  51. kwolfFor each package, we have a download URL, a build script and some patches
  52. kwolfWe only carry patches in our own repo
  53. kwolflbuilds is actually pretty nice to work with
  54. pcmattmanIt looks like it
  55. kwolfI just need to learn not to forget quilt add all the time ;-)
  56. pcmattmanI've been meaning to put together such a thing, so someone without a properly configured environment can change that and port something
  57. pcmattmanIt's just a *lot* of work
  58. kwolfHm, lbuilds is pretty simple. It's just a couple of short shell scripts.
  59. kwolfMost of it should even be independent of tyndur
  60. kwolfBut if you're going to copy it, we'll lose about the only thing where we are ahead :-(
  61. kwolf;-)
  62. pcmattmanNah, not gonna copy it
  63. pcmattmanNice idea though, might copy the concept
  64. pcmattman;)
  65. kwolfI guess it's even more useful with a working POSIX layer ;-)
  66. pcmattmanThat helps