OpenBSD www changes summary for 2017-11-12 to 2017-11-19 inclusive
==================================================================

amd64.html                              books.html
events.html                             faq
papers                                  want.html

== amd64.html ======================================================== 01/06 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/www/amd64.html

amd64.html


  > kaby lake is 7xxx series (tedu@)

== books.html ======================================================== 02/06 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/www/books.html

books.html


  > apue 3rd edition appeared way back in 2013.
  > diff from mazo comp (tb@)

== events.html ======================================================= 03/06 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/www/events.html

events.html


  > bsdtw is over (deraadt@)

== faq =============================================================== 04/06 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/www/faq

faq

  ~ current.html                          

  > ifconfig <if> deletetunnel replaced by -tunnel (benno@)

  ~ current.html                          

  > html is hard, lets go shopping. thanks tb@ for noticing (benno@)

  ~ faq15.html                            

  > In general, pkg tools are fairly sturdy.
  > Spell out more clearly that most use cases of pkg_check are tied to
  > filesystem problems (e.g., power failures at the wrong moment)
  > okay tb@, tj@, with minor cosmetic tweaks (espie@)

  ~ upgrade62.html                        

  > fix broken link: #AfterUpgrade -> #ConfigChanges.
  > from awoserra via danj, thanks (tb@)

  ~ faq15.html                            

  > Provide a PKG_PATH example with several mirrors and installpath value.
  > initial diff by me, simplified by tj@, ok tb@ (landry@)

== papers ============================================================ 05/06 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/www/papers

papers

  + bsdtw.pdf                             

  > bsdtw is over (deraadt@)

== want.html ========================================================= 06/06 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/www/want.html

want.html


  > better specs now that i looked deeper.. (landry@)


  > SAS disks are no longer needed in Vienna, Austria.
  > Remove entry on martin@'s request. (feinerer@)


  > clarify a sentence (deraadt@)


  > no longer need that (deraadt@)


  > The laptop request has been taken care of by the OpenBSD Foundation,
  > many thanks! (landry@)


  > Remove my request for Atheros AR5008E-3NX devices.
  > One such device was donated some time ago, thanks to Gerrit Meyerheim.
  > Additional thanks to everyone else who subsequently offered to obtain
  > such a device for me.
  > The card I got cannot yet work with our athn(4) driver because it does not
  > have an EEPROM (which, among other things, provides the PCI device ID).
  > I now need help with finding a generic EEPROM and/or a way to generate
  > EEPOM images which contain suitable data. Since this is a narrowly scoped
  > task which does not require kernel driver development skills, I want to
  > delegate it. If you are interested in working on this task, and especially
  > if you have contacts in the OpenWRT community (who have solved this issue
  > in their OS), let me know. (stsp@)


  > Add a request for AR7010 devices which I will need to continue working
  > on USB athn(4) open source firmware support.
  > These devices come in several variants, most of which are hard to track
  > down,
  > and some of which are relatively expensive.
  > See https://wikidevi.com/wiki/Atheros_AR7010 for product names.
  > I have already received an offer for financial reimbursement, but my
  > biggest problem is that hunting these devices down takes time and effort.
  > Perhaps somebody has such a device somewhere gathering dust?
  > I will need at least a 5GHz (11a/b/g/n) variant and a 2GHz (11b/g/n)
  > variant.
  > And having a device with accessible UART would be nice.
  > Some people have very vocally complained about closed wifi firmware on
  > our mailing lists. Now this is your chance to do something productive
  > about that issue and give back to the community. (stsp@)

===============================================================================
_______________________________________________
owc mailing list
[email protected]
http://www.squish.net/mailman/listinfo/owc

Reply via email to