Ustimenko Semen writes:
> Is this a good tactic to write working VOP_BMAP and
> VOP_STRATEGY handlers, and implement VOP_READ and VOP_WRITE
> via bread and bwrite of own vnodes?
Considering that that's how the primary filesystem layers (ufs/ffs) do
it, it should be fair to assume that it's at l
Kenneth Wayne Culver wrote:
>
> > I was just wondering if anyone has gotten a soundcard based on the Vortex
> > chip to work under FreeBSD. I know that OSS (www.opensound.com) supports
> > it, but I don't want to use OSS because of the problems with it. If nobody
> > has gotten that card to work,
> I was just wondering if anyone has gotten a soundcard based on the Vortex
> chip to work under FreeBSD. I know that OSS (www.opensound.com) supports
> it, but I don't want to use OSS because of the problems with it. If nobody
> has gotten that card to work, then can someone point me in the right
USB stopped working as of the recent cdevsw cleanup. This fixes it.
Index: usb.c
===
RCS file: /usr/cvs/freebsd/src/sys/dev/usb/usb.c,v
retrieving revision 1.12
diff -u -r1.12 usb.c
--- usb.c 1999/05/30 16:51:51 1.12
+++ us
> The basic problem is in the phrase "a timestamp of the last time
> they updated from freefall." There is no single timestamp that is
> representative of an update. Suppose I start an update at 15:00:00
> UTC, and it finishes at 15:10:00. Every file updated came from
> a snapshot at some point
Hi FS Guru!
Is this a good tactic to write working VOP_BMAP and
VOP_STRATEGY handlers, and implement VOP_READ and VOP_WRITE
via bread and bwrite of own vnodes?
Bye.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
John Polstra wrote:
> Kris Kennaway wrote:
>
> > The solution I see here is for the cvsup mirrors to maintain
> > a timestamp of the last time they updated from freefall (for
> > multi-tiered mirrors, this value should be passed down the chain so
> > each of them knows the age of their files relat
Several questions.
First, what's wrong with stamping the files in a mirror with the timestamp
it has on the master?
Second, how much work would it be to add, say, md5 checksums to CVS.
Third, isn't the version number useful for something?
Just some ramblings...
H
To Unsubscribe: send mail
Kris Kennaway wrote:
> The solution I see here is for the cvsup mirrors to maintain
> a timestamp of the last time they updated from freefall (for
> multi-tiered mirrors, this value should be passed down the chain so
> each of them knows the age of their files relative to the master
> server)
I'v
:On Mon, 31 May 1999, Bruce Evans wrote:
:
:> This isn't solved. It was less serious before rev.1.196 of vfs_bio.c
:> when B_ERROR buffers were discarded insead of re-dirtied in the above
:> code fragment. See also PR 11697, and about 20 PRs reporting problems
:> with i/o errors and EOF "errors"
True, I'm waiting for Hellmut to review and/or commit the patches I've
sent to him.
If you want to fix it locally you need to:
initialize d_maj in cdevsw
s/nullreset/noreset/
remove first and last args in cdevsw_add() calls.
In message , Christian Carstensen writes:
>
>hi
hi there,
it seems as isdn drivers have been broken with current cdevsw registration
changes. The current kernel does not link with i4b anymore.
--
christian
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Mon, 31 May 1999, Bruce Evans wrote:
> This isn't solved. It was less serious before rev.1.196 of vfs_bio.c
> when B_ERROR buffers were discarded insead of re-dirtied in the above
> code fragment. See also PR 11697, and about 20 PRs reporting problems
> with i/o errors and EOF "errors" (ENO
13 matches
Mail list logo