Popular Post pocopico Posted June 3 Popular Post Share #1 Posted June 3 (edited) As i have annouce on a previous message, it has been decided to split development and stable TCRP releases. In an effort to properly document the deplot. => So stable release will remain at 0.8 version and can be accessed through the main repo : https://github.com/pocopico/tinycore-redpill/tree/main No new features will come through the stable release. Only fixes will be applied as they come along. => Development release 0.9 will bring new features, refinement of old processes etc. So far the development release includes the following : Current : - New images containing latest development rploader.sh version 0.9.0.2 - New background wallpaper when landing into TCRP desktop - New system status landing page when you start desktop. You can now easily find your IP addess on screen. - rploader.sh development release 0.9.0.2 - Several missing packages from Tinycore (ntpclient/file/php-8-cli/scsi modules etc) Roadmap : - User manual module compilation process. - User manual extension creation - Custom.gz re-engineering Tinycore image will remain at version 12 as the binutils on 13.1 have gone passed the required maximum for module compilation. You can head to the development repo to download new images if you would like to test : https://github.com/pocopico/tinycore-redpill/tree/develop Please report any development additions and improvements you would to include on this thread. Do not post install issues here. Edited June 3 by pocopico 15 10 Quote Link to comment Share on other sites More sharing options...
tahuru Posted July 13 Share #2 Posted July 13 Hi, Is there a simple way to upgrade to 0.9 from 0.8 without running all the steps again? Thx! Quote Link to comment Share on other sites More sharing options...
luckcolors Posted July 14 Share #3 Posted July 14 (edited) 2 hours ago, tahuru said: Hi, Is there a simple way to upgrade to 0.9 from 0.8 without running all the steps again? Thx! I think the easiest solution to accomplish this would be to introduce a second empty image as the TC home directory. This way TC would be stored on one image that can be easily be swapped for another on update. This of course has the drawback of requiring 2 disks in the vm for these images. As follows: TC.img -> mounted as TC's /root TCHome.img -> mounted as TC /home/tc @pocopicoWould it be possible to implement this? Edited July 14 by luckcolors Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted July 14 Share #4 Posted July 14 25 minutes ago, luckcolors said: I think the easiest solution to accomplish this would be to introduce a second empty image as the TC home directory. This way TC would be stored on one image that can be easily be swapped for another on update. This of course has the drawback of requiring 2 disks in the vm for these images. As follows: TC.img -> mounted as TC's /root TCHome.img -> mounted as TC /home/tc @pocopicoWould it be possible to implement this? Another easy way would be to do something like this: Can I do this? Is it pocopico? curl --location "https://github.com/pocopico/tinycore-redpill/raw/develop/rploader.sh" -O ./rploader.sh fullupgrade Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted July 14 Share #5 Posted July 14 And, pocopico probably hasn't introduced it yet. There is an incredibly handy feature that has recently been modified in the his develop repo. For models using Device Tree such as DS920+, DS1621+, DVA1622 DTB patch to recognize Sataport's disk and NVMe is essential, This part has been converted from the existing static method to a dynamic method. The difference between the dtb static method and the dynamic method is huge. The static method requires rebuilding the loader whenever the number of disks and ports of sataport change, The dynamic method doesn't have to. Quote Link to comment Share on other sites More sharing options...
phone guy Posted July 14 Share #6 Posted July 14 4 hours ago, Peter Suh said: And, pocopico probably hasn't introduced it yet. There is an incredibly handy feature that has recently been modified in the his develop repo. For models using Device Tree such as DS920+, DS1621+, DVA1622 DTB patch to recognize Sataport's disk and NVMe is essential, This part has been converted from the existing static method to a dynamic method. The difference between the dtb static method and the dynamic method is huge. The static method requires rebuilding the loader whenever the number of disks and ports of sataport change, The dynamic method doesn't have to. I believe @pocopico worked with @fbelavenuto who did arpl project, to get that working... Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted July 14 Share #7 Posted July 14 14 minutes ago, phone guy said: I believe @pocopico worked with @fbelavenuto who did arpl project, to get that working... Perhaps it is. As soon as the dtbpatch addon for arpl is complete dtbpatch ext for TCRP was added. I also changed this ext to be used for the DTC-only model of the m shell. Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 14 Author Share #8 Posted July 14 (edited) 11 hours ago, Peter Suh said: And, pocopico probably hasn't introduced it yet. There is an incredibly handy feature that has recently been modified in the his develop repo. For models using Device Tree such as DS920+, DS1621+, DVA1622 DTB patch to recognize Sataport's disk and NVMe is essential, This part has been converted from the existing static method to a dynamic method. The difference between the dtb static method and the dynamic method is huge. The static method requires rebuilding the loader whenever the number of disks and ports of sataport change, The dynamic method doesn't have to. No major changes will be introduced in stable release. Only fixes. The dtcpatch by fbelavenuto should be included as a fix for 0.8. To upgrade your 0.8 to develop 0.9 image you may proceed with what @Peter Suh suggested. curl --location "https://github.com/pocopico/tinycore-redpill/raw/develop/rploader.sh" -O ./rploader.sh fullupgrade The automatic dtbpatch by fbelavenuto solves most of the issues we had with dtc patching in the past. Also dtc and dtbpatch binaries are copied during boot in runtime DSM for manual troubleshooting or for hotplug disk addition, if its required. CPP code is open and available at fbelavenuto repo. https://github.com/fbelavenuto/arpl-addons/blob/main/dtbpatch/src/main.cpp Edited July 14 by pocopico 2 Quote Link to comment Share on other sites More sharing options...
phone guy Posted July 27 Share #9 Posted July 27 Which platform to pick 920? geminilake? and it does auto create the dtc ? Quote Link to comment Share on other sites More sharing options...
pocopico Posted July 27 Author Share #10 Posted July 27 1 hour ago, phone guy said: Which platform to pick 920? geminilake? and it does auto create the dtc ? Geminilake is the option for DS920+ and it does create automatically the dtb. 1 1 Quote Link to comment Share on other sites More sharing options...
cferra Posted August 5 Share #11 Posted August 5 (edited) oh good something to try on my 6.2.3 upgrade project that I’ve been procrastinating on. Edited August 5 by cferra Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.