Jump to content
XPEnology Community

Jman420

Member
  • Posts

    119
  • Joined

  • Last visited

Everything posted by Jman420

  1. Poechi has left the XPEnoboot Team some time ago. At the last time of contact there were no legal claims against him. He simply felt that the risk of hosting his site, files, etc and the level of enjoyment he was getting out of the project no longer made sense. He made great contributions while he was with us and there is always an open seat for him on the team. We wish him well in whatever endeavors he is involved with now.
  2. Jman420

    QNAP QTS Port?

    mmmMMMmmm.... nope! And we have no plans on developing one.
  3. Lol, ok. That makes way more sense. In that case I would recommend doing incremental upgrades like AllGamer suggested; 4.2 -> 4.3 and so on. I doubt you will need to install the minor revisions in between, but updating incrementally on the minor and then major versions is probably a good idea.
  4. I dont think I've ever seen a question like this before. Are you running XPEnology on Synology hardware, like a real Synology box? I might be missing something here, but why wouldn't you run full Syno DSM if you have the hardware to do it? I don't have any answers for you (unfortunately), but I'm intrigued to know why someone would use XPEnology when Syno DSM is usable.
  5. This is really only an option for Synology. The XPEnology Dev Team will NEVER consider taking XPEnoboot commercial, it simply poses far too many legal issues which we are pushing already with the free versions.
  6. Ipkg feeds have not been updated in years. There is another package service which has more up to date packages. There should be a post floating around somewhere.
  7. NO! You do not want automatic updates enabled. You will need to wait until updates are approved by the community or dev team before installing. In some cases you will need to update the XPEnoboot bootloader before or after updating.
  8. Not sure how easy that is. We would need to patch that away. might be doable, would need to check with vortex; he's our patch guy.
  9. Release turn-around for previous major releases of DSM's source code have usually been around a month or so after the binary release. We are usually pretty quick to patch and add our pieces once it gets released, but I don't want to set any expectations for how long it will take us to get an XPEnoboot release ready after the DSM source code is released. We will work as hard as we can to get DSM6 to you guys as soon as we can.
  10. Thats where I get my Plex packages from. You will probably need to adjust the security settings in Package Manager to allow you to install self or un-signed packages (forget which of those Plex falls under).
  11. In the past donations have been split between (or at least available to) all XPEnoboot Team Members. Some of us have opted out of collecting (or cashing in) donations and passed our shares to the other team members instead. Donations are nice (and getting free beers even more so), but that isn't the driving force behind the project. In fact I'm not really sure what the driving force is... I expect we all have our own motivations. When Poechi ran his site all of the donations that went there were split between the team, but now that we have disconnected distribution locations its harder to consolidate donations and unfortunately we (as the XPEnoboot Team) have not put together a central site for the project (partially due to avoiding Synology & partially due to laziness). Unfortunately I've lost track of who operates what websites, so I can't give a suggestion for where to donate to ensure the XPEnoboot Team gets it. Maybe another Team Member has more details. Edit: Thanks for the support and asking how best to support us. We love hearing from the community and seeing you guys help each other and enjoy our work. Until we have solid donation system setup my suggestion is to pay us back by 'paying it forward'; support us by helping the next guy with questions.
  12. I just recently bought a DS415+ for my personal server (fully syno box). Its been running DSM 6 since I got it about 2 weeks ago and has been hosting my Plex Server the entire time. The Plex App on the Package Manager doesn't seem to get updated very regularly, but the install packages on the plex.tv site are always up to date (need to do manual install) and the Plex Clients usually give you a notification saying the server is out of date.
  13. FORUM ADMINS --> Please close this thread. Keeping this discussion open is helping no one and all points have been made.
  14. Quite frankly, as a member of the XPEnoboot Team I take offense to this. As I explained our hands are tied. We can not release until Synology releases their open source tools & packages. If you are 'tired of waiting for new releases' then replace your XPEno boxes with Syno ones.
  15. Since everyone seems to be holding their breath for XPEnoboot with DSM 6 support, I want to remind everyone that the XPEnoboot team relies on Synology releasing the open source portions of DSM and the toolchains required to compile it. None of this has been released yet and we can not make a release without them. So for those of you holding your breath for a new release, maybe take a breather every now and then. (Short version: we don't know when Synology will release the DSM 6 source code, so we can't give an estimate as to when a new XPEnoboot version will be ready).
  16. I recommend downgrading. If you leave your machine in its current state and wait for the XPEnoboot release that supports DSM 6.0 your system will be in a corrupted state and will as likely work as not work. This has to do with how our patching system works (which I've explained in detail when I built it). Your best bet is to downgrade to a supported DSM version.
  17. Quick answers to OP questions: 1. We have modified the configs to enable more drivers. I believe there is an effort within the team to make the config file we use publicly available. 2. The synology binaries are patched at compile time and the patched binaries are copied over the original synology binaries during boot. These patches will not be released in the hopes of extending the time that they remain effective. The source code found on my repository (https://github.com/Jman420/nanoBoot-DSM5.1/) is extremely dated, but can give you a VERY GENERAL idea of how Xpenoboot gets built. Finally, i also agree with with TBK in that if your motherboard only supports x86 and not x64 then you are probably wasting your time since the builds of Xpenoboot (and DSM) expect an x86_64 architecture.
  18. Here is a big 'You're Welcome' from the XPEnology Crew and a huge 'Thank You' from us too. Everyone on the team really appreciates the patience that the community has shown us, especially around recent releases and understanding when releases are late or sometimes partially broken. Personally I am always impressed and re-invigorated when I see the community helping each other and solving problems without needing us. We could not have asked for a more intelligent, helpful community. In short, Happy Holidays from the XPEnology Crew to all of you. We hope you have fun and relaxing holidays and enjoy the vacation time that comes with it. Catch you guys in 2016! - Jman
  19. IPKG has not been maintained in years and I don't recommend using it since all of its packages are also out-dated. There is a newer project called Entware which is compatible with DSM (https://forum.synology.com/enu/viewtopi ... 40&t=95346) and is actively maintained by zyxmon (whom I've worked with in the past and is very competent). I recommend using Entware and if the package you are looking for isn't included then make a request on the Synology Forum Thread from above.
  20. To try to clear up confusion; XPEnoboot 5.2-5644.1 was released on Nov 8, 2015 and was developed against DSM 5.2-5644 with build date of Oct 28, 2015. The current DSM build which Synology is distributing is still DSM 5.2-5644 but with a build date of Nov 12, 2015. (See the spoiler section below for more details.) So clearly our release of XPEnoboot 5.2-5644.1 could not take into account a build of DSM that was created after its release. We are unsure of whether or not DSM will silently update to this new build without user intervention or if the new build will only be used for new installations. Either way as soon as we identified the issue we posted here to keep the community up to date. I hope this helps clear things up. [spoiler=DSM Version Details]DSM Version for XPEnoboot 5.2-5644.1 : majorversion="5" minorversion="2" buildphase="hotfix" buildnumber="5644" smallfixnumber="0" builddate="2015/10/28" buildtime="12:35:31" unique="synology_bromolow_3615xs" extractsize=553808 indexdbextractsize=16328 synohdpackimgextractsize=12404 packageextractsize=60740 DSM Version currently being distributed by Synology : majorversion="5" minorversion="2" buildphase="hotfix" buildnumber="5644" smallfixnumber="0" builddate="2015/11/12" buildtime="17:15:53" unique="synology_bromolow_3615xs" extractsize=553804 indexdbextractsize=16328 synohdpackimgextractsize=12404 packageextractsize=60740
  21. Synology has released a 'silent' update to 5.2-5644 which breaks our patches. There was no change to the build number or version, only to the build date. This is out of the ordinary and is also, clearly, out of our control. We are trying our best to test and release a new bootloader which is compatible with the new update. As always, please be patient with us, we are doing our best to provide a fix.
  22. In the migration from QNAP to Synology your data will be lost (make a backup!). DSM will not recognize the QNAP partitions and will ask you to reformat the drives. Since both systems install their OS to all hard drives I would recommend reformatting anyway so that you don't end up with both OS installed on your HDDs.
  23. Provide me with some instructions and if I have everything I need (hardware, time, clear steps & expected results, etc) I'll give it a shot. For the record I have no idea what the esx nfs plugin is. I should probably add that this policy applies to any features that the community wants added to the tests that I run. I would point out that all of my testing is done manually; so if you ask me to test something that takes more than 5 minutes to test it might not make the cut. Also keep in mind that just because something may be part of the tests that I run doesn't guarantee that it will work when we go to release. For the sake of getting releases out only core DSM functionality needs to be functional.
  24. I just tested a new boot loader build this morning. It looks like iSCSI allows connections, but doesn't provide any mount points or volumes. Trying to figure out if this it's a syno bug or something we introduced. Other than that things are running smoothly. Hopefully we will sort the iscsi issue out quickly.
×
×
  • Create New...