Turtle Kevux Book
The Turtle Kevux distribution was originally started with Linux From Scratch (www.linuxfromscratch.org).
The more and more I began deviating from their designs, the less and less it became Linux and slowly began turning into something entirely new. While I was custom rolling my own distribution, I was participating in a local linux users group (lclinux.org). From there, I was noticed and hired by one of the members of that lug to "custom roll" servers for McNeese State Universities Academic Computing Center. This had given me the chance to test the distribution in which I was building on my own time in a real world scenario. As soon as I completed a given server, I was assigned to custom roll yet another. This allowed for even more experiments in the design of my distribution. At this time, it was called SALFS or Slighty Automated Linux From Scratch, given that my systems was based off of what I've learned from LFS.
After creating so many different systems, the size of the system had grown huge, in my opinion. With around 6-Gigabytes of space required by the system. In addition to that, I had started switching to the 2.6 kernel from the ever so stable 2.4 kernel. Then the final blow got me, I was tired of having so many different and unorganized ways in which all of the servers store and use data, as well as the security issues that arise from a system with 6 Gigabytes of data.
So, my first step was to figure out how to fix all of this as efficiently as possible. I began putting togethor a new system design around a new libc. This new design was to be called Turtle Linux; however, not long after I started these design, the local lug (lclinux.org) decided on their own that my system should not be called Linux, but instead Kevux. I by no means refused the name, in fact, I grabbed three domain names: kevux.org, kevux.net, and kevux.com. I then began to consider what is actually meant by calling my system Kevux and not Linux.
First of all, Linux is an operating system, and I have no intentions of ever writing one myself (from scratch at least). I then considered what it was that people called Linux. What is called linux today by the masses is not, in fact, the kernel itself (operating system), but instead the functionality that is expected. Take FHS for instance, FHS is a filesystem that is seen as the one and only linux filesystem, and most open source programmers build their compilation and installation tools around this, assuming this is how it is going to be. Also, there are a series of programs that are on pretty much every single linux system and many programs assume it is there.
When a person sits down on a "linux" machines, they might expect to change directory to /home/bob as that is a standard home directory path, they might expect to type "top" and get a specific program that works in a specific way, or they might also create a script that begins with "#!/usr/bin/env python" in order to have the system find where python is installed, but still assuming that /usr/bin/env exists in that location. None of these are the same with Kevux.
A Kevux system has no intentions of having a "linux" feel, a "windows" feel, a "macintosh" feel, or whatever other OS there might be out there. The goal of this system is to simplify the structure of the entire system, reduce the size of all code on the system, allow for both users and programs to easily parse data, and to allow for a user to completely change how the system is and works to how they want the system to work, no matter how bizarre, outragous, or stupid the idea may be.
Turtle Kevux is the first distribution of the Kevux Operating Systems.
The more and more I began deviating from their designs, the less and less it became Linux and slowly began turning into something entirely new. While I was custom rolling my own distribution, I was participating in a local linux users group (lclinux.org). From there, I was noticed and hired by one of the members of that lug to "custom roll" servers for McNeese State Universities Academic Computing Center. This had given me the chance to test the distribution in which I was building on my own time in a real world scenario. As soon as I completed a given server, I was assigned to custom roll yet another. This allowed for even more experiments in the design of my distribution. At this time, it was called SALFS or Slighty Automated Linux From Scratch, given that my systems was based off of what I've learned from LFS.
After creating so many different systems, the size of the system had grown huge, in my opinion. With around 6-Gigabytes of space required by the system. In addition to that, I had started switching to the 2.6 kernel from the ever so stable 2.4 kernel. Then the final blow got me, I was tired of having so many different and unorganized ways in which all of the servers store and use data, as well as the security issues that arise from a system with 6 Gigabytes of data.
So, my first step was to figure out how to fix all of this as efficiently as possible. I began putting togethor a new system design around a new libc. This new design was to be called Turtle Linux; however, not long after I started these design, the local lug (lclinux.org) decided on their own that my system should not be called Linux, but instead Kevux. I by no means refused the name, in fact, I grabbed three domain names: kevux.org, kevux.net, and kevux.com. I then began to consider what is actually meant by calling my system Kevux and not Linux.
First of all, Linux is an operating system, and I have no intentions of ever writing one myself (from scratch at least). I then considered what it was that people called Linux. What is called linux today by the masses is not, in fact, the kernel itself (operating system), but instead the functionality that is expected. Take FHS for instance, FHS is a filesystem that is seen as the one and only linux filesystem, and most open source programmers build their compilation and installation tools around this, assuming this is how it is going to be. Also, there are a series of programs that are on pretty much every single linux system and many programs assume it is there.
When a person sits down on a "linux" machines, they might expect to change directory to /home/bob as that is a standard home directory path, they might expect to type "top" and get a specific program that works in a specific way, or they might also create a script that begins with "#!/usr/bin/env python" in order to have the system find where python is installed, but still assuming that /usr/bin/env exists in that location. None of these are the same with Kevux.
A Kevux system has no intentions of having a "linux" feel, a "windows" feel, a "macintosh" feel, or whatever other OS there might be out there. The goal of this system is to simplify the structure of the entire system, reduce the size of all code on the system, allow for both users and programs to easily parse data, and to allow for a user to completely change how the system is and works to how they want the system to work, no matter how bizarre, outragous, or stupid the idea may be.
Turtle Kevux is the first distribution of the Kevux Operating Systems.