I got it running via this as well https://github.com/ericcurtin/podman-ollama
I got it running via this as well https://github.com/ericcurtin/podman-ollama
GitHub
Contribute to ericcurtin/podman-ollama development by creating an account on GitHub.
NI just ran the ./podman-ollama command on Bazzite and it pulled down a model and loaded it onto my 6900XT
Bi used ujust ollama - mayube the same underlying command
NI used that necessarily because Bazzite which is what I use on my gaming rig doesn’t ship with the ujust command afaik
NBut it uses the same docker image for sure lol
FI used curl, got burned by it when it downloaded corrupted file once, switched to wget, no problems ever since
Fbut this is just a personal experience
Xin my experience curl is more reliable, so i'm not sure what was up with our curl issue earlier
Nmore random yafti stuff...
Cthis is what the ujust command does:
C
DWhy does fedora have 3 bin dirs (/usr/bin /usr/sbin and /usr/libexec for things that are executed indirectly) but arch has just /usr/bin and one thing in /usr/libexec (on steamos)?
Ksbin is in the progress of being merged with bin
Klegacy stuff
Klibexec is likely to stay, that's better for selinux
Koffers a bin dir that's not in autocomplete and has execute perms
Dis redhat/fedora doing that or ublue?
Kfedora, we aren't a distro and would never make a change like that
Doh ok
Flibexec is for executables which should not be exposed for direct executing by the users I think
Mdnkmmr take look at more of the /usr/lib you'll see executables there as well. /etc and /var occaisionally has some. Unfortunely, not all applications follow FHS.
That said: /usr/libexec is excellent for attempting to have a directory for all things that should be executable but not on path.
That said: /usr/libexec is excellent for attempting to have a directory for all things that should be executable but not on path.
Dwhy were bin and sbin even separate?
Mold days sbin was for statically compiled binaries necessary for early boot operations
Lsbin - static binary ... that makes total sense
Dwhy does it need to be seperated
Ksbin was originally stuff that would be required to boot
DI thought that was /bin /lib and /sbin
Dbut what about /usr/sbin
B@dnkmmr remember the history of unix/linux started with the main subdirectories typically being completely separate storage devices, which would be mounted in a particular order to bring up the system. We still carry that "legacy" in the linux filesystem hierarchy.
Ais there a way to replace the kernel in a bazzite installation with one that the user has compiled themselves?
Ai wanna build a 6.7 fsync kernel with Matt's refresh patch
KBazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.
Kyou'd have to install that kernel yourself in a container, but the examples are all there
Kno need to fork
Dslackware still hasn't performed the usr merge (at least what I know of)
KKand it's not strictly necessary to do so in the first place, so for someone like slackware they might never do it
MFedora is just now doing /usr/bin and /usr/sbin merge.
Arch already did this. Effectively all binaries are in /usr/bin and everything else a symlink.
Why not get rid of them? Compatibility with old software.
Arch already did this. Effectively all binaries are in /usr/bin and everything else a symlink.
Why not get rid of them? Compatibility with old software.
DWhat's the benefit of using the ublue image template vs bluebuild?
Kublue image template is pure containerfile, bluebuild is module based w/ yaml
Dwhere is the repo?
Dfor bluebuild
NAsk in the BlueBuild discord.
DI didn't realize it was a swperate project
Dseperate
N
JSome random person who works in the embedded industry stopped by the booth I was working today to tell me about the 30m talk he gave at some embedded trade org show about universal blue. He wants to make "bluefin but for embedded systems" engineers.
JI was like, whoa.
N
K@bsherman ugh now tar is giving me shit about perms
