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.
That you can use lnav to quickly navigate in a log file :
Navigation
Code:
e/E : go to next/previous [e]rror
w/W : go to next/previous [w]arning
o/O : forward/back one h[o]ur
d/D : forward/back one [D]ay
s/S : go to the next/previous [s]lowdown (variation in number of lines by unit of time)
/<PCRE> : search for pcre
n/N : goto next/previous search result
Display
Code:
T : toggle elapsed [T]ime since first timestamp (like in wireshark)
i : toggle h[i]stogram of the logfile. This will show when were most messages logged. Use z/Z to zoom in, zoom out -minute,hour,day-
Filtering
Code:
:filter-in <PCRE> : only display lines matching the perl compatible regular expression with a bonus : some values/words scanned in the log file are tab-completable
:filter-out <PCRE> : hide lines matchine pcre
:disable-filter <PCRE> : disable filter <PCRE>. It is readline ready so you can use arrow keys or C-r/C-s to search in what you typed previously
:set-min-loglevel <loglevel> : hide lines below loglevel (tab completable)
Output
Code:
m : [m]ark current line
C : [c]lear all marked lines
u/U : go to next/previous marked line
:append-to <file> : append marked lines to file
Last edited by ychaouche; 10-17-2021 at 08:30 AM.
Reason: Formatting
That you can use lnav to quickly navigate in a log file :
This is what did you learn in last seven days or you just sharing your knowledge with the rest of us? If the latter just create a blog or wiki. You can put link into your signature. People here are Warhammer 40k veterans. Figuratively speaking. It is PITA reading YALB (Yet another Linux Bible).
This is what did you learn in last seven days or you just sharing your knowledge with the rest of us? If the latter just create a blog or wiki. You can put link into your signature. People here are Warhammer 40k veterans. Figuratively speaking. It is PITA reading YALB (Yet another Linux Bible).
That comment encapsulates everything I said in my earlier comment. In order to post knowledge, one must do enough research to make reasonably certain that what one learned is not widely known. If one doesn't, one will most likely get a gripe from someone (and/or a lecture from a moderator) that the information is already known and one is wasting everybody's time.
The reasoning behind my conclusion is this. If one is going to use LQ, one needs to know the culture. Perhaps one hopes one's discovery might help some newer user one day. But however many "newbies" visit regularly, a large proportion of the regular membership are quite experienced and probably know much more than the "newbie"; and are always the most likely to respond to a post. One can't share one's discovery with only other newbies; it displays to everyone at once. That in practice always means that it has to run a gauntlet of experienced users who probably saw it first. They are ready to evaluate the information; and, if it doesn't fit their level of experience, to dismiss it, possibly brusquely.
Or: try this.
Example of what might be useful to post: All these comments about what users did with the programming languages or advanced commands. Example of what would not be particularly needed and would just get a lecture: how I made my own church worship music collection by using audacity and youtube-dl to extract the audio from DVDs and youtube videos of services, respectively. (Which is perfectly legal and ethical for me to do as a member of my church--we pay the subscription fees out of money that came from tithes!--as long as I don't share it with others due to copyrights.) Why would that be not particularly needed? Because it's only a matter of finding and following instructions. All I did was read man pages and ask questions on LQ.
Last edited by newbiesforever; 10-17-2021 at 04:00 PM.
Most of what is in this thread was quite unknown to me and I've been using Linux for ten years! That's why I subscribe to it. Unfortunately, I'm not going to remember much of what I've read here.
i discovered that whilst bash would be the first go to,to get things done, python has its moments.
Thus for Arch i wrote a python script and compiled to ->elf ;it fetches full mirror and writes to /etc/pacman.d/mirrorlist(none enabled) , it also fetches full mirrorlist and enables all, or it can fetch mirror after you select from tkinter drop down, check likley speed of mirror using elapse time , sort a tuple where url=elapse time and then write fastest first.
So basically reflector and reflector simnple , all in one.
When i finished doing that , i then learned how to construct a PKGBUILD, and finally push to AUR.
This thread is what it is meant to be. All which responds to the question in the topic header must be on-topic, you cannot just come along on page 14 and then say: “What we expect to read here is ...”, then even argument with the senior-status of the readers... I am surprised in an utterly disagreeable way.
Do your own, then.
On-topic: I learned that there is no straight forward way (or no documentation about it) to enable unblocking input from STDIN with Bash. And YES, I wrote a blog post about it that some will disagree with.
How about criticizing my grammar. I might even appreciate that.
Last edited by Michael Uplawski; 10-18-2021 at 12:56 AM.
I used cat to join two short music mp3 files into a longer one ¯\_(ツ)_/¯
That might have worked only because most media players are very forgiving about buggy mp3 files, or (much less likely) your mp3 files do not have any headers at all.
That said, utilities to concatenate mp3 files without re-encoding them exist.
perhaps it ii good to add some sorting. I found this in man ps
Code:
$ ps ux --sort -%cpu
top processes with cpu usage.
Thanks for the tip. Apparently htop and ps give different output. ps seems much more stable, while htop there seems to be a constant dance. https://vimeo.com/manage/videos/644786445
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Unfortunately, I'm not going to remember much of what I've read here.
