Posted 16 April 2023 - 18:11
Don't think it is a must have, but it is a very, very, nice thing to have 
.
Not only because space is at a premium, but also because more than with other images, OpenPLi users are real end-users, and a real recovery image will prevent them from using slot 0 and potentionally break it.
Posted 16 April 2023 - 18:14
Don't think it is a must have, but it is a very, very, nice thing to have
Not only because space is at a premium, but also because more than with other images, OpenPLi users are real end-users, and a real recovery image will prevent them from using slot 0 and potentionally break it.
I agree it's a "nice to have", it just seems (maybe I am understanding it wrong, that others feel it is a "must have").
As I said, previous to multiboot being an option, 2+ gb of free space was being wasted (un-used), so using 250mb max for a recovery only slot is not a big issue imo, (you gain the use of more than you loose 10-fold).
As for the end users, I think most understand what the slot 0 (recovery) is for and understand the reasons for suggesting it is not used for daily use, but at the end of the day, you can't hand hold everything for everyone.
Edited by Ev0, 16 April 2023 - 18:15.
Posted 16 April 2023 - 18:49
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 16 April 2023 - 18:53
+1
Groetjes Cobus R
VU+ UNO 4K SE FBC DVB-C (8x)
MUTANT HD66SE FBC DVB-C (3x)
MAXYTEC MULTIBOX COMBO
MUTANT HD60 DVB-S
Ziggo (digitaal) Kabel TV (FTV) op alle decoders met oa fallback tuner
Posted 16 April 2023 - 19:00
When you tell the image in slot 0 is not the image that should be used it can better be an extreme small image with only a boot selector and something to flash.
So make the magic image then
Posted 16 April 2023 - 19:28
When you tell the image in slot 0 is not the image that should be used it can better be an extreme small image with only a boot selector and something to flash.
So make the magic image then
Creating a real recover or a stripped down image means that someone have to maintain and build another image for each box
Posted 16 April 2023 - 22:07
. There is simply an opening here for an improvement..:/ for no it is added value but still not optimal.
Edited by littlesat, 16 April 2023 - 22:09.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 17 April 2023 - 13:32
When you tell the image in slot 0 is not the image that should be used it can better be an extreme small image with only a boot selector and something to flash.
The factory image is the best option for it
Well openpli images are also less in size comparing to other teams builds.
DM-900 ,DM-520, Vu+Duo2
Posted 17 April 2023 - 13:57
Well openpli images are also less in size comparing to other teams builds.
Then it is a good idea to put an OpenPLi image in there 
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 17 April 2023 - 13:59
The factory image is the best option for it
How do you implement vu+ / kexec multiboot python3 code into a closed source factory python2 image with no support from the factory ?
Edited by Ev0, 17 April 2023 - 14:00.
Posted 18 April 2023 - 22:26
Posted 18 April 2023 - 22:31
It is not for you (or for us) to decide who this is useful to.
If we implement something it must be (made) end-user proof.
Posted 18 April 2023 - 22:33
Excuse my usual intrusion, but multiboot is of little use to the normal user because actually switching from one image to another for the simple sake of doing it is absolutely ridiculous!
What is it for the normal user?
It is only useful for those who are curious about the "profession".
I understand that it is a "challenge" but only for......
krime mobile.
We heard (and ignored you the first 2 times).
Posted 19 April 2023 - 09:16
Excuse my usual intrusion, but multiboot is of little use to the normal user because actually switching from one image to another for the simple sake of doing it is absolutely ridiculous!
What is it for the normal user?
It is only useful for those who are curious about the "profession".
I understand that it is a "challenge" but only for......
krime mobile.
For the normal user ( whoever that may be) there are some basic uses of multiboot….
1) upgrade to a new version without replacing the working image, means that the user minimises any issues with the new release.
2) some users still want python2 plugins that haven,t or cannot be converted to python3, so running both a python 2 and python3 image is possible with multiboot.
3) some normal users even have sufficient interest to try other images, whilst keeping their existing image.
Of course some users will just accept what they are given.
Edited by twol, 19 April 2023 - 09:16.
Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
.........DVB-S2X into 90cm dish (27.5W)
Octagon sf8008, AX HD61, Edision Osmio 4K+, Zgemma H9Combo using Legacy ports on multiswitches
Zgemma H9twin & Zgemma H9 C/S mode into Giga4K
Posted 22 April 2023 - 01:38
When you tell the image in slot 0 is not the image that should be used it can better be an extreme small image with only a boot selector and something to flash.
Open Vision sources: https://github.com/OpenVisionE2
Posted 22 April 2023 - 11:20
Looks like what I build for my XP1000 cardserver .
Like I wrote before, the challenge isn't creating a minimal bootable image. The challenge is writing and maintaining the recovery app.
We looked at porting the HiSilicon solution, but that is tightly integrated with their bootloader, and therefore difficult to adapt.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 23 April 2023 - 10:30
Just change the "alternative url for images listed on Flashimage" (Menu - Setup - System - Customize) into 'all' and all images will be visable.
And If I do, where do I leave my alternative URL?
Posted 24 April 2023 - 05:51
I think that’s a forgotten option….
Aan de rand van de afgrond is een stap voorwaarts niet altijd vooruitgang....
On the edge of the abyss, a step forward is not always progress....
Hardware: 2x Daily used Vu+ Ultimo 4K - Vu+ Duo 4K SE and a lot more.... - VisioSat BiBigsat - Jultec Unicable Multiswitch 4 positions: 19.2/23.5/28.2 East - Diseqc motorized flatdish antenna
Software : HomeBuild OpenPLi Develop and Scarthgap builds, local cards driven by OsCam
Press the 
button on the buttom right of this message
Have you tried our wiki yet? Many answers can be found in our OpenPLi wiki
Posted 24 April 2023 - 09:45
I just reviewed my notes regarding the time I designed the on line flashing and in this note I found that for foreign images I had the idea not to add for each image hardcoded a feed, but put it in one json feed. So every image offers their own json feed that also can include the images from other image builders and where also the differences in box names could be solved. So that what becomes in the feed is not done in enigma2.......
So when OpenPLi will offer OpenATV and Open VIX feeds then we can parse the feed from them on our 'servers' and offer a json list that includes them...
So basically having one feed, one alternative feed (for home building) should be sufficient....
Unless this adding filters to the code to select image builders yes/no can still be added in enigma2.... But having multiple feeds was something I never suggested and I think this is also not really a smart solution....
So I prefer to get rid of this:
FEED_URLS = [
("openATV", "https://images.mynonpublic.com/openatv/json/"),
("OpenBH", "https://images.openbh.net/json/"),
("Open Vision", "https://images.openvision.dedyn.io/json/"),
("OpenViX", "https://www.openvix.co.uk/json/"),
("OpenHDF", "https://flash.hdfreaks.cc/openhdf/json/"),
("TeamBlue", "https://images.teamblue.tech/json/"),
("Open8eIGHT", "http://openeight.de/json/"),
("OpenDROID", "https://opendroid.org/json/"),
("EGAMI", "https://image.egami-image.com/json/")
]
Edited by littlesat, 24 April 2023 - 09:48.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 24 April 2023 - 10:12
@Littlesat, I don't know what you mean by this. If there is a name difference the image will just not be present and the request will return empty.
OpenViX has had OpenPLi available in its ImageManager for years and no one has complained it doesn't work.
On the other hand I think PLi's implementation where it shows all distros in one screen is wrong. In ViX we select the distro we want to download from and then only show images from that distro.
0 members, 11 guests, 0 anonymous users
