Macintosh-HW/RASCSI
1
0
Fork 0
mirror of https://github.com/akuker/RASCSI.git synced 2024-11-22 16:33:17 +00:00
Code Issues Projects Releases Wiki Activity
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.
205 Commits 18 Branches 17 Tags 67 MiB
7dd93728f9
Go to file
akuker 7dd93728f9 Regenerated text versions of man pages. This was missed in PR #110
2021-06-22 19:30:33 -05:00
.github Issue #7 - implement a scsi monitor function for RaSCSI to log SCSI traffic (#46) 2020-10-19 07:31:06 -05:00
doc Regenerated text versions of man pages. This was missed in PR #110 2021-06-22 19:30:33 -05:00
docs Merge Hw 2p4 to develop (#109) 2021-06-08 19:06:29 -05:00
hw Merge Hw 2p4 to develop (#109) 2021-06-08 19:06:29 -05:00
src Use exception for unsupported LUN handling, reduces duplicate code (#111) 2021-06-22 19:05:47 -05:00
test/robot Cleanup test procedure to allow service to be inactive OR failed 2021-04-05 16:38:39 -05:00
_config.yml
.gitignore Add start script to simplify oled install 2021-03-07 09:28:40 -06:00
easyinstall.sh Merge pull request #96 from akuker/daynaport3 2021-05-26 10:50:13 -05:00
LICENSE
lido-driver.img improved HD creator with partioning and formatting Drive with HFS. (#51) 2020-11-07 18:10:09 -06:00
RASCSI_webpage_translated.pdf
README.md Update README.md 2021-01-24 21:45:53 -06:00

README.md

C/C++ CI Scrutinizer Code Quality Coverity Scan Build Status

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 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