OsMINI4k
- Thread starter lme
- Start date
el bandido
TNAP-Images
Anyone that downloads the image and updates it will be on the latest version. It does not hurt to have the downloadable image back one update, and this is done on purpose for more than one reason. If for example, Vix 6.8.010 has problems, then reloading the image will put you back on Vix 6.8.09.
el bandido
TNAP-Images
It's not a fake. Let me explain to you what happens and maybe it will make sense. First, those numbers mean little of nothing except when it comes to tracking bugs or issues. Then the numbers may be invaluable.
An image is updated by building the files and uploading them to the server. Almost all of the files are in .ipk form, and I think your OpenVix image has roughly 9,000 files on the server. On every update, these files are updated in bulk. Only a few files may actually be updated, but all of the files are built --every time. So an update consists of updating the files, sending them to the server, deleting the existing files, replacing them with the freshly built ones.
An enigma2 image is a few thousand files bundled together. Only a few of the images files are usually updated, but every file that the image needs is built when the image is made. Then almost the same process is followed, send the new image to the server, delete the existing image, and tag the new image.
The minor 0.xx image build numbers from OpenVix can move either by updating the image or updating the .ipk files. Lots of times only the updated.ipk files will be sent to the server and not the updated image as doing both is just extra work and uses resources. It all depends on what the updates are.
On the TNAP build, you have been seeing lots of online updates of 60-70 files. This represents the enigma2 package, and if you change or edit one file, then all 60 or 70 files require a build. It is what it is. Understand how it works and you will be more comfortable. But to the average user, those small .0xx build numbers do not mean much if anything. And for someone in North America, those little updates probably have nothing useful in them.
Want to see what changed, then look on GitHub: Commits · OpenViX/enigma2
Scroll through the list of commits and you will see very few are helpful in North America. For North America, usually updating the Release version of the OpenVix image once every 3 to 6 months is a gracious plenty. If something is done to help North America, it is by accident. Europe is the target. OpenVix is a great image, but for us, no need to worry about updating it much....
An image is updated by building the files and uploading them to the server. Almost all of the files are in .ipk form, and I think your OpenVix image has roughly 9,000 files on the server. On every update, these files are updated in bulk. Only a few files may actually be updated, but all of the files are built --every time. So an update consists of updating the files, sending them to the server, deleting the existing files, replacing them with the freshly built ones.
An enigma2 image is a few thousand files bundled together. Only a few of the images files are usually updated, but every file that the image needs is built when the image is made. Then almost the same process is followed, send the new image to the server, delete the existing image, and tag the new image.
The minor 0.xx image build numbers from OpenVix can move either by updating the image or updating the .ipk files. Lots of times only the updated.ipk files will be sent to the server and not the updated image as doing both is just extra work and uses resources. It all depends on what the updates are.
On the TNAP build, you have been seeing lots of online updates of 60-70 files. This represents the enigma2 package, and if you change or edit one file, then all 60 or 70 files require a build. It is what it is. Understand how it works and you will be more comfortable. But to the average user, those small .0xx build numbers do not mean much if anything. And for someone in North America, those little updates probably have nothing useful in them.
Want to see what changed, then look on GitHub: Commits · OpenViX/enigma2
Scroll through the list of commits and you will see very few are helpful in North America. For North America, usually updating the Release version of the OpenVix image once every 3 to 6 months is a gracious plenty. If something is done to help North America, it is by accident. Europe is the target. OpenVix is a great image, but for us, no need to worry about updating it much....
I know that most of the images are focusing on European users & satellite fleet, but I didn't understand why vix image was updated for edision only, and not for Vu boxes ?
Vix image builders stoped official support for edision boxes (& others), last october, so I was questioning where the new update was comming from for edision stb. Vu stb was not on the discontinued support list.
Vix image builders stoped official support for edision boxes (& others), last october, so I was questioning where the new update was comming from for edision stb. Vu stb was not on the discontinued support list.
el bandido
TNAP-Images
Edision has not updated anything in years.
As for the "Orphaned" OpenVix Edision images, they are pretty much setup as an automated build and are built automatically once a day. If there is a problem and the build does not complete, then it restarts or retries the next day. I occasionally update the images, but mostly just update the .ipk packages, which equals an online update. Whatever is on or in the OpenVix and other sources is built --automatically.
As for Vu+ or why Vu+ has a different build number, I cannot answer that, but most likely the difference is when the Vu+ Vix feeds are updated as compared to the orphaned Edisions. Both Vu+ and Edision are currently retired from FTA as companies. Rumors of a "New" Vu+ receiver are making the rounds on the European forums, but I think you will find that receiver is roughly a 2018 receiver being advertised as "New". Watch and see. The first clue will be the kernel version followed by the chip version.
As for the "Orphaned" OpenVix Edision images, they are pretty much setup as an automated build and are built automatically once a day. If there is a problem and the build does not complete, then it restarts or retries the next day. I occasionally update the images, but mostly just update the .ipk packages, which equals an online update. Whatever is on or in the OpenVix and other sources is built --automatically.
As for Vu+ or why Vu+ has a different build number, I cannot answer that, but most likely the difference is when the Vu+ Vix feeds are updated as compared to the orphaned Edisions. Both Vu+ and Edision are currently retired from FTA as companies. Rumors of a "New" Vu+ receiver are making the rounds on the European forums, but I think you will find that receiver is roughly a 2018 receiver being advertised as "New". Watch and see. The first clue will be the kernel version followed by the chip version.