OK, slow day at work and I was looking through my collection of shell scripts in Nautilus (I mostly use the shell and CLI) : and I see this one file that has a different icon and for the life of my I have NO IDEA why!
Camel face, not camel toe
The two files to either side of it - are also *.bash shell scripts - but have different icons⌠All have attributes â-rwxr-xr-xâ (i.e. 0755) and all start with the âhash bangâ : #!/usr/bin/env bash
All three scripts respond the same way to the âfileâ command :
â°â⤠file mon-xfer.bash
mon-xfer.bash: Bourne-Again shell script, ASCII text executable
â°â⤠file movavid.bash
movavid.bash: Bourne-Again shell script, ASCII text executable
Why? Why? Itâs not a biggy - but itâs perplexing!!!
Also - I probably wonât pastebin the contents of any of these scripts - 'cause I do a lot of swearing and pottymouth words in my shell scripts - like the âFâ bomb, and even the âCâ bomb
FYI : that mcfuck2mp3.bash script converts crappy apple m4a music files to âproperâ mp3 files (and removes the m4a file) - this is only when Iâm forced to buy music from the iSore [sic: deliberate] thatâs not available anywhere elseâŚ
I have never seen music only available on the Apple Store. If the artist I listen to would put their music only on there, I simply wouldnât buy it, because I wouldâve lost my interest in them.
It was an Australian band called Tropical Fuck Storm (fronted by The Dronesâ frontman Gareth Liddiard and bassist Fiona Kitschen [his missus]) - and their EP/Album only came out on iTunes - and I couldnât wait for it to come out on Google Play Music - and wasnât available to buy in a brick and mortar music outlet at the time
Also - I do have an iPad (Iâve got two actually) - and I had an iTunes card one of my kids got me few months earlier for XmasâŚ
Hereâs one song off that album (Album : A Laughing Death in Meatspace) - âThe Future of Historyâ - and it actually mentions a UNIX âversionâ - AIX (RS/6000 VLSI running AIX) :
Ofcourse camel toe is a bit best
but speaking serious, seems virus attack, despite
Linux have fews virus.It could to be a logomark of
some software, search in google using this image
to see the return.
Oh well : I understand now why itâs a âcamelâ :
but still no idea why Cosmic Cuttlefish thinks its a perl script (I NEVER write scripts from scratch in perl - I can modify / change kinda understand a perl shell script - but would never choose it to start something from scratch)
Does it run with that line? There might be some issues with that when running scripts with that line on Debian based systems. E.G. I couldnât execute a certain script at all with that first liner.
I always use that line these days⌠for maybe 5 years??? Donât remember when I switched from simple :
#!/bin/bash
to
#!/usr/bin/env bash
I think I got some shell scripts from an Amazon AWS Solutions Architect that were like that - and I just started using that formatâŚ
Debian?
Never found a Debian instance (from Wheezy to Stretch) that didnât have a /usr/bin/env binaryâŚ
Never found a RHEL/CentOS/OEL/Fedora instance like that either⌠and certainly not a Ubuntu instance - and - the same on FreeBSD - itâs âthereââŚ
Interesting read⌠now I remember why I started doing this - not all operating systems have âbashâ (or ksh/csh/sh) in /usr/bin - some (Solaris? Iâll have to fire up my Sunblade 2500 again! Older FreeBSD?) house them in /bin/ - however - on all the systems I looked at /usr/bin/env was âtrueâ - so I started doing thisâŚ
Just confirmed - on FreeBSD (my FreeNAS âNASâ) :
x@baphomet î° ~ î° which bash
/bin/bash
x@baphomet î° ~ î° which env
/usr/bin/env
So there ya go
And - to confuse things even further? TrueOS based GhostBSD :
ââx@puca ~
â°â⤠which bash
/usr/local/bin/bash
ââx@puca ~
â°â⤠which env
/usr/bin/env
ââx@puca ~
â°â⤠which tcsh
/bin/tcsh
ââx@puca ~
â°â⤠which zsh
/usr/local/bin/zsh
ââx@puca ~
â°â⤠which csh
/bin/csh
ââx@puca ~
â°â⤠which sh
/bin/sh
Note âtcshâ is usually the default shell on FreeBSD
