LaylaOS with Mesa/OpenGL

This forums is for OS project announcements including project openings, new releases, update notices, test requests, and job openings (both paying and volunteer).
Post Reply
User avatar
mohammedisam
Member
Member
Posts: 36
Joined: Tue Jan 06, 2015 5:15 pm
GitHub: https://github.com/moisam

LaylaOS with Mesa/OpenGL

Post by mohammedisam »

Hi all,

I wanted to share with you this version of my OS as I finally managed to port Mesa. The classic gears example app is running in the screenshot below.

In addition, this version (0.0.6) comes with many updates:
  • Qt6 port
  • Complete rewrite of the desktop, taskbar and systray to Qt-based versions
  • A host of new desktop utilities
  • Support for X11-style mouse cursors
You can find the LiveCD and bootable disk images in the Releases page: https://github.com/moisam/laylaos/releases

As always, comments, feedback and bug reports are welcome.

Best,

Mo

screenshot4.jpeg
klange
Member
Member
Posts: 692
Joined: Wed Mar 30, 2011 12:31 am
Libera.chat IRC: klange
Discord: klange

Re: LaylaOS with Mesa/OpenGL

Post by klange »

Your collection of ports is quite impressive, especially with Qt on your own windowing system. I'll need to steal borrow some of your patchset for my own Qt port...

That said, I had a lot of difficulty while trying the OS.

While you seem to have SATA drivers, neither the live CD nor the hard disk install booted as SATA disks. While trying things in bash in the CLI, I seem to have hit a global limit on file descriptors and the whole system came down as a result. The live CD was constantly printing debug messages about the network interface. The GUI is also very slow and unresponsive, even when running under KVM - menus take several seconds to appear, even inside of apps. The Qt text editor froze and I could not exit it. Several apps seemed to just not load at all - I couldn't get Doom to start from the menu, for example.

e: I'm not sure if you're aware, but you seem to have every single git command installed as a separate instance of the binary on your disk image, rather than hard links or symbolic links, resulting in git taking up >1GB of space.
Post Reply