English fork of the Japanese RaSCSI project. RaSCSI allows a Raspberry Pi to function as emulated SCSI devices (hard disk, CD-ROM, and others) for vintage SCSI-based computers and devices.
Go to file
Daniel Markstedt c887edfc8c
Remove special elevated privileges for the Web Interface (#536)
* Use the pi_shutdown method to restart the rascsi service

* Use the pi_shutdown method to restart the rascsi service

* Remove modifications to sudoers no longer needed

* Introduce sleeps attempting to connect to socket; reduce overall number of retries

* Remove systemd helped methods and the functionality that depends on it

* Attempts to speed up splash code

* Remove unneccessary verbosity

* Attempt to optimize service definition
2021-12-19 17:50:03 -06:00
.github
doc Optional authentication by access token (#529) 2021-12-19 11:54:10 +01:00
docs
hw Fix daisychain board files (#462) 2021-11-14 13:56:41 -06:00
src Remove special elevated privileges for the Web Interface (#536) 2021-12-19 17:50:03 -06:00
test/robot
_config.yml
.gitignore OLED Screen: Inquire device status over the protobuf interface (#349) 2021-10-19 19:59:04 -05:00
easyinstall.sh Remove special elevated privileges for the Web Interface (#536) 2021-12-19 17:50:03 -06:00
LICENSE Updated copyrights and versions 2021-10-29 21:55:24 -05:00
lido-driver.img
README.md Removed duplicated text (#397) 2021-10-27 19:33:33 -07:00

What is RaSCSI?

RaSCSI is a virtual SCSI device emulator that runs on a Raspberry Pi. It runs in userspace, and can emulate several SCSI devices at one time. There is a control interface to attach / detach drives during runtime, as well as insert and eject removable media. This project is aimed at users of vintage Macintosh computers and more (see compatibility list) from the 1980's and 1990's.

Please check out the full story with much more detail on the wiki!

How do I contribute?

RaSCSI is using the Gitflow Workflow. A quick overview:

  • The master branch should always reflect the contents of the last stable release
  • The develop branch should contain the latest tested & approved updates. Pull requests should be used to merge changes into develop.
  • The rest of the feature branches are for developing new features
  • A tag will be created for each "release". The releases will be named . (for the first release of the month). Hot fixes, if necessary, will be released as ... For example, the first release in January 2021 will be release "21.01". If a hot-fix is needed for this release, the first hotfix will be "21.01.1".

Typically, releases will only be planned every few months.

I sell on Tindie