• Content Count

  • Joined

  • Last visited

  • Days Won


Vileserver last won the day on November 6 2018

Vileserver had the most liked content!

Community Reputation

15 Good

About Vileserver

  • Rank
    Junior Member

Recent Profile Visitors

790 profile views
  1. Oh, that's great that you shared your code on GitHub. Thank you! What a good idea. There is a version 6? It looks like the latest version is 5.2, no? Thanks again for your work
  2. Thanks, John - it was actually really easy to do, USB drives show up in the DSM interface, the SATA attached drive appeared in the HDD list. Then I was able to use File Station with drag and drop.
  3. So maybe, yet another reason to just distribute in shell script format? I think all XPEnology users are smart enough to run a script. And: less work for you, less secrecy, more compatibility with DSM versions... Thank you for all that you do.
  4. You don't even need a login for a serial connection. Assuming you are using the right correction parameters, the output should just dump to your screen.
  5. OK. And you're encrypting this why, again? Because you are worried someone will steal your code?
  6. So what exactly are you using to make a binary executable from a shell script? I thought, if it is a proper executable then it doesn't need /bin/bash? Thank you for your code
  7. Also: Why does a compile script need to find the bash executable? I thought FOXBI was using the compile to make it easier to run... I still think source script (.sh) is easier, and better for sharing. Open source XPEnology
  8. Hi, I'm trying to connect to my bare metal XPenology box (Intel C236 board) via the serial port. I'm hooking it up to my PC's COM1. I am using a null modem cable, which is correct, right? I am connecting with PuTTY using the recommended settings. But when I reboot I only get garbage showing up in the console: ▒▒▒ Using Jun's loader, version 1.03b. Everything comes up fine, I'm just wondering why the serial output isn't working. Has anyone managed to get it running in a similar setup?
  9. Thank you FOXBI. As always, I am looking forward to the bash source of your script!
  10. You can actually get the number of CPU cores in just one line, like this: grep '^cpu cores' /proc/cpuinfo | uniq | awk '{print $4}' This works for CPUs that have hyper-threading. There are some more interesting methods discussed here:
  11. Fantastic! Thanks FOXBI. Any chance you can also post the shell script? I think most users here prefer the bash source. Thanks
  12. OK, here is a slightly updated version, I call it 4.01. Fixes: improve CPU core determination fix color output fix typos Thanks again to FOXBI for this great script! I hope you don't mind me making some small changes to it. gericb, does this work for you?
  13. Before I ran FOXBI's script, the specs said 4 cores for Xeon D-1527, which is the CPU in the DS3617xs: Note this is the number of cores, NOT threads which would be 8 for this CPU! Check Intel's datasheet here. So DSM is always meant to show physical cores, not logical ones. Therefore this is a small bug in the script....
  14. You have nothing to be embarrassed about, FOXBI! Your code is much more elegant than some of my bash scripts 감사합니다 !! Unfortunately, it still doesn't quite work for me - it recognizes my Core i3-6100T (specs) correctly, but it says I have 4 CPU cores: when in fact there are only 2. I am not sure why it thinks so, the commands get it right: # dmidecode -t processor # dmidecode 2.12 SMBIOS 3.0 present. # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmidecode. Handle 0x000C, DMI type 4, 48 bytes Processor In