Don't take the unnecessary risk of running #Wireshark as #root. Instead, create your capture file (.cap, .pcap) with #tcpdump (sudo tcpdump -i eth0 -w file.pcap), then open it for analysis in Wireshark as your regular non-root user. 👍 #networking#cybersecurity#soc#gnu#linux#cli
I'm thinking about how I could a good #cli for #hsml
I may orientate on existing CLIs like #Rust, #deno or #pnpm
so e.g.
hsml compile # compiles all .hsml files to .html inside current folder and recursive below
hsml compile ./example.hsml # just compiles the given file
hsml fmt # formats
hsml fmt # just formats given file
hsml parse ./example.hsml # parses the given file and std::out as json AST
But I'm not sure if this fulfills all need or if I need to change something
How could I miss out on #VisiData for so long? This might become my new favorite #CLI tool.
If you do anything with data and enjoy working in the terminal, check it out. It can
• provide a #TUI for viewing and editing data in #CSV, #Excel, #SQLite, #JSON, #YAML & #XML files and quite a few more
• sort, filter, join and edit that data, across files and across formats
• convert between the formats (interactively or not)
• record & play macros
• be scripted in #Python
Wie kann ich von einer Festplatte den Inhalt grafisch z.B. als Pixelbild darstellen? z.B. jedes Byte als Grauwert? Ich möchte eine formatierte Festplatte grafisch analysieren. Sind überall Nullen oder Einsen, oder Rest von Inhalten.
Gibt's da was? Oder stichprobenartig z.B. mit 'dd' einen Block lesen und darstellen?
When using the #gzip tool to create compressed copies of files, you can include the -c switch (to write to stdout), e.g. gzip -c file > file.gz, or use the -k switch (to keep original), e.g. gzip -k file. Otherwise, you'll overwrite the original, which you'll certainly want to avoid if working with important #backups. 👍 #gnu#linux#admin#cli
I am thinking about building a small #torrent machine to let it run 24/7 until all downloads are finished. (Don't want to let my laptop to run all the time...)
Are there any good #cli torrent clients with a #webinterface? (I want to make it #headless, but reachable via browser in the LAN)
“source” is a #bashism. The actual #POSIX name of the command is “.”. That’s right, a single dot.
Many people expect . to be some kind of a shortcut for “source”, and yes, they’re equivalent in #bash, but “source” is not guaranteed to exist in other shells. dash doesn’t have it, for example.
So, if you want to write your shell scripts as compatible as possible, use “.”, not “source”.
Before executing important commands and scripts over #SSH, use #screen in case of disconnect. If your connection drops or you close the terminal, you can SSH back in and enter screen -r to recover from where you left off. Being reunited with that hanging command prompt will be a relief! #tuesdaytip#gnu#linux#cli#admin
If you find the whole Calckey interface a bit too much for your device, or you just want to post something quickly, check out: https://calckey.social/cli
It's simple and gets the job done without any UI or UX other than a "Post" button.
One thing to keep in mind with regards to screen reader accessibility is that convention can be adapted to, even if that convention is less than ideal.
When people ask about plain text emphasis, even if people by standard chose a method i didn't prefer, but could recognize, i'd be able to know that's emphasis. This is why I like star - it means something to me in a way underline doesn't because it's less common.
Consistency and reliability mean so much, and this extends to navigation and site maps as well. Be boring and predictable, not quirky and new. This actually benefits everyone. It's the curb cut effect. No one likes having to dig for how to get to the place they need on your website. No one likes having to decipher what your typing quirks mean. Be unique in your content and what you can deliver, not your method.
@deilann go plain text! Plain text should be a universal option for every possible content format on the Internet. If you can't go with plain text, then at least go with good accessible HTML. This is why I like the command line so much. It's all plain text and very accessible.
Did you know there is a tool on your Raspberry Pi that will print out a diagram of the circuit board including ports and model name to the console? I'm not sure how I missed this over all these years!
I started to review the blog post requests, drafts, and ideas accumulated over time. Most topics revolve around #rex, #perl, #opensource, #gentoo, #cicd, #git, #testing, and #CLI — with some overlap.
Help me decide: which topic shall I focus on first?
Any reason to not scrub and recycle all my <= 2TB 3.5" SATA spinners? I generally keep old hardware forever but just can't imagine me ever using any of those again.
@paul So been there, so many times. Plus the internal debate once it’s been running for a while whether it’s worth hitting Ctrl-C and restarting with rdisk…
Wondering how to get readline working in a non-primary Node.js cluster process while keeping colour output via Chalk in your CLI app?
(I’m pretty sure you’re not but, hey, I ran into this today and I’m documenting it in hopes it might help someone else sometime.)
Check out the implementation in Kitten’s development-time process manager (this little file is what Kitten uses in place of a heavyweight module like Nodemon):
Never in a million years did I think I’d be using a command-line email client but Himalaya is actually really nice (I did set up some fish shell abbreviations for common commands, etc.) I’m particularly enjoying being able to compose messages in my regular editor (Helix Editor).