mirror of
https://github.com/akuker/RASCSI.git
synced 2025-01-24 03:32:31 +00:00
0032ce5010
* Set hostname
* Added option for hostname
* Support connecting from a different host
* Squashed commit of the following:
commit 6698b8b90a0760102ce9fb30a5ee0656dd46491c
Author: akuker <34318535+akuker@users.noreply.github.com>
Date: Mon Jul 19 01:19:41 2021 -0500
Remove extraneous carriage return (#135)
Co-authored-by: Tony Kuker <akuker@gmail.com>
commit af6e311e6eab40255572d2e55b20ab6edb6871ea
Author: uweseimet <48174652+uweseimet@users.noreply.github.com>
Date: Mon Jul 19 00:15:13 2021 +0200
protobuf-based rasctl/rascsi command interface (#129)
* Initial protobuf definition
* protobuf result message draft
* Merge with develop branch
* Makefile generates protobuf-based source files
* Interface update
* Fixed typo
* Fixed typo
* Updated returning status
* Serialize return data
* Use correct descriptor
* Made interface fields required
* Deserialize result
* Serialization update
* Updated serialization
* Serialization update
* Updated deserialization
* status handling update
* Evaluate status
* Revert "Evaluate status"
This reverts commit 3d8f2c3252a10618dede5f5fd80c84115551fc7d.
* Completed sense_key enum
* Renaming
* Added protobuf Command
* Updated command evaluation
* Interface update
* Interface update
* Added DeviceType enum
* Improved type-safety
* Fixed typo
* Type-safety update
* Fixed typo
* Error handling update
* Updated list handling
* Error handling update
* Use more C++ strings
* protobuf enums can provide their names
* Fixed listing devices
* Updated logging
* Enum usage cleanup
* More enum cleanup
* Fixed command check
* Updated type check
* Updated enums
* Removed unused variable
* Removed goto, added exception
* Socket handling cleanup
* Code locality cleanup
* Added helper method
* Extracted code
* Updated socket/file handling
* Use C++ I/O
* Use tolower()
* Renaming
* Simplified has_suffix
* Fixed typo
* Use spdlog namespace
* Simplified formatting (endl) of error messages
* Added -s option for changing the runtime log level to rasctl
* Renaming
* Renaming
* Updated error reporting
* Fixed log string formatting
* String conversion cleanup
* Fixed typo
* Log mmap error (happens on 64 bit)
* Improved proto3 compatibility, updated error handling
* CHanges based on review
* Fixed comment
* Comment update
* Updated ListDevice to not directly write to the stream
* Use size_t
* Renaming
* Buffering update
* MapController should not use fp
* Use fd, not fp
* rasctl has to display *all* results
* rasctl has to display *all* results
* Error handling update
* Updated to proto3 protocol
* Optimization by using protobuf-lite
* RaspBian outdated protoc does not support _Name
* Added protobuf-compiler to easyinstall.sh
Co-authored-by: akuker <34318535+akuker@users.noreply.github.com>
* Resolved merge conflicts
* Updated help message
* Re-added CR/LF
* Updated error handling
* Use fd instead of fp
* Removed CR/LF
* Comment update
* Fixed data types
* Data type update
* Updated help message
* Added new option to usage info, rascsi: use -s instead of -l for consistency
* Display name of (remote) host in error message
* Fixed buffer overflow, cfilesystem.cpp:1185 assumes size of 11 bytes
* Revert "Fixed buffer overflow, cfilesystem.cpp:1185 assumes size of 11 bytes"
This reverts commit 126592d411121e0a807c287b867895d9786025e0.
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.
