Write-Ahead File System (WAFS) v1.0 Release Notice.
The WAFS source code is now available for download at
http://www.eecs.harvard.edu/~stein/wafs/
WAFS is a simple file system designed to act as a logging
service for kernel subsystems. Reads and writes are keyed
by log-sequence number (LSN). Al
I am seeing a buffer in biodone() with block number 196656 (in
the bp->b_blkno field). This is a buffer containing data from
the raw, character device (bp->b_vp->v_type == VCHR).
(kgdb) p bp->b_lblkno
$36 = 196656
(kgdb) p bp->b_blkno
$37 = 196656
(kgdb) p bp->b_pblkno
$38 = 196719
The bp->b_
subscribe freebsd-hackers
-Chris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
That is only if the write is to a file within a partition mounted
as an FFS file system. vn_write() contains the VOP_WRITE switch, which
will switch to the write implementation based on the vnode type. VOP_WRITE
calls through the function hanging off the vnode in the vnode op
vector at the offset
n it lands on my system. Should make
great bedtime reading.
thanks
-Chris
On Mon, 18 Sep 2000, Kris Kennaway wrote:
> On Mon, 18 Sep 2000, Christopher Stein wrote:
>
> > I would like to do this via cvsup and `make world'.
> > My understanding is that `make world&#x
Hello, I don't wish to jump all the way forward to -CURRENT, but would
like to bring my 3.3 system up to 4.1 (would like to go beyond 4.0
for kqueue() and fxp PEX support).
I would like to do this via cvsup and `make world'.
My understanding is that `make world' is just buildworld followed
by i
Hi, I discovered the source of my problem and solved it. For those
interested, here is an explanation:
The flags of the serial I/O device to be used for remote
debugging needs to be changed in the config file. I plugged
a null modem cable across the two ports labeled 1 (the other one
labeled 2)
/dev/cuaa1 turned out to be the culprit. I tested this
by `echo "hello" > /dev/cuaa1` on the debugger and
`cat /dev/cuaa1` on the debuggee. The hello makes it across.
Now I'm having some "packet error" problems with kgdb.
On the debuggee I ctrl-alt-esc into ddb and do:
db> gdb
db> step
>Fro
.. does anyone know if this exists? It would
speed up the panic-edit-compile-boot-copy-boot kernel hacking
cycle by transforming it to panic-edit-compile-netboot.
thnx
-Chris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Hello,
I have been trying to connect to a remote gdb debug session via a serial
port (null modem cable) and can't seem to get the device right. I've tried
the devices:
/dev/ttyd*
/dev/cuaa0 (as suggested by the freebsd handbook).
hhmmm.. any suggestions? /dev/ttyd1 worked for a 3.3/4.0-pre ins
On Sun, 21 Nov 1999, Kris Kennaway wrote:
> On Sun, 21 Nov 1999, Christopher Stein wrote:
>
> > Dennis has a good point.
>
> Dennis has no point unless he provides some numbers to quantify his
> claim.
His point was not a claim about performance, rather he was bringing
Dennis has a good point.
> for slower? I've ran FreeBSD for years and now I run a combo of -STABLE
> and -CURRENT and you know what? It's all good! My hardware is the bottle
> neck and its just as fast as 2.x was.
Do you have some numbers to back this up? (unfortunately "It's all good!"
doesn'
Could someone please tell me why bdevsw has disappeared
from FreeBSD-current and what I should use for the block
device switch.
Thanks
Chris Stein
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
13 matches
Mail list logo
