Linking an issue thread made by the person who asked you about it to them, wew.
- Status
Linking an issue thread made by the person who asked you about it to them, wew.
Alright, I pushed a new release that adds the reboot patch from AuReiNand (the one from ~11 days ago, thanks Aurora, the patch is all her work, or work from others that helped her). This means O3DS should be safe when exiting Smash Bros. or MH4U when launching another application, and N3DS can now use 178MB mode applications. This also means Mizuki will have a patched firmware.bin called patchfw.bin in /mizuki. If you ever update your injector.cxi, please delete patchfw.bin as well.
https://github.com/thedax/Mizuki/releases/tag/1.1
https://github.com/thedax/Mizuki/releases/tag/1.1
Last edited by daxtsu,
I have been testing the beta for @daxtsu since wednesday last week and so far have found it pretty sweet, it is exactly what it says on the tin... a barebones CFW for those that use sysnand only
I haven't found any issues with it and find it fast booting and very responsive
Please don't litter the thread with requests for features, there are other CFW for that, respect the original idea.. barebones, works well
Big thanks daxtsu
I haven't found any issues with it and find it fast booting and very responsive
Please don't litter the thread with requests for features, there are other CFW for that, respect the original idea.. barebones, works well
Big thanks daxtsu
If you are referring to the reboot patch request, that one was sort of mandatory. Without it, O3DS users could have ended up in a situation where they're in sysNAND with no FIRM protection, and that's dangerous.
- Joined
- Apr 13, 2015
- Messages
- 1,916
- Trophies
- 0
- Location
- Under Tomato Hentai's stairs
- XP
- 1,537
- Country
no i was talking generally
no chain loaders, no menus no bells, whistles etc lol
Not even rainbows and unicorns?
(Just kidding)
Not even rainbows and unicorns?
(Just kidding)
well, every CFW needs a Unicorn lol, I am sure in good time Daxtsu will add this feature
well, every CFW needs a Unicorn lol, I am sure in good time Daxtsu will add this feature
I have an idea in mind that would be cool, but I have no idea if it'll work, or if I can even do it, so there's not much to say about it for now.
Okay, I apologize if I just started a trend of removing features from a CFW and giving it your own name. I regret that decision in hindsight. The reason why I made a name change is because I want a clear indicator that my CFW does not support sig-patching--something I see as the "main" feature of other CFWs. But if other people are going to do this now, it's going to be a shitshow like the PS3 scene where everyone has their own "CFW". It seems like all this does is remove the emuNAND feature (correct me if that's wrong). I think all these "feature removal" stuff can be done with compile time flags and Makefile paramaters instead of warranting a new repo that farther segments the community. (Yes, I could have done that but I was too lazy.)
Please let the "CFW forking" stop here. It will only confuse new users more in a community that's already confusing.
Please let the "CFW forking" stop here. It will only confuse new users more in a community that's already confusing.
I don't think you started a trend so much, and I agree, I hope it stops here. We have three main "versions" of ReiNand (Cosmo was for your personal use, if I'm not mistaken, so that's why I said three): the original, which focuses more on emuNAND, AuReiNand, which tries to cater to both sysNAND and emuNAND users, as well as have lots of extras, and this one, which focuses on sysNAND exclusively. If I still had reason for emuNAND, I would've just stuck with the original. Since that's not the case, I initially took ReiNand and made it sysNAND only, but then I added a few other things I really liked from AuReiNand.
My intention was never to fragment anything or to fuel a trend. I just wanted to share what I found to be the most useful for my particular setup and desires. Now that we have one for emuNAND (vanilla/original ReiNand), one for sysNAND (mine), and one that does both with lots of features (AuRei), in theory there shouldn't be much of a need to fork Reinand any further.
In my opinion, the "good" way of doing this is that 1) every "removed" feature is changed to compile time flags and 2) every "added" feature is added in your fork. Do not change the name. Then once you feel that your branch is stable, submit a pull request to AuReiNand and your "CFW" would just be a different make paramater instead of a different project. This is how things should be done in an open source community. Forking (especially your fork which does not link back) leads to fragmentation which is bad for both developers and users.
When I made the repo, I actually did mean to fork it rather than make a new one, so the original would display. Is there a way to link back to the original once a repo has already been created? With that being said though, trying to make a pull request out of my fork back into the original ReiNand (which is what I forked, not AuReiNand) would probably be a nightmare, since I reorganised the majority of the code. That, along with things I borrowed from AuReiNand that I assume Rei isn't interested in (such as the reboot patch; he made it rather clear that he had no interest in that) means there isn't much to do, as far as I can tell. If he's interested in some of the stuff I pulled in, great, I'll gladly make a pull request, but I figured he probably would have done these things (loading the injector on the fly) from the start.
I apologise if I've upset anyone with this, but it's a bit late to take it back now. If nobody wants to use this CFW, that's fine. I said from the beginning that I made it for myself. Encourage others to use AuReiNand, ReiNand, RxTools, or Cakes rather than this if you (you meaning people in general) prefer.
(Note that the tone of this reply isn't meant to be harsh, mean or sarcastic in any way.)
Well democracy supports this CFW, so I guess by popular choice, it's here to stay. ;p
Don't apologize. Only yifanlu is bothered by this CFW merely existing. (ok, and Nintendo I confess
)I mean, Linux has been forked 72394 times and people actually say that's it's strength, lol.
Last edited by zoogie,
@daxtsu
Please do not change a thing, continue with the way you have started, there is most definitely a need and a want for this type of release
Plenty of room for all CFW, If people don't like one particular flavour then it is quite simple, don't use it
Please do not change a thing, continue with the way you have started, there is most definitely a need and a want for this type of release
Plenty of room for all CFW, If people don't like one particular flavour then it is quite simple, don't use it
Don't apologize. Only yifanlu is bothered by this CFW merely existing. (ok, and Nintendo I confess
I mean, Linux has been forked 72394 times and people actually say that's it's strength, lol.
Try bricking a Linux computer!
Well democracy supports this CFW, so I guess by popular choice, it's here to stay. ;p
Don't apologize. Only yifanlu is bothered by this CFW merely existing. (ok, and Nintendo I confess
I mean, Linux has been forked 72394 times and people actually say that's it's strength, lol.
@yifan_lu isn't bothered by this CFW existing, he is bothered by the fact that @daxtsu, by mistake (a human error, that's pretty normal), broke the common agreement with open source things creating a new project instead of forking ReiNand, that's understandable is you know open source. Linux can include non-GNU/Linux that do not use only open source code and that ones using as excuse the non-open source code to claim not being a GNU/Linux just to not follow the open source common agreement (not every distro, but some of them).
Btw, @daxtsu, I loved your work, please, keep it that simplistic, I hope we get the unicorn soon
I am going to be honest and blunt with you. No, they shouldn't stop forking CFW's, in fact, there should be more forks and CFW's made. The point of making a project Open source, is for others to see and even work on the source code. If someone wants to make their own changes and make their own take on a CFW, it's completely within their own power and right to do so, if the source is open. If the original creator did not want their CFW edited, they would have kept their source code closed off.
Honestly, I am happy to see the community doing the kinds of projects, it's giving options to those who want them. You want a bare-bone cfw without any bells and whistles? Now you have! You want something more fancy? You have options! I am running 4 CFW's on my sysNAND right now and I am god damn happy to see that, because it shows the community is actually interested in these projects.
Quite honestly with your mindset, that would be like telling Ubuntu, "Look, you're good, now there can't be anymore Debian forks." The entire open source community is built on a mix of original ideas and forks from those ideas. That's what makes open source an amazing idea, because it opens the door to new options and projects.
- Status
Similar threads
-
BakerMan
I rather enjoy a life of taking it easy. I haven't reached that life yet though. -
Psionic Roshambo
- K Kaden Kyarel
-
-
@
a_username_that_isnt_cool:
new smilie ^
its much better than the rest (except for the fact that only touhou fans really understand it and im not a touhou fan and yes its bad apple thats like the testing thingy
) -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
