Re: cvs commit: src/sys/bus/cam cam_xpt.c src/sys/bus/cam/scsi scsi_cd.c scsi_ch.c scsi_da.c scsi_pass.c scsi_pt.c scsi_sa.c scsi_ses.c scsi_target.c src/sys/bus/firewire firewirereg.h fwdev.c fwmem.c fwmem.h fwohci.c src/sys/bus/iicbus iic.c ...

["Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>]

Matthew Dillon wrote:
>   Log:
>   MASSIVE reorganization of the device operations vector.  Change cdevsw
>   to dev_ops.  dev_ops is a syslink-compatible operations vector structure
>   similar to the vop_ops structure used by vnodes.

does this mean that we're turning away from the message based communication back to a monolithic execution, or is syslink just a different, better (address space agnostic) messaging system, which can be used within the kernel as well?

i just got the feeling that with this is will be really easy to forward devices via network to other boxes, like the sound card or the usb stick from a thin diskless client to the application server...  right?

good work!
 simon

--
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \

Attachment: signature.asc
Description: OpenPGP digital signature