Result for 56BE263A0B2E15B0DDFEEAF3CF10045C981BE395

Query result

Key Value
FileName./usr/share/licenses/tcmu-runner/LICENSE.LGPLv2.1
FileSize26525
MD5A7EF827A98FA240D37910AC4E8CE3F53
SHA-156BE263A0B2E15B0DDFEEAF3CF10045C981BE395
SHA-25687540DB2F3B8DEBC29C2871DB039998D77B4359D9000069FD3949920B73676CA
SSDEEP384:LE56OuAbn/0URef6wFDVxnFw7xqsvLt+z/k8E9HinIhFkspWM9bc7ups08ZuQW:LE5trzernFML1ReSWmc7GsNZuQW
TLSHT183C2953EB70113B206C206905A4FA4DFE32BD07932675964749DC15D23AB93543FBBEA
hashlookup:parent-total24
hashlookup:trust100

Network graph view

Parents (Total: 24)

The searched file hash is included in 24 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5F87C624414155D9F62FF73507F3F9051
PackageArchx86_64
PackageDescriptionA daemon that handles the complexity of the LIO kernel target's userspace passthrough interface (TCMU). It presents a C plugin API for extension modules that handle SCSI requests in ways not possible or suitable to be handled by LIO's in-kernel backstores.
PackageMaintainerFedora Project
PackageNametcmu-runner
PackageRelease2.fc32
PackageVersion1.5.2
SHA-100BA78A3D89B56AD4BFBF1450013E7F9F552DF5E
SHA-256026763BDA4B85207C2426879615AF560D0D7F200A64F74CE82BE40BBED32F960
Key Value
MD5CA8F72009E08C00F31AE3DD18F3E4C5A
PackageArchx86_64
PackageDescriptionLIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like.
PackageMaintainerhttps://www.suse.com/
PackageNametcmu-runner
PackageRelease150400.1.5
PackageVersion1.5.4
SHA-1128B028D6DF130F4CE761BDA601B45CD7DFCCF56
SHA-25616AE496AE3BAE99572A6935370AF3E6DADD7490E3E8168EF0A85E9B2A44440E0
Key Value
MD54969E8C85B7CB3C31F831E7057D28B68
PackageArchx86_64
PackageDescriptionLIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like.
PackageNametcmu-runner
PackageRelease39.18
PackageVersion1.5.4
SHA-117AE41F0F53C8ADA6E218E0B46702A4E7E31E58D
SHA-2562DE1A3868BB579548A6D556800C64ED0490FF3D4C3218CBC9A3CF486F98D489A
Key Value
MD5EFA4A3664CC2E2DC136BF84042A55FA3
PackageArchaarch64
PackageDescriptionA daemon that handles the complexity of the LIO kernel target's userspace passthrough interface (TCMU). It presents a C plugin API for extension modules that handle SCSI requests in ways not possible or suitable to be handled by LIO's in-kernel backstores.
PackageMaintainerFedora Project
PackageNametcmu-runner
PackageRelease8.fc34
PackageVersion1.5.2
SHA-11A9EFDDA9F5630B6A3DEB06C41B4755E4B12F2BC
SHA-256010463FFAD119A3C2E477511A598FDF9C0A671383A74BFBE110630B91EA1A5BC
Key Value
MD5528F6D208F83D38423DB820AED325E4F
PackageArchriscv64
PackageDescriptionLIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like.
PackageNametcmu-runner
PackageRelease39.18
PackageVersion1.5.4
SHA-11BB155F321776B355AA5563697FC13F96DA58955
SHA-256451517BE931D03BAF4DF4F5893ACBF54E81302827F1A621594634F589A2148AF
Key Value
MD5D3E2170F8A7F91C2452B94FD27874C1E
PackageArchi586
PackageDescriptionLIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like.
PackageMaintainerhttps://bugs.opensuse.org
PackageNametcmu-runner
PackageRelease1.2
PackageVersion1.5.4
SHA-11EE163138F2BC445C6CC5E587D2D10D934C07D73
SHA-256F413EE1EF046D65DB9332058A760B60497430F590590D12668C7CED02B9E416B
Key Value
MD59CF801849A9954F553CCB220D65BE805
PackageArchs390x
PackageDescriptionLIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like.
PackageMaintainerhttps://www.suse.com/
PackageNametcmu-runner
PackageRelease150400.1.5
PackageVersion1.5.4
SHA-124D50E5B09B937F2BC0B57468B86D78CC1A01451
SHA-2567137B8C93D0956F0A84B92ED6B7969BCA296656801D9CB592E06AF31E3727474
Key Value
MD5E90C72B89EA0FB65AA8E18C33D722B49
PackageArchaarch64
PackageDescriptionA daemon that handles the complexity of the LIO kernel target's userspace passthrough interface (TCMU). It presents a C plugin API for extension modules that handle SCSI requests in ways not possible or suitable to be handled by LIO's in-kernel backstores.
PackageMaintainerFedora Project
PackageNametcmu-runner
PackageRelease2.fc32
PackageVersion1.5.2
SHA-136B680A37957996E42A9A3E922505BB94EF8A1C7
SHA-2569A93644C2597A225E6D2E9EE622945040B3DFFCF8D7A7CC8055AAEB5EDA03274
Key Value
MD5CF55A6210FADCCFBA71FE3755CD45E76
PackageArchs390x
PackageDescriptionLIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like.
PackageNametcmu-runner
PackageRelease39.18
PackageVersion1.5.4
SHA-13DCDB2E53F50E6D7919B25C5F7702727EA5CB96F
SHA-256986327C840971DDAF55690CA602FAF4789FB1784BC03F9F6C93CEA47DC3F4F71
Key Value
MD5647F15344273245DC383C338A2AE80E6
PackageArcharmv7hl
PackageDescriptionLIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like.
PackageNametcmu-runner
PackageRelease39.18
PackageVersion1.5.4
SHA-14FB6260FED79A4D4D100271AFB2005FFE92961F0
SHA-256AEB58278F13DA10B97953C15806ED5D86A3BA68A33C7240CBD59ACF75138DEF7