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.
I just learned that ZSH comes with a directory changer called "cdr", which keeps a persistent history of your visited directories and lets you change to directories in that history. It's in the "zshcontrib" manpage, which gives you three lines to set it up.
Now I'm wondering how any of the people who wrote similar projects (fasd, autojump, z, and all their clones and reimplementations) didn't know about this.
I just learned how to customize my shell prompt for my user and root today,literally, and I am very happy. Just very basic customization, enough to give to distinguish on root mode from regular. Thanks to this wonderful guide.
I've reconfirmed that slackware is a pain and everyone who uses the garbage is here on LQ. ;-)
back when i ran an ISP, all the servers, except one, ran Slackware. they never had problems. but, Slackware is a lot of work. now, that i have retired and my eyes are getting bad (i have to use larger fonts everywhere), i have switched to Xubuntu, for less work with still full control.
back when i ran an ISP, all the servers, except one, ran Slackware. they never had problems. but, Slackware is a lot of work. now, that i have retired and my eyes are getting bad (i have to use larger fonts everywhere), i have switched to Xubuntu, for less work with still full control.
Slackware is fine for the right people.
I agree! Slackware can be intimidating to some who do not wish/want to put the time into learning the Slackware Gnu/Linux. Most users want/desire a hold your hand distribution. I have been using PV's Slackware since his first release.
As they say: If you use Slackware then you will learn Gnu/Linux!
BTW, I too use Slackware for my server(s) and my desktop units. The new Slackware64 15.0 Release Candidate (rc1) has been intrroduced today;
Quote:
Changing to /mnt/sdc2/slackware//slackware64-current ...
Mon Aug 16 08:49:41 CDT 2021 [7570]: Getting ChangeLog.txt...
0a1,483
> Mon Aug 16 05:28:16 UTC 2021
> Hey everyone, long time no see! No, I wasn't out fishing. Sadly, I haven't had
> a fishing rod in my hand (or even a fishing license in my wallet) for this
> entire season, but there may yet be a chance for that this year. Along with the
> usual suspects, I've been trying to clear out the list of things that needed
> to get done in order to reach the standard of excellence demanded from a
> Slackware release, and I think we've gotten it pretty close. GCC was bumped to
> version 11.2.0 (because we just can't send this out 2 versions behind), and
> everything was verified to build properly or fixed up so that it did. I don't
> see any benefit to another public mass rebuild, so we're not going to do one.
> Anyway, without further ado, here is Slackware 15.0 release candidate one.
> Consider most things frozen and the focus now to be any remaining blocker bugs.
> We'll more than likely take that next Plasma bugfix release, but it's soon
> time to get off this treadmill. Enjoy! :-)
Slackware®: -current <- 'You can use Alien_Bob's-script -mirror-slackware-current.sh <- To download -current, create cdrom/dvd Or Alien_Bob's-script -mirror-slackware-current.sh <- UK backup of script script to download the '-current' of choice ( 'x86' meaning 32bit or 'x86_64' meaning 64bit). + You can either pass parameters or edit the script to create the 'ISO' medium of choice. + Plus select a mirror to use. Or create a 'mirror-slackware-current.conf' by passing '-w' to the mirror-slackware-current.sh, the .conf file will be created in the same directory as the script file. You can edit 'mirror-slackware-current.conf' to suit your needs since the file is well documented. The script mirror-slackware-current.sh is well documented to allow you choices if you desire this route. + Alien_Bob is a Slackware® contributor and has graciously provided the scripts/tools. So an ata-boy and a big Thank You to Alien_Bob.
After 25 years of using Slackware, I learned how to install a fully encrypted Slackware system. I also learned how to convert a non-encrypted Slackware installation on a UEFI laptop to a fully encrypted one without re-installing (backup everything to an external disk, re-create filesystems following README_CRYPT.TXT guide but instead of running setup, restore the backup to the encrypted filesystem, chroot to it, create and install new initrd.gz).
I doubt that there is any other distribution easier than Slackware.
1 - The ancient 250Gb drive in my laptop had been failing for some time, and my Xubuntu installation in it was automatically keeping it alive and limping along using fsck on boot-up when any other OS would have simply died.
( I've replaced it with a solid state, and I've also discovered they are *fast*, and creepily light compared to platters )
2 - It's possible to have a complete OS squeezed onto a 4GB thumb drive that I can use to actually do my job on for a week. Not only that, but I could have gone still smaller - a full OS for 50Mb with all I need to work with. It's a weird thought.
I was running an update on my Mageia box and noticed that one of the programs being updated was named "marble."
Not knowing what this marble may be, I looked for a man page, but did not find one. So I started the program from the command line, as I use Fluxbox and didn't know about it, so I didn't have it on the menu.
^ related, I noticed that gnome-maps is nice & easy to use. Powered by Openstreetmap, one can paste geo links straight into the search bar. It does routing, also public transport, and apparently one can even edit Openstreetmap data.
Importantly, it's really easy to use.
Google may be unsurpassed, but there's plenty of open & more privacy-friendly choices for maps & routing.
I had an obsolete Debian duel boot partition I stopped using a very long time ago. Even though I wiped the partition completely, it would still show up as an option for me in the GUID Partition Table in my UEFI. If I tried booting into it, I would just get a Grub command line prompt. I finally learned how to get rid of it with 3 simple steps:
1. Run efibootmgr: "sudo efibootmgr -b # -B"
(# being the number associated with the partition intended to be deleted from the output of the "efibootmgr" command)
2. Delete the "/boot/efi/EFI/debian" file
3. Run "sudo update-grub"
Last edited by RichE; 08-31-2021 at 12:19 AM.
Reason: clarification
When I learn something new in Linux, I keep it to myself, because I assume most LQ members already know it perfectly well. This is based on experience from the last time I tried posting something I learned. It wasn't recent and thus I don't remember offhand what it was; but it promptly earned me an lecture from one of the mods that the information was well known.
So first, let's try...ehh, meta-knowledge about this topic, I guess. That is, I'll share something I figured out about posting knowledge on LQ. In order to usefully post knowledge, you need to first do research and make pretty certain that what you've learned is not widely known. If you don't do that, you're wasting...not everyone's time, but certainly many members' time. Fortunately, this issue doesn't often come up for me, because I don't learn something new in Linux every day anyway. It's simply because the stuff I learn is easy to find with a basic search of the internet. I would have to teach myself something more advanced than that.
Now: here's an example. I did in fact just learn something new: how to add a progress bar, if not a very helpful one, to the output of dd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.