In earlier times, the standard security model for GNU/Linux and Unix operating systems gave general users a minimal set of privileges, while granting full privileges to a single user account, i.e. root, that was used to administer the system and users, install software, mount and unmount filesystems, loading kernel modules, bind a process to a privileged port and run many services. This dependence upon the root account to perform all actions requiring privilege was recognized to be somewhat dangerous in that it was all or nothing and not suited to compartmentalization of roles. Furthermore, it increased the risk of vulnerabilities
I recently was involved in some development work for a quasi-parallel filesystem for Microsoft Windows. As a result of that involvement my interest was piqued and I decided to do so research on what the state of research and development is in the field of parallel filesystems designed specifically for Microsoft Windows. First a quick review of what I mean by a parallel file system. There are any number of different types of parallel file systems available. Some allow multiple systems and applications to share common pools of storage as in a clusered filesystem. Some split the data across two
ksh93 supports localization of internal error messages and getopts messages but localization of user messages in shell scripts is flawed. This post examines the issue and shows you how to easily support shell script message catalogs.
Yesterday my old friend and collegue Charles Merton Richmond (Charlie) died at home in Cebu PH of a massive heart attack. We go back a long time and worked on many projects together.