Language Selection

English French German Italian Portuguese Spanish

Kylin, a Chinese FreeBSD based, secure O/S

Filed under
BSD

The Kylin operating system is a server operating system focusing on high performance, availability and security. Its initial developement was funded by a Chinese government-sponsored Research and Development (R&D) program in 2002. The first public version of Kylin was released in 2007.

Kylin is based on FreeBSD 5.3 with some proprietary security extensions to add an extra level of security to that operating system. Kylin, named after qili, a mythical beast, has been organised in a hierarchy model, including the basic kernel layer which is responsible for initializing the hardware and providing basic memory management and task management, the system service layer which is based on FreeBSD providing UFS2 and BSD network protocols, and the desktop environment which is similar to Windows. It has been designed to comply with the UNIX standards and is compatible with Linux binaries.

rest here

Also: NeoKylin. China’s new domestic FreeBSD based desktop O/S




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more