Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Page: BSD Heritage #31

Merged
merged 19 commits into from Feb 19, 2019
Merged
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Update hugo-site/content/information/heritage.md
Co-Authored-By: beanpole135 <ken@ixsystems.com>
  • Loading branch information
Mrt134 and beanpole135 committed Feb 19, 2019
commit fac093991e965aaa348bd095c9501c10e32553cc
@@ -75,7 +75,7 @@ TrueOS provides the OpenRC system for managing services on the OS in place of th

### Base Packages

TrueOS uses the package system for installing the OS itself in addition to the pre-compiled "ports". This functionality is called "base packages" and allows single package repository to contain both the OS and all the available applications in a single unified collection of files. This functionality provides the following features:
TrueOS uses the package system for installing the OS itself in addition to the pre-compiled "ports". This functionality is called "base packages" and allows a single package repository to contain both the OS and all the available applications in a single, unified collection of files. This functionality provides these features:

* The OS and packages are always in sync. A single system update can be used for the entire end-to-end update of the system - even when OS changes (such as a new kernel) are provided during a major release cycle.
This conversation was marked as resolved by beanpole135

This comment has been minimized.

@Mrt134

Mrt134 Feb 16, 2019
Collaborator

Suggested change
* The OS and packages are always in sync. A single system update can be used for the entire end-to-end update of the system - even when OS changes (such as a new kernel) are provided during a major release cycle.
* The OS and packages are always in sync. A single system update can be used for the entire end-to-end update of the system, even when OS changes like a new kernel are provided during a major release cycle.
* System updates are *FAST* and clean. All updates are performed within a new Boot Environment, ensuring that your live system is never touched while you are using it. All it needs is a reboot to finish the procedures and boot into the newly-updated system.
This conversation was marked as resolved by beanpole135

This comment has been minimized.

@Mrt134

Mrt134 Feb 16, 2019
Collaborator

Suggested change
* System updates are *FAST* and clean. All updates are performed within a new Boot Environment, ensuring that your live system is never touched while you are using it. All it needs is a reboot to finish the procedures and boot into the newly-updated system.
* System updates are **fast** and clean. All updates are performed within a new Boot Environment, ensuring the live system is never touched while in use. Reboot to finish the update procedure and boot into the newly-updated system.