1. 06 Sep, 2001 5 commits
    • Chad Barb's avatar
      · f0bae36c
      Chad Barb authored
      Added real CRC-32 checksums, to replace "fake" add-bytes-together
    • Leigh B. Stoller's avatar
      Changes to nfree in how scheduled reloads are handled. Instead of · 2007505d
      Leigh B. Stoller authored
      firing off an os_load, just move the node from its current reservation
      to emulab-ops/reloadpending. This moves the operation out of band from
      the user's perspective (he gets more immediate response when an
      experiment ends, and besides we cannot handle mass reloads anyway, and
      so this approach is unusable until Frisbee.
      Change the reload_daemon to look for free nodes that need a reload (as
      before) *and* nodes in emulab-ops/reloadpending (as put there by nfree).
      In this case, the imageid comes from the reloads table instead of the
      node-types table. I also updated the reload_daemon to use libdb routines.
      Also change testbed/reloading to emulab-ops/reloading. Maybe someday
      I'll remove these hardwired strings.
    • Leigh B. Stoller's avatar
      Change testbed/reloading to emulab-ops/reloading. Maybe someday I'll · 2fe38a0d
      Leigh B. Stoller authored
      remove these hardwired strings.
    • Robert Ricci's avatar
      Changed examples from using FBSD40-STD to FBSD-STD, and RHL61-STD to RHL-STD. · 8e0c915d
      Robert Ricci authored
      Also went over references to FreeBSD 4.0 and RedHat 6.2, and changed them
      to 4.3 and 7.1 as appropriate
    • Leigh B. Stoller's avatar
      Minor hacks to support FBSD-STD and RHL-STD as generic OSIDs. These · d7532d24
      Leigh B. Stoller authored
      have been added as OSIDs so that the parser accepts them. os_setup
      maps them into whatever equiv OSID is loaded on the target node,
      according to the OS slot of the osid table entry. If no mapping can be
      made (no equiv OS loaded, as defined by the partitions table) os_setup
      fails. I've also changed the web page node control form so that the
      only OSIDs you can set for a node are the ones loaded (partitions
      table) or OSKit kernels (osid table entry has a path).
  2. 05 Sep, 2001 6 commits
  3. 04 Sep, 2001 6 commits
    • Robert Ricci's avatar
    • Robert Ricci's avatar
      Added some RMA notes · 9381f9f3
      Robert Ricci authored
    • Chad Barb's avatar
      · b81d7ee8
      Chad Barb authored
      Added checksums (simple add for now,) as well as Multicast leave-group on exit.
    • Robert Ricci's avatar
      Added the beginnings of frisbee support to os_load. Simply use the '-f' · 8e54fae7
      Robert Ricci authored
      switch to try it out. The main thing missing at this point is a way to tell
      frisbee _which_ disk image to load - it will load whichever image there
      happens to be a server running for.
    • Robert Ricci's avatar
      Added support for a next_pxe_boot_path column in proxydhcp, in preparation · c0c06bf0
      Robert Ricci authored
      for using frisbee to do mass disk-loading.
      Note that, unlike bootinfo, this does _not_ include support for clearing
      this field, since there does not seem to be a clean way to contact proxydhcpd
      to indicate that it can be cleared. This support will most likely be put into
    • Leigh B. Stoller's avatar
      Found and fixed the bug that Chad found last week and did not check · 2f2a8a28
      Leigh B. Stoller authored
      in. Sigh. Took me too long to find this. On the other hand, there is
      more debugging and more asserts in the code. Also a -d option to turn
      on progressive levels of debugging.
      Also changed the operation of imageunzip so that individual slice
      writes (ie, to unzip the BSD or Linux partition instead of the entire
      disk). Using the slice device (/dev/rda0s1) is actually a problem on
      BSD since it snoops writes to where the disklabel should be and alters
      the offsets. Even worse, on non BSD partitions it craps out completely
      because there is no disk label at all. This is really a dumb
      thing. So, I added code to read the MBR when the -s (slice) option is
      given, and use the MBR to compute the offsets from the beginning of
      the raw disk. Must always use the raw disk device now, and the new
      operation is:
      	imageunzip all.ndz /dev/rad0
      	imageunzip -s 2 rhat.ndz /dev/rad0
      Note that if you give a slice instead of a disk device, and there is a
      valid looking MBR in the slice (which is very possible), then things
      will get very confused. Not sure what to do about that yet.
  4. 02 Sep, 2001 1 commit
  5. 31 Aug, 2001 2 commits
  6. 30 Aug, 2001 10 commits
  7. 29 Aug, 2001 6 commits
  8. 28 Aug, 2001 4 commits