21–30 of 66 posts
This looks very nice, but the compiler version requirement is very painful for those of us working on machines installed more than a year ago... GCC 10, ouch. I mean, newer versions are great, but when you don't control your machine's OS distribution, installing GCC 10 is not the most trivial thing to do.
Quick word of warning, if you download it: The release archive doesn't create a directory, just untars into $CWD. So do this: mkdir btop cd btop tar xjvf ~/Downloads/btop.....tbz ./install.sh Apart from that, it looks really, really nice. I like it a lot!
This is why I have trust issues when github pulling or exploding a tar.
Doesn't seem a big deal or require/cause trust issues to me.
(And when I create one, I always have to check/look up what happens, so it doesn't surprise me that a variety of things get done at all.)
Quick word of warning, if you download it: The release archive doesn't create a directory, just untars into $CWD. So do this: mkdir btop cd btop tar xjvf ~/Downloads/btop.....tbz ./install.sh Apart from that, it looks really, really nice. I like it a lot!
This is why I have trust issues when github pulling or exploding a tar.
The first thing I do with a Linux installation it's always add htop, and this it's the first time I feel the need to try something new in my routine.
htop and multitail are always tied for me.
I never heard of this one before. What's the benefit instead of doing this with Tmux?
Earlier quoted context omitted.
This is why I have trust issues when github pulling or exploding a tar.
Maybe it's just me, but this seems like the more obvious behaviour? Personally I'd typically extract in /tmp/relevant-name, and sometimes that results in /tmp/relevant-name/relevant-name. Doesn't seem a big deal or require/cause trust issues to me. (And when I create one, I always have to check/look up what happens, so it doesn't surprise me that a variety of things get done at all.)
Not everyone does this, of course, but it's nice when they do. Because it means you can just wget the file into a dir and untar it without worrying about it messing up whatever is already there. Also handy for putting different versions of the project side-by-side.
Earlier quoted context omitted.
This is why I have trust issues when github pulling or exploding a tar.
Maybe it's just me, but this seems like the more obvious behaviour? Personally I'd typically extract in /tmp/relevant-name, and sometimes that results in /tmp/relevant-name/relevant-name. Doesn't seem a big deal or require/cause trust issues to me. (And when I create one, I always have to check/look up what happens, so it doesn't surprise me that a variety of things get done at all.)
But on *nix systems, the idiom for tarballs usually includes a directory containing all of the contents.
> (And when I create one, I always have to check/look up what happens, so it doesn't surprise me that a variety of things get done at all.)
True - I usually do a `tar tf foo.tar.xz |head` to get a quick peek at the archive. This generally avoids the problem of dumping a bunch of files into the current directory.
The first thing I do with a Linux installation it's always add htop, and this it's the first time I feel the need to try something new in my routine.
htop and multitail are always tied for me.
You just made my day. I always open multiple ssh sessions just to display various logs at the same time.
Seems like you can even docker-compose logs -tf | multitail -j.
edit: I never took the time to learn tmux but after just watching a use case video, seems like you could achieve the same result with tmux indeed, as the other comment suggested.
The first thing I do with a Linux installation it's always add htop, and this it's the first time I feel the need to try something new in my routine.
htop and ncdu
I've found some other cool CLIs written with rust at https://github.com/TaKO8Ki/awesome-alternatives-in-rust
Quick word of warning, if you download it: The release archive doesn't create a directory, just untars into $CWD. So do this: mkdir btop cd btop tar xjvf ~/Downloads/btop.....tbz ./install.sh Apart from that, it looks really, really nice. I like it a lot!
Quick word of warning, if you download it: The release archive doesn't create a directory, just untars into $CWD. So do this: mkdir btop cd btop tar xjvf ~/Downloads/btop.....tbz ./install.sh Apart from that, it looks really, really nice. I like it a lot!
I use atool ( https://www.nongnu.org/atool/ ) for unpacking random archives - it abstracts away all formats including zip/rar/7z, compression and also guarantees that nothing is ever extracted into $CWD.