med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

360
active users

#bash

14 posts11 participants1 post today
Hey fedi friends, what are the differences in USES and config options listed at #freshports for a #FreeBSD #port? I am familiar with USE in #Gentoo #Linux, which seem to be the config options here? For #Gentoo it is very common to use different USE settings for a packages, but for #FreeBSD I read from porter's handbook there are not many USE items and they looked different from the term in #Gentoo. I am still trying to wrap my head around what is happening that whenever I try to build a port, like #vim or #git in tiny flavors, I constantly noticed #Perl #Bash #lua #Rust #Python and all other seemingly unrelated stuff get pulled in. #BSD #RunBSD #Unix #FOSS
www.freshports.orgFreshPorts -- The Place For Ports - Most recent commitsMost recent commits
Continued thread

2/2
...aber große und attraktive, App ähnliche, Dinge habe ich mit der #bash noch keine gemacht.

Schluss damit!
Ich liebe ja dezent bunte Terminals - und wenn funktionale Scripts ihr Ding schön machen und optisch Rücksicht auf das nehmen worum es technisch geht...😍

Also habe ich mir erst mal (wieder) ne mini ANSI library gebastelt - diesmal für die bash.

Erstes Ding was darauf basiert und ziemlich fertig scheint ist der "auto-folding" Downloader... (siehe GIFs + Bildbeschreibungen).

Das #Bloat Prinzip vs. #KISS Prinzip.

Links #VScode - Rechts #Nano.

Sprache:
#Bash mit embedded #awk

Aus Bash Sicht ist das "awk in aqua Farbe" in #code OK. Aber optisch nicht besonders prickelnd.

Nano hingegen interpretiert die embedding Hochkommas nicht und colorriert fleißig weiter... Aus bash Sicht nicht OK - aber sehr geil zu lesen.

Ersten 500 Zeilen habe ich in nano via #ssh aufm #RaspberryPi gemacht - dann in code weiter - was hab ich mich erschreckt...🤪

@cleverboi @JadziaMD @davidgerard @RecurringBloatware @rdfhrn IMHO #scripting is a form of #programming and the distinction is arbitrary.

  • Unless one does raw, low-level accessing hardware components, there's almost always an #ABI or #API that gets utilized.

I just merely pointed out that #bash as a #shell is basically the only common denominator among mainstream #Linux distros, with the few exceptions that don't even implement a symbolic redirect to a bash-subset when calling

#! /usr/bin/env bash

being anomalies most of the time if not "statistical rounding errors" at best...

Replied in thread

@davidgerard @cleverboi @RecurringBloatware @rdfhrn and because "installing another shell" is like "installing a compiler on a production system".

  • At least a gross violation of #BestPractises with regulations, if not a ticket to get a nonconsensual meeting with HR and security escorting one off premises...

So yeah, I've deal with #bash simply because it's the only #shell I can reliably expect on any relevant #Linux distro I'm working on (aka. #Ubuntu LTS, #SLES / #SLED, #RHEL, #Debian) ...

Infosec.SpaceKevin Karhan :verified: (@kkarhan@infosec.space)@cleverboi@mastodon.social @rdfhrn@hessen.social @davidgerard@circumstances.run I know... - If I could change it, I'd make the default shell of #Linux into #fish instead of #bash...

Gibt's eigentlich irgend eine Merkregel / Erklärung, wann ich für rekursive Arbeiten ein -R brauche (cp, chown) und wann ein kleines -r (rm) ??? Vielleicht dass in rm selbst ein kleines r drin ist (wäre eine Merkregel, aber keine Erklärung).

Linux tip: you can edit files from within less by pressing "v". This will launch your default editor.

If you do not have a default editor specified, you can specify one by adding the following lines to your .bashrc:

# set default editor
EDITOR=/usr/bin/vim

Substitute vim for whatever editor you prefer. (Which is obviously vim :)

#Linux#Bash#vim