Linux - Reddit – Telegram
Linux - Reddit
760 subscribers
4.18K photos
207 videos
39.8K links
Stay up-to-date with everything Linux!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Download Telegram
Does that linux kernel internally use multiple threads ?

In kernelspace, does does linux kernel execute instructions in a sequential way, or there are cases in which the kernel itself will be processing multiple instructions internally ? Does the kernel internally spawn multiple threads for some tasks ?

https://redd.it/mp7cgi
@r_linux
Is it worth going through version 2.6 of the kernel?

I recently got the book Understanding the Linux Kernel 3rd edition. I noticed that the book goes through Linux 2.6, so I’m wondering before diving into 800 pages if it’s worth going through this version or if I should get more up to date material.

If you think I should go over more recent material, any recommendations?

https://redd.it/mp25zb
@r_linux
I'm teaching Linux Command line fundamentals for free

I teach about command line and linux in general on discord anyone interested can pm me to get the discord link. Apart from this on the discord I post resources, and you can ask anything related and meet people also interested in computer science in general. I am looking for mentors and teachers as well so anyone willing to teach can also join!

https://redd.it/mp9vzz
@r_linux
What is the best kid friendly distro for kid ?

I don't have anything for my sister birth day. So i decide to pack a present with my old laptop that are still function with xubuntu pre install But my sister is 10 year old she don't know anything about linux.

Should i just leave the laptop with xubuntu pre install or there other better option ?

https://redd.it/mpavdw
@r_linux
Hello Everyone, i am trying to put together a noscript that checks for the running processes at regular intervals and issue a warning mail if something is not running.

I have tried using ps -ef > log.txt in a noscript scheduled from ceontab to run every 1hr. log.txt has the necessary write and read permissions. when i run the noscript from terminal, it runs fine and writes to the log.txt
When the noscript runs from chrontab, its no longer writing to the file. Please help.

https://redd.it/mpbq9b
@r_linux
What is a problem/minor pet peeve you have with Linux that you wish would get fixed?

Just a disclaimer: when I say “Linux” I mean everything from a problem you have with the kernel to a typo in a man page or even an OS specific problem.

What is something that bothers you that you wish could be fixed?

https://redd.it/mpe35n
@r_linux
Submitted bug report yesterday: fixed in less than 24h – Open Source rulez!

I’ve already thanked the two involved people by private mail, but I think it’s important to thank all those package maintainers and open source developers for their hard work – thus this post.

# Here is my story:

I did submit a bug report on my Linux distributions bug tracker as of Yesterday noon about a really annoying bug in the video editor Kdenlive which started to occur with the newest KDE-Plasma version (btw. I use Arch).

* [https://bugs.archlinux.org/task/70409](https://bugs.archlinux.org/task/70409)

The first (reflexive?) reaction was: This is an upstream bug; file it upstream. However I didn’t read this reply until late morning today.

Nevertheless in the meantime the Arch package maintainer obviously decided to not wait for me to open this bug upstream but (I guess) he talked to the Kdenlive developers by himself.

And one of the Kdenlive developers was like: Hold my beer.

So this early morning some minutes after 7 AM (imagine that, 7 AM!!) he did a patch upstream which addressed a possible QT5 regression:

* [https://invent.kde.org/multimedia/kdenlive/commit/f86dbde2.patch](https://invent.kde.org/multimedia/kdenlive/commit/f86dbde2.patch)

Shortly after, around 8 AM (imagine – in the middle of the night!!) the Arch package maintainer included this fix into the Kdenlive package:

* [https://github.com/archlinux/svntogit-packages/commit/874bb3c20425871f202e7fa4fe43e7f14586b2e2#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a](https://github.com/archlinux/svntogit-packages/commit/874bb3c20425871f202e7fa4fe43e7f14586b2e2#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a)


All the time I wasn’t aware of all this but sleeping like a baby. I did a "pacman -Syu" (Arch Linux package update command) around 10:30 AM and there was a Kdenlive package update popping in.

Hmm – it wouldn’t possible address my bug report, would it? But imagine my surprise: It was!!

Kdenlive worked fine again. I still couldn’t believe this was because of my bug report so I started looking at the package build (something like an srpm source). And then I just reconstructed the timeline from above… What an amazing stunt by those two people (Antonio the package maintainer and Jean-Baptiste the developer).

All this on a Sunday/early Monday! Much too unhealthy early in the morning!

And this is my experience from a lot of open source bug reports I did. Well – perhaps not this fast but anyway.

So a big Thank You to all those open source developers and package maintainers which in most cases working in their spare time just for the phun of it! Thank you guys!



## Now: Imagine the same with a commercial solution (I have this often enough in my job):

1. Check if your support contract really covers this kind of problem. Else you are on your own.

2. Try to explain it to their support. They want you to do a lot of senseless things just to make sure the “protocol” is correct. 1 week for this, after a lot of email ping pong (“your /var/log/messages file has the wrong format!!”).

3. Eventually the support will tell you that your current \[insert lib here\] version is not supported. Backport it (and live with the security problems) or: You are on your own.

4. If you can convince the support that your problem is valid you may eventually speak to a dev. The dev will send you test versions (“please try this version with a fix in it!”). The test versions won’t work at all. After some incarnations of more or less non working test versions you realize, the dev works on MacOS all the time. You convince him of installing Linux in a VM. After a while he proudly tells you, he is on Ubuntu 18.04 now. Before you complain that he should at least use 20.04 you remember that your company uses RHEL7, so 18.04 is better but not quite right. But now the dev is going on vacation for a month and a substitute is taking over, but he doesn’t realize your problem at all plus he is on Windows. … If things go really smooth you’ll have a solution
after 3 months. Paid support is all about this.

## how to do a bug report the right way

Now – please don’t think an open source bug report is always a breeze like the one I described. Before you spam your favorite projects with bug reports please do:

* Check if your problem is already solved upstream.
* Check if your problem is already addressed by another bug report.
* Check if you might instead want a feature request. Think about it!

Only then start writing it!

When doing an bug report use clear language. Use a clear structure (most bug trackers give you a structure, you “just” have to fill it out), that’s usually: A short denoscription, version numbers and how to reproduce the bug. Don’t tell unnecessary details. The developers/maintainers will ask for it when it matters. Keep it short!

Be prepared to help! That means you should know how to anonymise a log efficiently, how to deal with a .patch, how to compile from git, so you can try things out and report back. If you unable to operate on this level but really want to do a bug report anyway – tell this (very!) soon! No developer wants to explain how to apply a patch to you.

And not at least: Be friendly. You may be annoyed by the bug but please remember. Most of the open source people are not paid for it. They do that in their spare time. They may be in more stress than you right now. They may be female (so you oughta behave!!). Remembering all that will help you to stay friendly!

That’s all (sry for the wall of text).

TL'DR: Got a bug fixed in less than 24 hours what would take 3 months in corporate world. And if you do bug reports, keep it short and clear. Be friendly.

https://redd.it/mpkft5
@r_linux
Blurred a default GNOME wallpaper and added a white Arch logo. Thoughts? I'm semi-new to photo editing so this is kinda new to me.
https://redd.it/mple5k
@r_linux
Someone can teatch me how to install it using the ProntonDB?
https://redd.it/mpqqt7
@r_linux