Hi all,
I'd like some help examining LWP backtraces on a running NetBSD system
in a qemu-kvm virtual machine.
I've successfully done the following to examine LWP backtraces in crash
dumps:
$ gdb /path/to/netbsd.gdb
(gdb) target kvm /path/to/netbsd.0.core
(gdb) dir
Hello,
On my NetBSD 5.1.2/i386 system, there are man pages for ppbus. But from
grep'ing the sources, it seems the support is only included (optionally)
for acorn32. There is a conditional in
sys/arch/i386/pnpbios/files.pnpbios for !ppbus and that's all.
Is there no support except in acorn32?
I'm looking at possibly using iSCSI at work, and would prefer to use
NetBSD for it - the machine is currently 4.0.1; a version change might
fly if necessary for this. I found iscsi-target(8) and related
manpages, but I have been unable to find any support for the other
side, for a NetBSD machine
Hello. I'm pretty sure iscsi-initiator support is only provided for
NetBSD through the netbsd-iscsi-initiator package in the net category of
the pkgsrc tree. Because it relies on the fuse interface to get its work
done, I am also pretty sure the earliest version of NetBSD on which it
[iSCSI initiator support?]
I'm pretty sure iscsi-initiator support is only provided for NetBSD
through the netbsd-iscsi-initiator package in the net category of the
pkgsrc tree. Because it relies on the fuse interface to get its work
done, I am also pretty sure the earliest version of
On Feb 28, 2013, at 0:09, Brian Buhrow buh...@nfbcal.org wrote:
Hello. I'm pretty sure iscsi-initiator support is only provided for
NetBSD through the netbsd-iscsi-initiator package in the net category of
the pkgsrc tree. Because it relies on the fuse interface to get its work
done,
I'm looking at writing driver code for 5.2. A few manpages (notably
selinit(9) and other aliases for the same page) speak of non-MPSAFE
drivers, but I have been unable to find what a driver has to do in
order to be MPSAFE - nor for that matter how it is that drivers are or
aren't marked as
Hello. The way to write a driver to be mpsafe is to use the mutex(9)
calls for locking exclusively. Then, when you do things like create
threads, setup interupt handlers or start callout timers, you pass an
MPSAFE flags argument to the calls themselves. I did this for the zaptel
drivers
On Thu, Feb 28, 2013 at 12:40:27AM -0500, Mouse wrote:
I'm looking at writing driver code for 5.2. A few manpages (notably
selinit(9) and other aliases for the same page) speak of non-MPSAFE
drivers, but I have been unable to find what a driver has to do in
order to be MPSAFE - nor for
On Thu, Feb 28, 2013 at 01:27:57AM -0500, Mouse wrote:
[iSCSI initiator support?]
I'm pretty sure iscsi-initiator support is only provided for NetBSD
through the netbsd-iscsi-initiator package in the net category of the
pkgsrc tree. Because it relies on the fuse interface to get its
10 matches
Mail list logo
