Orlandox
Huoltovalikon jäsen
- Sijainti
- Pohjois-Savo
- Laitteisto
- Vu+ Ultimo 4K (2 x DVB-S2X, 4 x DVB-T2/C), OpenViX 6.6 Developer
Vu+ Uno 4K SE (2 x DVB-T2/C), OpenViX 6.6 Release
ViX Beta Tester
Member of OpenViX Dev team
OpenViX 6.7.001 julkaistu. HUOM ! Vaatii flashauksen + asetusten ja lisäosien palautuksen !
So what is different in OpenViX 6.7?
OpenViX 6.7 builds on the success of the 6.x series and aims to bring you the important things such as improved stability and bug fixes, rather than gimmicks.
The main change from previous versions to version 6.7 has been to upgrade to 5.5.1 oe-alliance-core branch. The OE (Open Embedded) core on which the image is built has also undergone major changes, updates and fixes, and uses the latest bitbake version. Version 6.7 uses Python version 3.12 which is on average 25% faster than Python 3.10 when measured with the performance benchmark suite. For more info on Python 3 major speed improvement see the official documentation. What’s New In Python 3.11 What’s New In Python 3.12
OpenViX 6.7 switches to udev (userspace /dev). udev is a device manager for the Linux kernel. As the successor of devfsd and hotplug, udev primarily manages device nodes in the /dev directory. At the same time, udev also handles all user space events raised when hardware devices are added into the system or removed from it, including firmware loading as required by certain devices.
udev supports persistent device naming, which does not depend on, for example, the order in which the devices are plugged into the system. The default udev setup provides persistent names for storage devices. Any hard disk is recognized by its unique filesystem id, the name of the disk and the physical location on the hardware it is connected to.
udev executes entirely in user space, as opposed to devfs's kernel space. One consequence is that udev moved the naming policy out of the kernel and can run arbitrary programs to compose a name for the device from the device's properties, before the node is created; there, the whole process is also interruptible and it runs with a lower priority.
Please note the following applications are not available on OpenViX 6.7 feeds yet: nodejs, kodi, stalker, openhbbtv, qthbbtv. These will be added as server time to build them becomes available. If you need them stay with the 6.6 image for the time being.
OpenViX 6.7 Released!
http://www.world-of-satellite.com/banners/openvix-logo.png Important notice: If you want to keep using OpenViX you need to donate towards keeping the servers online. Keeping OpenViX and this Forum online is getting more and more expensive. It is already February and so far donations...
www.world-of-satellite.com
So what is different in OpenViX 6.7?
OpenViX 6.7 builds on the success of the 6.x series and aims to bring you the important things such as improved stability and bug fixes, rather than gimmicks.
The main change from previous versions to version 6.7 has been to upgrade to 5.5.1 oe-alliance-core branch. The OE (Open Embedded) core on which the image is built has also undergone major changes, updates and fixes, and uses the latest bitbake version. Version 6.7 uses Python version 3.12 which is on average 25% faster than Python 3.10 when measured with the performance benchmark suite. For more info on Python 3 major speed improvement see the official documentation. What’s New In Python 3.11 What’s New In Python 3.12
OpenViX 6.7 switches to udev (userspace /dev). udev is a device manager for the Linux kernel. As the successor of devfsd and hotplug, udev primarily manages device nodes in the /dev directory. At the same time, udev also handles all user space events raised when hardware devices are added into the system or removed from it, including firmware loading as required by certain devices.
udev supports persistent device naming, which does not depend on, for example, the order in which the devices are plugged into the system. The default udev setup provides persistent names for storage devices. Any hard disk is recognized by its unique filesystem id, the name of the disk and the physical location on the hardware it is connected to.
udev executes entirely in user space, as opposed to devfs's kernel space. One consequence is that udev moved the naming policy out of the kernel and can run arbitrary programs to compose a name for the device from the device's properties, before the node is created; there, the whole process is also interruptible and it runs with a lower priority.
Please note the following applications are not available on OpenViX 6.7 feeds yet: nodejs, kodi, stalker, openhbbtv, qthbbtv. These will be added as server time to build them becomes available. If you need them stay with the 6.6 image for the time being.