592 replies to this topic

[WanWizard]

Correct, he is very busy with work atm...

[littlesat]

Where are your ofgwrite patches?

[Dimitrij]

Where are your ofgwrite patches?

https://github.com/o...is:pr is:closed

[Dimitrij]

[FlashImage] add flashing recovery image

[littlesat]

I cannot find the patches there that backup and put back the slots. And the changes you offer to enigma2 are again exceptions for kexec we should try to avoid. And that is possible when it was just covered as a normal slot and not as special slot zero… when it was made a bit more with a stealthy point of view.
I’m afraid we should not go for exception on exception.

Edited by littlesat, 12 June 2023 - 22:26.

[Huevos]

I cannot find the patches there that backup and put back the slots. And the changes you offer to enigma2 are again exceptions for kexec we should try to avoid.
I’m afraid we should not go for exception on exception.

Sorry to disappoint you but there is no standard. The whole multiboot implementation is exception on exception for every manufacturer.

Edited by Huevos, 12 June 2023 - 23:54.

[littlesat]

For the other multiboot I had a lot of discussions to get it aligned. At least I reached that all was driven by the startup files. This same standard the kexec implementation is using. So telling me there is no standard is a fairy tail. All implementations are using ofgwrite to flash the slots that is also a standard. What manufacturers do different is implementation. Because I arranged in the past that all in enigma2 was driven is doing via the startup files. Previously enigma2 did create these files with exception on exception which is already gone. I need me lot of time to get that arranged.

To get standards it is mandatory to discuss things and stop thinking your current implementation is the only possible and only good solution. The kexec implementation is made by the community itself. So we should set the standard together.

 

the current implementation does work. But the slot 0 mechanism is a kind of compromised for what was technically possible. It adds as implementation an exception because slot 0 is a special slot.

It seems we go in circles that cannot be broken when some of us are convinced the current solution is the most optimal solution.

[Dimitrij]

 

I think we should not do this…. First get it alligned. I prefer having a kind of recovery image or make the slot 1 a normal slot and arrange the other slots are somehow backed up on HDd/usb in a stealthy way via e.g. ofgwrite

 

See my comments. As it is now it is better not to get this exception slot flashed.

I suggested the simplest option for flashing the recovery image.

This, by the way, removes the multiboot, without the need to flash a new image via USB.

And this is used by other images. Why complicate things (reinvent the wheel). Moreover, I am 99.9% sure that no one will ever make some kind of code for ofgwrite.

 

P.S.I don't have to answer (something to prove), it's just thinking out loud.

[Huevos]

@Littlesat, Look in ofgwrite.

@Dima73, yes, everything is possible by couch flash in other images. No idea why PLi would want this limitation.

Edited by Huevos, 13 June 2023 - 08:35.

[littlesat]

@Littlesat, Look in ofgwrite.

Where?

[littlesat]

Then give it a normal slot number and cover it as nothing 'special'. For this no changes to enigma2 itself are needed...

 

I suggested the simplest option for flashing the recovery image.

This, by the way, removes the multiboot, without the need to flash a new image via USB.

And this is used by other images. Why complicate things (reinvent the wheel). Moreover, I am 99.9% sure that no one will ever make some kind of code for ofgwrite.

 

P.S.I don't have to answer (something to prove), it's just thinking out loud.

Edited by littlesat, 13 June 2023 - 10:15.

[Dimitrij]

 

Then give it a normal slot number and cover it as nothing 'special'.

This is not just a slot, but a slot that can turn on / off the multiboot.

 

For this no changes to enigma2 itself are needed...

And where, then, to make changes for this slot?

Again, let's say that the manufacturer is obliged to do this?

In this case, we will assign the guilty dpeddi

 

[littlesat]

It can still be a normal slot and when ofgwrite arrange backing up the other slots when they are on the flash and put them back it can be done stealthy.
When you remove kexec you should be warned
-or-
Arrange slot 0 will become a real recovery slot.

Edited by littlesat, 13 June 2023 - 14:59.

[Huevos]

 

@Littlesat, Look in ofgwrite.

 

Where?

 

Look through the code comments.

[littlesat]

When I need to look throught de code comments it is not stealthy…. I at least do not see anything that does the backup.

[Huevos]

When I need to look throught de code comments it is not stealthy…. I at least do not see anything that does the backup.

I was not talking about the backup.

[littlesat]

The backup is easy and can be created from each slot as you can find all in the /boot directory... (linuxrootfs1, linuxrootfs2 etc... kernel in zImage file)

 

Actually it would be 'nice' to have some kind of executable that does something with the OSD and can accept input from the remote control the recovery image can be a real recovery image... that is the most optimal situation I think.

 

I saw e.g. VIX made changes to enigma2 that arranges removing files/packages from the recovery image via e.g. the StartUp Wizzard when the image is in slot 0 and the box can do kexec. This is indeed something that can make the slot 0 smaller and more behave like a real recovery image. But at the end (and I hope all do agree) the most optimal we could have is one small binary with only some helpfull stuff (e.g. access to console via telnet/putty) that the OSD can work, the remote control buttons can be seen and you have something to select an image or flash an image in a slot.

 

Evaluating the situation by myself over the last days I think making the slot 0 stealthy is not an optimal idea.

 

For the time being as long this is not made (or even never will be made) we have to live with the current situation....

Edited by littlesat, 14 June 2023 - 14:34.

[Dimitrij]

By the way, my PR

[FlashImage] add flashing recovery image , it was a request from a user, which I fulfilled after spending a few days.

Edited by Dimitrij, 14 June 2023 - 17:10.

[littlesat]

I understand but it is kind of hacky with a lot of exceptions. And I’m afraid you lost the other slots without any warning.
I feel sorry. As every time better to discuss it here.

Edited by littlesat, 14 June 2023 - 17:12.

[Dimitrij]

 

And I’m afraid you lost the other slots without any warning.

I knew it.
I would add a warning in the next PR.
And what does the exception mean?
Do other manufacturers make multiboots equally?
Gigablue has its own way, Dags has another way, et8500 has a third way and etc...
Excuse me, but this is just some kind of demagoguery.

Edited by Dimitrij, 14 June 2023 - 17:21.