Earlier quoted context omitted.
That's the nature of these spare time one (wo)man side projects: packaging a piece of software for a wide variety of distributions and platforms is tedious and boring, so unless there's a large community (or money) involved, you have to compile it from source. Of course, you can always package your favourite utility for your favourite distribution. I'm sure the author would be thrilled to endorse your package in the…
How is that musl based binary built ? I saw the repositories travis configuration and wasn't able to find anything relevant.
What: A terminal tool to check what is taking up your bandwidth
71–80 of 190 posts
Re: What: A terminal tool to check what is taking up your bandwidth
#72Earlier quoted context omitted.
Agreed, and I had the same problem. It seems like an easy fix to add a requires_rust_version thing in Cargo.toml, and devs could at least set it to "the version I'm currently using" so we know it's guaranteed to build on that.
It’s not that easy; the real world has a lot of complexity. That said, we finally did accept a design for this in October; it’s not clear when it’s going to land though.
Re: What: A terminal tool to check what is taking up your bandwidth
#73Bad naming.. WHAT(1) BSD General Commands Manual WHAT(1) NAME what -- show what versions of object modules were used to construct a file (MacOS ...)
Marketers were forced into this by trademarks, but it shouldn't take the threat of a trademark lawsuit to convince you that stepping too close to something else's toes is annoying for everyone.
(And don't be afraid to go with words that have negative meanings: Aside from git, MUMPS has been a successful medical records database environment for decades.)
Re: What: A terminal tool to check what is taking up your bandwidth
#74Earlier quoted context omitted.
It’s not that easy; the real world has a lot of complexity. That said, we finally did accept a design for this in October; it’s not clear when it’s going to land though.
Because of dependencies, you mean? Even an indication of "this builds fine for me at version X" would be good.
It took about a year to get stuff figured out.
Re: What: A terminal tool to check what is taking up your bandwidth
#75I am the author of "what" and am very happy to hear people like this tool I made. :)
"what" was my first real attempt at rust, and I love the project very much.
That said, it is a hobby project - and so I will likely be a few days responding to all issues and contributions that came from this thread.
"what" has already received some great contributions that are major parts of the code base. I would be very happy for more (in the form of features, bug fixes, issues and packaging).
A note to those having issues installing: as mentioned in this thread, packaging for all the various linux distributions and mac is a great effort. I apologize that at the moment the installation is a little bumpy (especially for those not very familiar with rust).
A good first step for if "cargo install what" isn't working is to try to `rustup update` so you get the latest version of rust and cargo.
Other than that, I hope to support your setup in the future, and/or hear from you in the issues of the repo. Debug help for OSes I do not have access to would be greatly appreciated. :)
Thank you all!
Re: What: A terminal tool to check what is taking up your bandwidth
#76Earlier quoted context omitted.
This is in the top class of utilities (htopm etc). A good name could probably be bwtop, or tcptop or iftop. Actually I searched for these, and turns out iftop exists! ( https://linux.die.net/man/8/iftop )
My complaint about the name is that it would be hard to "google" it. This means if I don't bookmark it or remember where I found it, then a couple of years from now when my laptop needs to be rebuilt, I'll have the darndest time finding it to install it again.
Re: What: A terminal tool to check what is taking up your bandwidth
#77Re: What: A terminal tool to check what is taking up your bandwidth
#78Error: Failed to listen on network interface: No such file or directory (os error 2) on macOS. Anyone else getting this error?
Re: What: A terminal tool to check what is taking up your bandwidth
#79Earlier quoted context omitted.
Very first result for "cargo tool programming" https://binx.io/blog/2018/11/27/learning-cargo/ You're getting snark because your own snarky comment is the equivalent of saying "Why do I need Make to run it on the MacOS?" If you had asked instead, "What is cargo, and how do I install it?" you would get more helpful responses. Snark is met with snark.
And how people are supposed to know that it is a programming tool? I assumed that it is yet another package manager and googling about cargo brings results about logistics. It took me a few tries before figuring it out. What worked was "Install cargo MacOS" and it was hard to tell if the results are not a scam to make me install some spyware.
Re: What: A terminal tool to check what is taking up your bandwidth
#80Earlier quoted context omitted.
iftop is a remarkably useful utility. It's often one of the first things I install on new openwrt installations.
Ever since I installed SQM on openwrt, I don’t really care what’s using the bandwidth anymore since it doesn’t impact any other users on the network. :) It’s true though that iftop is a very useful tool.