Disowning, since I don't use it and it is deprecated.
Maybe somebody interested in the original branch can adopt it.
Search Criteria
Package Details: lio-utils 4.1-10
Package Actions
| Package Base: | lio-utils |
|---|---|
| Description: | deprecated low-level configuration tool set for LIO (Target and iSCSI) |
| Upstream URL: | http://linux-iscsi.org/wiki/Lio-utils |
| Category: | system |
| Licenses: | |
| Submitter: | JonnyJD |
| Maintainer: | None |
| Last Packager: | None |
| Votes: | 5 |
| First Submitted: | 2011-10-04 11:26 |
| Last Updated: | 2013-09-14 09:08 |
Latest Comments
Comment by JonnyJD
Comment by JonnyJD
By the way, this is deprecated by upstream [1]. Since it is still a dependency of targetcli, I recommend using https://aur.archlinux.org/packages/targetcli-fb/, which has fewer deps overall.
[1]: http://www.linux-iscsi.org/wiki/Lio-utils
Comment by JonnyJD
This package is in https://github.com/JonnyJD/PKGBUILDs/tree/master/_lio/lio-utils
For like when somebody wants to fix a systemd file. Upstream doesn't include one. I just patch an upstream rc-script.
Comment by JonnyJD
added security patch concerning symlink attacks with the logfile.
See also: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654262
Comment by JonnyJD
I made some fixes in the rc script in the 7th iteration of this package. The integration into the arch boot process is now much better.
I also created the free branch package for targetcli: https://aur.archlinux.org/packages.php?ID=57081
That package now works without lio-utils and has an own rc script (conflicting with lio-utils). Targetcli is supposed to be the new way of configuring LIO targets.
Comment by JonnyJD
I went ahead and created a separate package lio-snmp: https://aur.archlinux.org/packages.php?ID=56365 which provides the snmp modules and the mib data.
This package has no dependency from snmp anymore. If you don't need snmp, you don't need to upgrade.
Comment by JonnyJD
Hm. Technically you can build it with net-snmp and then uninstall net-snmp again and you won't have problems, if you don't use snmp explicitly yourself. (build-requirement)
I can also make a separate lio-utils-snmp package. Then only the few people that actually use this, need snmb for the build. I should also include pre- and postinstall scripts to include the mibs/libs in the snmp configuration.
The snmp-libs are also architecture dependent, in contrast to the rest of the package. Must have missed that.
I am not quite sure which way to go. Any preferences?
Comment by chmod777
The PKGBUILD will fail unless extra/net-snmp is installed before hand.
It needs to be made a dependency.
Comment by JonnyJD
I updated the PKGBUILD. A symlink should not be necessary. Thx for reporting.
Anonymous comment
The tcm-py package was trying to run 'python setup.py install'. But there was only python2 available on my Arch install. I create a /usr/bin/python symlink to /usr/bin/python2 and then the package build completed.
Comment by JonnyJD
Corrected in a new PKGBUILD. Thx a lot for reporting.
Comment by tomprogrammer
Hello,
I'd like to use your packet, but building it gives me an error.
Here some information:
running install_egg_info
Writing /home/thomas/lio-utils/pkg/usr/lib/python2.7/site-packages/tcm-4.1-py2.7.egg-info
running install
running install_lib
copying build/lib/lio_node.py -> /home/thomas/lio-utils/pkg/usr/lib/python2.7/site-packages
copying build/lib/lio_dump.py -> /home/thomas/lio-utils/pkg/usr/lib/python2.7/site-packages
byte-compiling /home/thomas/lio-utils/pkg/usr/lib/python2.7/site-packages/lio_node.py to lio_node.pyc
byte-compiling /home/thomas/lio-utils/pkg/usr/lib/python2.7/site-packages/lio_dump.py to lio_dump.pyc
writing byte-compilation script '/tmp/tmp1xXGCd.py'
/usr/bin/python2 -O /tmp/tmp1xXGCd.py
removing /tmp/tmp1xXGCd.py
running install_egg_info
Writing /home/thomas/lio-utils/pkg/usr/lib/python2.7/site-packages/lio-4.1-py2.7.egg-info
install -m 0755 iscsi-name /home/thomas/lio-utils/pkg//usr/sbin/iscsi-name
mkdir -p /home/thomas/lio-utils/pkg///usr/lib/snmp/dlmod
install iscsiTargetMib.so /home/thomas/lio-utils/pkg///usr/lib/snmp/dlmod
mkdir -p /home/thomas/lio-utils/pkg///usr/share/snmp/mibs
(cd mibs ; install -m 644 LIO-IPS-AUTH-MIB.txt LIO-ISCSI-MIB.txt LIO-SCSI-MIB.txt /home/thomas/lio-utils/pkg///usr/share/snmp/mibs)
sed: can't read /home/thomas/lio-utils/pkg/usr/sbin/lio_dump: No such file or directory
sed: can't read /home/thomas/lio-utils/pkg/usr/sbin/lio_node: No such file or directory
sed: can't read /home/thomas/lio-utils/pkg/usr/sbin/tcm_dump: No such file or directory
sed: can't read /home/thomas/lio-utils/pkg/usr/sbin/tcm_fabric: No such file or directory
sed: can't read /home/thomas/lio-utils/pkg/usr/sbin/tcm_loop: No such file or directory
sed: can't read /home/thomas/lio-utils/pkg/usr/sbin/tcm_node: No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
ls /home/thomas/lio-utils/pkg/usr/sbin/:
-rwxr-xr-x 1 thomas users 13K 9. Okt 17:45 iscsi-name*
lrwxrwxrwx 1 thomas users 44 9. Okt 17:45 lio_dump -> /usr/lib/python2.7/site-packages/lio_dump.py
lrwxrwxrwx 1 thomas users 44 9. Okt 17:45 lio_node -> /usr/lib/python2.7/site-packages/lio_node.py
lrwxrwxrwx 1 thomas users 44 9. Okt 17:45 tcm_dump -> /usr/lib/python2.7/site-packages/tcm_dump.py
lrwxrwxrwx 1 thomas users 46 9. Okt 17:45 tcm_fabric -> /usr/lib/python2.7/site-packages/tcm_fabric.py
lrwxrwxrwx 1 thomas users 44 9. Okt 17:45 tcm_loop -> /usr/lib/python2.7/site-packages/tcm_loop.py
lrwxrwxrwx 1 thomas users 44 9. Okt 17:45 tcm_node -> /usr/lib/python2.7/site-packages/tcm_node.py
Do you have an idea? If i could test something or you need me to provide more information, let me know.
Thanks in advance
Thomas Bahn <tomprogrammer>
Comment by JonnyJD
LIO is in the kernel since 2.6.38 but the iSCSI target support is in 3.1. So you either have to wait or try 3.1rc linux-mainline: https://aur.archlinux.org/packages.php?ID=50893
Either way you have to somehow build the iscsi_target module. Without iscsi you can also use tcm_loop or tcm_fc, which are already working in 3.0