Revision as of 13:12, 27 March 2023 edit Bumm13 (talk \| contribs) Administrators 79,719 edits m →Policy by project: punctuation/spelling and formatting fix ← Previous edit		Revision as of 13:15, 27 March 2023 edit undo Bumm13 (talk \| contribs) Administrators 79,719 edits m →Use via wrappers: capitalization/spelling fix and formatting fixes Next edit →
Line 91: == Use via wrappers == A [[Driver wrapper\|wrapper]] is software which allows one operating system to use a binary proprietary device driver written for another operating system. Examples of wrappers are [[~~NdisWrapper~~NDISwrapper]] for [[Linux]], and [[Project Evil]] for [[FreeBSD]] and [[NetBSD]]. These wrappers allow these operating systems to use network drivers written for [[Microsoft Windows]] by implementing [[Microsoft]]'s [[Network Driver Interface Specification\|NDIS]] [[~~Application programming interface\|~~API]]. Another example is providing compatibility layers so that foreign utilities could be used to service the hardware. Examples include some [[Disk array controller\|RAID controller]] drivers in [[FreeBSD]], where the [[system administrator]] would have to enable [[FreeBSD#OS compatibility layers\|Linux compatibility layer in FreeBSD]] and independently procure Linux-specific binary blobs directly from the hardware manufacturer in order to monitor and service the hardware.<ref name=f-aac>{{cite web \|url= http://bxr.su/f/share/man/man4/aac.4 \|title= aac(4) — Adaptec AdvancedRAID Controller driver Line 119: \|quote= drivers designed for binary only Linux RAID management tools }}</ref> Circa 2005, this state of affairs prompted [[OpenBSD]] to create and popularise its [[bioctl\|bio(4)]], [[bioctl]] and [[sensor drive]] concepts as an alternative solution for [[RAID]] monitoring,<ref name=theo-misc-38>{{cite mailing list \|url= //marc.info/?l=openbsd-misc&m=112630095818062 \|author= Theo de Raadt

Binary blob: Difference between revisions