There are highly optimized installation packages (for 32 Bit bullseye/bookworm and 64 bit bullseye/bookworm) with release versions and regular builds of the development version.
SCSI2Pi is installed or updated in a matter of seconds. Just install the binary package:
>sudo apt install ./scsi2pi_BUILD_ARCH.deb
A warning like "Download is performed unsandboxed as root" can be ignored.
After the first installation you should adjust the settings in /etc/s2p.conf, e.g. the default path for drive images.
During the installation the PiSCSI system service, if active, will be deactivated. The SCSI2Pi system service will be enabled instead, but will not be started automatically. Note that the PiSCSI and the SCSI2Pi system service cannot be running at the same time.
The standard installation path of the SCSI2Pi binaries and manpages is /opt/scsi2pi. You should add these paths to your environment, e.g. in .profile or .bash_profile:
export PATH=/opt/scsi2pi/bin:$PATH
export MANPATH=/opt/scsi2pi/man:$MANPATH
SCSI2Pi is de-installed with:
>sudo apt remove scsi2pi
SCSI2Pi is compatible with the PiSCSI web UI, which you can install before or after installing SCSI2Pi. Thus SCSI2Pi just like PiSCSI can also be managed with a browser.
Note that there are known issues with the PiSCSI web UI (see the PiSCSI issue list and the PiSCSi release notes). In case of a web UI malfunction, check whether there is the same issue with PiSCSI.
According to the usual standards the SCSI2Pi settings are managed in a separate configuration file /etc/s2p.conf and not in the startup file for the system service.
SCSI2Pi can also be managed without the web UI. You can either do this with the s2pctl tool (see the manpage for details) or with the SCSI Control App.
You can also compile SCSI2Pi yourself, e.g. for a customized build. The SCSI2Pi wiki provides more information.
sudo apt install ./scsi2pi_BUILD_ARCH.deb.sudo systemctl start s2p, or start s2p manually with /opt/scsi2pi/bin/s2p.