Further commands can be found here
shutdown -r nowdoas restorepoint create your-namerestorepoint statusdoas restorepoint rollbackpkg infopkg info | lessUseful keys in less:
Space= next pageb= previous page/text= searchq= quit
Before updating or upgrading your system make sure to have a proper restore point created beforehand
doas pkg upgradedoas pkg update -f && doas pkg upgrade
doas pkg install tcbsd-upgrade
doas tcbsd-upgrade majorafter upgrading, dont forget to restart system with
doas shutdown -r nowThe dataset zroot/ROOT/default, which contains most of the system and TwinCAT, is protected against write accesses when the write filter is active. No other datasets are covered by the write filter. For example, user files can still be persistently stored at /usr/home or log files at /var/log, even if the rest of the system is reset after a restart.
doas service bwf enabledoas service bwf disableExceptions for the write filter can be defined by creating new zfs datasets, since only the dataset zroot/ROOT/default is protected from write accesses; all other system datasets, including newly created datasets, are excluded from the protection.
- Delete the current boot directory and all it's contents
doas rm -rf /usr/local/etc/TwinCAT/3.1/Boot/*. - Create a new ZFS dataset named zroot/usr/TwinCAT-Boot and mount it at /usr/local/etc/TwinCAT/3.1/Boot.
doas zfs create -o mountpoint=/usr/local/etc/TwinCAT/3.1/Boot zroot/usr/TwinCAT-Boot
Any data stored in this dataset will be accessible at this location and is excluded from the write filter
In case you need to reverse the changes made in the above example and revert the directory to being managed by zroot/ROOT/default, you can follow these steps:
- Unmount the new dataset:
doas zfs unmount zroot/usr/TwinCAT-Boot
- Destroy the new dataset
doas zfs destroy zroot/usr/TwinCAT-Boot
- Recreate the directory within the original dataset
doas mkdir -p /usr/local/etc/TwinCAT/3.1/Boot
ads localhost netiddoas service pf stopdoas service pf startdoas ee /etc/pf.confAdd the following to the file,
pass in quick proto tcp to port 502 keep state
Restart the firewall with new rule
doas pfctl -f /etc/pf.confpasswdThe following command will set one core as being isolated. You can see core informtion using TcCoreConf.
TcCoreConf –s 1| Directory | Description |
|---|---|
| / | Root directory and top-level directory hierarchy. |
| /bin/ | Basic user applications for single-user and multi-user environments. |
| /boot/ | Kernel, drivers, programs and configuration files for the boot process. |
| /dev/ | Device nodes, which can be used to access hardware directly, for example. |
| /etc/ | System-relevant scripts and configuration files. |
| /home/ | Link to /usr/home, where the home directories of the users are located. |
| /mnt/ | Empty directory; usually serves as a mount point for USB sticks, for example. |
| /root/ | Home directory of the superuser root. |
| /sbin/ | Basic system applications for single-user and multi-user environments. |
| /usr/ | Unix system resources, contains most of the user applications. |
| /usr/bin | General applications. |
| /usr/include/ | Contains header files for C compilers. |
| /usr/local/ | Local programs and libraries, i.e., software installed by a user, such as software unrelated to the basic FreeBSD system itself. |
| /usr/local/bin/ | Mainly Beckhoff applications |
| /usr/local/etc/ | Configuration files, TwinCAT directory with TwinCAT Functions and PLC project. |
| /usr/local/include/ | Including ADS header files TcAdsDef.h and TcAdsAPI.h |
| /usr/sbin/ | System applications that are executed by the user. |
| /var/ | Variable files, i.e. temporary files with changing content such as log files. |
| /var/log/ | Contains system log files. |