Result for 32BFEAC1FCB49770129005307B081F961DF88925

Query result

Key Value
FileName./etc/dbus-1/system.d/tcmu-runner.conf
FileSize486
MD5A99B7442ACC6122BFE6883631760092C
SHA-132BFEAC1FCB49770129005307B081F961DF88925
SHA-25610340E4DFE0862CB32AD085ED49B1CF639968085211DB192A98646EC44A2A66C
SSDEEP12:TM14kWa03MDLnCLSS46NfRT3au3TFrSaReiuTrn:GWaVHSffjFew5Qr
TLSHT1D2F05943D9AD68F752412702985349B357A03BED74CD140423A6DDE452D0B19D10A690
hashlookup:parent-total62
hashlookup:trust100

Network graph view

Parents (Total: 62)

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

Key Value
FileSize95216
MD5164607AB4382775A153E1D63ABC3EE8A
PackageDescriptionDaemon that handles the userspace side of the LIO TCM-User backstore LIO 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 one want to get fancier with the capabilities of the device one is 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 one would 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. . This is the daemon package
PackageMaintainerFreexian Packaging Team <team+freexian@tracker.debian.org>
PackageNametcmu-runner
PackageSectionadmin
PackageVersion1.5.2-2~bpo10+1
SHA-10061B42BA13A92E99F3BFCA8C58A18D28B117333
SHA-256A5E46A33DF322736270D15114D752273E18412CD657F13A60EBCEDC556D24486
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
FileSize101068
MD5E25454E9FB8CA29804E328C2EE4420D9
PackageDescriptionDaemon that handles the userspace side of the LIO TCM-User backstore LIO 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 one want to get fancier with the capabilities of the device one is 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 one would 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. . This is the daemon package
PackageMaintainerFreexian Packaging Team <team+freexian@tracker.debian.org>
PackageNametcmu-runner
PackageSectionadmin
PackageVersion1.5.2-6
SHA-100BCBE4C114835A461FDFF63F4E898EADE8FA843
SHA-256378D2ABC554F84F84F289D25CCAC5CBE53D9008D5F18DEDCAA24EA16AD4E05F5
Key Value
FileSize89488
MD56AEAFC2DE2D171E9A8D785FF120BF158
PackageDescriptionDaemon that handles the userspace side of the LIO TCM-User backstore LIO 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 one want to get fancier with the capabilities of the device one is 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 one would 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. . This is the daemon package
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNametcmu-runner
PackageSectionadmin
PackageVersion1.5.2-5ubuntu0.20.04.1
SHA-104A05CE678FC75E87C00CCBC1C154DCB6AE732C0
SHA-256E21359D504BC9FDE7A4AA1C91303A94912813FC21F5DC80AD4AFEFC937A873BF
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
FileSize98036
MD5B09954B66A91542A1F8E1C829AA64C16
PackageDescriptionDaemon that handles the userspace side of the LIO TCM-User backstore LIO 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 one want to get fancier with the capabilities of the device one is 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 one would 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. . This is the daemon package
PackageMaintainerDebian QA Group <packages@qa.debian.org>
PackageNametcmu-runner
PackageSectionadmin
PackageVersion1.5.4-2
SHA-113D69190D0896B19C8E19270FE840B1089E1D764
SHA-256D29BF1860EBD1E160351A26F828DD503681ABE40398FAFD1B13928536E37E316
Key Value
FileSize82780
MD56482D98A731B81B1DD6A0D425BE21541
PackageDescriptionDaemon that handles the userspace side of the LIO TCM-User backstore LIO 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 one want to get fancier with the capabilities of the device one is 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 one would 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. . This is the daemon package
PackageMaintainerFreexian Packaging Team <team+freexian@tracker.debian.org>
PackageNametcmu-runner
PackageSectionadmin
PackageVersion1.5.2-2~bpo10+1
SHA-1142C69D596378D3617B80F68DDCE670B0C1C4626
SHA-256C2A62E2E4D0DC1EDEF8F2A2297E88D7ABBF9552484041EE571885054415A3B49
Key Value
FileSize90616
MD577A662614F6243A50D4BA0D1CE665A14
PackageDescriptionDaemon that handles the userspace side of the LIO TCM-User backstore LIO 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 one want to get fancier with the capabilities of the device one is 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 one would 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. . This is the daemon package
PackageMaintainerFreexian Packaging Team <team+freexian@tracker.debian.org>
PackageNametcmu-runner
PackageSectionadmin
PackageVersion1.5.2-6
SHA-11588615028455C3AD1695809E7EB310A70791832
SHA-256E0FB7E920D220D7F701D98A635A1A4A4B7BDFF9B402F99D6BF3CF938613C3A8A
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