Macintosh-HW
/
RASCSI
mirror of https://github.com/akuker/RASCSI.git
1
0
Fork 0
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.
658 Commits 17 Branches 16 Tags 67 MiB
Go to file
RaSCSI User 3cc04a8dcf Update revision for release 2022-01-01 20:48:30 +00:00
.github Disable the rpi build for develop and master (#330) 2021-10-14 13:20:57 -07:00
doc Initial remote interface error message localization support (#555) 2021-12-23 08:49:04 +01:00
docs Merge Hw 2p4 to develop (#109) 2021-06-08 19:06:29 -05:00
hw Loopback tester pcb (#545) 2021-12-19 22:30:22 -06:00
src Update revision for release 2022-01-01 20:48:30 +00:00
test/robot Create new test cases for checking that the user can specify the TCP Port number (#154) 2021-07-27 18:40:00 -05:00
.gitignore Web Interface i18n (#564) 2021-12-26 15:36:12 -06:00
LICENSE Updated copyrights and versions 2021-10-29 21:55:24 -05:00
README.md Added list of sponsors 2021-12-19 21:02:50 -06:00
_config.yml Set theme jekyll-theme-midnight 2020-07-04 20:39:04 -05:00
easyinstall.sh Improve token auth and oled monitor install scripts; better venv cleanup logic (#587) 2022-01-01 11:38:10 -06:00
lido-driver.img improved HD creator with partioning and formatting Drive with HFS. (#51) 2020-11-07 18:10:09 -06:00

README.md

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

Github Sponsors

Thank you to all of the Github sponsors who support the development community!

Special thank you to the Silver level sponsors!