How to Install and Uninstall libtcmu2 Package on Kali Linux
Last updated: December 23,2024
1. Install "libtcmu2" package
Please follow the steps below to install libtcmu2 on Kali Linux
$
sudo apt update
Copied
$
sudo apt install
libtcmu2
Copied
2. Uninstall "libtcmu2" package
Here is a brief guide to show you how to uninstall libtcmu2 on Kali Linux:
$
sudo apt remove
libtcmu2
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libtcmu2 package on Kali Linux
Package: libtcmu2
Source: tcmu
Version: 1.5.4-5
Installed-Size: 137
Maintainer: Debian QA Group
Architecture: amd64
Depends: libc6 (>= 2.34), libglib2.0-0 (>= 2.38.0), libnl-3-200 (>= 3.2.27), libnl-genl-3-200 (>= 3.2.21)
Size: 39124
SHA256: a589e7652a1baa21c73b3e7286cf215d8811488d6d4abb07802e66207336b299
SHA1: f66ecf900de7bccedbd375fdb27d130ae2c8e4f7
MD5sum: aebd38af7bf9f68b390adc8e5e597b49
Description: Library 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 library package
Description-md5:
Homepage: https://github.com/open-iscsi/tcmu-runner
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/t/tcmu/libtcmu2_1.5.4-5_amd64.deb
Source: tcmu
Version: 1.5.4-5
Installed-Size: 137
Maintainer: Debian QA Group
Architecture: amd64
Depends: libc6 (>= 2.34), libglib2.0-0 (>= 2.38.0), libnl-3-200 (>= 3.2.27), libnl-genl-3-200 (>= 3.2.21)
Size: 39124
SHA256: a589e7652a1baa21c73b3e7286cf215d8811488d6d4abb07802e66207336b299
SHA1: f66ecf900de7bccedbd375fdb27d130ae2c8e4f7
MD5sum: aebd38af7bf9f68b390adc8e5e597b49
Description: Library 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 library package
Description-md5:
Homepage: https://github.com/open-iscsi/tcmu-runner
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/t/tcmu/libtcmu2_1.5.4-5_amd64.deb