Sometimes it is better to COPY the Linux kernel (&includes) from a Live distro - effect: ZERO dmesg's about sr0 drive!

• Knoppix Linux distribution is good example. Compilation (Kbuild) is often (or very often?) waste of time - this, that switch – with SATA / PATA driver, .config-file IMO strange combinations — is time-waster. Linux should bring normality, NOT Windows-typed bugs (which one is hibernation spinning down HDD three times). [But actual Linux versions have THIS hiber-bug still – Torvalds IMO seems not concerned about it if this bug is... BY DESIGN. „Design = resign”.]. One problem [CD] you can resolve but other is, as far as I study code – algorithmic one. Knoppix launches even from GRUB (the ISO file placed somewhere...) and this technique should be recommended when dealing with new hardware (avoiding unnecessary compilations if they produce so many hardware - year after year....). Some DVD drive not lasted even about several months.
• Includes' have symlink – pointing to kernel includes (so important, without need to seach for ....-headers package)
• Kernel, now 5.10.10-64 seems a bit faster sometimes
• ZERO dmesg's about sr0 drive! No horkages, no CD driver speed limit

LuxCore uncrash stabilization Bash/Py scripts – Blender console rendering

Bash & Python toolkit to trick LuxCore Renderer plugin exporter/&standalone to the normality, with latencied preface descr... . Blender render preview is erratical & even distractionful. This is NOT full fix, but makes fun:: —Lux Standalone is for previewing rendering. And, 4abstraction(kosherization), •Standalone LuxCore UI window is for single, AND „unshown process” standalone script module is for animations (VERY QUICK **OPENCL** KERNELS RENDERING DESPITE RELAUNCHING BLENDER PROCESS). Trick to step above bad bug of SUSPENDING rendering „packet”: Blender+LuxCore+Python in combination. Even if this occurs only in „too complex” scenes – behind scenes is laziness of US programmers. AND By USA I mean whole USA worldwide collony. Occupation of minds by this, that, old, new versions of software & other inventions, –That rendering is known to be simply stable. BUT I TESTED IT – OPENCL KERNEL COMPILATION IS VERY FAST TO THIS POINT, –Both commandline & Linux, first script small & ultra simple, 2nd longer. FIRST CAN RENDER OPENCL ANIMATIONS BY SHORTLY RENDERING ITS KERNELS!!, –Application ver. Blender 2.80, •Lux ver. 2.2 . I don't bother with SSE3+ / AVX... instruction set motherboards „ultra super hiper–viper change of [ha ha] renewal” (in other words, pokemonnism). –Triade of softwares in packet, as I searched, can p r o b a b l y be repaired by new Python multithreaded ongoing version......... . Remember: All in USA is an experiment. This has heavy implications. Pokemonny nature of ppl is reflecting also on the programming spheres, informatics, IT tech. —thus, I decided NOT to inform forums additionally. USA has its „freedom” – I think that it should be read as laziness & more of the rome... . #strictness #LuxCore #standalone #combination #programming #OpenCL #Blender #script #tools #scientific #rendering #Bash #Python #KDevelop #crash #error #debugging #workaround #toolset #toolkit #GIL #GlobalInterpreterLock #buggy #solution #step #opencl #kernels #Featherpad #trick #hack #stability #test #unattended #preview #UI #ZRAM #listing #coding #clipboard #parcellite