The bio(4) pseudo-device driver and the bioctl(8) utility implement a generic RAID volume management interface in OpenBSD and NetBSD.[1][2] The idea behind this software is similar to ifconfig, where a single utility from the operating system can be used to control any RAID controller using a generic interface, instead of having to rely on many proprietary and custom RAID management utilities specific for each given hardware RAID manufacturer.[3][4][5][6][7] Features include monitoring of the health status of the arrays, controlling identification through blinking the LEDs and managing of sound alarms, and specifying hot spare disks. Additionally, the softraid configuration in OpenBSD is delegated to bioctl as well; whereas the initial creation of volumes and configuration of hardware RAID is left to card BIOS as non-essential after the operating system has already been booted.[4] Interfacing between the kernel and userland is performed through the ioctl system call through the /dev/bio pseudo-device.
^Cite error: The named reference bio.4 was invoked but never defined (see the help page).
^Cite error: The named reference bioctl was invoked but never defined (see the help page).
^Cite error: The named reference onlamp-37 was invoked but never defined (see the help page).
^ abCite error: The named reference theo-misc-38 was invoked but never defined (see the help page).
^Cite error: The named reference onlamp-38 was invoked but never defined (see the help page).
^Cite error: The named reference onlamp-40 was invoked but never defined (see the help page).
^Cite error: The named reference opencon06 was invoked but never defined (see the help page).
The bio(4) pseudo-device driver and the bioctl(8) utility implement a generic RAID volume management interface in OpenBSD and NetBSD. The idea behind this...
approach taken by OpenBSD in 2005 with its bio(4) pseudo-device driver and the bioctl utility, which provide volume status, and allow LED/alarm/hotspare control...
The bio(4) interface for vendor-agnostic RAID volume management through bioctl has been available in NetBSD since 2007. The WAPBL journaling filesystem...
with integrated volume management NetBSD § 5.0 (2009) bioctl arcmsr No No Yes Yes Yes Yes bioctl on NetBSD can be used for both maintenance and initialisation...
OpenBSD and NetBSD, ioctl is used by the bio(4) pseudo-device driver and the bioctl utility to implement RAID volume management in a unified vendor-agnostic...
Many open source projects started as components of OpenBSD, including: bioctl, a generic RAID management interface similar to ifconfig CARP, a free alternative...
state of affairs prompted OpenBSD to create and popularise its bio(4), bioctl and sensor drive concepts as an alternative solution for RAID monitoring...
can perform data scrubbing and preventive maintenance. In OpenBSD, the bioctl(8) utility allows the system administrator to control these patrol reads...
provides ioctl access to devices otherwise not found as /dev nodes, used by bioctl to implement RAID management in OpenBSD and NetBSD. /dev/sysmon – used by...
approach taken by OpenBSD in 2005 with its bio(4) pseudo-device and the bioctl utility, which provide volume status, and allow LED/alarm/hotspare control...
the same time when bio(4) and bioctl were ported from OpenBSD to NetBSD.: §7.1 Free and open-source software portal bioctl hw.sensors lm_sensors SpeedFan...
Global Information