On Tue, 8 Jan 2002, Michael Reifenberger wrote:
Hi,
the following script panics my system when executed twice:
(uncomment the dd lines for the first time or do it manually)
##
#!bin/sh
block_size=512
blocks=$((120 * 1024 * 1024 / $block_size))
heads=16
sectors=63
In message [EMAIL PROTECTED], Bruce Evans writes:
This seems to be just another null pointer panic caused by the dk macros
creating half-baked devices with null devswitches. I sent the following
quick fixes for this to the devfs maintainer a couple of weeks ago. They
also fix the non-creation
On Wed, 9 Jan 2002, Bruce Evans wrote:
...
This seems to be just another null pointer panic caused by the dk macros
creating half-baked devices with null devswitches. I sent the following
quick fixes for this to the devfs maintainer a couple of weeks ago. They
also fix the non-creation of
I am going to commit my work for quite a few months on locking a pgrp
and session to -current in two weeks. The patch is at:
http://people.FreeBSD.org/~tanimura/patches/pgrp.diff.gz
This patch has been running quite well on my box with kern.giant.proc
set to zero for more than a month. Could
Hi,
attached are three backtraces (sorry, no matching kernel.debug for them)
of some panics of today.
The first was during an copy operation from CDROM to /tmp (md disk)
The next where during background fsck-ing after the first dump...
Bye!
Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis,
What are the plans about replacing XFree86 3.3.6 with XFree86 4?
According to plan, FreeBSD 4.6-RELEASE will have XFree86 4, so sometime
after this month and before the next release.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
CLICK BELOW for Naughty GAY SEXUAL ACTS!! Pure Hardcore Action! Hot Male Celebs
EXPOSED!!!
http://www.xpays.com/clients/08862/gay/promo.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Wed, 9 Jan 2002, Michael Reifenberger wrote:
On Wed, 9 Jan 2002, Bruce Evans wrote:
...
This seems to be just another null pointer panic caused by the dk macros
creating half-baked devices with null devswitches. I sent the following
quick fixes for this to the devfs maintainer a
