provided by Martin Husemann on:
http://mail-index.netbsd.org/tech-kern/2007/11/16/0006.html
This fixes the uninitialized lock when calling bio_register() on mfi(4)
and other drivers, caught by LOCKDEBUG.
Ok'ed by Andrew Doran <ad@netbsd.org>
- initialize inode generation numbers with random numbers for NFS
like newfs(8) as man page said
XXX: sys/ufs/ext2fs/ext2fs_alloc.c:ext2fs_valloc() seems to override
these generated numbers.
support shared libraries). Reported by he@.
This was an attempt to test the exact same id binary in the system but
using fake library calls to provide fictitious but stable user/group
entries. Instead, build a helper id binary linked against our fake
functions. This is what we already do in, e.g. the tests for util/df.
cmd1 && cmd2 && cmd3
| | |
v v v
target:
cmd1
cmd2
cmd3
This makes the script (cmd1 && cmd2 && cmd3) slightly easier to debug. No
functional change expected.
With this we no longer need machine-dependent code in framebuffer console
drivers and we can use genfb at pci for otherwise unsupported graphics
chips as long as there's firmware support.
Revert Max LBA calculation when returning the Maximum LBA from the target
to the iinitiator, following an email conversation with Jonathan Kollasch,
who points out a number of things:
+ the NetBSD scsipi driver reads the value returned by the drive and adds
one to it, so that standard SCSI drives return the 0-based Max LBA in a
READ CAPACITY command.
+ it is up to the initiator to add 1 to the Max LBA to find out the size
of the LUN (Jonathan verified this by using the UNH iSCSI initiator on
to a NetBSD target)
+ an analogous change to the NetBSD initiator (revision 1.4 of
iscsifs.c) is needed.
and we need to add 1 to it to get the size of the LUN.
Revert Max LBA calculation when returning the Maximum LBA from the target
to the iinitiator, following an email conversation with Jonathan Kollasch,
who points out a number of things:
+ the NetBSD scsipi driver reads the value returned by the drive and adds
one to it, so that standard SCSI drives return the 0-based Max LBA in a
READ CAPACITY command.
+ it is up to the initiator to add 1 to the Max LBA to find out the size
of the LUN (Jonathan verified this by using the UNH iSCSI initiator on
to a NetBSD target)
+ an analogous change to the NetBSD target (revision 1.34 of
disk.c) is needed.
