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

Patched sr0 loading (Linux CD-ROM) @udev: 5 TIMES OK now WHEN in /usr/lib/initcpio/hooks/udev changed into systemd-udevd -c 1 to avoid parallelization.

4 warm reboots + 1 full turn off/on power cycle so far.

Seems NOT to be a problem with master/slave statuses in BIOS — bigger probability that udev sequence is a solution, more tests required. Some null BIOS entries also turned into manual none option – but correlation is with udev command (below). We have several udev command, but this is a initial one.

Part of new initcpio hook – remember to mkinitcpio -p ... to recreate CPIO

(...)

    quiet="$(getarg quiet)"

    if [ "${quiet}" = "y" ]; then

        /usr/lib/systemd/systemd-udevd -c 1 --daemon --resolve-names=never >/dev/null 2>&1

    else

        /usr/lib/systemd/systemd-udevd -c 1 --daemon --resolve-names=never

    fi

(...)

The cost is is booting is slower, black screen. Not the same as Porteus distro.

But better than to replace the udev, or bothering with SysV IMO nonsense.

When with systemd we have soft-reboot, containers (for example, an additional user-mode Debian in the form of a fs tree) and good status-info system with systemd' commands and wrappers (timertab program is one interesting wrapper example).

One most important thing is that udev has two „parts”: the main system's one -and- the initcpio one.

Thus, there is the necessity to update initcpio files.

Testing DVD mastering suite was k3b application – outputting diagnostic messages to terminal emulator (after usual-slower k3b init). If I remember, is is important – early mounting CD doesn't suffice when after „umount” situation can return the same. This is reason to check it with k3b, and additionally, this app has CD verify option within burning process (a contrario to xfburn).

Linux has several mainline BUGS. One with CD-ROM, second with REDUNDANT SPIN-DOWN during hibernation.

One can think that US programmers aren't lazy... NO, NO..... reality is that bunch, BUNCH of them are derailed persons. Why they concentrate on „new, new new”??!!!! Even kexec reboot is their amnesia.

Testing /lib/modules-load.d/cdrecord.conf interference (of cdrecord package)

Still bugs – this ZEROS want to „create” new forums to boast it. They simply need new bugs in disorder to announce that they make „progress” and work. An paper SHIT of work... . This Linux sado-masochists, as other masses, stay at old BIOS traditions of bug, bugs, bugs. Crappy apes to boast with other liars, and shit cycle of „you can”. Idiots using new SSD, while Linux allways have big amount of small files. CAN YOU UNDERSTAND WHILE I NOT USE „CANDY” WORD „DIFFERENT” STUPID OVERSCIENTIFIC SHIT?

And why „sg” module in other place than udev? You put in in udev, crap... maybe and you stupid talking you made new distro? Aha – you already taked that systemd is „bad”... what in exchange, USA without future?

And you even cannot tell your people at start, that systemd-udevd DOES IS in the initcpio (I found it by using lsinitcpio command). If  y o u   can't explain work of basic system tool, why you open APE-epic mouth at forums (OFTEN W/O EVEN ONE REPLY YOU FALLIING AMERICA). USA is the place of corruption, lie, colonialism, void „oy” „oy” things.

Possible RACE CONDITION?? Could not initialize device "/dev/sr0". Already updated kernel, NO EFFECT – STRICTER: A HALFY (0.5) EFFECT.

HALFY (0.5) EFFECT. Race condition... – as in life...

Next example how STUPID are open source guys. Similar problems are with NVIDIA – everything seems to depend on random & initrd (MB size!??).

–or– maybe udev rules loading randomly in order?

Yes, systemd is so bad. I experienced it – cannot help in system-wide „threads” – a queue of driver modules. How to hard-core it in startup process??

HOW SHIT YOU ARE, USA.

Then, I cannot stand on POV that Linux is better that Windows. BOTH are faulty, source of bugs.

On Linux, you see plenty of it. One (more) example Xorg can't start sometimes, HALFY it can simply.

It's random. But in reality, a random means that if don't know the real cause – yews, simply. Nothing more. No bigger threading study here, then.

... and, you don't know precisely how to remove fsck runs. Trust a „new” boot parameter or not?

In IT, something new can't mean useful. I contains plenty of, even most stupid (3×HD spindown by s2disk, in summary) –things.