121–130 of 138 posts
Earlier quoted context omitted.
Git for Windows relies pretty heavily on MinGW, though. And it's best used from the included bash shell.
Why is git so heavily "posix-y" in a way that e.g. svn is not?
Learn just enough GNU coreutils and bash to get things done.
Earlier quoted context omitted.
Then by that point of view no commercial OS is made for developers, including UNIX ones. It was the way that commercial UNIX vendors started selling their SDKs, with Sun being the first one, that made people actually contribute to gcc.
Being either a commercial product or open source doesn’t preclude Unix from being designed for development.
Quitting is ctrl+d
Ctrl+c is for interrupting the current job.
Some repl like the mysql cli does not rrspect that and it is a PITA
In place of the "tabview" command (which is a non-standard, pip-installed program) a simple "column -t" would be less trouble for most users.
Thanks. I was looking for tabview but it wasn't easy to find, and in python (not that it's bad, but it wasn't a native tool). Rather, column -t is definitely a better choice, since it is a native posix tool.
It originates from BSD, but it's also part of util-linux, so it should be available on most Linux distros.
Earlier quoted context omitted.
Over years I've heard a lot of complains on tar being hard to use, but in real-life I really ever had to use only these two commands: tar zcvf and tar zxvf. It's actually quite easy to remember: tar Zip Compress Verbose File, and tar Zip eXtract Verbose File.
It's even easier than that! Less memorization, more understanding. You can think of Tar arguments as either subcommands or options . The dashes are optional The "subcommands" are x (extract), c (create), t (list), among others. The "options" are f (read from named file rather than stdin), v (verbose mode), and z (run gzip on the archive before processing). The fact that these options can be written without leading da…
Earlier quoted context omitted.
Technically it's correct. It's just really odd in tone; it almost sounds like it's unusual or negative that these utilities were not written to be completely cross-platform, as if that would be a norm.
But git is not an example of software that wasn't ported to windows. It was ported to windows.
Great list for starters. But getting real work done requires much more. Having just walked through some basic steps with a novice, I can concur, modern linux is impossible without "recipes". Just setting up a hello world web app can involve: ssh login to running instance, using curl to download the gcloud sdk, tar to unpack, sudo to install, systemctl to start local processes, useradd dedicated www, chmod and chroot…
>> For beginners, without a trusted hand to guide them, its beyond intimidating. These systems must become more accessible to the average human. I cringe at thinking about what a newbie has to go through. Install the right version of php/python etc on your platform Install a virtual environment Install a package manager Install a framework Install a database
It's no wonder MySpace and then Facebook became popular. This was the dumbed down web presence people wanted but didn't want to have to manage.
Earlier quoted context omitted.
> While Linux distros have been getting better and easier for many years, installing and maintaining Linux on my own machine still requires sysadmin Linux knowledge to this day. I'm not sure that's true. You can buy a few computers (including from Dell) with Linux pre-installed, and maintenance doesn't take a lot more than clicking on the upgrade button with the daily update-manager prompt. I _do_ have sysadmin knowl…
> I'm not sure that's true. You can buy a few computers (including from Dell) with Linux pre-installed, and maintenance doesn't take a lot more than clicking on the upgrade button with the daily update-manager prompt. Is it really that good these days? I can definitely appreciate the constancy of Linux, it feels like Windows/Chrome/etc stacks move under my feet constantly. But my experience with Linux is still that w…
Earlier quoted context omitted.
add 'tar r' and 'tar u' to your arsenal.
In about 40 years of using Unix I have never used r or u.
I use them frequently as an "rsync"-ish into the archive file, which I can then use to take point-in-time snapshot/backups.