-
Chip1972nimaje: I using xfe as test to try running an alpine gui program under chroot
-
Chip1972I want to know how to fix display :0 error
-
nimajeany progress after sharing /tmp and xauth?
-
nimajeprobably easier to first test if it works without the chroot
-
Chip1972good idea
-
rwpChip1972, There are a lot of articles describing how to run GUI programs from jails. Such as this one: tumfatig.net/2024/running-web-browsers-in-freebsd-jail
-
skeredbash
-
skeredoops.
-
Chip1972rwp: just what I need
-
kerneldove_anyone know a diagramming tool that works on freebsd? i need to be able to place squares, connect them with arrows, move squares around, scroll vertically and horizontally, and zoom in/out
-
skeredAre you willing the use Linux emu?
-
skereder well I guess they have a native port for FreeBSD.
-
skereddrawio
-
skeredCould just use the web interface too.
-
kerneldove_no
-
kerneldove_drawio is related to graphviz?
-
skeredNot sure I've only used it on Windows.
-
kerneldove_can use it offline?
-
skeredYeah
-
kerneldove_ok ty. looks like drawio will work ok
-
rwpkerneldove_, Take a look at dia which is in ports and has pkgs available for install. It's something like Visio. wiki.gnome.org/Apps/Dia
-
kerneldove_tried it, drawio is easier to use tho
-
rwpAwesome! I will have to try out drawio the next time I need to draw something.
-
rtprioi'm a fan of asciiflow.com
-
kerneldove_i dont want to use an online service
-
ltsAh, the feeling of troubleshooting a slow VNET bridge just to realize after a few hours it's a bandwidth issue between certain ISPs and fully out of my control
-
AmyMalikah
-
AmyMalikI'm sorry
-
titouhey
-
titouwhy FreeBSD 15 didn't switched to default 3.12 python version rather than the oldy 3.11?
-
ivytitou: Python isn't part of FreeBSD operating system. it's part of the ports collection, which is independent of OS version - all version of FreeBSD use the same ports. i believe the reason ports hasn't updated to python 3.12 by default yet is due to a few ports still not working with it
-
titouok! great answer
-
titouthank you
-
titoubut that's crazy that some ports is still not working... on linux, python is version 3.14..
-
titous/is/are
-
titouand for 3 ports I need custom port configuration. I'm using synth since several years but it's quite boring since I need to give to him all my needed ports and it only download part of them but recompile MOST of them.. it takes huge time. For only 3 ports, that's really boring
-
titouwould you have another idea? (ports are: nginx for only two extra plugins, nextcloud to get it using postgresql rather than mysql and scponly to get rsync and scp working..)
-
nimajehm, can synth use the official repos for packages with default options (like poudriere can)? If yes, then use that and keep the commit of the ports tree you are building in sync with the official builders
-
nimajeyes, it can do that "Fetch prebuilt packages" synth(1)
-
ivytitou: it's probably rebuilding all dependencies when one of their dependents changes. perhaps try poudriere, which recently had logic added to avoid doing that so often
-
antranigvtitou new version(s) of Python are available on FreeBSD as well, typically even before they are available on mainstream Linux distros. the question here is more abut the default flavor of Python set in Ports.
-
titouthank you for all your answers. I had a look on poudriere long years ago but it let me afraid because its configuration looked very hard
-
titouonly for 3 ports :)
-
titouivy: it's what the synth developer answered to me but i don't understand why 50 packages needs to be recompiled for an "end software" like nginx :)
-
titouantranigv: yes I see that there are different versions of the interpreter but not for packages?
-
titouantranigv: for instance sqlalchemy is only available for py311
-
ivytitou: if a package containing a shared library is updated, such as cURL, it will rebuild everything that depends on cURL to make sure they're using the most recent version of the library, then it will rebuild everything that depends on those things (because they might contain shared libraries themselves), and so on, so a single update can resulting in a lot of packages being rebuilt
-
titoui understand that
-
ivythe change poudriere made is that if the shared library version hasn't changed, it won't rebuild all the dependents, which is correct in 99% of cases and saves a lot of rebuilding
-
titouthat's a very great thing for poudriere!
-
ivywell, you said you didn't understand it, so i was trying to explain :-) which part of it don't you understand?
-
titouthank you. the part about the fact that I though nginx was not used by other packages and are installed because I need it so if I update its compilation options, it would only recompile itself
-
titoubut maybe I'm wrong and I also installed other packages that depends on it..
-
ivyrecompiling nginx shouldn't rebuild anything else, except maybe any external DSOs. that might be something synth is doing, i've never used it
-
titouit should be the same thing for nextcloud and scponly which are "end software" (I mean software which use others but are not used by my other packages)
-
titoubut anyway :) I'll have a look on poudriere again..
-
nimajewell, both synth and poudriere can fetch packages from the official repos as long as versions and options match, so if you enable that you should only rebuild your three leaf ports (as long as there was no versions update for some transitive dependency between the commit of the ports tree the official builder build and the commit you are building)
-
titouthat's perfect! I'll try
-
titouI'm googling but if you know a good and up-to-date "easy" tutorial for poudriere, i would be interesting in it :)
-
titou(i'm reading the vermaden one)
-
nimajeInstead of using poudriere options I recommend to use <option_name>_{,UN}SET in some -make.conf as poudriere options will save all options as you currently have selected them and with -make.conf you can just change those you care about and if defaults change for options you don't care about, you will automatically get that change instead of still using the value from the time you used
-
nimajepoudriere options
-
titouok good
-
nimajeto give you an example for nextcloud with postgres instead of mysql it would be www_nextcloud_SET=PGSQL and www_nextcloud_UNSET=MYSQL
-
titouand I read aboutthat's great! thanks
-
titoui think poudriere will become my new friend..
-
titouwhen you use it, do you configure all the packages you need and then only use the poudriere repository? Or do you use a mix between freebsd repository and poudriere's one for custom packages?
-
nimajeI only use my poudriere repository, as I make deep changes via OPTIONS_SET and OPTIONS_UNSET (like <option_name>_{,UN}SET but affecting all ports) for example I disable pulseaudio that way
-
titouok
-
nimajeIf I didn't do that I would probably enable that fetching from the official repo and use only poudriere, to make sure the repos can't go out of sync (but probably not as important)
-
antranigvtitou yes, packages are compiled only for the main flavor for Python. I think the PHP team, on the other hand, compiles it for multiple versions.
-
titounimaje: yup
-
titouantranigv: what a pity:)
-
antranigvtitou always welcome to complain at bugs.freebsd.org :-)))
-
antranigvit would benefit me too :P
-
antranigvbut I run a package server anyway, so I'm not worried that much.
-
titou(-:
-
titouI would complain about that when I'll have enough time to help also..
-
titou[00:00:07] Building 141 packages using up to 8 builders
-
titou[00:00:07] Building 141 packages using up to 8 builders
-
titou[00:00:07] Building 141 packages using up to 8 builders
-
titou"Building 141 packages [...]" for 4 end-softwares..
-
titou(sorry for multiples copy of the same line..)
-
titouthat's strange since it fetches no packages even with PACKAGE_FETCH_BRANCH=latest set
-
nimajethe .conf.sample says it still needs -b <branch> for bulk or testport
-
titouups
-
titouit's the same.. but in the log it is written unable to update repository FreeBSD
-
titou
-
titoumaybe the problem comes from here
-
nimajeok, that seems strange, bdrewery do you know more about that?
-
ivyif this is on 15.0, there is no "FreeBSD" repository - perhaps the fix for that in poudriere didn't make it into the release yet
-
titou:-(
-
ivyyou might try using poudriere-devel instead and see if that helps
-
titouthat so greaat it solved the bug and only compiles my updated package! thank you a lot:)
-
titouwhat is strange is that i even ask poudriere to generate package for custom python version without changing the default python version?
-
titoufor instance py-sqlalchemy@py312
-
titouit tells me that there is no py312 flavor and the only flavor available is py311..
-
nimajeyou can set BUILD_ALL_PYTHON_FLAVORS="YES" in a -make.conf to have all flavors available, without that python ports only have a flavor for the default python version to avoid having so many copies which mostly aren't needed in a bulk -a
-
titounimaje: oh
-
titouthank you
-
titoui'll try
-
dchhas anybody got a non-pkgbase FreeBSD 15.0-p1 handy?
-
dchI'd like to see what `uname -a` and `freebsd-version -kru` reports on it
-
dchmy pkgbase systems report 15.0-RELEASE-p1 for all of these, and I have 1 non-pkgbase system that only shows -p1 for `freebsd-version -u`
-
ivydch: this is probably expected, for pkgbase the entire kernel package is updated, for freebsd-update, only the specific modules are updated
-
dchivy yes this is what I was wondering
-
dchI have run out of non-pkg base systems to test things on ...
-
dchthanks for the clarification
-
zipEarlier this week I don't think I even found a -p1 image at all
-
zipGotta install and upgrade before running rtsold
-
dchalso the different hash of `/boot/kernel/kernel` confused me mightily
-
nimajehm, sad that when using sysctl kern.corefile=/var/coredumps/%U/%N.core (as in the example in core(5)) the directories for the uids aren't created on need, but have to be created before
-
rtprioit's too busy dumping core to create directories
-
antranigvI've always wondered if coredumps (not kernel of course) can be uploaded to NFS, regardless of the user
-
antranigvthe reason why I'm asking is because we have a lot of programs in our HPC env that I'd like to collect and see what the bugs are.
-
skeredis root squash enabled?
-
antranigvyou mean user map? I think "root sqaush" is a Linux thing, yes?
-
mzarsquashfs is not suported skered
-
mzarperhaps you meant "-maproot=root" in exports file
-
mzarplease guys don't escalate, dumping core is hard task for the OS, thus it's only possible to dump cores into existent dump directory
-
mzarantranigv: it should work
-
ziantranigv: kern.coredump=1 kern.corefile=/path/to/%U.%N.%P.core
-
zithe path must be writeable by whatever will dump core
-
mzarif you have dumping cores enbled, core directory exists, and is writeable, but your core still doesn't show up, consider turning on one more sysctl knob: kern.sugid_coredump
-
mzarsometimes, the app suppresses core creation by itself, it's usually no any issue but limitation
-
rtprionot a problem for me, all the software I write is 100% bug free
-
mzarit will be also nice to send suspicious signal to a healthy app to collect core just for testing
-
antranigvrtprio my software is also 100% bug free... but my team uses other people's software because mine is not "user friendly" whatever that means.
-
antranigv:P
-
AmyMaliki'm sorry
-
rtpriolol
-
rwpThere are kernel dumps and there are userland process core dumps and those are two very different things. I think the previous discussion mixed those two different things together.
-
rwpOne can dump core over NFS. I almost said no problem but it does create problems because the core dumping process is in the kernel and if the core is a 256GB memory image then it preempts other activities until it is done. That sometimes creates other problems!
-
rwpSince the userland core dump is done as the user not root the root mapped user is a don't care for userland process core dumps.
-
rwpThe directory must be writable and all other normal permissions apply. If one makes a directory called "core" for example and the core is called core too then it blocks the core dump. That's an old workaround for running processes which might dump core but the user had no way to disable the feature and no disk space to hold the result either.
-
rwpThat's as zi mentioned of course.
-
zioh yea, trying to kernel dump over nfs, if that's even possible, sounds dumb as fuck to me
-
ziYou'd want a partition/whatever in the box and to set kern.shutdown.dumpdevname for that
-
karolyihello, are there any recent issues with the freebsd ports? it seems pkg wants to download packages that are nonexistent at the remote
-
ziguess the correct thing would be rc.conf's dumpdev
-
zikarolyi: can you elaborate
-
karolyizi: for example, I wanted to install py311-pymacaroons for testing, and pkg looks for pkg.freebsd.org/FreeBSD:14:amd64/la…pymacaroons-0.13.0_2~ea8a819f4f.pkg, then bails out on 404
-
karolyiI've never seen these Hashed stuff before
-
zikarolyi: pkg update -f and try again?
-
zithere's a newer PORTREVISION out there that is current (py311-pymacaroons-0.13.0_3~ee536aa2c7.pkg)
-
zikarolyi: what IP does pkg.freebsd.org resolve to for you?
-
karolyizi: pastebin.com/5pUNLMQQ, but just downloaded pkg.freebsd.org/FreeBSD:14:amd64/latest/data.pkg and it contains the same hashed url for that package
-
zithat's not ideal, one moment
a minute ago