ayush_xeneva
Our custom kernel, Aurora, is built to handle real-time priority based interrupt handling, minimal IPC overhead & focuses on minimizing abstraction layers to achieve low latency and optimization.
Codebase is open for feedback here: https://github.com/manaskamal/XenevaOS
We're a small team and we’d love to hear from people who have worked on custom kernels or XR display stacks. What are we missing?
Show HN: Launching Our XR-Native Operating System
https://explore.getxeneva.com/
Hello HN, we are thrilled to announce that we are now launching the Beta Version of XenevaOS as a sandbox next month. For the first time, you’ll be able to experience our Free & Open Source Operating System that has been written with a custom kernel from the ground up for XR.The finished version of the Operating System is targeted to run on XR (AR/VR/MR) devices natively in a standalone...
Ask HN: Use-Cases for an Operating System with a Custom Kernel
If you were to be given an Operating System with a Custom Kernel, what features would you want it to have and what problems would you want it to solve?We're currently building an OS by designing the Kernel strictly for XR, but we're interested to know what the community has to say.
We intend to plain a clearer picture with proven results of what we're doing in the coming few weeks and months. Stay tuned!
It currently doesn't support any open standard but we're targeting OpenXR standard and also some native way of application writing where developer doesn't need to care about whether they are writing for XR devices or other devices. The OS will take care of it.
Currently we are more focused on building a lifestyle product experience, which includes Games, Entertainment and general daily use cases like navigation, etc.
Stay tuned for our Public Beta/Prototype showcase scheduled later this year!
Also you're right in one sense about how building a new kernel from scratch may not be the best way to tackle XR. But our whole point in creating this kernel was to be able to solve issues like latency and resource optimization on a completely different level and create a lively playground/environment for both software developers and hardware engineers to work on.
Basically, we're currently actively working hard towards proving the claims and fulfilling promises that we're currently making!
We've scheduled a prototype launch later this year. We would make much more progress till then and the public would get proven answers from our side once that happens!
Coming to the "vids or it didn't happen" feeling, we totally get that as well. To be fair, we would've had the same feeling if we watched ourselves from a third person perspective. But we're actively working on bringing visible proof (benchmark is a better work) on the claims and promises that we're making. And in your analogy, the vids are coming soon, stay tuned ;)
It's kinda hard to have a single answer for this but we like to think that this project did not work out for META particularly. We believe that it was perhaps not the right project for someone like META who already had other on-going projects to deal with. Although a setback, it doesn't necessarily mean there's a fault in the idea itself. We'd like to address the problems that were mentioned with the development of a custom XROS -
1) Cost : We've managed to do everything up until this point at the cost of 0$. However, we're in initial stages and expect to incur costs in the next few months. But those costs are mostly associated with building the company and our own line of products, not in the actual development and engineering of the OS. We've managed to remain extremely cost efficient and intend to continue that practice.
2) Burden on third-party/new developers : We anticipated this problem right when we started building the OS. Over time, we've come up with plans to encounter it and are currently working on making sure that the barrier to enter and create applications and software on Xeneva remains as non-existent as possible. We intend on making the process easy, try to bring no learning curve whatsoever, thus allowing developers to port their existing software and applications to XenevaOS conveniently. Also create a beginner friendly environment so that new programmers are able to create an app on XenevaOS from scratch easily.
App development wouldn't necessarily be the only functionality of AI in the OS but it will definitely be a primary one.
Show HN: An Open Source XR(AR/VR) Operating System
We're two college students building an XR(AR/VR) native Operating System with a custom kernel. We're also Open Source so feel free to check our GitHub Repository- https://github.com/manaskamal/XenevaOS .The journey hasn't exactly been easy, we've been criticized by a lot saying that whatever we're doing is impractical and that we're too ambitious. Regardless, we've...
Thank you, Team Xeneva.
Team XENEVA.
Xeneva is built from scratch with modern hardware and modern computing on mind. We're working on making a transitional shift from legacy systems. You can refer to our website, getxeneva.com to get a hint about our purpose, future goals and vision!
Thank you, Team XENEVA.
It's possible to run the system using Hyper-V. Required configuration are clearly mentioned in the documentation. Windows add extra security called Virtualization Based Security which needs to be disabled while running XenevaOS. Xeneva is well tested on VMware Workstation Pro and Virtual Box. We're working on real machine support, making the project to be beyond hobby os project.
XenevaOS is built from ground up with modern computing in mind. We're currently working on bringing it to XR systems (AR/VR devices). Compared to other OS, Xeneva doesn't holds legacy legacy hardware code which make it easy to focus on modern technologies. The project aims to be multi architectured, minimal abstractions in software for better performance and to put user as first priority rather than user fixing software requirements.
You can refer to our website, getxeneva.com to get a hint about our project's purpose, goals and vision!
Thank you, Team XENEVA.
- Xeneva is not intending to be Unix like, but some core principles of Unix are followed.
- Xeneva has its own libc implementation called XECLib that are attached to Xeneva's own system call interface.
- Xeneva supports IPC via shared memory, IPC via socket and IPC via its own message based communication called PostBox IPC. Xeneva currently use framebuffer for Graphics Output, no working video driver is implemented. The framebuffer is mapped onto Windows Managers address space and the Windows Manager composes the final image to framebuffer by writing to that mapped virtual address.
- Xeneva uses PE format for executable,no doubt ELF support can be implemented. XELoader is a dynamic linker and loader process which is responsible for resolving running processes symbols by linking it to its specific shared library. Whenever a new process get spawned,and an executable is loaded, the XELoader loads all required shared libraries and link them to the process.
You can refer to our website - getxeneva.com to get a hint of our future goals and vision.
Thank you, Team XENEVA.