Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Not always true!if you use any product for which you are not paying, YOU are the product.
That's because there's no such thing as 'file extensions' in Linux. At least not originally.there are very few Linux programs that have a ubiquitous file extensions like .doc and .xls
Linux IS an exception, not the rule. Yes, it's the result of massive collaboration of programmers. However, there are very few Linux programs that have a ubiquitous file extensions like .doc and .xls - YES there are converters and emulators and simulators... so enjoy your FREE stuff! Most people, however, are at the mercy of Big Tech: and all they (we) can do is minimize their intrusion into our lives.
Linux IS an exception, not the rule. Yes, it's the result of massive collaboration of programmers. However, there are very few Linux programs that have a ubiquitous file extensions like .doc and .xls - YES there are converters and emulators and simulators... so enjoy your FREE stuff! Most people, however, are at the mercy of Big Tech: and all they (we) can do is minimize their intrusion into our lives.
That's because there's no such thing as 'file extensions' in Linux. At least not originally.
I started on UNIX in the '80s, and file names could contain any character, including non-printables [which could cause big problems for sysadmins], but the general convention was to use 'regular' characters--including dots. So these were [and still are] perfectly good names:
June.20.2020.11.38.00.am
this_is_a_text_file
fstab.original
.profile
and so on. Unlike idiotic DOS, *nix actually determines a file's type, rather than use its 'extension' to tell it what it is. The venerable 'file' command, run in a directory full of files [with no silly 'extensions'], spits out exactly what type of file each one is.
As I recall it [and I could easily be wrong], it wasn't until the Internet became widely accessible, and files like images and videos started being widespread, that 'extensions'--such as .jpg .mp3 .gif--became part of my world.
Today, Android apps that I really like, and paid for, irritate the hell out of me when I'm on a network drive, and try to open this_is_a_text_file, and--having been programmed by window$ users--prompt for what to open it with.
All I can say is that UNIX, when I started in the 1980s, had no such thing as extensions; file names were just file names, as in my earlier examples.File extentions to tell the OS what type of file is it, is really something from the 60s and 70s isn't it, with mainframes, minicomputers, and 8-bit, like CP/M. Commodore 64, etc.
All I can say is that UNIX, when I started in the 1980s, had no such thing as extensions; file names were just file names, as in my earlier examples.
'fstab.original' does not consist of the file name 'fstab' and the extension 'original'--its entire file name is 'fstab.original' plain and simple.
How things worked prior to UNIX, I really can't say, but am interested in learning.
All I can say is that UNIX, when I started in the 1980s, had no such thing as extensions; file names were just file names, as in my earlier examples.
'fstab.original' does not consist of the file name 'fstab' and the extension 'original'--its entire file name is 'fstab.original' plain and simple.
How things worked prior to UNIX, I really can't say, but am interested in learning.
Exactly! I had never heard of anything so stupid as DOS/window$ programs requiring the .exe 'extension.' In *nix, a file named some_file.exe could be a daily calorie journal text file.And you can mark any file as being executable.
You're absolutely right--and I had completely forgotten about that. I think of my real computing life starting in 1985, when I first laid hands on UNIX. My C64, and VIC20, before it, were more like fascinating playthings, and the only 'programming' I did was typing the sample programs from the manual. Today, I have ZERO recollection of the names I gave them when storing them on the attached tape recorder.During the 80s I had a Commodore 64, and that had things like .PRG for program files.
Oh, goodness! Slackware, circa 1998, was for über-*nix geeks! If only you had tried one of the other distros instead--you would've gotten them 'unleashed' and had a blast!I didn't actually know much about Linux until about 1998 probably, when I tried to install Slackware from a book and CD-ROM called Slackware Unleashed, but I never did get it "unleashed"
During the 80s I had a Commodore 64, and that had things like .PRG for program files.
Nice, right?! I love reminiscing, and I also love thread drift--it's more like talking in real life.Funny how this thread has turned into a reminiscing fest.
300 baud? That predates my first modem, a 2400 baud sucker that, when used to connect to the server in my office at work [via Wyse 60 terminal], spit out lines character by character. It was tantamount to watching grass grow. Aw, the good old days! (I do actually remember that time very fondly.)I wrote a BBS for the C64 in basic after I bought a modem that could actually answer the phone as opposed to dialing the phone, and then unplugging the cord to the receiver and plugging it in to the modem,which ran at a blazing 300 baud.
Nice, right?! I love reminiscing, and I also love thread drift--it's more like talking in real life.
300 baud? That predates my first modem, a 2400 baud sucker that, when used to connect to the server in my office at work [via Wyse 60 terminal], spit out lines character by character. It was tantamount to watching grass grow. Aw, the good old days! (I do actually remember that time very fondly.)