mirror of
https://github.com/akuker/RASCSI.git
synced 2024-11-22 16:33:17 +00:00
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.
735aff6cd1
* Extended protobuf interface with rascsi server information * Added default_image_folder (to be used in a different feature) * Remember log level because not all versions of spdlog support get_log_level() * Display enum names instead of values * Added support for default image folder * Added method that returns the available image files * Added list of image files to protobuf interface * Error handling update * Filter image files * Update setting up image file list * Message update * Replaced if/else cascade by switch * Updated log level handling * Renaming, sort rasctl list output * Added -lstdc++fs (required by gcc 8.3.0) * Changed option shortcut * Sorted log levels by severity * Fixed sorting of log levels * Use map for storing available log levels * Replaced explicit typ * Revert "Replaced explicit typ" This reverts commit |
||
---|---|---|
.github | ||
doc | ||
docs | ||
hw | ||
src | ||
test/robot | ||
_config.yml | ||
.gitignore | ||
easyinstall.sh | ||
LICENSE | ||
lido-driver.img | ||
RASCSI_webpage_translated.pdf | ||
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 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.