Linux - Reddit – Telegram
Linux - Reddit
761 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
Xanmod vs Liquorix

I always use Liquorix. But now I'm kinda thinking if xanmod or liquorix is better. Some benchmarks say it Liquorix some say thats Xanmod. I would want to know which one is the fastest/most secure.

​

I'm kinda new to Linux. But I'm creaving for knowledge. Thanks everyone for reading/answering.

https://redd.it/mozk9g
@r_linux
starting a native adaptive Linux client for Signal

Please do not respond with criticisms of Signal. I am trying to get something done here, not start a debate.

I just ordered a PinePhone and the biggest obstacle for me to use it as my daily driver to replace Android will be having a Signal client. I've been following the issue of getting Signal working on Linux smartphones for a while and I've come to the conclusion that it is probably best if we start a new client application. The Signal developers are uninterested in making their clients work for our use case. The Signal "Desktop" (Electron) client does not and will not support registering an account, is not designed for small screens, and does not build on ARM. The latter two issues may be fixed upstream (eventually), but they've specifically said they do not want to make the Electron client have feature parity with the Android and iOS clients. I doubt using the Android client in Anbox would be a good long term solution for battery or RAM usage.

So I think we need a native Linux client. I do not think Axolotl is a viable long term solution because it uses its own implementation of the Signal network protocol (written in Go). Reimplementing the cryptography and network protocol is a ton of work and will continue to be a ton of work as upstream adds more features. Axolotl has only just started reimplementing the new Signal groups protocol which was introduced 5 months ago. Also, the security of a reimplementation is dubious. Whisperfish is a nonstarter because it uses the proprietary QML libraries from Jolla. It is also using the unmaintained libsignal-protocol-c library, but the developers plan to switch to the new upstream Rust libraries.

Fortunately, the Signal developers are now using a new Rust library with bindings to C, Java, Swift, and TypeScript for their own clients. Currently this is undocumented and does not yet implement all the logic necessary to write a complete client. However, upstream has advised that using this new library would be the best option for starting a new client.

There are several paths forward:

1. A new application with the GTK Rust bindings. This would have the advantage of not needing any intermediate layers between the upstream libraries and the client application.
2. A new application with Qt and Kirigami. I discussed this idea with the Plasma Mobile developers and they suggested it could work by making a QObject wrapper class around the Rust libraries using cxx, run that in its own thread to handle the networking, and use Qt signals & slots to communicate with QAbstractItemModels backing the QML.
3. Integrate the Rust Signal libraries with an existing chat application instead of writing a whole new GUI. Integrating into Chatty would have the advantage of also handling SMS & MMS like the Signal Android client, but I'm unclear how audio and video calls could be integrated into Chatty. Maybe that could be separately integrated into Calls. Integrating Signal into Fractal or NeoChat could be other approaches, but would make those applications much more complex and I'm not sure their developers would welcome that.

I am leaning towards using QML and cxx because I'll be able to reuse those skills for my main project. That's an old QWidgets application that we're planning on rewriting with QML and have discussed integrating Rust libraries. The thought of using C to add Signal support to Chatty is unappealing to me. I have no
experience developing with GTK, so that would add a lot of work to this project for me. Ultimately, which technical path to choose will be up to whoever does the work.

For push notifications, I think we should implement a native Linux daemon for Firebase Cloud Messaging without Android. This would require no extra effort for the Signal Foundation. It could also be used for reimplementations of other Android chat applications such as WhatsApp, Facebook Messenger, Slack, Zulip, and more. microG has already reimplemented the Android API in Kotlin so studying that code could be helpful.

If someone wants to make this client work on Windows and macOS, notifications could be done with WebSocket. But I'm far more interested in getting it working on Linux smartphones.

I don't really have the capacity to lead this long term, so right now I am trying to organize people who are interested in doing the work. Hopefully once there is a minimal proof-of-concept that can register an account and send & receive text messages, more developers will join.

I've also started a discussions on the Pine64 and Signal forums about this.

https://redd.it/mp2j0j
@r_linux
Can I flash iso without downloading file?

Is there a way to make a bootable usb piping axel downloader to dd command as in (flash iso directly from link) I have little space , is there a way? I don't care if it takes time but if there's a way , maybe download and compress at same time?

TL:DR : Can I Flash iso without downloading?

https://redd.it/mp3s03
@r_linux
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