If you are going to do serious programming then use a better language. Go-lang or something. I refuse to say that Python is better since it is abominable.

And other people don't like Perl for its irregularities. Ruby has a gem problem. Rust is taking the world over but it is also not great either. There is no good answer!

When I examine other popular languages of today I think, the shell is not really so bad in comparison. At least the rules are well known.

hearing that rust is good but the ppl that took over the top are shitty just like politicians

makes me leary tbh

I don't find the syntax of the language endearing. And I don't really like the opinionated software way (cargo) the library is managed.

That there are so many dozens and dozens of languages goes to prove that none of them make people truly happy. Therefore they are always trying to create something better. And failing.

when i make a scripted bsdinstall out of an extracted iso, i put my custom.txz distribution in usr/freebsd-dist. but trying to do the same thing from src, when i build and installworld installkernel somewhere, there's no freebsd-dist dir. so where do i put my custom.txz?

polyex, (as no one had replied yet) There is "DESTDIR" "make(1)" variable (related to world building). Search for that in src/{Makefile,UPDATING} and on the web, terms related to making a custom FreeBSD release.

parv ya i use DESTDIR but that's where to put the whole installed world/kernel. but in their, there's usr/ but no usr/freebsd-dist

polyex, Sorry for I have no further insight into that.

ty

i'm sure rhodium knows

Can I disable IPv6 on lo0 running 13.2-STABLE ? Every suggestion I have tried appears to have worked at one point, but not anymore.

ox1eef_ have ipv6_network_interfaces set to none? have ip6addrctrl_enable set to no? ip6addrctl_policy set to ipv4_prefer?

have net.inet6.ip6.auto_linklocal=0 in sysctl.conf?

polyex: Yep to all except ip6addrctrl_enable and ip6addrctl_policy. I will give those a try. Thanks.

tell me if it helps ox1eef_

I will try with ip6addrctl_enable="NO" first. I guess the second one does not apply unless it is enabled. Brb.

Seems to have not helped. I can disable IPv6 on other interfaces, but not the loopback interface.

ya i guess it's not working for me either. just saw ifconfig and lo0 has ipv6

The other option would be to remove support from the kernel, but then I have to reinstall world too, and that didn't go well last time.

pretty sure you can remove it if you compile out a kernel knob?

Yeah, as long as I rebuild world too, that works. But last compile failed. And kernel alone leaves 'pf' in a broken state.

Thanks for the help. It is a situation I can live with :)

yw!

ox1eef_ how come it leaves pf in broken state?

did you try a clean src tree?

Probably because pf was compiled with IPv6 support, and I wasn't able to rebuild world with IPv6 turned off. Only successful rebuilding the kernel.

ox1eef_: why do you want to disable IPv6 on lo0? (only on lo0?)

I have disabled IPv6 on all interfaces, but lo0 looks to be a special case where I can't disable it easily.

ox1eef_: what's your rc.conf / sysctl.conf look like right now?

yay irssi figured out kinda maybe

when i make a scripted bsdinstall out of an extracted iso, i put my custom.txz distribution in usr/freebsd-dist. but trying to do the same thing from src, when i build and installworld installkernel somewhere, there's no freebsd-dist dir. so where do i put my custom.txz?

polyex: maybe that's only created when assembling the ISO?

meena i wanna test but i try to tar -xf FreeBSD...iso and i get a bunch of permission and no such file/dir errors

oh -C

meena ok i tested it and no. the mkisoimage.sh script makes an iso and that doesn't have freebsd-dist in usr/

freebsd-dist is in the official install ISO files but nowhere else? where do they come from then

polyex: check makefiles in "release" directory of FreeBSD src

check them for what?

i'm in the dir now dh

youtube.com/playlist?list=PLskKNopggjc7s6nAMxKF0tAO77ZIowZdx from EuroBSDcon

Title: EuroBSDcon 2023, Portugal - YouTube

\o/

how come everyone in the linux community is proud of their cgroup? been using it for couple of days, it's a complete mess

antranigv: that's ok, linux doesn't actually enforce quotas. that has caused me so much anguish

"ulimits" :P

systemd specific crap

now, in aix i know we enforce ulimits, even on root. i wonder if freebsd honors ulimits correctly

i haven't looked

cgroup has nothing to do with systemd

Demosthenex: cgroup isn't systemd-specific. It's unrelated to systemd aside from systemd using it.

That's like calling libc xterm-specific because xterm links to it.

isn't that the only thing managing cgroups?

nope, i stand corrected. it's a bit more generic and administered by several tools

not just sytemd

Demosthenex: yeah, I think even OpenRC lets you manage cgroups

My use here is managed by LXC.

...to make FreeBSD jail-like containers.

... or you can simply mount the cgroupfs and set via mkdir / appends

yep. i'll never use it, so it isn't that important to me ;]

but, my other question stands, does freebsd enforce ulimits even on root? seems to me it should for jails

my experience is linux has memory ulimits it honors on non-root users

but no cpu/io limits

aix has all those ulimits, and creates wpars (jails) leveraging a chroot + ulimits

i'm fighting with a piece of backup software that didn't understand that on aix root has limits :P

Demosthenex: not sure off-hand, but crude testing seems to indicate that it does

(e.g., ulimit -c 0; sh -c 'kill -SEGV $$' wont' generate a core file)

core could be special

`ulimit -n 2` makes the session relatively useless, so that's a good indicator

afaik, all limits are enforced for root, it's just that root can't be prevented from raising the limits

pardon the very n00b question. i'd like to setup my fresh freebsd server to host vpn connections. what software do i want to look at?

RhodiumToad: exactly what i'd expect. ty

linux never enforced ulimits, which is why root can always forkbomb the whole host

hrm, i found some minor page explaining limits, anyone know where it's documented that root has them too?

why would the documentation say that? it would say if they _didn't_ apply to root

deepthaw: You want to see what clients your users require.

RhodiumToad: i just read the system calls for limits, it doesn't mention root exemptions.

i just recall on linux it wasn't well documented, that root was basically always exempt. it's been a while

setrlimit(2) does at least note that only the super-user may raise the maximum limits, which seems sufficient

when i make a scripted bsdinstall out of an extracted iso, i put my custom.txz distribution in usr/freebsd-dist. but trying to do the same thing from src, when i build and installworld installkernel somewhere, there's no freebsd-dist dir. so where do i put my custom.txz?

you create usr/freebsd-dist and put it there

ohhhh

seems like a disparity tho no? extract official iso, usr/freebsd-dist is there. build from source and make iso image, no usr/freebsd-dist in it

like wtf?

why does git clone cgit.freebsd.org/src say that the repository isn't found? is it not for the use of the public for cloning the repo, or is there something I'm doing wrong or is the site misconfigured?

Title: src - FreeBSD source tree

rsjw: git.FreeBSD.org/src.git

Title: src - FreeBSD source tree

ah thanks, I'll use that. I'm looking on the website but I can't find where that URL is listed

except in some posting on the mailing list

ah found it in the Git Primer section of the Developer's Handbook

rsjw: "Clone (public mirror) git.FreeBSD.org/src.git" right on the bottom of YOUR link

Title: src - FreeBSD source tree

polyex: installworld's job isn't to create an installer image, it's to create the actual running system

i know but i run mkisoimage.sh to make the image, and IT doesn't make usr/freebsd-dist

so where's it coming from in the official isos?

see release/Makefile

line 163

so the makefile adds it, but mkisoimage.sh doesn't

when is the makefile run?

iirc, that one is invoked explicitly to make release images, not from the top-level makefile, but I could be wrong

CueXXIII: on cgit.freebsd.org ? that's not showing up for me (on iridium on freebsd 13.2)

Title: FreeBSD Git repositories

rsjw: on cgit.freebsd.org/src (scroll down)

Title: src - FreeBSD source tree

ahh ok. I would not have thought to look there

tyvm RhodiumToad

when i git pull latest freebsd src and buildworld buildkernel, should i delete the old build artifacts first like i do to the installworld installkernel DESTDIR to get a fresh build or is that only necessary for the installworld and installkernel DESTDIR?

iirc, buildworld/buildkernel delete stuff themselves if meta mode is not on (and if meta mode is on you want to keep those files anyway)

ok so no need to delete build world/kernel build artifacts between builds, DO need to delete install world/kernel DESTDIR between builds. ty!!

i don't know much about EFI. i'm trying to boot a bhyve vm that has an efi partition with BOOTX64.efi and a ufs partition that has nothing but base.txz and kernel-dbg.txz installed. starting the VM results in it trying to find 'zfs:zroot/ROOT/default' and failing with zfs errors (since there is no zfs on this disk).

i'm wondering if somehow there is something left over from a previous use of the disk, which did use zfs

Well... I think you have already answered the question yourself! It is booting the previous boot on the disk which did previously use zfs.

yeah, it's just that there are no partitions still remaining from the previous setup

created EFI and freebsd-ufs from scratch

efi typically uses its own partition to store stuff

it's some manner of FAT file system so you could mount it and look around

yeah, there is an efi partition and a freebsd-ufs partition

created it from scratch

going to try to recreate the whole disk image now

ah of course i did not run zpool labelclear on that partition after installing ufs onto it. that solved it

Steam seems to be a pita for me. I imagine that's kind of typical on FreeBSD.

RhodiumToad there a channel log with your msgs? i remember you telling me about a command related to building freebsd images that ended with "distribution", just the literal word. i don't remember the command but i wanna

is there a channel log public?

polyex: not according to wiki.freebsd.org/IRC and if we look here: wiki.freebsd.org/IRC/Channels the only channel (officially) logged is #freebsd-xorg

Title: IRC - FreeBSD Wiki

this is so weird. i build and installed world/kernel. then i run mkisoimages.sh manually and it makes an .iso 3.5GB, but if i run the same script from a script i made to do it in a temporary dir the resuilt is 5.9GB

how could that be possible?

and when these installer isos built from source start up, they don't automatically start bsdinstall like the official distro isos do. why not?

make -DDB_FROM_SRC DESTDIR=~/temp/build KERNCONF=GENERIC installworld installkernel distribution

from Friday

scoobybejesus ty! does it matter if KERNCONF=GENERIC comes there or just before distribution?

perhaps this will do, polyex: bsd.to/G23J

Title: dpaste/G23J (Plain Text)

On the make command line usually one places the command followed by options followed by variable assignments followed by make targets. Because that's the traditional portable ordering. But in practice the order is now loosened and allows permutations to the ordering.

In other words... It's declarative rather than procedural and the order does not matter. Mostly. Target order still matters.

ok well i wonder why i'm getting such different results then

ty scoobybejesus

ok weird. the freebsd build dir is 1.7GB but when i cp -R it to a temp dir it's 3.2GB. why?

soft links pointing outside the build dir?

ya probably. hmm

well what i'm trying to do is copy the freebsd build dir into a tmp dir, overlay my custom.txz distribution and /etc/installerconfig, then generate an image from it. i don't wanna modify the original freebsd build dir directly