Because I inherit a lot of stuff … so far I upgraded my sister to a Lenovo Thinkpad and inherited her old Toshiba Satelite that I also bought for her many years ago and upgraded to a Western Digital Blue 1TB SSD … now I get it back and looking at playing with something a little different this time … mind you this is my first foray into Intel anything territory … been AMD/Nvidia since day one (minus the PS/2 years) (toss in some Cyrix/Nextgen) and another one I can’t even remember the name of … so I been looking at Kalpa just because It’s based on TW and has transactional/immutable/etc… stuff I’ve never dealt with before …
Whatta you think? BTW … Kalpa … you could use a couple screenshots on your website hightlighting why I would want to try your distro over others …
Edit: Also happens to be my first Laptop …
I’m not sure that providing screeshots would really offer anything of tangible/unique value. Is the overview not enough? It you like openSUSE Tumbleweed, and you like the concept of transactional updates then give it a whirl.
FWIW, I’m enjoying using Slowroll on the first laptop I ever dedicated solely to openSUSE. (Previously, I’ve always stayed with dual boot set ups, especially for those machines used for work.)
It may not provide much real info but people like to click on stuff and say "Ooooh … that looks nice … " Screenshots aren’t about “tangible info” they’re about getting people interested in the nuts-n-bolts and saying “why this and not that?”
What screenshots do you think might help ‘sell it’ to inquisitive types? I mean I can understand screenshots of the Plasma desktop in general if I wanted to know about the look and feel perhaps, but what about from a Kalpa-specific POV?
Gimme a visual example of why transactional updates are good for me, why is microOS good for me?
I can give you a visual example of why TW should include vkconfig/vkconfig-gui in the tools rpm … yet you don’t … why?
That’s what I though you might say. Fair enough. 
I’d love to hear from the @sfalken … just as a “ballpark” sorta thing
1 Like
Really !?! … cause that’s not how I roll … 
Each to their own! It’s essentially Tumbleweed with a delayed release pace. Up until recently I have stayed with using Leap (I still have it running on one machine as a guest OS) - a conservative operator I guess.
I’m just the opposite … I tried to put the CUDA SDK on a 13 year old machine with 8 GB of memory and a 750ti … trust me … just don’t … 
@dart364:
Please be aware of the following issue related to “newer” Leap releases and possibly, therefore, also, Kalpa – <openSUSE SDB:System upgrade - Major changes>
Leap 16.0 will no longer run on machines that do not support x86_64-v2.
> ld.so --help
.
.
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
>
This machine supports x86-64-v2 and x86-64-v3 but, not x86-64-v4 …
BTW, in my collection I have a Lenovo G505s – manufacturing date 13/11/08 « 2013 November 08 » – which is happily running Leap 15.6 but, I suspect that, I won’t be upgrading it to Leap 16 – need to check with “ld.so --help” the next time I boot it …
The Kalpa roadmap includes dropping support for x86_64-v1 and v2, even though the current installer does support installation on that hardware.
We also don’t support BIOS booting.
Just food for thought.
2 Likes
@sfalken Thank you for the info
@dart364 because openSUSE is a Do-ocrity, if you want something and it’s not packaged up, jump on OBS, build (from source, no binary blobs), submit and maintain for everyone to enjoy…
Hi @malcolmlewis … been looking at OBS … but Opensuse is already building Vulkan (correct?) and it should be there along with vkcube
@dart364 It is not present these days in the current source…
hmmm … it’s present in my source vulkansdk-linux-x86_64-1.4.309.0.tar.xz from the vulkan website and I’ve built it (after some hack-arounds for python) It wants /usr/bin/python so I just symlinked it to /usr/bin/python3.13 … even after I installed the python and vulkan patterns
@dart364 ok, not sure what your confused about, openSUSE uses the Kronos Groups version of Vulkan (NO vkconfig etc) not the LunarG version… openSUSE targets the end user, not the developer…
