FreeBSD

By Google’ing the web I got a 1.1.5.1-RELEASE tarball. FreeBSD 1.x was based on Net/2 and the USL lawsuit has caused FreeBSD project to re-start from 4.4BSD-Lite2, and 1.1.5.1 was the last 1.x RELEASE permitted to be released.

I have requested src/usr.sbin/timed/timedc/timedc.c, v 1.5 to be MFC’ed to RELENG_4 and RELENG_4_10 so it will get its way into the upcoming release. It has not decided whether this will be merged into RELENG_4_10 yet, however, it is very likely that this will.

I have employed the following (ugly) script for MFC’ing, as I do not want to really make big difference between FreeBSD and my fork version:

It turns that I need to set up my own cvsup server so I can deploy my fork elsewhere. Here comes how.

Today I have finally started my lightweight fork of FreeBSD. The methodlity taken was, use the official mirror (cvsup5.cn)’s cvsup service and derive my own repository with CVSup’s local repository ablity by disabling its delete function, and exploiting FreeBSD’s stock CVS’s local branch numbering feature.

Wow… Erwin Lansing is requesting for a pointy hat with a blinking light in the top :-)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

erwin       2004/05/02 23:35:27 PDT

  FreeBSD ports repository

  Modified files:
    .                    modules 
  Log:
    kscope --> ports/devel/kscope
  
  Revision  Changes    Path
  1.10000   +1 -0      CVSROOT/modules

Shortly after OpenBSD’s 3.5 splash web, Matthew Dillon has released a thrid “known stable” iso for DragonFlyBSD. It can be obtained from ftp://ftp.dragonflybsd.org/iso-images/dfly-20040502.iso.gz.

This snapshot included many new features, yet stable:

What’are LORs? To quote Robert Watson:

“These warnings are generated by Witness, a run-time lock diagnostic system found in FreeBSD 5-CURRENT kernels (but removed in releases). You can read more about Witness in the WITNESS(4) man page, which talks about its capabilities. Among other things, Witness performs run-time lock order verification using a combination of hard coded lock orders, and run-time detected lock orders, and generates console warnings when lock orders are violated. The intent of this is to detect the potential for deadlocks due to lock order violations; it’s worth observing that Witness is actually slightly conservative, and so it’s possible to get false positives. In the event that Witness is accurately reporting a lock order problem, it’s basically saying “If you were unlucky, a deadlock would have happened here”. There are a couple of “well known” false positives, which we need to do a better job of documenting to prevent spurious reports. The non-well-known ones typically correspond to bugs in newly added locking, as lock order reversals usually get fixed pretty quickly because Witness is busy generating warnings :-).”

Today Joe Marcus Clarke [marcus@, a member of portmgr@] has announced that the port freeze for FreeBSD 4.10-RELEASE has been released. Now FreeBSD ports has been tagged as RELEASE_4_10_0.

刚刚揭露的那个TCP漏洞OpenBSD在1999年就修正了……和FreeBSD现在用的方法类似，只是更严厉一些。折服了……