# uname -a

FreeBSD bsd 15.0-RELEASE-p5 FreeBSD 15.0-RELEASE-p5 releng/15.0-n281018-0730d5233286 GENERIC amd64

how 2 freebsd

step 1) do computer; step 2) profit

ty

lol

I'm on 15.0-RELEASE-p5. at some point in this machine's history, I tried to switch to pkg-devel and then (tried to) abandon that approach and go back to normal ports-mgmt/pkg (on 2.7.4). I'm trying to pull packages from FreeBSD-latest and it wants me to upgrade to pkg-devel (2.6.99.6). Is there a way to tell pkg "do not ever use pkg-devel" (other than pkg lock)?

mfisher: i think you can do # pkg set -o ports-mgmt/pkg-devel:ports-mgmt/pkg

this will force the origin back to the stable pkg

thought I tried that but I totally may have called it incorrectly

thank you!

BUT, if you are using a development repository, it may still be picked up

so latest or quarterly only

still battling with ipfw/nat issues on 15.0, so i thought the one from the manual, that should work. docs.freebsd.org/en/books/handbook/firewalls/#in-kernel-nat // i can ping the world but nothing works tcp/udp // anybody maybe bored try it :) driving me nuts

iRobbery: I don't have suggestions but as I want to roll out something like that, I'm keenly interested in how your search goes.

well it always worked as i thought on pre 15.0 :)

but 15.0.. i'd be pulling my hair out if i didnt shave it regularly

fwiw i use in kernel nat with ipfw on 15 just like i did on 14

isley: can you share your rules? the rules i used for years give some weird loop in a skipto line, self dos attack, and the manual does not nat

Hello Everyone !

Is there a chatgroup or mail list for Artificial Intelligence related infrastructure in FreeBSD ? Like Ollama, llama.cpp, pi-coding-agent, Vulkan and drivers to run LLMs ?

It seem that claude-code works as it is pi-coding-agent, ollama works with Vulkan... but where is the community for it ?

Then, I have forever question about ultra basics --- it seem that root has no history, that is so anoying because if you want to see what was installed etc... nothing is there --- what is the solution for it ?

It seem that most of the ai coding agents (including pi-coding-agent assumes that the system has bash - I wonder what is the difference between Sh (Bourne Shell) and Bash (Bourne-Again Shell)

oh. llama.cpp just worked for me using both gpu on my x86 machine and cpu on my arm 128core machine

havent tried pi-coding-agent.

dont know what it is.

acu: bash is newer and encompasses all functionality of sh, plus a bunch more

see also gnu.org/software/bash/manual/bash.html#What-is-Bash_003f

drobban: thanks, I have to search if there is any tutorial deploying llama.cpp in freebsd, and how to use it...so far, I am very familiar with ollama, pi-coding-agent, librechat -first two run OK on a freeBSD 15 machine with NVIDIA RTX and Vulkan (I did not compare yet the speed on debian linux vs freebsd) --- and I will try to see if I can install librechat ----- anyhow, if you are aware about any llama.cpp tutorials deployments I would love to

look at them --- and if you know any interests group about AI on FreeBSD - I would appreciate if you share

multisn8, thanks, I am aware about the superficial differences -including license (which is not trivial), my interest was - while deploying pi-coding-agent in a freebsd, I wonder if there are things I need to be aware - since most of the testing was on bash (linux) and freebsd has sh... I already run ollama and pi-coding-agent, it works, but I wonder how reliable and if there are bottlenecks and whether I should install bash (though I am trying to

minimize GPL - otherwise I would just run linux)

if the GPL license is your primary concern (unclear why but that is your fair decision), you might as well use zsh which is under the MIT license. most scripts floating around the internet work with it as well

there's not much of a bottleneck i could think of, beyond failures you'd need to handle with a coding agent anyway (e.g. command/script failure, escapes, vulnerabilities, ...)

sh vs. bash isn't much of a change in the realm of "giving remote code execution to the internet"

Either a script uses "bashisms" or it doesn't, really. sh vs zsh vs. ksh vs. dash vs. whatever "not bash" doesn't work with bashisms

Most bash'isms started out as ksh'isms and so ksh will interpret many bashisms correctly. But for my sentiment I prefer portable POSIX sh scripts. sh is a lot faster than bash, if that is a concern. bash features change with version so bash on FreeBSD, linux Stable, Mac OS X, often will all be quite different. That's why I prefer /bin/sh for portability.

acu, I am confused by your statement that the root shell has no history. There is the /root/.sh_history file holding it. Run "history" to see a dump of the recent commands.

However you then said "anoying because if you want to see what was installed etc... nothing is there" and I am confused by that because to see what is installed outside of base run "pkg info".

acu: huging face is where I got models running on llama.cpp

Having said that, I do not like /bin/sh for a command line shell. I install bash and for root I set up toor with bash leaving root to sh. Maybe more convenient the other way around. But it allows me to always have a root login with /bin/sh which is in base (I locked myself out once) but most of the time use bash from ports.

pretty straight forward getting it to run on fbsd, cant remember having to do something special. just followed the instructions from their site.

What are the chances the freebsd project publishes compiler_commands.json?

i've never heard of that, so i'd say pretty low

It seems like the project should be able to make one?