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 058dbbc68ef9bd7f3c8b1a4fb05c34a762b56dee
@@ -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"
This conversation was marked as resolved by beanpole135

This comment has been minimized.

@Mrt134

Mrt134 Feb 16, 2019
Collaborator

Suggested change
* 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"
* Some services have different names: **dhcpcd** instead of *dhclient*, **network** instead of *netif*.
* Many OpenRC services are "multiplexed" for individual device/profile management
This conversation was marked as resolved by beanpole135

This comment has been minimized.

@Mrt134

Mrt134 Feb 16, 2019
Collaborator

Suggested change
* Many OpenRC services are "multiplexed" for individual device/profile management
* 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.
This conversation was marked as resolved by beanpole135

This comment has been minimized.

@Mrt134

Mrt134 Feb 16, 2019
Collaborator

Suggested change
* 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.
* 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.
This conversation was marked as resolved by beanpole135

This comment has been minimized.

@Mrt134

Mrt134 Feb 16, 2019
Collaborator

Suggested change
* 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.
* 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.