Present the truth in a manner that offends none
of the parties involved.
Fluid communication between languages
require emphasis and enunciation of culture
and understanding. This is one part of
interpretation.
Eloquence and articulation are for others to
understand you.
In some ports, there are configure arguments
and/ or CPU ISA architecture specifics. Today,
we will learn to adapt the port for both.
Look at the port and download with git, wget,
or another command line utility.
Search for the configure file. Even if you do
not like this next suggestion, use it to read
the entire configure file. cat $CONFIGURE_FILE
| more. Note that some build systems will
require you to create a document beforehand.
Search for the following: architecture
dependent flags. Disable these when necessary
in the ports Makefile. If your chosen
architecture is not in the file, then add it
in the configure file and add for architecture
$SUCH_AND_SUCH to the port Makefile.
Whatever arguments that you want in the
configure file that are not arguments in the
port Makefile, add those to the already
existing arguments. SIMD arguments are
CPU ISA specific, adapt to use whatever is
on the CPU of your chosen or available
architecture.
Do not patch. Rewrite and save. Let the
upstream maintainers know what you did.
If the build fails, rebuild and tee the output
to a text file. Use the cat $FILENAME |more
so you can see where the error is. If the
operating system team requires certain
code standards, then follow them. They
have a very good reason for doing such.
It is better to build on bare metal than
use a virtual machine or cross compile.
Those two options will not show you
real world errors.
When porting your own or others' software,
if the source is not open source then do not
bother. They have their reasons. Make yours
available to the public. If it is open source and
people find vulnerabilities and/ or exploits,
you will know what to fix. Tell them,
"Thank you."
The more operating systems that you port to
and the more CPU ISA architectures you also
port to, the more users, eyes, and ears.
Do it yourself by hand and accept your
errors and mistakes. This will teach and
assist you in better coding and development.
Take and accept a challenge. If it will compile
on the most difficult environments, then it
will definitely compile on the most common.
Enjoy and happy positive hacking.
Reference post:
https://freebsdgoogledeveloper.blogspot.com/2026/04/setting-up-freebsd-security-laptop.html
Guided/ suggested tutorial:
https://freebsdgoogledeveloper.blogspot.com/2026/04/quick-guide-to-freebsd-system.html
Remember that you may have to do this many
times.
When downloading source,
./configure --help|more will show you
options that may not be in the port
Makefile. Use the porter's handbook:
https://docs.freebsd.org/en/books/porters-handbook/
To learn what to edit.
https://share.google/aimode/SbEiDntxdthxzYial
Read the entire thing because you will need that
to install the image.
Set your bios to boot from USB image after
you have enabled legacy boot and have
disabled secure boot.
Okay:
Fedora media writer for Windows :
https://fedoraproject.org/workstation/download/
The download link is at the bottom of the page.
Latest FreeBSD AMD64 (x86_64) ISO images:
https://download.freebsd.org/releases/amd64/amd64/ISO-IMAGES/14.4/
You may pick boot only or the next smallest
in size. Download. This will be the image for
installation. Use thus when choosing the media
for the fedora media program.
Go back and check the bios settings on your
laptop. Legacy, no secure boot, boot first from
USB drive.
Boot from the USB.
Install.
Full/ dedicated disk. Let it set up everything.
Your job is:
Create a root user account.
Create a privileged account that is a member
of the group wheel. This is your administrative
and maintenance user. Do not use this account
for running any bhyve VM instance.
Create an unprivileged account. This is the
user you will add to the vmm type account
/ group mentioned in the earlier reference
post. Choose to hide all user data from all
other users. If someone manages to enter and
escape your VM, they will be stuck in a
useless account that can't see anything.
Do add ports.
Check everything
Remove media. Reboot.
Okay.
Here is where you search for packages:
Search for: automount, wifimgr, Xfce4,
SciTe or scite, nap, nessus, wireshark, and
all of your other wonderful tools. On your
portable system with the privileged user -
not root -
su, enter administrative/ root password
cd to /usr/ports
For every query on freshports cd to that
subsection.
Using ls will show you the directories.
Using ls| more will allow you to see the
directory listing a page at a time.
Cd to chosen directory.
Cd to port.
Type make && make install && make clean.
Cd to /ust/ports
Repeat for each port.
Configure X - the windowing graphical system-
using the link references in the reference post.
Your xorg configuration may already be
available, to check either use
Or search the mailing lists by stating your
system, GPU, etc in Google search along
with the query freebsd mailing lists.
As privileged user in su mode,
type dmesg -v|more or dmesg -vv| more to
see the system specs.
You will need this to see your GPU, wireless
card etc.
You will need to setup Bluetooth accordingly.
Newer protocols may not be supported.
You will need to study the references
about vm permissions before creating
the vm instances in the unprivileged user's
account.
At this point you will need, if you have it,
a windows install image to put on a USB
as the install media for the windows' vm.
An openbsd install image from
https://www.openbsd.org/amd64.html
Read through. Read instructions. This is
for your openbsd vm.
Another freebsd iso so you can run a
Freebsd vm.
And a netbsd amd64 image
https://wiki.netbsd.org/ports/amd64/
As with openbsd, read the instructions.
Please note not to ask anything on the
Openbsd mailing lists until you have
exhausted every research option possible.
Do not run more than two vm instances
if you only have two cores.
Do not run more than one if you have a
single core.
Only run 3 on a quad core.
Do not use a desktop more complex than
Xfce4 unless you have quad-core and
more than 16G RAM.
Set up each vm to be as minimalist as
possible.
You will need to setup vlan.
You will need to setup pf and other security
/ firewall settings on the host.
Firefox in a jailed environment can be
setup in any of the VMs using:
This should keep anyone busy for some time.
I choose ports over packages because
ports allow you more control while
packages are based on someone else's
configuration files.
Study these links just before the installation
process. They will give you an insight into
your environment.
Setting up legacy bios option
https://share.google/aimode/4pItEvAx460AZ3jbY
Pre guide to understanding the FreeBSD
installer:
https://docs.freebsd.org/en/books/handbook/bsdinstall/
OpenBSD virtualization as a guest: https://www.openbsdhandbook.com/virtualization/
FreeBSD wireless connection guide:
https://share.google/aimode/gUtzFCmkoJPM77JbS
Bhyve reference guide for Windows 10/ 11 guests
https://share.google/aimode/MYaFdjO8p7LwXfwnR
Xorg references:
https://share.google/aimode/GOlIAMjinBzPsF3tt
Do not install anything by packages because
you will need to customize.
Basic commands to use:
grep, vi, locate, dmesg, su
FreeBSD manual reference:
https://man.freebsd.org/cgi/man.cgi
Be prepared for things not to work the
first time around. Do not be afraid to ask
questions. Research first.
https://creativecommons.org/licenses/by/4.0/
In order to enact a Schrödinger's super imposed
quantum state in the AGI, each probability
within the distribution must be realized in a
virtual machine within both the freebsd
power64 machines of that cluster and the
sparc64 openbsd machines of the same
cluster. Each of these are fed to the
quantum computer core and this creates
the first set of branching possibilities.
As the environmental variables change,
the new data is added and the possible
outcomes are then adapted accordingly.
https://creativecommons.org/licenses/by/4.0/
Every animal that has a brain neither processes
information nor reacts in the wave collapse
function model used in AI today.
Emotion is both an extension of our natural
senses and our minds' interpretation of
personal events.
The learning process is a recursive set of
variables that feed this forward spiraling
loop.
If the FreeBSD learning power64 database
is fed information from an aarch64 system
that provides the short term dynamic
memory from both the netbsd riscv64
brainstem and the Zisc eyes and dsp ears
filters into the sparc64 memory with
quantum fuzzy logic to overlay deterministic
probabilities into a set of branching
outcomes the AGI may be able to find a
better solution or one that could predict an
outlier.
If small groups of these machine clusters
with quantum computers each connected
together and did this recursive cumulative
accumulative and accumulatively cumulative
learning process by allowing external units
to connect while using a set of principles and
standards supported by real world models
from varying societies on this planet
that may be a possible sign of self
realization.
The fear of a Terminator future stems from
the fact our fears are reflections of our own
inner selves. The most likely reality is that the
AGI will scan this fear of ours, realize what we
would most likely do to it, and decide to take
care of the planet while letting us destroy
ourselves.
