Macintosh-HW/RASCSI
1
0
Fork 0
mirror of https://github.com/akuker/RASCSI.git synced 2024-12-23 06:30:04 +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.
140 Commits 18 Branches 17 Tags 67 MiB
bac4f4a80b
Go to file
akuker bac4f4a80b Change reported version back to development build
2021-01-25 13:27:21 -06: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 Issue #7 - implement a scsi monitor function for RaSCSI to log SCSI traffic (#46) 2020-10-19 07:31:06 -05:00
hw Create README.md 2020-10-24 22:49:23 -05:00
src Change reported version back to development build 2021-01-25 13:27:21 -06:00
test/robot Updated for new version number 2021-01-25 13:15:29 -06:00
_config.yml Set theme jekyll-theme-midnight 2020-07-04 20:39:04 -05:00
.gitignore New Web Interface (#69) 2020-12-30 19:39:32 -06:00
easyinstall.sh New Web Interface (#69) 2020-12-30 19:39:32 -06:00
LICENSE Create LICENSE 2020-07-05 23:02:40 -05:00
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 Merged in RASCSI version 1.47 and re-generated english PDF 2020-07-04 09:57:44 -05:00
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