About: LinuxCOBD

Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: LinuxCOBD Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

To access a virtual device imported into colinux, you must first have setup an appropriate block device in your /dev file system. By convention, these devices are named /dev/cobdN, where N in the index number of an element in the XML configuration file. Incidently, "cobd" stands for "Colinux Block Device." The block device nodes should be existing, if you use a Linux image provided by the coLinux community. If you do not yet have such devices on your system, you'll need to create them. This is done with the mknod command (running as root): Alternatively, you can do them all at once like this:

Attributes	Values
rdfs:label	LinuxCOBD
rdfs:comment	To access a virtual device imported into colinux, you must first have setup an appropriate block device in your /dev file system. By convention, these devices are named /dev/cobdN, where N in the index number of an element in the XML configuration file. Incidently, "cobd" stands for "Colinux Block Device." The block device nodes should be existing, if you use a Linux image provided by the coLinux community. If you do not yet have such devices on your system, you'll need to create them. This is done with the mknod command (running as root): Alternatively, you can do them all at once like this:
dcterms:subject	Configuration
abstract	To access a virtual device imported into colinux, you must first have setup an appropriate block device in your /dev file system. By convention, these devices are named /dev/cobdN, where N in the index number of an element in the XML configuration file. Incidently, "cobd" stands for "Colinux Block Device." The block device nodes should be existing, if you use a Linux image provided by the coLinux community. If you do not yet have such devices on your system, you'll need to create them. This is done with the mknod command (running as root): root$ mknod /dev/cobd0 b 117 0 root$ mknod /dev/cobd1 b 117 1 root$ mknod /dev/cobd2 b 117 2 ... root$ mknod /dev/cobd7 b 117 7 Alternatively, you can do them all at once like this: root$ for i in 0 1 2 3 4 5 6 7; do mknod /dev/cobd$i b 117 $i; done Once an appropriate block device is defined in /dev, you can now access the corresponding device number which is declared in your XML configuration file. See also: * Windows Device Paths for 2.6 kernel users, you may want to replace /dev/cobd0 by /dev/cobd/0 and so on. in fact, you can create both set of devices, it wont hurt. MassTranslated on Sun Apr 23 17:36:25 UTC 2006

OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software