| Git Clone URL: | https://aur.archlinux.org/scst.git (read-only, click to copy) |
|---|---|
| Package Base: | scst |
| Description: | Administration utilit for SCST |
| Upstream URL: | http://scst.sourceforge.net |
| Keywords: | fc ib iscsi scst target |
| Licenses: | GPL |
| Submitter: | AlexTalker |
| Maintainer: | AlexTalker |
| Last Packager: | AlexTalker |
| Votes: | 1 |
| Popularity: | 0.000000 |
| First Submitted: | 2017-04-08 14:58 (UTC) |
| Last Updated: | 2018-06-23 23:01 (UTC) |
SVN source URL broken, should be
- scst-svn::svn+https://svn.code.sf.net/p/scst/svn/trunk/branches/$_branch
+ scst-svn::svn+https://svn.code.sf.net/p/scst/svn/branches/$_branch
scst.install has a bug too, looking for EXTRAMODULES=extramodules-4.11-ARCH being out of date. Set to extramodules-ARCH for myself made it work properly.
@ozz regarding your half-of-the-year old comment, I think many people won't use SCST because it is not so "user-friendly"(scstadmin is hardly friendly in any way). But I totally admire how sysfs interface works, it is original in some way but quite reliable. In fact, often I regret that some things(like DRBD for example) do not provide their own sysfs interface in simiar way. Also, scstadmin is quite messy from point of a code-style. Once upon a time I thought to implement some sample client on python but I haven't got time for it yet. But considering well-defined structure of sysfs, that shouldn't be a problem.
I used SVN instead of tarball(quite old by now). I don't want to rename the package since it seems that source code tarballs aren't fitting SCST project workflow. Anyway, Vlad's reply on production quality of 3.3: https://sourceforge.net/p/scst/mailman/message/36326570/
Sorry for delaying the update, was quite busy living.
I haven't built this in a while. It appears to be broken currently. The sourceforge link fails. Plus it's way out of date anyway.
Thanks for creating this even though it doesn't seem popular. I don't think very many people use iSCSI and those that do are using very old stuff. I was a fan of IET and hated the move to LIO because LIO has never worked as well. At this point LIO is totally broken in 4.14+ kernels to the point that diskless iSCSI clients can't boot at all and requests to fix are going ignored.
I understand why people don't use SCST though because it's a real PITA to install on many distros, often requiring compiling your own kernel. I wish it was chosen to be mainlined in the kernel instead of LIO.
Anyway, I digress. Thanks!
Pinned Comments
AlexTalker commented on 2017-05-12 17:10 (UTC) (edited on 2017-05-12 17:15 (UTC) by AlexTalker)