2019/02/13: The UNIX market is in inexorable decline:Only 1 in 85 servers deployed this year uses Solaris, HP-UX, or AIX. Most applications on Unix that can be easily ported to Linux or Windows have actually already been moved.
Most of what remains on Unix today are customized, mission-critical workloads in fields such as financial services and healthcare. Because those apps are expensive and risky to migrate or rewrite, Bowers expects a long-tail decline in Unix that might last 20 years. “As a viable operating system, it’s got at least 10 years because there’s this long tail. Even 20 years from now, people will still want to run it,” he says.
2000/01/26: I got tired of configuring half a dozen separate filetype/handler systems for individual applications and wrote the Launcher to centralize type/handler managment across all my applications. Since the Launcher is a command-line program (with a separate GUI process) it can used as a drop-in replacement for every type/handler pairing in most applications. Launcher is an attempt at an all-in-one file handling solution for use with any software that uses file type to file handler mappings. This utility is the one point of configuration for programs like netscape, the dfm filemanager, tkArchive, tkmail, or any other software that uses filetype/handler pairs. Features include multiple type-discovery methods, apache mime.types parsing for extension mapping, and GUI-based disambiguation. Launcher uses it's own type-to-handler mapping file which is much more flexible than metamail's .mailcap. Unfortunatly the two are not compatible.
The init daemon is going to be replaced with daemon systemd on some of the Linux Distributions, while a lot of them have already implemented it. This is/will be creating a huge gap between traditional Unix/Linux Guard and New Linux Guard.
I was a historian before I was an activist, and I've been reminded recently that a lot of younger hackers have a simplified and somewhat mythologized view of how our culture evolved, one which tend...
This article will try to convince you that adding some limitations on legal Unix/Linux/POSIX filenames would be an improvement. Many programs already presume these limitations, the POSIX standard already permits such limitations, and many Unix/Linux filesystems already embed such limitations so it'd be better to make these (reasonable) assumptions true in the first place. This article will discuss, in particular, the three biggest problems: control characters in filenames (including newline, tab, and escape), leading dashes in filenames, and the lack of a standard character encoding scheme (instead of using UTF-8). It also discusses spaces in filenames and shell metacharacters in filenames, including why setting the Bourne shell IFS value to newline and tab is a good idea.
open source / open discussion software projects working on interoperability and shared technology for X Window System desktops. The most famous X desktops are GNOME and KDE, but developers working on any Linux/UNIX GUI technology are welcome to participate.
For Unix Admins, By Unix Admins