TrueOS2017-08-10T01:42:21Zhttps://www.trueos.org/feed/atom/WordPresshttps://web.trueos.org/wp-content/uploads/2016/10/cropped-TrueOS_Icon_2-32x32.pngTimhttps://web.trueos.org/?p=16002017-08-07T13:31:34Z2017-08-07T13:26:17ZA new UNSTABLE update for TrueOS is available! Released regularly, UNSTABLE updates are the full “rolling release” of TrueOS. UNSTABLE includes experimental features, bugfixes, and other CURRENT FreeBSD work. It is meant to be used by those users interested in using the latest TrueOS and FreeBSD developments to help test and improve these projects. WARNING: […]

Released regularly, UNSTABLE updates are the full “rolling release” of TrueOS. UNSTABLE includes experimental features, bugfixes, and other CURRENT FreeBSD work. It is meant to be used by those users interested in using the latest TrueOS and FreeBSD developments to help test and improve these projects.

WARNING: UNSTABLE updates are released primarily for TrueOS and FreeBSD testing/experimentation purposes. Update and run UNSTABLE “at your own risk”.

Note: There was a CDN issue over the weekend that caused issues for early updaters. Everything appears to be resolved and the update is fully available again. If you encountered instability or package issues from updating on 8/6 or 8/5, roll back to a previous boot environment and run the update again.

Changes

UNSTABLE .iso and .img files beginning with TrueOS-2017-08-3-x64 will be available to download from http://download.trueos.org/unstable/amd64/. Due to CDN issues, these are not quite available, look for them later today or tomorrow (8/8/17).

The libhyve-remote aims to abstract functionalities from other third party libraries like libvncserver, freerdp, and spice to be used in hypervisor implementation. With a basic data structure it is easy to implement any remote desktop protocol without digging into the protocol specification or third part libraries – check some of our examples.We don’t statically link any third party library, instead we use a dynamic linker and load only the functionality necessary to launch the service.Our target is to abstract functionalities from libvncserver, freerdp and spice. Right now, libhyve-remote only supports libvncserver. It is possible to launch a VNC server with different screen resolution as well as with authentication.With this patch we implement support for bhyve to use libhyve-remote that basically abstract some functionalities from libvncserver.

Also, we add a new -s flag for vncserver, if the libhyve-remote library is not present in the system, we fallback to bhyve RFB implementation. For example:-s 2,fbuf,tcp=0.0.0.0:5937,w=800,h=600,password=1234567,vncserver,wait

New SysAdm Client pages under the System Management category:

System Control: This is an interface to browse all the sysctl’s on the system.

Devices: This lists all known information about devices on the designated system.

Lumina Theming: Lumina is testing new theming functionality! By default (in UNSTABLE), a heavily customized version of the Qt5ct engine is included and enabled. This is intended to allow users to quickly adjust themes/icon packs without needing to log out and back in. This also fixes a bug in Insight with different icons loading for the side and primary windows. Look for more information about this new functionality to be discussed on the Lumina Website.

Update to Iridium Web Browser: Iridium is a Chromium based browser built with user privacy and security as the primary concern, but still maintaining the speed and usability of Chromium. It is now up to date – give it a try and let us know what you think (search for iridium-browser in AppCafe).

Early addition of new translation files for Australian.

Additional Resources

Handbooks

As “TrueOS” incorporates the Lumina Desktop Environment and SysAdm, new users are encouraged to reference all three projects documentation:

The TrueOS handbook contains a comprehensive guide to assist in downloading and installing TrueOS. It also walks the reader through a basic post-install configuration and has application recommendations for a few common tasks such as printing and multimedia playback.

The Lumina handbook contains numerous instructions for customizing every aspect of the desktop environment. Instructions for customizing desktop appearance, default applications, menu contents, and general system settings are all contained in this handbook. Additionally, full descriptions of each included Lumina Utility and plugin are available, to further help fine tune the desktop experience.

The SysAdm Client handbook describes and guides users through using system management utilities via the SysAdm client. Here is a short list of system utilities discussed in this handbook:

User Manager: Manage system users and groups, including adding encryption to users.

Life Preserver: Manage system backups using the features of ZFS <LINK>.

These handbooks are designed to help users initialize and configure TrueOS to meet their specific desktop needs.

Community Help

If you encounter difficulty while using or configuring TrueOS, there is a knowledgeable and friendly community of users who are happy to help you troubleshoot TrueOS. Many of the developers and contributors to the TrueOS, Lumina, and SysAdm projects can also be found answering questions or discussing Open Source development in these channels. Here is a general breakdown of our community channels:

Discourse: The primary TrueOS forum. Discourse is used for lengthy discussions on particular topics, as well as a good place to ask questions or get assistance troubleshooting TrueOS. You don’t need an account to view posts on Discourse, but posting does require logging in with either a Discourse, Facebook, or GitHub account.

Gitter: Gitter provides real-time collaboration with TrueOS users and developers. Gitter does not require an application to use, but a GitHub or Twitter account is required to log in.

IRC: Like many open source projects, TrueOS has an Internet Relay Chat (IRC) channel so users can chat and get help in real time. To get connected, use this information in your IRC client:

Server name: irc.freenode.net

Channel name: #trueos (note the “#” is required)

TrueOS Subreddit: The TrueOS Project also has a Subreddit for users who prefer to use Reddit to ask questions and to search for or post how-tos. A Reddit account is not required in order to read the Subreddit, but it is necessary to create a login account to submit or comment on posts.

Bug Reporting

If you discover a bug while using TrueOS, report it via one of our GitHub issue trackers. Here are the various TrueOS project bug trackers:

trueos-core: Used for general TrueOS issues, Pico issues, and feature requests.

The TrueOS handbook has detailed instructions to help report a bug. It is recommended to refer to these instructions when creating new GitHub issues. Better bug reports usually result in faster fixes! To request a new feature, open a new issue in one of the related GitHub issue repositories and begin the title with “Feature Request:”.

]]>0Timhttps://web.trueos.org/?p=16132017-08-04T20:20:15Z2017-08-04T20:20:15ZA very small update has gone out to the TrueOS STABLE track today! There are just two changes: Chromium is updated to its latest available FreeBSD version. VM-bhyve is updated to its latest version.

]]>0Timhttps://web.trueos.org/?p=15092017-07-28T17:41:21Z2017-07-28T17:41:21ZThe OpenRC conversion project is done! Over one thousand script/port conversions are complete, and all will be available in the TrueOS UNSTABLE and STABLE tracks soon. The project wants to extend a huge thank you to all those who contributed to completing this milestone, and a special thank you to contributors ZackaryWelch and elarge011 for […]

The OpenRC conversion project is done! Over one thousand script/port conversions are complete, and all will be available in the TrueOS UNSTABLE and STABLE tracks soon. The project wants to extend a huge thank you to all those who contributed to completing this milestone, and a special thank you to contributors ZackaryWelch and elarge011 for doing the lion’s share of the work.

List of Contributors:

beanpole135

elarge011

kmoore134

NorwegianRockCat

mremski

pkgdemon

rebost

ZackaryWelch

(Apologies if I miss anyone – message me and I’ll add your Github user name to the list)

]]>8Timhttps://web.trueos.org/?p=14202017-07-26T15:06:32Z2017-07-26T15:04:18ZThe TrueOS project is always looking for community contribution. Documentation changes are a great way for users to not only make a solid contribution to the project, but learn more about it too! Over the last few months, many users have asked for both simple and detailed instructions on making documentation changes. These are now […]

The TrueOS project is always looking for community contribution. Documentation changes are a great way for users to not only make a solid contribution to the project, but learn more about it too! Over the last few months, many users have asked for both simple and detailed instructions on making documentation changes. These are now added to the TrueOS handbook in the Contributing to TrueOS section.

If interested in making a small alteration to the TrueOS handbook, here are some instructions for submitting a patch through the GitHub website. These instructions are also applicable to the Lumina and SysAdm handbooks. Lumina documentation is in the the lumina-docs repository, and SysAdm guides are in sysadm-docs.

Make a Doc change!

A GitHub account is required to submit patches to the TrueOS docs. Open a web browser and sign in to GitHub or make a new account. When making a new account, be sure to use an often checked email address, as all communication regarding patches and pull requests are sent to this address. Navigate to the trueos-docs GitHub repository. Click on the trueos-handbook directory to view all the documentation files. Open the .rst file corresponding to the chapter needing an update. The chapter names are reflected in the title of the .rst files. For example, open install.rst to fix an error spotted in handbook chapter 3: “Install”. This first image shows the trueos-docs repository and the contents of the trueos-handbook directory:

Contents of the /trueos-handbook directory

Open the desired chapter file by clicking its entry in the list. The trueos.rst file is an index file and should be ignored. Begin editing the file by clicking the Pencil icon in the upper right corner above the file’s text. The file moves to edit mode, where it is now possible to make changes, as the next image shows.

Editing install.rst with GitHub

When making a simple change, it is recommended to avoid adjusting the specific formatting elements and instead work within or around them. Once satisfied, scroll to the bottom of the page and write a detailed commit summary of the new changes. Click Propose file change (green button), then Create pull request to submit the changes to the project. GitHub then does an automated merge check. Click Create pull request again to submit the change to the repository. In the final step, a developer or project committer reviews the changes, merging them into the project or asking for more changes as necessary.

]]>0Timhttps://web.trueos.org/?p=13722017-07-27T17:11:20Z2017-07-24T13:49:41ZA new, very small hotfix to the update mechanism released today/yesterday. We believe there was breakage from the ino64 FreeBSD work merged into UNSTABLE that was causing TrueOS updater issues. After some heavy tinkering, the patch to fix the updater is functional and applied to both the STABLE and UNSTABLE update tracks! This update is […]

]]>A new, very small hotfix to the update mechanism released today/yesterday. We believe there was breakage from the ino64 FreeBSD work merged into UNSTABLE that was causing TrueOS updater issues. After some heavy tinkering, the patch to fix the updater is functional and applied to both the STABLE and UNSTABLE update tracks! This update is installed whenever the updater itself checks for updates. It may not trigger an update notification from the built-in SysAdm Update Manager.

This is a small hotfix to adjust the way in which the updater bootstraps itself and updates a TrueOS system. Because this is an updater fix, users may see their system update twice: once for the updater fix and once again for any broken/outstanding updates to the system itself. Please give feedback in our issues tracker or Discourse forum if you are still encountering problems with the updater after today, 7/24/17.

]]>0Timhttps://web.trueos.org/?p=13512017-07-18T15:10:28Z2017-07-18T15:09:25ZWe’d like to spotlight TrueOS community member Brad Alexander for documenting his experience repairing ZFS dataset replication with TrueOS. Thank you! His notes are posted here, and they’ve been added to the TrueOS handbook Troubleshooting section for later reference. Forcibly Resetting ZFS Replication Using Command Line lpreserver ZFS replication can be somewhat complex, […]

]]>We’d like to spotlight TrueOS community member Brad Alexander for documenting his experience repairing ZFS dataset replication with TrueOS. Thank you! His notes are posted here, and they’ve been added to the TrueOS handbook Troubleshooting section for later reference.

Forcibly Resetting ZFS Replication Using Command Line lpreserver

ZFS replication can be somewhat complex, and keeping all of the fiddly bits aligned can be fraught with danger. I recently had both of my TrueOS machines start failing to replicate. My desktop is called defiant, and has two pools, NX74205 and NCC1764. My laptop is yukon, and the pool is NCC74602. I am replicating to my FreeNAS server luna, to dataset NX80101/archive/<FQDN>. I will focus on what I did to get yukon working again in this document.

Original indications

The SysAdm Client tray icon was pulsing red. Right-clicking on the icon and clicking Messages would show the message:

send from @auto-2017-07-12-01-00-00 to NCC74602/ROOT/12.0-CURRENT-up-20170623_120331@auto-2017-07-14-01-00-00
total estimated size is 0
TIME SENT SNAPSHOT

And no useful errors were being written to the lpreserver_failed.log.

Repairing replication

First attempt:

The first approach I tried was to use the Sysadm Client:

I clicked on the dataset in question, then clicked Initialize. After waiting a few minutes, I clicked Start. I was immediately rewarded with a pulsing red icon in the system tray and received the same messages as above.

Second attempt:

I was working with, and want to specially thank @RodMyers and @NorwegianRockCat. They suggested I use the lpreserver command line. So I issued these commands:

It turned out there were a number of children. I logged into luna (the FreeNAS) and issued this command as root:

zfs destroy -r NX80101/archive/defiant.sonsofthunder.nanobit.org

I then ran the replicate init and replicate run commands again from the TrueOS host, and replication worked! It has continued to work too, at least until the next fiddly bit breaks.

Be a part of the TrueOS Community! Users are friendly and knowledgeable about TrueOS and general Open Source computing, so stop by one of our channels and ask questions or join a discussion! TrueOS uses Gitter for real time chat and Discourse for our public forum.

]]>0Timhttps://web.trueos.org/?p=13262017-07-14T16:34:53Z2017-07-14T16:34:53ZA new UNSTABLE update for TrueOS is available! Released regularly, UNSTABLE updates are the full “rolling release” of TrueOS. UNSTABLE includes experimental features, bugfixes, and other CURRENT FreeBSD work. It is meant to be used by those users interested in using the latest TrueOS and FreeBSD developments to help test and improve these projects. This […]

Released regularly, UNSTABLE updates are the full “rolling release” of TrueOS. UNSTABLE includes experimental features, bugfixes, and other CURRENT FreeBSD work. It is meant to be used by those users interested in using the latest TrueOS and FreeBSD developments to help test and improve these projects.

This is the first “true” UNSTABLE update since the 6-month STABLE image was released (June 2,2017). Previous UNSTABLE updates from June and July were maintaining parity between the two tracks. Now, UNSTABLE is ready to break away from STABLE and fulfill the developer goal to have an experimental, rolling-release, but still full-featured version of TrueOS.

WARNING: UNSTABLE updates are released primarily for TrueOS/FreeBSD testing/experimentation purposes. Update and run UNSTABLE “at your own risk”.

Current TrueOS users can update using the built-in update manager. Users already on UNSTABLE need to run pc-updatemanager syncconf in a command line to properly switch over to the new UNSTABLE repository URL. An alternate method is to switch from UNSTABLE to STABLE and click “Save” in the update manager, then switch back to UNSTABLE and click “Save” again. This resyncs the configuration files for the new repositories.

New UNSTABLE .iso and .img files beginning with TrueOS-2017-07-14-x64 are also available to download from http://download.trueos.org/unstable/amd64/ ! As of now, UNSTABLE and STABLE TrueOS .iso/.img files have the same naming. This is going to change very soon, but for the moment, users are cautioned to keep their UNSTABLE downloaded .iso files separate from the STABLE equivalent.

Changes

The UNSTABLE update repository has a new URL.

TrueOS UNSTABLE is synced with FreeBSD CURRENT as of June 22.

The TrueOS UNSTABLE branch of FreeBSD-ports is synced with FreeBSD as of July 11.

New UNSTABLE .iso and .img files beginning with TrueOS-2017-07-14-x64 are available to download and test.

Modules now load before running the sysctl init.d script.

trueos-server and trueos-desktop now select the proper package repository at load (installer fix).

HBSD: net/haproxy: Update LibreSSL patch

Added OpenRC script for OpenVPN

Add many more OpenRC service files:

dnscrypt-wrapper

dnscrypt-proxy

Courier

beanstalkd

ceph

dhcpd

foreman_proxy

glusterd

linknx

mosquitto

ntpa

ovsdb_server

repeater

rtgpoll

srelay

stone

Fixes to gdm

cx88d

emby_server

ffserver

freevo

zoneminder

Update to pc-updatemanager port

Fix config.sh location

Add XCB to ffmpeg options

FreeBSD ino64 patch is implemented for testing.

Known issues

VirtualBox is completely broken in this latest UNSTABLE version. Investigation is ongoing, but it initially appears to be a FreeBSD regression in CURRENT.

Additional Resources

Handbooks

As “TrueOS” incorporates the Lumina Desktop Environment and SysAdm, new users are encouraged to reference all three projects documentation:

The TrueOS handbook contains a comprehensive guide to assist in downloading and installing TrueOS. It also walks the reader through a basic post-install configuration and has application recommendations for a few common tasks such as printing and multimedia playback.

The Lumina handbook contains numerous instructions for customizing every aspect of the desktop environment. Instructions for customizing desktop appearance, default applications, menu contents, and general system settings are all contained in this handbook. Additionally, full descriptions of each included Lumina Utility and plugin are available, to further help fine tune the desktop experience.

The SysAdm Client handbook describes and guides users through using system management utilities via the SysAdm client. Here is a short list of system utilities discussed in this handbook:

User Manager: Manage system users and groups, including adding encryption to users.

Life Preserver: Manage system backups using the features of ZFS <LINK>.

These handbooks are designed to help users initialize and configure TrueOS to meet their specific desktop needs.

Community Help

If you encounter difficulty while using or configuring TrueOS, there is a knowledgeable and friendly community of users who are happy to help you troubleshoot TrueOS. Many of the developers and contributors to the TrueOS, Lumina, and SysAdm projects can also be found answering questions or discussing Open Source development in these channels. Here is a general breakdown of our community channels:

Discourse: The primary TrueOS forum. Discourse is used for lengthy discussions on particular topics, as well as a good place to ask questions or get assistance troubleshooting TrueOS. You don’t need an account to view posts on Discourse, but posting does require logging in with either a Discourse, Facebook, or GitHub account.

Gitter: Gitter provides real-time collaboration with TrueOS users and developers. Gitter does not require an application to use, but a GitHub or Twitter account is required to log in.

IRC: Like many open source projects, TrueOS has an Internet Relay Chat (IRC) channel so users can chat and get help in real time. To get connected, use this information in your IRC client:

Server name: irc.freenode.net

Channel name: #trueos (note the “#” is required)

TrueOS Subreddit: The TrueOS Project also has a Subreddit for users who prefer to use Reddit to ask questions and to search for or post how-tos. A Reddit account is not required in order to read the Subreddit, but it is necessary to create a login account to submit or comment on posts.

Bug Reporting

If you discover a bug while using TrueOS, report it via one of our GitHub issue trackers. Here are the various TrueOS project bug trackers:

trueos-core: Used for general TrueOS issues, Pico issues, and feature requests.

The TrueOS handbook has detailed instructions to help report a bug. It is recommended to refer to these instructions when creating new GitHub issues. Better bug reports usually result in faster fixes! To request a new feature, open a new issue in one of the related GitHub issue repositories and begin the title with “Feature Request:”.

]]>0Timhttps://web.trueos.org/?p=13182017-07-07T12:18:50Z2017-07-05T12:41:22ZWith the release of Lumina 1.3.0, The devs decided to back-port that release into TrueOS STABLE. In truth, most of the 1.3.0 changes already exist in STABLE. However, this update brings in a few missing patches and bumps the Lumina version up to its proper 1.3.0 tag. Update Notes Here is the short […]

]]>With the release of Lumina 1.3.0, The devs decided to back-port that release into TrueOS STABLE. In truth, most of the 1.3.0 changes already exist in STABLE. However, this update brings in a few missing patches and bumps the Lumina version up to its proper 1.3.0 tag.

Update Notes

Here is the short list of changes added to TrueOS STABLE:

Lumina is updated to version 1.3.0

Small fix to pc-xgui to prevent the dialogue from growing too large for the screen.

The system link to the offline TrueOS handbook is fixed.

pcdm autologin now can happen if the delay is set to less than two seconds.

]]>0Timhttps://web.trueos.org/?p=13152017-06-26T19:29:52Z2017-06-26T19:29:52ZA new version of Lumina is available, with the full announcement and changelog available on the Lumina Website. Notable changes include new icon themes, a number of updates to the file manager, and the release of the lightweight lumina-mediaplayer utility. There appear to be a large number of performance improvements and bugfixes too, which are […]

Notable changes include new icon themes, a number of updates to the file manager, and the release of the lightweight lumina-mediaplayer utility. There appear to be a large number of performance improvements and bugfixes too, which are always welcome.

For TrueOS users, the majority of the Lumina 1.3.0 release is already included in the latest STABLE update, with a few small elements (and the version number update) to be back-ported into STABLE very soon.

]]>0Timhttps://web.trueos.org/?p=13092017-06-23T18:11:55Z2017-06-23T18:11:55ZWe’ve pushed several fixes to the UNSTABLE and STABLE branches over the last week: /etc/init.d/routing startup errors. Virtualbox now properly loads vboxnet modules. Webcamd is enabled by default. The TrueOS installer now defaults to a “fresh” installation. UNSTABLE also has an update coming soon to add a couple important items for testing: […]