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.
784 Commits 18 Branches 17 Tags 67 MiB
ca918818bf
Go to file
nucleogenic ca918818bf
Fix unescaped shell arguments
2022-07-30 21:01:22 +01:00
.github Disable the rpi build for develop and master (#330) 2021-10-14 13:20:57 -07:00
doc Fixed missing media change handling (#690) 2022-02-21 21:01:17 +01:00
docs
hw Added Schematic PDF file and Step 3D model (#726) 2022-03-13 20:32:28 -05:00
python Fix unescaped shell arguments 2022-07-30 21:01:22 +01:00
src Rebrand to RaSCSI Reloaded in key places in the code (#772) 2022-07-26 10:20:50 -05: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
_config.yml
.gitignore Added Schematic PDF file and Step 3D model (#726) 2022-03-13 20:32:28 -05:00
easyinstall.sh Create the secret file in .config/rascsi instead. Plus some added code comments, and removing a superfluous sudo -v. 2022-07-28 22:48:18 -07:00
LICENSE Updated copyrights and versions 2021-10-29 21:55:24 -05:00
lido-driver.img
README.md Rebrand to RaSCSI Reloaded in key places in the code (#772) 2022-07-26 10:20:50 -05:00

README.md

What is RaSCSI Reloaded?

RaSCSI Reloaded 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 and Atari 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 Reloaded 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 Gold level sponsors!

Special thank you to the Silver level sponsors!