On Mon, 2004-01-12 at 11:32, Wes Peters wrote:
> A few years ago Perforce was working on a write-through cache so you could
> have a local duplicate of the server environment, but I haven't seen that
> work come out of the company. That would've rocked for our development
> model.
They release
On Wed, 2003-06-11 at 06:22, Terry Lambert wrote:
> Someone should port the network debugging from Darwin using
> the tiny IP stack from NetBSD.
Well, there's this:
http://ipgdb.sourceforge.net/
> IPGDB is a collection of extensions to GDB and FreeBSD-4.3
> to allow two-machine kernel debugging
On Mon, 2003-02-03 at 18:06, Terry Lambert wrote:
> But if that's the argument for removing it, then it's probably
> time to remove the ability to use non-DMA IDE drives from the
> ATA driver, and kill all the ethernet drivers that have alignment
> requirements for their DMA engines, making m_pullu
On Sun, 2002-02-10 at 00:55, Kip Macy wrote:
> A working version of gdb 5.1 with full user thread support (fixes for bin/24066,
> gnu/33182, and as yet unfiled seg fault when resuming from a non-running
> thread) is available at:
> http://www.eventdriven.org/freebsd.html
Excellent!
Thanks for do
understand the anti-perl reactions some people
have. Maybe it's not your favorite language, but it's not going
away. It's time to accept that.
--nat
--
nat lanza --- there are no whole truths;
[EMAIL PROTECTED] --
vark solution are right --
directory hashing is a well-known solution to this problem. It isn't
a hack at all. No matter what method you use for storing directories,
larger directories are going to be slower to use than smaller ones,
and hashing filenames fixes that.
--nat
--
re's been some discussion of having ATA
become part of CAM, but I don't remember what the result of it
was. You might want to check the list archives.
--nat
--
nat lanza -- there are no whole truths;
[EMAIL PROTECTED] -
l kernel source editing tools, I'll echo the
emacs+etags suggestion.
--nat
--
nat lanza - research programmer, parallel data lab, cmu scs
[EMAIL PROTECTED] http://www.cs.cmu.edu/~magus/
there are no whole truths; all truths are ha
you might be interested in.
--nat
--
nat lanza - research programmer, parallel data lab, cmu scs
[EMAIL PROTECTED] http://www.cs.cmu.edu/~magus/
there are no whole truths; all truths are half-truths -- alfred north whitehead
To Unsubscribe:
versions of 2.1. Nothing
documented the current kernel, and because of the drastic changes
between versions, much of the documentation for 2.0 was misleading.
--nat
--
nat lanza - research programmer, parallel data lab, cmu scs
[EMAIL PROTECTED] -
and produce a patch.
If you want to take a look, my version is running at
http://lxr.pdl.cs.cmu.edu/freebsd/source/.
--nat
--
nat lanza - research programmer, parallel data lab, cmu scs
[EMAIL PROTECTED] http://www.cs.cmu.edu/~magus/
there
nix). You need the second one (which is SRM if I recall
> correctly, I keep mixing them up) for FreeBSD/OpenBSD and friends too.
You can also boot Linux from SRM, but it's a pain in the ass to
set it up. It's worth it, though, 'cause then you get a handy se
T_SCSI_IO.
> If you're writing a generic ramdisk, this is a really masochistic way to
> go about doing it. 8)
It's really a mix of an exercise in writing a CAM HBA driver and a
first step towards a SCSI-over-IP driver. Also, a SCSI ramdisk can be
handy for some of the bench
ly have real devices or a real IO bus.
Anyone feel like explaining this?
Thanks.
--nat
--
nat lanza - research programmer, parallel data lab, cmu scs
[EMAIL PROTECTED] http://www.cs.cmu.edu/~magus/
there are no whole truths; all truths are h
14 matches
Mail list logo
