From 141cea2b6e02af315ffcbfff7fc84ae15614a3b9 Mon Sep 17 00:00:00 2001 From: Ken Moore Date: Sat, 16 Feb 2019 00:26:52 -0500 Subject: [PATCH 01/19] New Page: BSD Heritage This page details the ancestry of Project Trident and goes into the differences between PT and TrueOS/FreeBSD as well as similarities. Also fix a number of icons on various blog posts. --- hugo-site/content/docs/introduction.md | 2 +- hugo-site/content/information/features.md | 4 +- hugo-site/content/information/heritage.md | 75 +++++++++++++++++++ .../post/2019-01-23_18.12-U1_available.md | 2 +- .../post/2019-01-29_18.12-U2_available.md | 2 +- .../post/2019-02-06_18.12-U3_available.md | 2 +- .../post/2019-02-13_18.12-U4_available.md | 2 +- 7 files changed, 81 insertions(+), 8 deletions(-) create mode 100644 hugo-site/content/information/heritage.md diff --git a/hugo-site/content/docs/introduction.md b/hugo-site/content/docs/introduction.md index 88823f7..7c68712 100644 --- a/hugo-site/content/docs/introduction.md +++ b/hugo-site/content/docs/introduction.md @@ -14,7 +14,7 @@ The goal of the Project is to provide a simple, secure, and highly usable FreeBS Project Trident is completely independent and [financially backed through the generous contributions of the Open Source community](/sponsors). [Project Trident](https://project-trident.org) began in 2018 when TrueOS was reorganized into a scaled down server installation of FreeBSD. -The discontinued desktop portion of TrueOS was taken by Ken Moore and J.T. Pennington and rebuilt into Project Trident. +The discontinued desktop portion of TrueOS was adopted by Ken Moore and J.T. Pennington (two of the desktop-focused TrueOS developers) and rebuilt into Project Trident. Project Trident is essentially a customized installation of TrueOS and FreeBSD, not a forked derivative. Project Trident has a simple graphical installer that has partition support and other customization options. diff --git a/hugo-site/content/information/features.md b/hugo-site/content/information/features.md index 758f1e5..0c658a2 100755 --- a/hugo-site/content/information/features.md +++ b/hugo-site/content/information/features.md @@ -18,7 +18,7 @@ Project Trident treats user privacy as a primary goal. We takes many steps to en * For enhanced privacy, we have a pre-defined firewall profile for routing all network traffic through the "tor" anonymizing service. While this profile is not enabled by default due to the speed limitations of the tor network, it can be easily enabled after installation. -* The "Falkon" web browser that is pre-installed has ad-blocking functionality both built-in and pre-enabled. With the addition of private browsing and more advanced browsing protection options are also available within the preferences as well. +* The "Falkon" web browser that is pre-installed has ad-blocking functionality both built-in and pre-enabled. Private browsing and additional browsing protection options are also available within the application preferences as well. ## Reliability @@ -33,6 +33,4 @@ Project Trident utilizes a number of mechanisms to safeguard the data of each sy Utilizing leading security enhancements from OpenBSD, Project Trident also builds on TrueOS to provide a desktop focused operating system which keeps security implication and mitigation procedures as a top priority for the everyday user. Some of the security enhancements that we implement: - * LibreSSL is used as a drop-in replacement for OpenSSL. This prevents *most* of the security issues that touch the SSL systems from impacting Project Trident. We also use LibreSSL when building all the 3rd-party applications/packages unless the application *specifically* requires OpenSSL for some reason. - * All 3rd-party packages are built, signed, and sealed by Project Trident before being placed into a public repository. This allows the user to download and install trusted builds of applications from an official source, rather than having to fetch files from unknown sources. diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md new file mode 100644 index 0000000..96693f0 --- /dev/null +++ b/hugo-site/content/information/heritage.md @@ -0,0 +1,75 @@ ++++ +title = "BSD Heritage" +MenuTitle = "BSD Heritage" +description = "Relationship and differences from other BSD operating systems" +chapter = false +weight = 2 +pre = " " ++++ + +Project Trident is a desktop-focused disribution of [TrueOS](http://trueos.org), which in turn is a variation of the [FreeBSD](http://freebsd.org) operating system which was officially started [in the early 1990's](https://www.freebsd.org/doc/handbook/history.html) but is itself a direct decendant of the [original AT&T UNIX](http://www.unix.org/what_is_unix/history_timeline.html). + +Rather than re-iterate the history of the FreeBSD and TrueOS projects, this page focuses on the similarities and differences between Project Trident and TrueOS/FreeBSD. + +## Similarities +The base operating system and kernel are identical between the various projects, as they are all built directly from the same source code - albeit at different times or from different branches of the source repositories. This includes the kernel, hardware drivers, file systems, and more. + +All of the applications which are available in the form of packages are built from the exact same "ports tree" - a source repository of build instructions for over 35000 applications, libraries, and more. These "ports" generally result in binaries which are compiled to run specifically on FreeBSD-based operating systems which are a particular architecture. + +### Architectures +FreeBSD itself supports multiple types of computer architectures (i386, amd64, various flavors of ARM, etc..), but TrueOS and Project Trident are specifically focused on the amd64 architecture (often called x86-64, or "64-bit"), but also include the support capabilities to directly run i386 binaries ("32-bit"). + +### Ports +Due to the addition of OpenRC to TrueOS for service management, the TrueOS project maintains a version of the FreeBSD ports tree which includes many additional files. These extra files are generally to ensure that OpenRC versions of service files are available alongside the traditional rc.d service files from FreeBSD, in addition to some other changes which the TrueOS project works on before they get submitted back to FreeBSD (new ports, new versions of ports, and more). TrueOS also utilized Github for managing it's ports repository[1], whereas FreeBSD still uses a privately-hosted SVN repository[2]. + +*[1] [TrueOS ports repository](https://github.com/trueos/trueos-ports)* +*[2] [FreeBSD ports repository](https://svn.freebsd.org/)* + +## Differences From TrueOS +*Note: The differences listed here generally also apply to other TrueOS-based distributions* + +Being a desktop-focused distribution, Project Trident provides many different graphical solutions for common tasks on TrueOS based systems: + +* Graphical front-end to the "pc-sysinstall" utility from TrueOS for managing the installation. +* Graphical system setup + * While this is typically a manual task on TrueOS/FreeBSD, Project Trident provides a suite of scripts and utilities which handle all of the setup and maintenance of the graphical systems. These utilities are setup to run during the bootup routine and will dynamically provide the following features: + * Automatic "best-driver" setup for your hardware based upon which graphical drivers are installed and whether they match the type of GPU contained by your hardware. + * Automatic failover to one of two different graphical drivers ("vesa" or "scfb") should the main graphics driver fail to work (such as installing the wrong version of the NVIDIA driver for your system). + * Dynamic loading of the video driver and any associated kernel modules on bootup, allowing the system harddrive to be moved between systems as needed with little to no loss of functionality (provided that the drivers for both are installed already - otherwise one of the failover drivers may be used). +* Graphical utilities for common tasks + * The PCDM login manager. + * The [Lumina Desktop Environment](https://lumina-desktop.org) is pre-installed and pre-configured for out-of-box usage. + * A [graphical system-update utility](https://github.com/project-trident/trident-updatemgr) has been written just for Project Trident. This provides easy access to configuring and performing updates in addition to the ability to roll-back a system update as desired. + * Removable media detection and on-demand usage is provided via integrations between Project Trident and the Lumina Desktop. +* Stable OS, Rolling Ports + * Project Trident uses the 6-month "stable" branch of TrueOS for the OS-components themselves. This ensures there are no radical changes or binary compatibility issues for a 6-month period of time. + * Project Trident also builds and provides a package repository of every "port" contained in the TrueOS ports repository. This package repository is also updated every week, ensuring a steady stream of new or updated applications very soon after they appear in FreeBSD/TrueOS. + * Project Trident uses a [customized build configuration](https://github.com/project-trident/trident-build/blob/master/trident-master.json/) for both OS and ports to ensure that everything is built specifically to be used for a graphical operating system. + +## Differences From FreeBSD + +Many of these differences from FreeBSD actually come from the TrueOS project, so this list will change over time as the TrueOS and FreeBSD projects continue to evolve. + +### OpenRC + +TrueOS provides the OpenRC system for managing services on the OS in place of the "legacy" RC system currently used on FreeBSD. This difference is most notable in a few key ways: + +* Faster bootup - OpenRC starts up services much faster and with better dependency handling than FreeBSD. +* Better status reporting - the `rc-status` utility provides an instant look of all the services on your system and their current status. +* Service files are located in "[/usr/local]/etc/init.d" rather than "[/usr/local]/etc/rc.d" +* Some services have different names: "dhcpcd" instead of "dhclient", "network" instead of "netif" +* Many OpenRC services are "multiplexed" for individual device/profile management + * Example: The "network.wlan0" service controls the first wifi device, and should be started/stopped instead of the "network" service when reconfiguring the wifi settings. +* The [service-name]_enable="YES" entries on FreeBSD are no longer needed to enable services on bootup. Instead, OpenRC provides a method for grouping services together (called "runlevels"), and the `rc-update` utility is used to add/remove bootup registrations for services within these groups. + * Example: `rc-update add dbus default` will add the "dbus" service to the "default" runlevel and enable it to automatically start on bootup. + * Example 2: `rc-update delete dbus default` will remove the "dbus" service from the "default" runlevel and prevent it from starting during bootup. +* The "service" utility can be used exactly the same way as on FreeBSD to interact with services. + * Example: `service dbus stop` will stop the "dbus" service if it is running. + * Example 2: `service network.wlan0 restart` will restart the networking associated with the first wireless device. + +### 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: + +* 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. +* 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. diff --git a/hugo-site/content/post/2019-01-23_18.12-U1_available.md b/hugo-site/content/post/2019-01-23_18.12-U1_available.md index 56325ae..2755487 100644 --- a/hugo-site/content/post/2019-01-23_18.12-U1_available.md +++ b/hugo-site/content/post/2019-01-23_18.12-U1_available.md @@ -4,7 +4,7 @@ menutitle = "18.12-U1 Available" description = "" date = "2019-01-23" draft = false -pre = " " +pre = " " +++ Package update 1 for 18.12-RELEASE is now available. diff --git a/hugo-site/content/post/2019-01-29_18.12-U2_available.md b/hugo-site/content/post/2019-01-29_18.12-U2_available.md index 85e3b8f..372600a 100644 --- a/hugo-site/content/post/2019-01-29_18.12-U2_available.md +++ b/hugo-site/content/post/2019-01-29_18.12-U2_available.md @@ -4,7 +4,7 @@ menutitle = "18.12-U2 Available" description = "" date = "2019-01-29" draft = false -pre = " " +pre = " " +++ Package update 2 for 18.12-RELEASE is now available. diff --git a/hugo-site/content/post/2019-02-06_18.12-U3_available.md b/hugo-site/content/post/2019-02-06_18.12-U3_available.md index 2d2b4c3..fe28943 100644 --- a/hugo-site/content/post/2019-02-06_18.12-U3_available.md +++ b/hugo-site/content/post/2019-02-06_18.12-U3_available.md @@ -4,7 +4,7 @@ menutitle = "18.12-U3 Available" description = "" date = "2019-02-06" draft = false -pre = " " +pre = " " +++ Package update 3 for 18.12-RELEASE is now available. diff --git a/hugo-site/content/post/2019-02-13_18.12-U4_available.md b/hugo-site/content/post/2019-02-13_18.12-U4_available.md index 1decd5c..6c1fccb 100644 --- a/hugo-site/content/post/2019-02-13_18.12-U4_available.md +++ b/hugo-site/content/post/2019-02-13_18.12-U4_available.md @@ -4,7 +4,7 @@ menutitle = "18.12-U4 Available" description = "" date = "2019-02-13" draft = false -pre = " " +pre = " " +++ Package update 4 for 18.12-RELEASE is now available. From 3df626fce8c22ae22f68609d8653f3cacac4e98b Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:21:00 -0500 Subject: [PATCH 02/19] Update hugo-site/content/docs/introduction.md Co-Authored-By: beanpole135 --- hugo-site/content/docs/introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/docs/introduction.md b/hugo-site/content/docs/introduction.md index 7c68712..6cad410 100644 --- a/hugo-site/content/docs/introduction.md +++ b/hugo-site/content/docs/introduction.md @@ -14,7 +14,7 @@ The goal of the Project is to provide a simple, secure, and highly usable FreeBS Project Trident is completely independent and [financially backed through the generous contributions of the Open Source community](/sponsors). [Project Trident](https://project-trident.org) began in 2018 when TrueOS was reorganized into a scaled down server installation of FreeBSD. -The discontinued desktop portion of TrueOS was adopted by Ken Moore and J.T. Pennington (two of the desktop-focused TrueOS developers) and rebuilt into Project Trident. +The discontinued desktop portion of TrueOS was adopted by Ken Moore and J.T. Pennington, two desktop-focused TrueOS developers, and rebuilt into Project Trident. Project Trident is essentially a customized installation of TrueOS and FreeBSD, not a forked derivative. Project Trident has a simple graphical installer that has partition support and other customization options. From 1c91360affce8a746b95f6415d7246dd174c43f1 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:21:41 -0500 Subject: [PATCH 03/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 96693f0..a4e6c43 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -14,7 +14,8 @@ Rather than re-iterate the history of the FreeBSD and TrueOS projects, this page ## Similarities The base operating system and kernel are identical between the various projects, as they are all built directly from the same source code - albeit at different times or from different branches of the source repositories. This includes the kernel, hardware drivers, file systems, and more. -All of the applications which are available in the form of packages are built from the exact same "ports tree" - a source repository of build instructions for over 35000 applications, libraries, and more. These "ports" generally result in binaries which are compiled to run specifically on FreeBSD-based operating systems which are a particular architecture. +All of the applications which are available in the form of packages are built from the exact same "ports tree", which is a source repository of build instructions for over 35000 applications, libraries, and more. +These "ports" generally result in binaries which are compiled to run specifically on different FreeBSD-based operating system architectures. ### Architectures FreeBSD itself supports multiple types of computer architectures (i386, amd64, various flavors of ARM, etc..), but TrueOS and Project Trident are specifically focused on the amd64 architecture (often called x86-64, or "64-bit"), but also include the support capabilities to directly run i386 binaries ("32-bit"). From 9ddf6d632de016a8379aa87c7d175cc9860bfb28 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:22:11 -0500 Subject: [PATCH 04/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index a4e6c43..32c8255 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -12,7 +12,8 @@ Project Trident is a desktop-focused disribution of [TrueOS](http://trueos.org), Rather than re-iterate the history of the FreeBSD and TrueOS projects, this page focuses on the similarities and differences between Project Trident and TrueOS/FreeBSD. ## Similarities -The base operating system and kernel are identical between the various projects, as they are all built directly from the same source code - albeit at different times or from different branches of the source repositories. This includes the kernel, hardware drivers, file systems, and more. +The base operating system and kernel are identical between the various projects, as they are all built directly from the same source code, although at different times or from different branches of the source repositories. +This includes the kernel, hardware drivers, file systems, and more. All of the applications which are available in the form of packages are built from the exact same "ports tree", which is a source repository of build instructions for over 35000 applications, libraries, and more. These "ports" generally result in binaries which are compiled to run specifically on different FreeBSD-based operating system architectures. From e4053d570fb3acf6a8bcbedf622e9514ecf2eda7 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:22:43 -0500 Subject: [PATCH 05/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 32c8255..a77ee18 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -22,7 +22,10 @@ These "ports" generally result in binaries which are compiled to run specificall FreeBSD itself supports multiple types of computer architectures (i386, amd64, various flavors of ARM, etc..), but TrueOS and Project Trident are specifically focused on the amd64 architecture (often called x86-64, or "64-bit"), but also include the support capabilities to directly run i386 binaries ("32-bit"). ### Ports -Due to the addition of OpenRC to TrueOS for service management, the TrueOS project maintains a version of the FreeBSD ports tree which includes many additional files. These extra files are generally to ensure that OpenRC versions of service files are available alongside the traditional rc.d service files from FreeBSD, in addition to some other changes which the TrueOS project works on before they get submitted back to FreeBSD (new ports, new versions of ports, and more). TrueOS also utilized Github for managing it's ports repository[1], whereas FreeBSD still uses a privately-hosted SVN repository[2]. +Due to the addition of OpenRC to TrueOS for service management, the TrueOS project maintains a version of the FreeBSD ports tree which includes many additional files. +These extra files ensure that OpenRC versions of service files are available alongside the traditional *rc.d* service files from FreeBSD. +They also provide a testing area for other TrueOS changes before submission back to FreeBSD, including new ports, new versions of ports, and more. +TrueOS also uses GitHub for managing it's ports repository[1], whereas FreeBSD still uses a privately-hosted SVN repository[2]. *[1] [TrueOS ports repository](https://github.com/trueos/trueos-ports)* *[2] [FreeBSD ports repository](https://svn.freebsd.org/)* From 7be1c92a5c7b705231eb53e8e89383311f167f62 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:23:02 -0500 Subject: [PATCH 06/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index a77ee18..5743c03 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -31,7 +31,7 @@ TrueOS also uses GitHub for managing it's ports repository[1], whereas FreeBSD s *[2] [FreeBSD ports repository](https://svn.freebsd.org/)* ## Differences From TrueOS -*Note: The differences listed here generally also apply to other TrueOS-based distributions* +*Note: Differences listed here also generally apply to other TrueOS-based distributions* Being a desktop-focused distribution, Project Trident provides many different graphical solutions for common tasks on TrueOS based systems: From 56d7271642df6574eb27f25d0542edd9493f3c35 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:23:22 -0500 Subject: [PATCH 07/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 5743c03..687f8e8 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -69,7 +69,7 @@ TrueOS provides the OpenRC system for managing services on the OS in place of th * Example: `rc-update add dbus default` will add the "dbus" service to the "default" runlevel and enable it to automatically start on bootup. * Example 2: `rc-update delete dbus default` will remove the "dbus" service from the "default" runlevel and prevent it from starting during bootup. * The "service" utility can be used exactly the same way as on FreeBSD to interact with services. - * Example: `service dbus stop` will stop the "dbus" service if it is running. + * Example: `service dbus stop` stops the **dbus** service when it is running. * Example 2: `service network.wlan0 restart` will restart the networking associated with the first wireless device. ### Base Packages From dd703cfb9e2be3f0718c84ab1e1c32f60a3337f7 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:23:46 -0500 Subject: [PATCH 08/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 687f8e8..890ed33 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -37,7 +37,8 @@ Being a desktop-focused distribution, Project Trident provides many different gr * Graphical front-end to the "pc-sysinstall" utility from TrueOS for managing the installation. * Graphical system setup - * While this is typically a manual task on TrueOS/FreeBSD, Project Trident provides a suite of scripts and utilities which handle all of the setup and maintenance of the graphical systems. These utilities are setup to run during the bootup routine and will dynamically provide the following features: + * While this is typically a manual task on TrueOS/FreeBSD, Project Trident provides a suite of scripts and utilities which handle all of the setup and maintenance of the graphical systems. + These utilities run during the bootup routine and dynamically provide these features: * Automatic "best-driver" setup for your hardware based upon which graphical drivers are installed and whether they match the type of GPU contained by your hardware. * Automatic failover to one of two different graphical drivers ("vesa" or "scfb") should the main graphics driver fail to work (such as installing the wrong version of the NVIDIA driver for your system). * Dynamic loading of the video driver and any associated kernel modules on bootup, allowing the system harddrive to be moved between systems as needed with little to no loss of functionality (provided that the drivers for both are installed already - otherwise one of the failover drivers may be used). From 0f8b59ebc97bcc6370356f78a93093658aca2c8b Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:24:01 -0500 Subject: [PATCH 09/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 890ed33..24c1ef0 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -71,7 +71,7 @@ TrueOS provides the OpenRC system for managing services on the OS in place of th * Example 2: `rc-update delete dbus default` will remove the "dbus" service from the "default" runlevel and prevent it from starting during bootup. * The "service" utility can be used exactly the same way as on FreeBSD to interact with services. * Example: `service dbus stop` stops the **dbus** service when it is running. - * Example 2: `service network.wlan0 restart` will restart the networking associated with the first wireless device. + * Example 2: `service network.wlan0 restart` restarts the networking associated with the first wireless device. ### Base Packages From fac093991e965aaa348bd095c9501c10e32553cc Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:24:25 -0500 Subject: [PATCH 10/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 24c1ef0..8ed2a91 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -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. * 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. From abbd27e333a0d600ad0bbb0ab9732a571928a8c8 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:24:47 -0500 Subject: [PATCH 11/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 8ed2a91..a46d814 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -77,5 +77,5 @@ TrueOS provides the OpenRC system for managing services on the OS in place of th 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. +* 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. From 18646523035340805d6c474b8e62ad0722e4a46b Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:25:03 -0500 Subject: [PATCH 12/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index a46d814..640b7e5 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -78,4 +78,4 @@ TrueOS provides the OpenRC system for managing services on the OS in place of th 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 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. +* 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. From 22ddf68725ba6a6f8b34a7f69a4494f54d75b3ac Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:25:24 -0500 Subject: [PATCH 13/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 640b7e5..c72dd9f 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -40,7 +40,7 @@ Being a desktop-focused distribution, Project Trident provides many different gr * While this is typically a manual task on TrueOS/FreeBSD, Project Trident provides a suite of scripts and utilities which handle all of the setup and maintenance of the graphical systems. These utilities run during the bootup routine and dynamically provide these features: * Automatic "best-driver" setup for your hardware based upon which graphical drivers are installed and whether they match the type of GPU contained by your hardware. - * Automatic failover to one of two different graphical drivers ("vesa" or "scfb") should the main graphics driver fail to work (such as installing the wrong version of the NVIDIA driver for your system). + * Automatic failover to one of two different graphical drivers (**vesa** or **scfb**) if the main graphics driver fails to work for some reason. * Dynamic loading of the video driver and any associated kernel modules on bootup, allowing the system harddrive to be moved between systems as needed with little to no loss of functionality (provided that the drivers for both are installed already - otherwise one of the failover drivers may be used). * Graphical utilities for common tasks * The PCDM login manager. From 25156e68bfdfc08ea291bd5e29a4cfffd32b4366 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:25:49 -0500 Subject: [PATCH 14/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index c72dd9f..9e22779 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -41,7 +41,9 @@ Being a desktop-focused distribution, Project Trident provides many different gr These utilities run during the bootup routine and dynamically provide these features: * Automatic "best-driver" setup for your hardware based upon which graphical drivers are installed and whether they match the type of GPU contained by your hardware. * Automatic failover to one of two different graphical drivers (**vesa** or **scfb**) if the main graphics driver fails to work for some reason. - * Dynamic loading of the video driver and any associated kernel modules on bootup, allowing the system harddrive to be moved between systems as needed with little to no loss of functionality (provided that the drivers for both are installed already - otherwise one of the failover drivers may be used). + * Dynamic loading of the video driver and any associated kernel modules on bootup. + This allows the system hard drive to move between systems as needed with little or no loss of functionality. + This requires that the video drivers for both systems are installed already, or one of the failover drivers can be used. * Graphical utilities for common tasks * The PCDM login manager. * The [Lumina Desktop Environment](https://lumina-desktop.org) is pre-installed and pre-configured for out-of-box usage. From e27c4d9fabfb02468d2c9bab0b9abfd49fcc2139 Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:26:12 -0500 Subject: [PATCH 15/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 9e22779..8f78622 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -52,7 +52,8 @@ Being a desktop-focused distribution, Project Trident provides many different gr * Stable OS, Rolling Ports * Project Trident uses the 6-month "stable" branch of TrueOS for the OS-components themselves. This ensures there are no radical changes or binary compatibility issues for a 6-month period of time. * Project Trident also builds and provides a package repository of every "port" contained in the TrueOS ports repository. This package repository is also updated every week, ensuring a steady stream of new or updated applications very soon after they appear in FreeBSD/TrueOS. - * Project Trident uses a [customized build configuration](https://github.com/project-trident/trident-build/blob/master/trident-master.json/) for both OS and ports to ensure that everything is built specifically to be used for a graphical operating system. + * Project Trident uses a [customized build configuration](https://github.com/project-trident/trident-build/blob/master/trident-master.json/) for both OS and ports. + Everything in Project Trident is built specifically to be used for a graphical operating system. ## Differences From FreeBSD From 977b53460c9afc27319b3444057ceb47f9a4a34a Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:26:28 -0500 Subject: [PATCH 16/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 8f78622..ef33099 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -64,7 +64,7 @@ Many of these differences from FreeBSD actually come from the TrueOS project, so TrueOS provides the OpenRC system for managing services on the OS in place of the "legacy" RC system currently used on FreeBSD. This difference is most notable in a few key ways: * Faster bootup - OpenRC starts up services much faster and with better dependency handling than FreeBSD. -* Better status reporting - the `rc-status` utility provides an instant look of all the services on your system and their current status. +* Better status reporting. The `rc-status` utility provides an instant look at all system services and their current status. * Service files are located in "[/usr/local]/etc/init.d" rather than "[/usr/local]/etc/rc.d" * Some services have different names: "dhcpcd" instead of "dhclient", "network" instead of "netif" * Many OpenRC services are "multiplexed" for individual device/profile management From 058dbbc68ef9bd7f3c8b1a4fb05c34a762b56dee Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:27:11 -0500 Subject: [PATCH 17/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index ef33099..382b417 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -66,7 +66,7 @@ TrueOS provides the OpenRC system for managing services on the OS in place of th * Faster bootup - OpenRC starts up services much faster and with better dependency handling than FreeBSD. * Better status reporting. The `rc-status` utility provides an instant look at all system services and their current status. * Service files are located in "[/usr/local]/etc/init.d" rather than "[/usr/local]/etc/rc.d" -* Some services have different names: "dhcpcd" instead of "dhclient", "network" instead of "netif" +* Some services have different names: **dhcpcd** instead of *dhclient*, **network** instead of *netif*. * Many OpenRC services are "multiplexed" for individual device/profile management * Example: The "network.wlan0" service controls the first wifi device, and should be started/stopped instead of the "network" service when reconfiguring the wifi settings. * The [service-name]_enable="YES" entries on FreeBSD are no longer needed to enable services on bootup. Instead, OpenRC provides a method for grouping services together (called "runlevels"), and the `rc-update` utility is used to add/remove bootup registrations for services within these groups. From 7670047537287f63b3fe40e640da847fa6d910df Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:27:36 -0500 Subject: [PATCH 18/19] Update hugo-site/content/information/heritage.md Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index 382b417..b833608 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -65,7 +65,7 @@ TrueOS provides the OpenRC system for managing services on the OS in place of th * Faster bootup - OpenRC starts up services much faster and with better dependency handling than FreeBSD. * Better status reporting. The `rc-status` utility provides an instant look at all system services and their current status. -* Service files are located in "[/usr/local]/etc/init.d" rather than "[/usr/local]/etc/rc.d" +* Service files are located in `[/usr/local]/etc/init.d` rather than `[/usr/local]/etc/rc.d`. * Some services have different names: **dhcpcd** instead of *dhclient*, **network** instead of *netif*. * Many OpenRC services are "multiplexed" for individual device/profile management * Example: The "network.wlan0" service controls the first wifi device, and should be started/stopped instead of the "network" service when reconfiguring the wifi settings. From f3014fc88ff5df79aa13e3c3acc287a94303785f Mon Sep 17 00:00:00 2001 From: Tim Moore Date: Tue, 19 Feb 2019 09:29:06 -0500 Subject: [PATCH 19/19] Apply suggestions from code review Co-Authored-By: beanpole135 --- hugo-site/content/information/heritage.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/hugo-site/content/information/heritage.md b/hugo-site/content/information/heritage.md index b833608..5581183 100644 --- a/hugo-site/content/information/heritage.md +++ b/hugo-site/content/information/heritage.md @@ -67,12 +67,12 @@ TrueOS provides the OpenRC system for managing services on the OS in place of th * Better status reporting. The `rc-status` utility provides an instant look at all system services and their current status. * Service files are located in `[/usr/local]/etc/init.d` rather than `[/usr/local]/etc/rc.d`. * Some services have different names: **dhcpcd** instead of *dhclient*, **network** instead of *netif*. -* Many OpenRC services are "multiplexed" for individual device/profile management - * Example: The "network.wlan0" service controls the first wifi device, and should be started/stopped instead of the "network" service when reconfiguring the wifi settings. -* The [service-name]_enable="YES" entries on FreeBSD are no longer needed to enable services on bootup. Instead, OpenRC provides a method for grouping services together (called "runlevels"), and the `rc-update` utility is used to add/remove bootup registrations for services within these groups. - * Example: `rc-update add dbus default` will add the "dbus" service to the "default" runlevel and enable it to automatically start on bootup. - * Example 2: `rc-update delete dbus default` will remove the "dbus" service from the "default" runlevel and prevent it from starting during bootup. -* The "service" utility can be used exactly the same way as on FreeBSD to interact with services. +* Many OpenRC services are "multiplexed" for individual device/profile management. + * Example: The **network.wlan0** service controls the first wifi device, and should be started/stopped instead of the **network** service when re-configuring the Wi-Fi settings. +* The *[service-name]_enable="YES"* entries on FreeBSD are no longer needed to enable services on bootup. Instead, OpenRC provides a method for grouping services together (called "runlevels"), and the `rc-update` utility is used to add/remove bootup registrations for services within these groups. + * Example: `rc-update add dbus default` adds the **dbus** service to the **default** runlevel and enables it to automatically start on bootup. + * Example 2: `rc-update delete dbus default` removes the **dbus** service from the **default** runlevel and prevents it from starting during bootup. +* The "service" utility is used identically to FreeBSD for interacting with services. * Example: `service dbus stop` stops the **dbus** service when it is running. * Example 2: `service network.wlan0 restart` restarts the networking associated with the first wireless device.