What is something *new* you have learned about Linux within the past 7 days?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's more a hardware related means to run GNU/Linux, but I found out that it's dead simple to boot GNU/Linux on Raspberry Pi models 3B+ and 4B off of USB devices. That method occupies a USB port of course, but if all four are not needed it is a lot faster and more robust physically, not to mention more cost effective.
TIL the vim-tiny package has a little bug. If you invoke "vi" from a shell in an xterm, and it's the vi from vim-tiny, the program asks the terminal to alert it to focus changes. But when it's in vi compatibility mode, vim.tiny doesn't know what to do with those alerts. So it beeps and does a "stopInput" event. Jumps from input mode to edit mode if you move the mouse out of its terminal window.
That's because "set compatible" is NOT commented out, in /etc/vim/vimrc.tiny.
I hit this annoyance in Raspberry Pi OS Bullseye but they got it from upstream Debian due to their package choices. Armbian on Orange-Pi and Nvidia L4T on Jetson don't have the problem because they ship with vim-basic, not vim-tiny.
You can fix it by putting "set nocompatible" in your ~/.vimrc if you don't want to touch /etc/vim/vimrc.tiny
I've been installing Arch a lot lately (sole system on an old laptop, 2 bootable systems on a new desktop, plus another in VirtualBox). I like the idea of minimal desktops - Openbox, IceWM - so ran into plenty of challenges getting everything to hang together. Polkit authentication agents and Notification daemons were a whole new world for me. They would be included in a fully fledged desktop by default, but you have to install them yourself if you go down the 'minimal' route.
Installing Arch is a great way to learn new things about Linux, and the documentation available is excellent.
I learned that being on the bleeding edge of things isn't always a good idea. I updated my Artix system with `pacman -Syu` and updated the Linux kernel from 5.15.6 to 5.16.0; after the reboot for some reason an old kernel was booted up (like, 5.12!) even though 5.16 was installed. Still not quite sure why it happened, but I somehow managed to fix it... but there was that moment of quite literal 'kernel panic' --- not on my computer, but in my head!
I've been trying to find a way to replace Zoom + VoiceMeter Banana on Windows, in which a desktop with sound is shared and there are two usb headsets plugged into the local machine so that these two and remote participants can all hear each other and the desktop sound.
Using jack and pipewire (pulseaudio emulation) allowed me to mix & route audio between the headsets and zoom just fine.
But the zoom desktop sharing sound doesn't work with pipewire, even when it is emulating pulseaudio.
You can understand the problem from the zoom developers' point of view - which sound api should they support? And why?
But it does mean I have one more reason to keep a Windows machine live.
I have learned that out of all the KDE-distros that even vaguely appeal, only OpenMandriva gets the settings right for a network printer. Well, at least once I had the right settings, I could copy 'em to the other systems... tho you'd think since they all use the same config utility, they'd all spit up the same results??! Nooo, that would be too easy!!
I have learned that Qutebrowser is a fantastic browser for people like me who don't like /can't use a mouse. Combining this withkeynav makes life a lot easier.
I taught myself to set up Bluetooth on Kali and pair up with another device.
I had never used Bluetooth before and after several unsuccessful attempts at pairing up to my tablet got out spooftooph. I watched it for a bit to get the hang of what it was doing and that was enough to get me going.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.