Not without a clearer description, including specific errors, the exact code triggering the error, the command it's compiled/executed with, and so on.

I fail to see how this topic has anything to do with the Linux Kernel, and so should probably be removed from this part of the forum.

This attachment shows some buggy features!

Attached Thumbnails

 

I've never seen any of these commands before. Are they bash aliases?

If they are and the names are in any way descriptive, then some of them look like the sort of thing you would never run from a console command line anyway. For example MyKernel.

Sure, but it's lacking the details that make it valid in any technical section, so... *shrug*


irajjs:
If you think you can demonstrate a bug in the Linux kernel, read this.

If you want help fixing bugs in your software, you should remind yourself of this, and provide relevant details. (And not as photographs!)

Well, there is the "general" section as well:
https://www.linuxquestions.org/questions/general-10/

Those and nearly 600 more commands are my own created programs
I have tried running them by many other programs such as konqueror, systemd, sed, plasma-desktop, autostart, Autostart, kdeinit,... etc
I tried using insmode and modeprobe as i said before
During the last 10 years i tried every possible option but since they were x-executable and because bash responds and shows some output I use konsole too! As you see they fail! Because the system/kernel are not designed to accept other than the parental sites software! And this is notaccording to what a free software agreement licence is!

As a last note:
If you really think tainting the Kernel can solve anything, you could build and include your own Kernel module(s), with which you can do a number of things.

And yes, it is possibe to make your own Kernel (fork), that's the freedom that comes with free and open source software.

Other than that I don't think this thread has anything to do with the Kernel, so please mark it as solved and continue other related discissions in the appropriate part of the forum.

This new attachment is another evidence of what kernel/system does!

Attached Thumbnails

 

Nah, those are to do with libstdc++ and libc, not the Kernel, so please mark this (kernel) thread as solved and ask further questions in the appropriate part of the forum.

dmesg is a command which shows kernel messages and libstdc++ /libc can not abort/terminate my programs! As shown in attachment1.

Exactly! It's the kernel which sends segfault messages to programs and it always logs those messages.
Why not?

I'm going to post once and unsubscribe, because the OP is at 26 posts at this stage, has divulged very little, and has learned nothing.

@OP This should have been sorted in about 8 posts. A segmentation fault is a memory fault.Run memtest86 on your pc and leave it running overnight. That will check the memory. These folks are being very patient with you. Make sure to thank them.

Read ALL of this: How_To_Ask_a_Question

Your box apparently boots. Check dmesg and your logs (the big ones) in /var/log looking for errors. Does X start? If not, you can use thye following trick to get the text into a file so you can copy and paste it into your posts. With your text highlighted, run

You're wasting your time, Business Kid. This user does not have a hardware problem. He has an attitude problem. He thinks that because Linux is "free software", he should be free to run self-composed mish-mashes of software that do not respect the internals of the OS. There's no cure for that.

1 members found this post helpful.

That is ofcourse unless he changes the OS, which he is free to do. I'm not an expert on the internals of the Kernel, but he can probably do that by tainting it with his own module, and if not, he can do it by forking the Kernel. Which brings this thread to a close in regards to the Kernel

Anyways, I think I will do the same as businesskid suggested.