Jump to content
XPEnology Community

Polanskiman

Administrator
  • Posts

    2,734
  • Joined

  • Last visited

  • Days Won

    119

Everything posted by Polanskiman

  1. Hello, Have you read the description? I'll move it to the right place but please make an effort the next time.
  2. If the OP comes back please contact me and I'll unlock this thread. For now I don't see the point in leaving this thread open for people to post irrelevant content. There a 2 functional loaders out there.
  3. @batistameaYou do realize this is a 2+ years old thread right? And beyond that, it looks to me you are also doing some advertisement here which is clearly against the rules of the forum. Anymore of this type of posts and that will be the end of it.
  4. haha I didn't take it the wrong way, no worries In fact those files I mentionned earlier can be removed, well at least I did remove them, then recreated the backups obviously with the commands. I wanted to see how the space was affected. backups then were able to proceed and I was then able to reboot and all was fine. Great, thank you.
  5. Yes obviously everything is there for a reason. I don't doubt that but see what I experienced yesterday. Running the clean command solved the issue BUT what if the loader get's bloated? All my comments above regarding deleting were merely to mitigate potential space errors. Curious, what exactly get's deleted with the clean command? The output of the command says: Clearing local redpill files but I am not entirely sure what those files are and where they are located?
  6. Message addressed to @pocopico Regardless of the resizing, I think something would need to be clarified and addressed and that is what can and cannot be deleted from that partition. Has this been mentioned somewhere? I played around this morning and flashed the usb key like 10 more times with different versions of the loader to see the behaviors and what I could or could not delete but I think it would be worth you saying explicitly what can safely be deleted and what needs to be actually backed up. Here is what I have after running backup and backuploader. tc@box:/mnt/sdc3$ ls -la total 449184 drwxrwxrwx 6 root root 4096 Jan 1 1970 ./ drwxrwxr-x 5 root staff 100 Oct 7 10:53 ../ drwxrwxrwx 3 root root 4096 Oct 7 02:59 auxfiles/ drwxrwxrwx 2 root root 4096 Oct 7 10:56 backup/ -rwxrwxrwx 1 root root 6108352 Oct 7 03:00 bzImage-friend drwxrwxrwx 3 root root 4096 Feb 18 2021 cde/ -rwxrwxrwx 1 root root 12031520 Jan 5 2022 corepure64.gz -rwxrwxrwx 1 root root 2957 Oct 7 03:08 friendlog.log -rwxrwxrwx 1 root root 28498432 Oct 7 03:08 initrd-dsm -rwxrwxrwx 1 root root 35825281 Oct 7 03:00 initrd-friend drwxrwxrwx 2 root root 4096 Oct 7 03:00 lastsession/ -rwxrwxrwx 1 root root 356232110 Oct 7 03:41 mydata.tgz -rwxrwxrwx 1 root root 1658 Oct 7 03:43 user_config.json -rwxrwxrwx 1 root root 5366304 Feb 18 2021 vmlinuz64 -rwxrwxrwx 1 root root 15859712 Oct 7 03:08 zImage-dsm What I gathered from this is that the backup/ directory can safely be deleted to make space as well as the mydata.tgz compressed file. Would there be anything else that could be deleted for a user to make space? These 2 alone will basically take half the partition space with the current 900 MB size. There is also the auxfiles directory that contains the pat file. Can this be deleted or is this required for boot? You also mentioned earlier: What do you define as necessary? In other words what are the files that should be backed up? I noticed that each time we run backuploader, a new directory will be created under backup/ with the date and time (e.i: 2022-Oct-07-03-02). This saves both partitions. My question is, is it really necessary to created new backups each time? Why not overwrite the previous backup. I'm just trying to think how to make this a bit less of a data hog. I doubt that people need to have multiple backups of their loader in the drive, but I could be wrong. I am pretty confident that in fact the large majority of people have no clue what they are backing up when running those commands and how to even recover them in case of need. I know there are these restoreloader and restoresession commands. Anyhow, perhaps what could be added to the code is some confirmation question when one decides to do a backup. User would be prompted with the possibility of over-writing previous backups. What do you think? This would limit how fast the partition get's filled. I am still playing around with the loader and I have to say there is still plenty I need to do to feel confortable with it but I'm getting there. You've done an excellent job man.
  7. @pedroj666and @sam juan Both your posts have been deleted. Read the Developers forum title and explicit comment:
  8. Seems to have worked with the clean statement. This is very odd because I did not issue that command a week ago. I am certain of it. 🤷‍♂️
  9. Which are? What I am failing to understand is why I am getting this now and not a week ago when I did the exact same procedure with a blank usb key, which is what I am doing exactly now.
  10. There is no reason for this to happen. As I said I started from a fresh formatted usb key and proceeded with the exact same commands as a week ago:
  11. Something seems off. I started from scratch and burned the loader. used v0.9.2.7. At the end of the process I can't backup. No space. Didn't have this issue when I first did the loader a week ago. tc@box:~$ ./rploader.sh backup Please make sure you are using the latest 1GB img before using backup option Current /home/tc size is 844M , try to keep it less than 1GB as it might not fit into your image Should i update the sdc with your current files [Yy/Nn] y Backing up home files to sdc : Backing up files to /mnt/sdc3//mydata.tgz \ There was an issue, see /tmp/backup_status. Error: Couldn't backup files tc@box:~$ vi /tmp/backup_status tc@box:~$ ./rploader.sh backuploader No adequate space on TCRP loader partition /mnt/sdc3 tc@box:~$ So I went ahead anyways and exitcheck.sh reboot to be greeted with the following error: DSM is not visible on the network.
  12. Not sure I get it. So let me see if I get this right. On next reboot, TCRP Friend will update to v0.0.2 and the autoupdate will be disabled? Reason I am confused is because you also say the default will remain true. Not sure what you intended to say there.
  13. Well anyone is free to create a guide or tutorial. The developers develop, the moderators moderate and myself I administer and moderate the forum which is our way to contribute to the XPEnology community. When extra time is available we make additional contributions and create guides, help others etc etc but nothing stops regular members to do the same thing. Many have done so. Remember we are doing this on our free time. 🙂
  14. Is it only me or wouldn't it be sensible to allow the user to at least be able to enable/disable this auto update feature? Or perhaps this is just temporary considering it's still in development? I can imagine a scenario where there could be a bug in an updated code of TCRP Friend which would then prevent DSM from booting, or would that not be possible? Just thinking out loud here.
  15. I will post this here since I am using the development version of TCRP 0.9.2.6. So today was maintenance day. Server was dismantled and cleaned and dusted. Thermal paste was re-applied. The important bit is that once re-assembled and booted and plugged to TV I noticed that TCRP Friend updated by itself without my intervention. TCRP said it detected a new version and went on an updated. Unfortunately I was too slow to take my phone and take a picture of the process. @pocopico Is this auto update intended? Also coincidently, TCRP Friend still shows v0.0.1 after the update. It was already v0.0.1 prior the update.
  16. This is the noob lounge. I will tolerate other languages in this sub forum alone since there is no such sub forums in the foreign language forums. Additional to this, topics created here are bound to be moved to other areas of the forum in due time.
  17. Thread has been moved to the appropriate forum: General Installation Questions/Discussions (non-hardware specific)
  18. Thread has been slightly renamed to TinyCore RedPill Loader (TCRP)
  19. Ok thank you. In this case I will be moving in to the Loader sub forum.
  20. Yes. More so it was TTG who incorporated that. I am not sure. I haven't updated to 7.1.1 You can still update manually through the GUI. ./rploader.sh postupdate is needed not matter what unless you are using TRCP withfriend.
  21. The question(s) in this topic have been answered and/or the topic author has resolved their issue. This topic is now closed. If you have other questions, please open a new topic.
  22. @fbelavenuto Do you consider this loader to be stable at this stage?
  23. @Madasafish Please read this and subsequent posts: https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=289444
×
×
  • Create New...