Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Oct 1995 07:12:29 +0200
From:      Heikki Suonsivu <hsu@cs.hut.fi>
To:        "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc:        stable@freebsd.org
Subject:   2.1.0-951020-SNAP - 2.1 *Release Candidate*
Message-ID:  <199510220512.HAA11965@shadows.cs.hut.fi>
In-Reply-To: "Jordan K. Hubbard"'s message of 21 Oct 1995 17:02:36 %2B0200

next in thread | raw e-mail | index | archive | help

   The 2.1 release candidate is now available for testing.  Modulo
   whatever problems all of you find between now and the final build,
   this will be what you find in 2.1!

   There are a few small things known-missing or broken in this snapshot,
   and those things ARE scheduled to be added before 2.1 is built.
   However, it may still be instructive to list them here so that
   snapshot installers don't stumble over them:

   o The WEB configuration is unimplemented.

   o The package installer may or may not do the right thing with chained
     adds.  I haven't had the chance to adequately test this, given my limited
     testing hardware (I'm using a laptop with an 120MB hard disk!).

   o Some instrumentation is probably missing from the configuration file
     mechanism.

   o The HTML documentation reader menu may need some work.

   o The commercial distribution is still the 2.0.5 version - this will 
     be updated before the final 2.1 release.

   o The bindist now includes all documentation from /usr/share/doc.  If this
     ends up blowing up some of the minimally configured systems, we may
     need to make an optional `doc' distribution sooner than planned.

Is the slirp panic bug already catched up or still there?  I have seen it
PR'd at least two times in addition to my case, and we get regular panics
almost every day on this.  I can provide dumps & kernels with full symbols
if someone is interested, it always panics in fchmod and it is quite
consistent.  v_mount is NULL, I don't know what circumstances this happens
(it is a pipe or something which isn't on any file system, maybe?).  Could
just returning error from the fchmod system call when v_mount is NULL be
enough of a workaround?

The code seems to be similar in several other system calls, but I know too
little about the kernel to know whether any of these could exhibit the same
problem, if suitably misused.

The PR is kern/782.  ftp://clinet.fi/pub/FreeBSD/crashdumps/*.29.gz is one
example (I have more of them).

slirp is quite popular slip/ppp emulation kludge, unfortunately large
number of our users use it.

-- 
Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND,
hsu@cs.hut.fi  home +358-0-8031121 work -4513377 fax -4555276  riippu SN



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510220512.HAA11965>