Tuesday, May 5, 2026

Linear logic will not function in an asynchronous simuktaneously multiprocessing environment

 Reference material here is published under

https://creativecommons.org/licenses/by-sa/4.0/deed.en



My maternal parents were Pardo Brasileiro 

grandfather and Paraguaiana mestiça grand-

mother. I am only three generations separated 

from the rainforest.  My knowledge of tribal 

civilizations is based on my family, not some 

anthropological study.

I have actually worked with, fixed, and ported

to aarch64 arm sparc64 amd64 i386 ppc using 

freebsd netbsd openbsd including medical pro-

gramming.

The mind of a tribal individual functions closer 

to a quantum computer centered group of

heterogeneous RISC clusters with each archi-

tecture functioning as a virtual processing 

equivalent of certain parts of the animal brains.

Some parts of western civilization have made 

themselves dependent on the limited branching

logic of wave collapse functioning when the

brain simultaneously processes all external 

physical stimuli and recalls/ references 

- also and synchronously - of the internal data- 

base known as memory. 

The functioning and processing of large

data sets is best performed on SPARC64; yet,

this architecture is becoming defunct. 

OpenPOWER now does the dual functions

of data processing and learning. 

Yes, I am aware of neurological chips but,

these only carry the message. They do not

process. A single architecture and a single 

operating system will not be able to emulate 

all processes of any biological brain because

the brain is composed of different types of

tissues and cells doing different simultaneous 

functions for varying evolving purposes. 

Aarch64 functions good for memory input,

short term memory for recursive learning feed-

back between OpenPOWER learning and data-

base management. 

I suggest you find any SPARC64 server that can

run OpenBSD natively to see the performance 

of long term database stability and Solaris 

for intermediate data exchange. 

ZFS for memory comparison. 

If the single OpenPOWER based machine is

incapable of handling the database on its own, 

a fpga can be programmed to function as a

SPARC64 Niagara T1 or T2 core or single 

function. If it is dedicated to a single function 

Then the maximum number of asynchronous 

simultaneous register functions must have

that many FPGAs working and access to for

advanced memory adaptability and self 

correction while using external GPUs for

Python based recursive math and fuzzy

logic processing. 

RISCV64 will be able to emulate both the

brainstem and emotional response.  The

latter is a 128bit function that can be

reduced to simple 8 and 16 bit or 32 and 64

bit functions on references to a different 

environment or environmental variables. 

A stable custom build of NetBSD with exact

compiler flags set to optimum performance 

will produce the best libraries and binaries. 


FreeBSD for learning.


Okay,  back to the biological background. 

If a person is incapable of physically mapping 

out her or his cognitive and learning process

on a piece of paper with a pen or pencil, 

that person is incapable of understanding the

logical differences between processing of

external stimuli with and through sensory 

organs and the brains multiple areas dedicated 

to each then combining the lower unconscious,

the middle subconscious or cerebrum 

- the brainstem is the unconscious -

And the conscious which is the cerebrum.

DSP for audio aural processing. 

ZISC for visual. 

My opinion is that overlapping probability 

distributions should be used to allow 

adaptive plasticity in reasoning through a

fuzzy logic set of such nodes would

produce a better result.

This would establish a better base. 

Linux systems could function better with

base processing delegated to the BSDs.

NFS and SSH between the systems with

dedicated rewrite solely assigned to the

AGI's internal equivalent of adding a 

new memory through rewriting which is 

a learning function. 

Kant did not live a life of simplicity and/ or

survival nor did or do most philosophers. 

When you exist within a controlled environ-

ment, your sensory organs and the areas of

the brain will atrophy and/ or become vestigal

in functioning and purpose. Nothing exists in

a truly collapsible state. Even the Planck second

is a fluid temporal state not an exact locked

moment in time.

The more data from more areas that use 

different sets of ethics, morals,  principles, 

and standards, the more results it will be

able to compare.  If outliers and sudden

unknown variables are taken into

consideration in the processing algorithm, 

the more likely a black swan opinion can

be perceived and used for creative self 

awareness and adaptive survivability 

in a symbiotic environment. 


Hey, this is the why behind the how of

groups more in tune with their bodies and

environments because they know they are

part of the biosphere.

Thursday, April 16, 2026

Ideas and Observations

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. 

Further customization of FreeBSD ports

 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.

Both FreeBSD reference and tutorial in one post

 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.



Wednesday, April 15, 2026

Quick guide to a FreeBSD system

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:

https://www.freshports.org/

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 

forums.freebsd.org

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: 

https://forums.freebsd.org/threads/how-to-execute-firefox-in-a-jail-using-iocage-and-ssh-jailme.53362/


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. 

Setting up a FreeBSD security laptop

 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.

Tuesday, April 14, 2026

VM states within the cluster

 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.