There’s nothing special, it can be replaced with any TOTP/HOTP implementation. In particular, oathtool is supplied in most distros (it has only command line interface, probably there are also some GUI tools in your repos). However it does not support JSON key format that is provided as QR code for mobile 2FA apps. You have to copy and paste values from it manually.

However this will likely violate your employer’s security policy. The point of 2FA is that secret key is stored on a separate device, so that it cannot be stealed together with your password.

I recommend to try other Android apps on your phone. I use FreeOTP+ and have no problems with font readability. Some of my collegues use AndOTP and like it.

the .deb file would be the equivalent of an .exe file on Windows

Not .exe. If you want to find an equivalent, .msi is the closest.

I don’t recommend using anything new to you unless you are ready to learn it. If you are, welcome aboard!

Lolwhat? It is the same in any distro: adding the repo and installing the app.

This wiki article contains the information you need. It can seem too long, but I highly recommend to read it.

You don’t have to do everything through terminal. You can use synaptic for example. What you have to do is to learn new concepts. If you want to do everything like in windows, use windows.

Yes, it is. You can achieve the same usung GUI of course, but this would be more difficult to describe because there are multiple GUIs and they change with new distro versions.

This is more convenient than “downloading and intalling” a file because you don’t have to track updates manually, the package manager will do this for you. You have to read something about what package manager is and how does it work. It is the main concept of all linux distros except LFS.

Thank you, I forgot this.

I don’t like the idea of configuring pm (or anything else) using a programming language. So I would try nix first if I feel that I need it. However I don’t.

TLDR: Companies should be required to pay developers for any open source software they use

You need to read the article yourself before writing TLDR. Spoiler: it is not about payments, it is about source code availability.

You forgot cowsay.

Yes, but for a very specific case. I used to write highly portable scripts that could be executed in different environments (various linux distros, including minimal containers, freebsd and even solaris 10). I couldn’t use bash, perl, python and even gawk. Only POSIX shell (I always tested my scripts with dash and ksh93, for solaris 10 compatibility - with its jsh), portable awk (tested with original-awk, gawk and mawk) and portable sed (better forget it if you need to support solaris).

Before that I didn’t understand why should I need awk if I know perl. And awk really sucks. Once I had to replace a perl one-liner with an awk script of ~30 lines for portability.

P.S. I never use awk just for print $1 as many do. It’s an overkill.

Multicast.

I don’t think that formula is the right tool to do this. You need to write a macro.

Try asking at !libreoffice@lemmy.ml

Brand does not matter. You will likely get in trouble with any new laptop model. Install the latest kernel, and probably most of them will be gone. But some can be fixed only after a year or so.

My Dell with preinstalled Ubuntu had a fingerprint scanner not working, wifi chip losing connection and disabled “subwoofer” (lol). After a year or two of upgrading a distro everything works (well, I mapped subwoofer output in config and idk if this still needed or not).

It seems you need to read the official documentation yourself.

I did. Debian man page, GNU grep manual.

I’m sorry for your loss, however the egrep deprecation is a fact. Of course you can continue using it as a veteran, but it is not correct to recommend this to beginners.

Perl has introduced powerful backtracking regexes that were widely adopted. However they can be damn slow in some cases, that’s why RE2 refused backtracking while using some perl-like elements. Both basic and extended POSIX regexes are also non-backtracking because they are older than perl.

Yes, it could find partitions removed long time ago if filesystem headers were not overriden.

GNU grep, the most widespread implementation, does not include egrep, fgrep and rgrep for years. Distributions (not all, but many) provide shell scripts that simply run grep with corresponding option for backward compatibility. You can learn this from official documentation.

Also, my scripts are not full of bashisms, gnuisms, linuxisms and other -isms, I try to keep them portable unless it is really necessary to use some unportable command or syntax.

Try testdisk. It can copy files from damaged filesystem without touching it. But only if you are lucky enough and the filesystem is not so heavily damaged that testdisk will be unable to find it.