3 ms·
It's not a bad exercise. In a Unix class I took, we had to implement an RDBMS using only the traditional Unix software tools. A little later, for work, I had
by neilv 8y ago
It's not a bad exercise. In a Unix class I took, we had to implement an RDBMS using only the traditional Unix software tools. A little later, for work, I had to learn to write highly portable and fairly secure shell scripts.
A few reasons to do exercises like this:
* To understand the Unix software tools and Bourne/etc. shell scripting models. There are good lessons, and also examples of what not to do (or the tradeoffs), which I don't think you'll find anywhere else. (For example, the simple Unix streams model is very powerful, and also often used in very kludgey ways in practice, and the Bourne evaluation model is probably much worse and dangerous than a beginner might think.)
* Knowing how to do things with just shell scripts is great for some kinds of bootstrapping, commands in build tools, or other situations in which you can only assume a shell interpreter and possibly certain command-line tools.
* Handy for configuring your interactive shell to do what you want.
* It's one way to familiarize with parts of a Unix-ish system that you might not normally, especially if you're spending all your time learning your way around huge stacks of tools that obscure the lower-level mechanics.
* You'll appreciate Perl and other languages much more, in some ways.