Hacking Is it possible to "dual boot" 2 CFW's

[Deleted member 414991]

yay, I succesfully baited 5 pages of cfw war
go me

 

[adrifcastr]

HorizonM doesn't have a kernel extension you dolt.

I remember to the thread and also the repo pointing it out as the "first custom 3ds sysmodule"

 

[sp3off]

yay, I succesfully baited 5 pages of cfw war
go me

The medal of the CFW talkabout warrior.

 

[SciresM]

Wow HZMod also is a custom sysmodule, that doesn't turn it into an actual custom firmware, if somone presents me something like the linux 3ds project (which doesn't really do that much atm) that boots a complete different os, thats a custom firmware

I would like to propose we refer to Luma et. al as "customized firmware", since the "custom firmware" label is apparently inaccurate and we're all pedants.

How does "CFW" sound as an abbreviation to everyone?

 

[adrifcastr]

yay, I succesfully baited 5 pages of cfw war
go me

well you started it Mr.Luma so don't complain about it.

 

[sp3off]

I remember to the thread and also the repo pointing it out as the "first custom 3ds sysmodule"

There is also differences on the way it works. Considering that both are sysmodules, they do not patch at the same destination.

 

[proflayton123]

The war over CFWs is quite petty.. don't blame AW for leaving the 'public' scene of things.

 

[gnmmarechal]

It runs a custom sysmodule with a kernel extension, that's pretty actual-cfwy to me.

hmm

eh, we don't actually have a definition on how much of anything needs to be custom enough to be a custom firmware, so fair enough.

 

[Deleted member 414991]

well you started it Mr.Luma so don't complain about it.

?
Why would I complain? This is all hilarious.

 

[adrifcastr]

I would like to propose we refer to Luma et. al as "customized firmware", since the "custom firmware" label is apparently inaccurate and we're all pedants.

How does "CFW" sound as an abbreviation to everyone?

Yeah, customized is actually the best term for 3ds signature patchers, can we just take that and use it instead of custom? that would make some things clearer to some people

 

[astronautlevel]

The war over CFWs is quite petty.. don't blame AW for leaving the 'public' scene of things.

She's still publicly available, just not on temp.

--------------------- MERGED ---------------------------

Yeah, customized is actually the best term for 3ds signature patchers, can we just take that and use it instead of custom? that would make some things clearer to some people

You missed the joke. Completely.

 

[sp3off]

But now, the thing is we are completely off-topic talking about preferences and "blabla cfw and bla bla yeah better etc etc.."

 

[SciresM]

Yeah, customized is actually the best term for 3ds signature patchers, can we just take that and use it instead of custom? that would make some things clearer to some people

The problem is that "customized" gets naturally abbreviated as "custom"...

I think the best solution is just to roll with the terminology and suppress the urge to be pedantic over a distinction that's pretty meaningless these days in the face of patchers doing genuine kernel extensions.

You'll probably like my next 3DS release, but it's a while away.

 

[Deleted member 414991]

You'll probably like my next 3DS release, but it's a while away.

Damnit, now you're just fucking with us.

 

[astronautlevel]

Damnit, now you're just fucking with us.

It's pretty neat

 

[SciresM]

It's pretty neat

It also provides zero new functionality to end users!

 

[sp3off]

You'll probably like my next 3DS release, but it's a while away.

Oh mah gawd, cannot wait to see that !

--------------------- MERGED ---------------------------

It also provides zero new functionality to end users!

Ah.

 

[Deleted User]

By duel boot you mean run 2 different cfw's correct? If so you may want to run bootctr9 with ctrbootmanager.Thats pretty much what I run so I can switch between luma,reinand,cakes and corbenik (the bin version with working splash screens before the dev ditched the unfinished firm version)

 

[Aurora Wright]

The reason I started Luma in the first place was because I liked ReiNand's "just works" approach (over Cakes' manually selecting everything approach) but I didn't agree with removing sysnand support in a old reinand release. I then made it work on O3DS by using the firmlaunch patch code from Cakes. I then started adding features (thanks to Tux and Delebile too), made it work with CTRNAND FIRMs (still with simplicity in mind, only one file needs to be copied to SD now), and for the same reason made it so patches which have no downside to the user are always enabled or enabled when needed (as an example FIRM protection isn't enabled for EmuNANDs). You're free to think that any patch should be toggleable even when there's no downside, but this is why this even existed. What you shouldn't do though is going around shitting on Luma saying it's "bloated" (which means nothing, as the extra features have no negative effects for anyone not using them, and as a whole the patching of *everything* takes *a few milliseconds* at most, we actually timed this once). When a patch has downsides (see the AGB_FIRM logo patch which makes some romhacks not work, or the "Show NAND in System Settings" which users might want to disable for cosmetic reasons) I made it possible to turn it off.

 

[CrimsonMaple]

If the primary loader for a platform (as B9S does) provides argc/argv, all applications designed to be run on the arm9 can and should expect it -- that kind of standardization of execution environment is part of what I mean by saying it's a platform.

Luma, as far as I'm aware, complies with this in order to support payloads that rely on this standardized execution environment, as it should.

Payloads can ignore what's passed to them trivially, by simply overwriting the contents of R0 and R1 in init and thus losing argc and argv....but every chainloader should (and does, presently) comply to the standard to support the payloads that rely on it.

Ah! Thank you for clearing that up!