AboutWelcome to Free Software Daily (FSD). FSD is a hub for news and articles by and for the free and open source community. FSD is a community driven site where members of the community submit and vote for the stories that they think are important and interesting to them. Click the "About" link to read more...
This post is the second in a series on shell script debugging, error handling, and security. The content of this post will be geared mainly toward BASH users, but there will be information that’s suitable for users of other shells as well. Information such as techniques and methodologies may transfer very well, but BASH specific constructs and commands will not.
Bash error messages, like so many error messages, can be more cryptic than helpful. But the good news is bash has a built-in mechanism for creating your own customized error messages, and you don't have to be an ace programmer to do it. Ubuntu and openSUSE already use this; Akkana Peck shows us how to do it ourselves.
This post is the first in a series on shell script debugging, error handling, and security. Although I’ll be presenting some methodologies and techniques that apply to all shell languages (and most programming languages), this series will focus very heavily on BASH.
One writer's vision of an error reporting system meant to serve users and not the manufacturer of the system--sparked by Microsoft's unwillingness to speak with him about Windows Error Reporting
At first, I doubted that the world wanted yet another Linux distribution. But Cloud Linux Inc. seems to be proving me wrong. Based in New Jersey, Cloud Linux Inc. seems to be catching on with several hosting companies. Here’s why.
Have you ever wondered what really happens to those Windows error reports you can send to Microsoft whenever a Windows app crashes? How many reports it must receive before taking action? Or whether it's worth your time and effort to send duplicate reports if the error occurs repeatedly?