BSD
GhostBSD Reaffirms To Being TrueOS+BSD Desktop OS With Official MATE Desktop
Submitted by Roy Schestowitz on Friday 18th of October 2019 12:42:10 AM Filed under
With Project Trident moving away from a TrueOS/FreeBSD base to instead Void Linux, if you are looking for a good BSD-based desktop operating system it largely comes down to the likes of MidnightBSD and GhostBSD providing good out-of-the-box setups. As for GhostBSD, they are reaffirming their commitment to using TrueOS/FreeBSD and MATE as their official desktop.
The project reaffirmed on Wednesday that they are sticking to their TrueOS with FreeBSD 12-STABLE base while being a "slow-moving rolling release' that will eventually migrate to TrueOS with FreeBSD 13-STABLE after it is available.
Direct: Dealing with the misunderstandings of what is GhostBSD
»
- Login or register to post comments
Printer-friendly version- Read more
- 859 reads
PDF version
OpenBSD 6.6 Released
Submitted by Roy Schestowitz on Friday 18th of October 2019 12:37:16 AM Filed under-
OpenBSD 6.6
This is a partial list of new features and systems included in OpenBSD 6.6. For a comprehensive list, see the changelog leading to 6.6.
-
OpenBSD 6.6 Arrives: Disables GCC In Base For ARMv7/i386, SMP Improvements, AMDGPU Added
Theo de Raadt released OpenBSD 6.6 today as the newest feature update to this popular BSD operating system known for its security focus.
OpenBSD 6.6 has moved to disabling GCC in its base packages for i386 and ARMv7, LLVM Clang platform support has been expanded, various SMP improvements and more system calls being unlocked, improved Linux compatibility with ACPI interfaces, a number of new hardware drivers, wired and wireless networking stack improvements, various installation enhancements, and the never-ending work on improving the security. OpenBSD 6.6 ships with OpenSSH 8.1, LibreSSL 3.0.2, OpenSMTPD 6.6, and other updated packages.
»
Project Trident 2020 OS Migration
Submitted by Roy Schestowitz on Wednesday 16th of October 2019 12:17:07 AM Filed under
After several months of examination and testing of the various operating systems that are available right now, we have reached a conclusion. Project Trident will rebasing with Void Linux.
Also: Project Trident Switching From TrueOS/FreeBSD Distribution To Basing On Void Linux
»
FreeBSD 12.1-RC1 Now Available
Submitted by Roy Schestowitz on Saturday 12th of October 2019 08:13:56 AM Filed under-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The first RC build of the 12.1-RELEASE release cycle is now available.
Installation images are available for:
o 12.1-RC1 amd64 GENERIC
o 12.1-RC1 i386 GENERIC
o 12.1-RC1 powerpc GENERIC
o 12.1-RC1 powerpc64 GENERIC64
o 12.1-RC1 powerpcspe MPC85XXSPE
o 12.1-RC1 sparc64 GENERIC
o 12.1-RC1 armv6 RPI-B
o 12.1-RC1 armv7 BANANAPI
o 12.1-RC1 armv7 BEAGLEBONE
o 12.1-RC1 armv7 CUBIEBOARD
o 12.1-RC1 armv7 CUBIEBOARD2
o 12.1-RC1 armv7 CUBOX-HUMMINGBOARD
o 12.1-RC1 armv7 RPI2
o 12.1-RC1 armv7 PANDABOARD
o 12.1-RC1 armv7 WANDBOARD
o 12.1-RC1 armv7 GENERICSD
o 12.1-RC1 aarch64 GENERIC
o 12.1-RC1 aarch64 RPI3
o 12.1-RC1 aarch64 PINE64
o 12.1-RC1 aarch64 PINE64-LTS
Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access. Additionally,
the root user password is set to root. It is strongly recommended
to change the password for both users after gaining access to the
system.
Installer images and memory stick images are available here:
https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/
The image checksums follow at the end of this e-mail.
If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.
If you would like to use SVN to do a source based update of an existing
system, use the "releng/12.1" branch.
A summary of changes since 12.1-BETA3 includes:
o A NULL pointer dereference that could lead to a system crash had been
fixed.
o A fix to correctly implement pmap_page_is_mapped() on arm64 and riscv.
o A fix to tun(4) and tap(4) when destroying interfaces had been added.
o A fix to krping to notify sleeping threads of device removal had been
added.
o Several updates to mlx5core, mlx5en(4), and mlx5ib(4).
o Several fixes in libusb(3) and xhci(4) have been added.
o Several SCTP and TCP fixes have been added.
A list of changes since 12.0-RELEASE is available in the releng/12.1
release notes:
https://www.freebsd.org/releases/12.1R/relnotes.html
Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 12.1-RELEASE cycle progresses.
=== Virtual Machine Disk Images ===
VM disk images are available for the amd64, i386, and aarch64
architectures. Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):
https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-RC1/
The partition layout is:
~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label)
~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)
The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats. The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.
Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images. See this page for more information:
https://wiki.freebsd.org/arm64/QEMU
To boot the VM image, run:
% qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \
-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
-drive if=none,file=VMDISK,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-device virtio-net-device,netdev=net0 \
-netdev user,id=net0
Be sure to replace "VMDISK" with the path to the virtual machine image.
=== Amazon EC2 AMI Images ===
FreeBSD/amd64 EC2 AMIs are available in the following regions:
eu-north-1 region: ami-0c2caa354f54dcc8e
ap-south-1 region: ami-011f6d0b22b4179ae
eu-west-3 region: ami-0e633b1e66b94dc5e
eu-west-2 region: ami-06f77908c8875b5ce
eu-west-1 region: ami-07d5b3d4ffa682d66
ap-northeast-2 region: ami-0a0d9969831c99d3f
ap-northeast-1 region: ami-092398d1a41a67f27
sa-east-1 region: ami-023dd6db41165f441
ca-central-1 region: ami-0cf9fd10259cf4eb2
ap-east-1 region: ami-0e255d1bb4a1f76f4
ap-southeast-1 region: ami-0404212cff3236606
ap-southeast-2 region: ami-0fea81c67debcba8b
eu-central-1 region: ami-08e32f4e90fd250f4
us-east-1 region: ami-0e6e401d0ffebd916
us-east-2 region: ami-0d094195cae5bf901
us-west-1 region: ami-04c1e10d06064e68d
us-west-2 region: ami-02d0010139a9a494e
FreeBSD/aarch64 EC2 AMIs are available in the following regions:
eu-north-1 region: ami-022e4644320e82ac1
ap-south-1 region: ami-0e421a1864d53d226
eu-west-3 region: ami-0bffb1c264a4b8d09
eu-west-2 region: ami-0f596a538918dc9c8
eu-west-1 region: ami-063c017d8b9086b55
ap-northeast-2 region: ami-0b34ed283d7dd41ae
ap-northeast-1 region: ami-0071602b3e78a8de0
sa-east-1 region: ami-07986820662819e67
ca-central-1 region: ami-0d9ee49739059957b
ap-east-1 region: ami-00ae1e2b897eb6230
ap-southeast-1 region: ami-0018127ce245410e0
ap-southeast-2 region: ami-02fa0380052cd268f
eu-central-1 region: ami-01836dc7a9f273243
us-east-1 region: ami-0018654c0af06d99d
us-east-2 region: ami-06a4203b93836b927
us-west-1 region: ami-09c5010072b44bd96
us-west-2 region: ami-063fae5c2ec327807
=== Vagrant Images ===
FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:
% vagrant init freebsd/FreeBSD-12.1-RC1
% vagrant up
=== Upgrading ===
The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases. Systems running earlier
FreeBSD releases can upgrade as follows:
# freebsd-update upgrade -r 12.1-RC1
During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.
# freebsd-update install
The system must be rebooted with the newly installed kernel before
continuing.
# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new
userland components:
# freebsd-update install
It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 11.x. Alternatively, the user can install misc/compat11x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:
# shutdown -r now
Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:
# freebsd-update install
»
- 1 comment
- Printer-friendly version
- Read more
- 1312 reads
- PDF version
Announce: OpenSSH 8.1 released
Submitted by Roy Schestowitz on Wednesday 9th of October 2019 06:06:34 AM Filed under
OpenSSH 8.1 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly.
»
- Login or register to post comments
- Printer-friendly version
- Read more
- 2142 reads
- PDF version
Project Trident 19.10 Now Available
Submitted by Roy Schestowitz on Monday 7th of October 2019 01:00:43 AM Filed under
This is a general package update to the CURRENT release repository based upon TrueOS 19.10
»
- Login or register to post comments
- Printer-friendly version
- Read more
- 2957 reads
- PDF version
FreeBSD 12.1-BETA3 Now Available
Submitted by Roy Schestowitz on Saturday 5th of October 2019 03:08:25 AM Filed under
The third BETA build of the 12.1-RELEASE release cycle is now available.
Installation images are available for:
o 12.1-BETA3 amd64 GENERIC
o 12.1-BETA3 i386 GENERIC
o 12.1-BETA3 powerpc GENERIC
o 12.1-BETA3 powerpc64 GENERIC64
o 12.1-BETA3 powerpcspe MPC85XXSPE
o 12.1-BETA3 sparc64 GENERIC
o 12.1-BETA3 armv6 RPI-B
o 12.1-BETA3 armv7 BANANAPI
o 12.1-BETA3 armv7 BEAGLEBONE
o 12.1-BETA3 armv7 CUBIEBOARD
o 12.1-BETA3 armv7 CUBIEBOARD2
o 12.1-BETA3 armv7 CUBOX-HUMMINGBOARD
o 12.1-BETA3 armv7 RPI2
o 12.1-BETA3 armv7 PANDABOARD
o 12.1-BETA3 armv7 WANDBOARD
o 12.1-BETA3 armv7 GENERICSD
o 12.1-BETA3 aarch64 GENERIC
o 12.1-BETA3 aarch64 RPI3
o 12.1-BETA3 aarch64 PINE64
o 12.1-BETA3 aarch64 PINE64-LTS
Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access. Additionally,
the root user password is set to root. It is strongly recommended
to change the password for both users after gaining access to the
system.
Installer images and memory stick images are available here:
https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/
The image checksums follow at the end of this e-mail.
If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.
If you would like to use SVN to do a source based update of an existing
system, use the "releng/12.1" branch.
A summary of changes since 12.1-BETA2 includes:
o An issue with imx6-based arm boards had been fixed.
o An issue with 64-bit long double types leading to link failures had
been fixed.
o An overflow logic error had been fixed in fsck_msdosfs(8).
o An issue in destruction of robust mutexes had been fixed.
o Support for the '-vnP' flags to the zfs send subcommand had been
added for bookmarks.
o The ixgbe(4) driver had been updated to prevent a potential system
crash with certain 10Gb Intel NICs.
o A regression with the zfs send subcommand when using the '-n', '-P',
and '-i' flags had been fixed.
o The freebsd-update(8) utility had been updated to include two new
subcommands, updatesready and showconfig.
o Support for 'ps -H' had been added to kvm(3).
o An issue when compiling certain ports targeting Intel Atom CPUs had
been fixed.
o A use-after-free in SCTP had been fixed.
o A regression that could lead to a system crash when using vmxnet3 had
been fixed.
A list of changes since 12.0-RELEASE is available in the releng/12.1
release notes:
https://www.freebsd.org/releases/12.1R/relnotes.html
Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 12.1-RELEASE cycle progresses.
=== Virtual Machine Disk Images ===
VM disk images are available for the amd64, i386, and aarch64
architectures. Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):
https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-BETA3/
The partition layout is:
~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label)
~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)
The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats. The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.
Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images. See this page for more information:
https://wiki.freebsd.org/arm64/QEMU
To boot the VM image, run:
% qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \
-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
-drive if=none,file=VMDISK,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-device virtio-net-device,netdev=net0 \
-netdev user,id=net0
Be sure to replace "VMDISK" with the path to the virtual machine image.
=== Amazon EC2 AMI Images ===
FreeBSD/amd64 EC2 AMIs are available in the following regions:
eu-north-1 region: ami-07085de4e26071c9e
ap-south-1 region: ami-095bd806d8acfffb1
eu-west-3 region: ami-0314542b8d7579bdd
eu-west-2 region: ami-06ec921eb87ef4d7b
eu-west-1 region: ami-0f0051c800be4091e
ap-northeast-2 region: ami-0f109258a463177bb
ap-northeast-1 region: ami-0224a1cb8e19333b8
sa-east-1 region: ami-0536a86bff5f33356
ca-central-1 region: ami-06709921360dccfa3
ap-east-1 region: ami-0142af9336f6e529c
ap-southeast-1 region: ami-0c439e0bc0c567dd3
ap-southeast-2 region: ami-0fa770b7f07583b48
eu-central-1 region: ami-0dfca49cf2ba89c43
us-east-1 region: ami-06884b4e2e511590f
us-east-2 region: ami-06c687665309d8b17
us-west-1 region: ami-0dce597e8b07a6c6d
us-west-2 region: ami-0e1f5ccdd2221b1d6
FreeBSD/aarch64 EC2 AMIs are available in the following regions:
eu-north-1 region: ami-0914805810f9fcca2
ap-south-1 region: ami-0862409434d8089f2
eu-west-3 region: ami-08e6dc501b060fa7c
eu-west-2 region: ami-000f2362fef121710
eu-west-1 region: ami-0c7a18e2b216a1b0c
ap-northeast-2 region: ami-047bc72d91ab47b95
ap-northeast-1 region: ami-082dcca6b9ac52f3f
sa-east-1 region: ami-0a9fd8ffffc889430
ca-central-1 region: ami-0d513e584801de3fa
ap-east-1 region: ami-089a6b231886f692f
ap-southeast-1 region: ami-09c6f305a761c8712
ap-southeast-2 region: ami-0ee5e02b85aecbef3
eu-central-1 region: ami-08321cbac28d28d71
us-east-1 region: ami-0a9c2fdd733536b50
us-east-2 region: ami-0a5b46f4260ed9ca5
us-west-1 region: ami-01aca4de517a623fe
us-west-2 region: ami-0ac8b561fb3597d89
=== Vagrant Images ===
FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:
% vagrant init freebsd/FreeBSD-12.1-BETA3
% vagrant up
=== Upgrading ===
The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases. Systems running earlier
FreeBSD releases can upgrade as follows:
# freebsd-update upgrade -r 12.1-BETA3
During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.
# freebsd-update install
The system must be rebooted with the newly installed kernel before
continuing.
# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new
userland components:
# freebsd-update install
It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 11.x. Alternatively, the user can install misc/compat11x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:
# shutdown -r now
Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:
# freebsd-update install
»
- Login or register to post comments
- Printer-friendly version
- Read more
- 1501 reads
- PDF version
Programming, Open Hardware and BSD
Submitted by Roy Schestowitz on Friday 4th of October 2019 05:52:12 PM Filed under
-
The rise of open-source computing
is a set of open-source designs for microchips that was initially developed a decade ago at the University of California, Berkeley. These days it is attracting attention from many big technology firms, including Google, Nvidia and Qualcomm (see article). In August IBM made its Power chip designs open-source. These moves are welcome, for two reasons.
-
A Message to Our Readers
We ask for your help in getting the word out (in addition to hopefully buying the issue when it's released). We know there are many thousands out there who no longer have bookstores that carry 2600 in their neighborhoods or who live in parts of the world where getting our publication has always been, at best, a challenge.
Please show your support and buy this issue which you can then enjoy forever - and let everyone know what we're doing. Because if this is a success, we will be able to invest more into the magazine (paper and digital) to make it even better, as well as support more projects like HOPE.
-
Binary Hardening in IoT products
Unfortunately, with few exceptions (notably Synology) we see there is very little coverage, and even Synology struggles to adopt basic hardening features like ASLR and stack guards.
A perfect score, where all binaries had all 5 basic safety features, would result in a chart that looks like a regular pentagon. Instead, in most vendors’ cases, they struggle to achieve polygon status at all.
-
Milky Way v0.3 release
Added
LibreSSL as the default provider of SSL and TLS protocols
Xenocara as the default provider of display server for the X Window System -
sysupgrade(8) Added to OpenBSD 6.5
In a move bound to be greeted with great enthusiasm, the newly-released Patch 012 for OpenBSD 6.5 adds sysupgrade(8) to the system.
»
- Login or register to post comments
- Printer-friendly version
- Read more
- 1465 reads
- PDF version
FreeBSD 12.1-BETA2 Now Available
Submitted by Roy Schestowitz on Sunday 29th of September 2019 02:40:50 AM Filed under
The second BETA build of the 12.1-RELEASE release cycle is now
available.
Installation images are available for:
o 12.1-BETA2 amd64 GENERIC
o 12.1-BETA2 i386 GENERIC
o 12.1-BETA2 powerpc GENERIC
o 12.1-BETA2 powerpc64 GENERIC64
o 12.1-BETA2 powerpcspe MPC85XXSPE
o 12.1-BETA2 sparc64 GENERIC
o 12.1-BETA2 armv6 RPI-B
o 12.1-BETA2 armv7 BANANAPI
o 12.1-BETA2 armv7 BEAGLEBONE
o 12.1-BETA2 armv7 CUBIEBOARD
o 12.1-BETA2 armv7 CUBIEBOARD2
o 12.1-BETA2 armv7 CUBOX-HUMMINGBOARD
o 12.1-BETA2 armv7 RPI2
o 12.1-BETA2 armv7 PANDABOARD
o 12.1-BETA2 armv7 WANDBOARD
o 12.1-BETA2 armv7 GENERICSD
o 12.1-BETA2 aarch64 GENERIC
o 12.1-BETA2 aarch64 RPI3
o 12.1-BETA2 aarch64 PINE64
o 12.1-BETA2 aarch64 PINE64-LTS
Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access. Additionally,
the root user password is set to root. It is strongly recommended
to change the password for both users after gaining access to the
system.
Installer images and memory stick images are available here:
https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/
The image checksums follow at the end of this e-mail.
If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.
If you would like to use SVN to do a source based update of an existing
system, use the "releng/12.1" branch.
A summary of changes since 12.1-BETA1 includes:
o An off-by-one error in fusefs(5) had been fixed.
o A problem with in-place strip(1) on msdosfs(5) had been fixed.
o Stability fixes for mpr(4) and mps(4) have been merged from head.
Note, support for these drivers have been removed for 32-bit powerpc.
o A regression had been fixed in the ping6(8) utility when the system is
built without capsicum(4).
o A regression in the jme(4) driver had been fixed.
o A change to the bhyve(4) uart(4) driver had been fixed to support
running under syzkaller.
o The WITH_PIE and WITH_BIND_NOW build knobs have been added.
o The 'updatesready' and 'showconfig' subcommands have been added to
freebsd-update(8).
o The camcontrol(8) 'devtype' subcommand had been fixed to correctly
report SATL devices.
A list of changes since 12.0-RELEASE is available in the releng/12.1
release notes:
https://www.freebsd.org/releases/12.1R/relnotes.html
Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 12.1-RELEASE cycle progresses.
=== Virtual Machine Disk Images ===
VM disk images are available for the amd64, i386, and aarch64
architectures. Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):
https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-BETA2/
The partition layout is:
~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label)
~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)
The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats. The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.
Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images. See this page for more information:
https://wiki.freebsd.org/arm64/QEMU
To boot the VM image, run:
% qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \
-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
-drive if=none,file=VMDISK,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-device virtio-net-device,netdev=net0 \
-netdev user,id=net0
Be sure to replace "VMDISK" with the path to the virtual machine image.
=== Amazon EC2 AMI Images ===
FreeBSD/amd64 EC2 AMIs are available in the following regions:
eu-north-1 region: ami-0fde974647f2afb71
ap-south-1 region: ami-08c5b6c3c67660000
eu-west-3 region: ami-0d2295cb848b04044
eu-west-2 region: ami-0defe97a58c32e336
eu-west-1 region: ami-04794e03ec4994477
ap-northeast-2 region: ami-0376260338b9a442c
ap-northeast-1 region: ami-030b542da16e02b36
sa-east-1 region: ami-09fef4294a171f081
ca-central-1 region: ami-0444d3dbbb3d973d2
ap-east-1 region: ami-01870b4cd52cd63f5
ap-southeast-1 region: ami-0ef470ae9dddc6d31
ap-southeast-2 region: ami-0eb87756562803e37
eu-central-1 region: ami-0d4f1151306798937
us-east-1 region: ami-0aa4feba66441f8cb
us-east-2 region: ami-073aac094f7a1e753
us-west-1 region: ami-0b702fd3bc6987d9e
us-west-2 region: ami-01e70706d53dcbd16
FreeBSD/aarch64 EC2 AMIs are available in the following regions:
eu-north-1 region: ami-004e595acdaea9f8a
ap-south-1 region: ami-043ee11f276cbac49
eu-west-3 region: ami-0a3ca0207e9a78b42
eu-west-2 region: ami-04cf3e3951b03f0e7
eu-west-1 region: ami-0846d71aa6ed537a7
ap-northeast-2 region: ami-0c8b2410ee65152eb
ap-northeast-1 region: ami-0d0495617fe90c04d
sa-east-1 region: ami-08f2f3eb468314f2f
ca-central-1 region: ami-0ea0dff5097085c4f
ap-east-1 region: ami-0e8e411b892c424f3
ap-southeast-1 region: ami-0552d07457be8afe7
ap-southeast-2 region: ami-0f89f9d16dc3fc949
eu-central-1 region: ami-05f5b271d7603e2cb
us-east-1 region: ami-0dd2d517058d5c225
us-east-2 region: ami-06d46829d315d1e20
us-west-1 region: ami-047a11f3142a87598
us-west-2 region: ami-0df2f50be88aa4073
=== Vagrant Images ===
FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:
% vagrant init freebsd/FreeBSD-12.1-BETA2
% vagrant up
=== Upgrading ===
The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases. Systems running earlier
FreeBSD releases can upgrade as follows:
# freebsd-update upgrade -r 12.1-BETA2
During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.
# freebsd-update install
The system must be rebooted with the newly installed kernel before
continuing.
# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new
userland components:
# freebsd-update install
It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 11.x. Alternatively, the user can install misc/compat11x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:
# shutdown -r now
Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:
# freebsd-update install
»
- Login or register to post comments
- Printer-friendly version
- Read more
- 1200 reads
- PDF version
DragonFlyBSD's HAMMER2 Gets Basic FSCK Support
Submitted by Roy Schestowitz on Monday 23rd of September 2019 09:15:12 AM Filed under
While the Copy-on-Write file-system shouldn't technically require fsck support, basic file-system consistency checking support has been implemented anyhow. In the initial implementation, the fsck code for HAMMER2 cannot repair any damaged file-system but can only verify that the file-system is intact.
»
- Login or register to post comments
- Printer-friendly version
- Read more
- 1159 reads
- PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
Leftovers: GNOME/GTK, Android-x86, Fedora, LibreOffice and More
| Proprietary Software, Games, Patent Traps/Tax and Openwashing
|
Linux Devices/Open Hardware
| Graphics: Gallium3D and AMDGPU
|
.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.
Recent comments
3 hours 9 min ago
5 hours 1 min ago
6 hours 46 min ago
6 hours 49 min ago
6 hours 55 min ago
7 hours 23 min ago
7 hours 30 min ago
7 hours 34 min ago
14 hours 51 min ago
20 hours 51 min ago