M Shell for tinycore-redpill

https://paypal.me/PeterSuhQ3

---

• GitHub ACTIONS-COOL Loader Auto Build Feature Distribution (Using Issues)

1. You must have a GitHub account.

https://github.com/

Create an account with Sign Up and then log in with Sign In.

2. If you write an issue in this issue, the loader will be automatically built based on the model in the content you wrote.

https://github.com/PeterSuh-Q3/tinycore-redpill/issues

This is using the GitHub ACTIONS-COOL build bot.

3. The title of the issue (the word custom must be included in the title.)

custom DS920+

The content of the main text is

{"model":"DS920+","version":"7.2.2-72806"}

Or

If you have a full-size serial and Mac address, please enter it in the following format. (Mac addresses are supported up to 4, mac4 only.)

{"model":"DS920+","version":"7.2.2-72806","mac1":"112233445566","mac2":"77889900aabb","sn":"1111222233333"}

If the Mac address and serial are omitted, they will be randomly generated.

You must write it in the form of a JSON body like this.

You can change the model and version, but if you make even the slightest mistake in spelling, the build will not be done properly.

4. Save the issue

If you go to the Actions side, you will see an orange icon and the loader build will proceed.

https://github.com/PeterSuh-Q3/tinycore-redpill/actions

Workflow runs · PeterSuh-Q3/tinycore-redpill github.com Contribute to PeterSuh-Q3/tinycore-redpill development by creating an

If you want to see the details, you can click on the workflow in progress.

If the loader build is successful, the workflow will turn green.

If you select Summary,

The artifact result, which is the loader file generated at the very bottom, is saved in the form of a zip file.

In this MshellImage-*.zip, the img file and vmdk file are each recompressed in tgz format.

The core content of this function is

Originally, you burn the official img of the TCRP-mshell loader to USB,

Enter ./menu.sh, select the model, version, serial, MAC address, etc., and go through manual build to complete the loader,

but this function is a function that allows you to receive an already completed loader from GitHub, bake it, and use it.

Since the Grub boot menu is created in the same way as when you manually build,

you can also build the loader created in this way by entering the manual build menu again.

---

Please note that minimum recommended memory size for configuring the loader is 4GB

Instructions

A typical build process starts with:

1. Burn images

   A. To burn physical gunzip and img files to a USB stick

   B. For virtual gunzip use the provided vmdk file

2. Boot Tinycore

3. Loader Building

    A. Choose one of the Synology models.

    B. Create a virtual serial number or enter a prepared serial number.

    C. Select the real mac address of the nic or create a virtual mac address or 
       input the prepared mac address. 
       (If there are 2 nics, you can enter up to the 2nd mac address)

    D. Build the loader.

6. Reboot

< Version History >

1.0.1.1 Fix monitor fuction about ethernet infomation
1.0.1.2 Fix for SA6400
1.0.2.0 Remove restrictions on use of DT-based models when using HBA (apply mpt3sas blacklist instead)
1.0.2.1 Changed extension file organization method
1.0.2.2 Recycle initrd-dsm instead of custom.gz (extract /exts), The priority starts from custom.gz
1.0.2.3 Added RedPill bootloader hard disk porting function
1.0.2.4 Added NVMe bootloader support
...
1.0.5.0 Improved internet check function in menu.sh
...
1.0.6.2 Changed to use only the first one when multiple bootloaders exist
1.0.6.3 Added ability to force loading mmc and sd modules when loading Tinycore Linux
1.0.6.4 Expanded MAC address support from 4 to 8.
1.0.6.5 Includes tinycore linux scsi module for scsi type bootloader support.
1.0.6.6 Discontinuing support for DS3615xs.
1.0.6.7 Applying REDPILL background image to grub boot
1.0.6.8 i915.modeset=0 menu processing improvement (FRIEND guidance console is activated when i915 transcoding is disabled)
1.1.0.0 Added features for distribution of xTCRP (Tinycore Linux stripped down version)
1.1.0.1 When using a single m.2 NVMe volume, the DDSML error issue has occurred, so menu usage has been excluded and related support has been strengthened.
1.2.0.0 Added new platforms purley, broadwellnkv2, broadwellntbap and started supporting all models for each platform
1.2.1.0 Create tinycore-mshell and xTCRP together in grub boot. Merge Re-install boot entries without USB/SATA distinction and fix KP bug.
1.2.1.1 Renewal of SynoDisk bootloader injection function
1.2.1.2 SynoDisk with Bootloader Injection Supports NVMe DISK
1.2.1.3 SynoDisk with Bootloader Injection Supports Single SHR DISK
1.2.1.4 SynoDisk with Bootloader Injection Stop Supports BASIC or JBOD DISK
1.2.1.5 SynoDisk with bootloader injection uses UUID 8765-4321 instead of 6234-C863
1.2.1.6 DS3615xs(bromolow) support again, LEGACY boot mode must be used!
1.2.1.7 SynoDisk with Bootloader Injection Supports 2.4GB /dev/md0 size (before dsm 7.1.1)
1.2.1.8 Modify the method of checking Internet connection in menu.sh
1.2.1.9 Fixed to keep graphic console screen even in Jot Mode/Legacy Boot environment (use gfxpayload=keep)
1.2.2.0 Activate Tinycore TTYD web console (port 7681, login use tc/P@ssw0rd)
1.2.2.1 TTYD web console baremetal headless support fix
1.2.2.2 Added to change the default value of the Grub boot entry (in the submenu)
1.2.2.3 Added a feature to immediately reflect changes to user_config.json (no need for loader build)