View Single Post
Old 07-26-2016, 04:30 PM   #708
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Right!
But back on-topic for a change . . . .

I can think of something we could do for the people who have boot-looped their Kindles.

Issue a 'patch package' for Kubrick.

There is only one Kubrick distribution and we control how it behaves internally.
So there is only one solution set to maintain.

What I imagine, is:
*) Install Kubrick on read/write media (USB stick)
*) Add our 'patch package' to that media
*) Boot Kubrick
*) Escape to command line
*) Run our 'patch package' (which would add u-dev rules and/or drop some scripts with mount points that we know will happen inside of Kubrick environment).
*) Then do something magic to make it all wait for a Kindle
*) Plug in bricked Kindle and re-boot the Kindle.

I.E: we wouldn't have to deal with every OS distribution in the world, only our own.
knc1 is offline   Reply With Quote