Talk:Bootlace

From iDroid Project

Revision as of 16:25, 13 October 2021 by Rekoil (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

To Do

1.0

  • [FIXED] Change path path to remove Documents folder as its not a standard directory.

1.0.1

  • [FIXED] Fix one time display popup appearing twice if settings are reset.

1.1 2.0

  • [DONE]iDroid download and install feature.

2.1

  • [IN PROGRESS] Flash OpeniBoot from within iOS

1.2 2.2

  • Configure OpeniBoot options using menu.lst in a GRUB-like style
  • Theme OpeniBoot

The Future

Thanks to Bluerise and CPICH we can flash from iOS to NOR. Next plan is the grub-style OpeniBoot. After this I intend to drop support for installing iDroid via Bootlace. Instead iDroid and other OSes will be managed by dpkg & debs. Bootlace will revert to its intended original plan as a companion to OpeniBoot. Installing, upgrading, configuring.

By this, do you mean host iDroid as a deb with Bootlace, hosted on a community repo, as a dependency? -Rekoil (talk) 12:04, 9 October 2021 (UTC)
Not as a dependency. Rather Bootlace will link to the Cydia page OR possibly I'll work in a way of controlling the APT backend. As for repos I think it should be on our own repo and Bootlace can have our repo source as a dependency. --Neonkoala 13:07, 13 October 2021 (UTC)
So: Bootlace hosted on community repo, distributions hosted on our repo, Bootlace has our repo, hosted as a package on a community repo, as a dependency? If so, then people could just install our repo and install the distributions without Bootlace, do we want this?
I think it should be like this, distributions hosted wherever they are wanted, with Bootlace (on a community repo) as a dependency, that way, when someone attempts to install the iDroid package, they will also install Bootlace, enabling them to install OpeniBoot from there and boot into iDroid. Maybe remind them that installing OpeniBoot from Bootlace is also necessary before being able to boot iDroid, otherwise they will flood the forums with "HALP! NO IDROIDS ON MY IPHOWNQQQ!!!" Oh, and also, maybe we should add an nvram flag to OpeniBoot, make it not display the android option if no android build is present in /var/idroid (or whatever), determined by Bootlace. --Rekoil (talk) 16:23, 13 October 2021 (UTC)

Comments

See if planetbeing wants to post about Bootlace on his blog? --Rekoil (talk) 18:54, 22 May 2022 (UTC)

I want to get the openiboot changes merged before I think about stuff like that. I'll probably get it on a community repo once they are merged. --Neonkoala 09:05, 23 May 2022 (UTC)

Could this be ported to android? or does it not have the hardware access --Wrightcj01 12:46, 23 May 2022 (UTC)

I haven't looked into this yet but I will do soon. I should think the only requirement is that openiboot sets up the NOR and makes it accesible in the preboot loading. Obviously the nice APIs/tools won't be there that I'm using in iPhone OS. However the nvram utility's source is available from Apple. [1] Of course there's no IOKit so porting it won't be easy. --Neonkoala 13:27, 23 May 2022 (UTC)

OpeniBoot scripting features?

Are you using my scripting feature in openiboot which I set up (and was merged in planetbeing tree)? --Dranfi

Unfortunately not. It was what gave me the idea to make openiboot do all this but your scripting solution doesn't work in a way that can accomplish these things. Your scripts can only be run after choosing a menu item. A lot of what bootlace configures is done at initilization so I use NVRAM flags instead. I have had another look at your scripting and it looks like it could be used however in combination with my current modifications to allow bootlace to write a script to update openiboot. I had been looking to accomplish this via a kernel patch and flashing the IMG3 directly but that's beyond me currently without help. --Neonkoala 09:11, 8 June 2022 (UTC)