01:35:17 ivy, try also setting the mask width the same as the non alias IP on the same subnet. 01:36:02 CrtxReavr: that's impossible as the non-alias IP is 127.0.0.1/8. but it works fine once i rebooted with a kernel that supports IPv4 :-) 01:36:22 Yes, I know what the ifconfig manpage says. . . and that used to be a requirement, but it hasn't been for many years. 01:37:22 I think that requirement went away in the 6.x or 7.x timeframe. 01:37:38 okay, maybe i don't understand your suggestion. there is no non-alias IP in this subnet, it's a /32 01:37:55 Try an appropriate mask width or subnet mask to a 1918 address then. 01:38:51 the appropriate mask is /32 01:45:23 Maybe. 01:45:45 no, definitely... 01:47:58 jb1277976, bluetooth is not something I've ever attempted with FreeBSD before, sorry. 01:51:01 rwp: you know, my terminal supports text attributes such as dim, underline, reverse, blink,... but it seems it only supports one at a time. like, you start a reverse text here, then back to normal, it looks as expected. but then if you want to do a blinking text later, now the text that was bold, is now blinking 01:52:12 hjf, which terminal software? 01:55:15 CrtxReavr: https://i.imgur.com/CRwrnTa.jpg 01:56:04 Oh, *THAT* kind of terminal. 01:58:14 heheh 01:58:51 your *THAT* appeared as reverse video 01:58:58 You have $TERM set to something the terminal supports? 01:59:19 yes i found a terminfo entry for something similar 01:59:22 ADDS 3A+ 01:59:31 this terminal is configured to be a 3A+ 01:59:42 That's not one I'm familiar with. 02:00:17 I've dealth with some vt10x TN3270, TN5270. .. 02:00:28 And if I go way back, some TVI312. 02:01:02 hmm. how would i go about debugging something that freezes the terminal? 02:01:12 this is a port causing the problem 02:01:36 What kind of port? 02:01:55 *posts a picture of a parallel port* 02:02:23 Is it IEEE-1284 compatible? 02:04:31 i've never heard of this 02:05:07 this is a real thing? 02:05:40 It was a cable spec for bi-directional parallel port support. . . wasn't actually well supported until the mid-'90s. 02:06:23 it says usb2.0 displaced it. 02:06:24 You had to look at the cable for 'IEEE-1284' 02:06:30 Indeed. 02:06:45 no loyalty among technology companies 02:13:11 one day i need to sit down and work out Forgejo never starts properly on boot. usually it just fails, this time it started but refused to connect to the database and never recovered, works fine after restart... 02:15:29 sounds like fun. can i tag along 02:17:12 Forgejo? 02:17:31 CrtxReavr: fork of Gitea, think github/gitlab but lighter 02:18:00 it's pretty nice when it works 02:18:01 Good bet it's a race condition. 02:18:15 well i thought that but the error was really weird 02:18:26 Tried using /etc/rc.d/netwait ? 02:18:34 2024/10/18 02:32:17 cmd/web.go:194:serveInstalled() [I] PING DATABASE postgres 02:18:35 2024/10/18 02:32:17 routers/common/db.go:36:InitDBEngine() [E] ORM engine initialization attempt #9/10 failed. Error: dial tcp: lookup postgres-1.svc.eden.le-fay.org on [::1]:53: server misbehaving 02:19:08 it's not a DNS problem and it's not a Postgres problem, and after restarting it works... so maybe it's cached some failure condition 02:19:30 Local DNS server? 02:19:39 yes, unbound (from ports) on localhost 02:19:58 I've not used unbound. . . 02:20:07 but the system gets its default route via BGP so sometimes networking isn't available early in startup even if rc thinks networking is up 02:20:24 (this causes problems with some other things, but usually i've been able to fix/work around them) 02:20:34 But I've had issues with bind giving me startup errors basically saying that IPs weren't (yet) bound on NICs it was set to listen on. 02:21:04 i might just move it to a VM, i've been meaning to do that anyway, maybe that'll work better 02:21:36 Or just add a 'sleep 10' to the startup script in the right place. 02:22:17 that is too hacky for me :-) for Kerberos (kdc) i wrote a new rc.d script that waits for openldap to be available before it starts, might need something like that here 02:24:15 I would edit this section of the startup script: 02:24:18 #!/bin/sh 02:24:18 # PROVIDE: named 02:24:18 # REQUIRE: NETWORKING ldconfig syslogd 02:24:18 # BEFORE: SERVERS 02:24:18 # KEYWORD: shutdown 02:24:51 And yes, those lines are supposed to be commented - rc.subr parses the, despite them being comments. 02:36:54 after adding HDD disk to a existed zfs Pool (ssd disk), how to save some file on HDD (/dev/ada1), and another in ssd(/dev/ada0)? 02:37:29 xxy: you can't do that, if you added the disk as another vdev (a stripe) zfs will automatically distribute the data between all disks 02:38:47 ivy: could i create multiple pool in one Os? each disk give one 02:39:34 xxy: yes, you can have (more or less) unlimited number of pools if you want 02:40:40 you can also use the ssd as a cache for the hdd (l2arc/zil) but this does not improve performance in all workloads, in a desktop/laptop type of system it's probably not very helpful 02:46:26 ivy: HDD is used to store big files like videos, after executing "zpool add zroot /dev/ada1" and followed execute "zpool remove zroot /dev/ada1" it prompt "out of space", 02:56:37 xxy: i've never tried removing a disk from zpool so not sure what's going on there, sorry 03:09:28 so i'm like, way-behind on upgrading a machine i've got (12.2-RELEASE behind) is the safest upgrade method still rebuild world from source, reboot, etc? 03:10:02 the packages i imagien would be quite messy being that behind, i imagine 03:10:59 gewt: you should be able to freebsd-update to 12.4 then 13.4 then 14.1 (do not skip 13.4 as you will run into a freebsd-update bug) but if you normally upgrade from source you should be able to go straight to 14.1 that way 03:12:25 i *think* the 12.4 freebsd-update files are still online even though the release is EOL... although i'm not 100% sure about that 03:13:42 seems that way 03:13:55 it didn't complain about specifying that release 03:14:35 after you've done those upgrades, pkg will be broken, use pkg-static to update the pkg package, then do a normal pkg upgrade 03:14:52 ah, dang. i think the host failed in a different way so this upgrade might be moot lol 03:15:22 seems the disks may have died 03:15:47 that could perhaps cause a problem with the upgrade 03:15:57 i can't ctrl/c ping and top won't launch 03:17:26 hjf, That matches my memory of those terminals. There were often several attributes available. But only one at a time. 03:19:46 how do you turn off the green text attribute 03:26:26 You turn off the green text attribute by removing and replacing the CRT with an amber one. :-) 03:27:05 amber is prettier than uranium, so that sounds like a win 03:28:42 In my museum piece collection I am keeping my amber 13 inch CRT monitor. You never know when you might need it. 03:30:23 i saw an amusing news story recently that a nuclear power plant had a failure of their Honeywell control computer, so they replaced it with the backup PDP-11 03:31:14 wonder if HPE still sells parts for those 03:31:25 It's good to have spare backup minicomputers. 03:31:40 Minicomputers that can be easily simulated on a Raspberry Pi these days. 03:31:56 i'm not sure rpi is approved for controller nuclear reactors though 03:37:14 boot drive is toast but my VM drive is intact 03:37:22 so i need to buy a new ssd lol 03:38:32 gewt: or two new SSDs, so you can set up a root mirror and a failed disk doesn't break your computer :-) 03:38:40 true! 03:38:49 i think i am out of drive caddies in the server tho 03:40:29 eh, 2'll be here tomorrow and i can take a trip to the datacentre and swap 'em in 03:40:34 I mirror everything possible these days. It's just so much less hassle for when something fails. Just replace it and keep going. 03:40:37 guess i don't need to upgrade the OS after all. :P 03:40:40 yeah 03:41:16 it's possible the raid card failed...but the other virtual drive's intact so i think it's just the boot drive 03:41:57 If it is just the boot drive and the rest of the data is intact then you should be able to replace the boot drive, install a new system, and mount the data and be good to go. 03:41:58 ivy: i once read a website claiming in the nuclear apocalypse the z80 would be the dominant computing device due to its sheer amount of mass production 03:48:51 did an `fsck` of the vms virtual drive without issue 03:49:06 rebooted and the raid card finally failed the boot ssd out 03:57:13 The Z-80 might do acceptably well in a large radiation environment due to the large geometry transistors used in it too. Not radiation hard by any means. But as compared to this year's silicon? Yes. 05:10:05 kevans: ran into a weird issue where ever time i type 'kevin' on the serial console (ttyu0) the kernel panics, any idea what's up with that? 05:10:29 just says 'panic: you sneaky shit' 05:16:30 i installed FreeBSD UNIX years ago on a virtual private server (VPS) with a company that says they 'support' that, maybe starting with v11. I upgraded every version since then, and asked them to allow newer .ISOs, which they said they would then never did. Now they say people can't 'afford' newer .ISOs (they're not English speakers, the VPS is in Moldova) despite all the .ISOs are free. FreeBSD 14.1 barely fit on this VPS because I used the full DVD ISO. 05:16:30 next time can I use the CD or USB or mini-USB ISO and have it not take so much space? 05:17:14 darwin: not really cler what you're asking -- using the 'full DVD ISO' has nothing to do with how much space freebsd takes up once it's installed 05:17:44 so the other methods just download a lot of stuff and install the same amount of software? 05:17:50 yes 05:18:13 the 'full' image is not a bigger version of freebsd, it just includes more stuff on the distribution media 05:18:45 then I guess I'll be stuck not upgrading or switching VPS or installing something else on it. OpenBSD UNIX still fits on a CD. 05:19:31 a base installed of freebsd is something like 200MB, which would also fit on a CD if you wanted to install the OS on a CD for some reason 05:21:07 i just installed a new VM here and it's using 1.5GB (with a bunch of ports installed), if your VPS has less than 2GB space it really might be time to upgrade 05:22:43 it's taking up 8.2GB on mine, but I only installed binutils, gcc, gcc13, gettext-runtime, gmp, indexinfo, liblz4, mpc, mpfr, nano, pkg, screen, tcl86, tcltls, zstd, and compiled eggdrop. I don't think any of this even takes up 1GB nor close 05:23:25 so, have you tried to use 'du' to find out what's taking up the space? 05:24:39 /usr, var are almost 4GB+ each 05:25:02 a lot is /usr/src 05:25:06 okay, so freebsd itself definitely doesn't put 4GB of data in /var, you have something using up the space there, use du to find out what it is 05:25:13 and don't install /usr/src if you're on a tiny VPS 05:25:55 can I uninstall /usr/src ? 05:26:18 if you're not using pkgbase (you would know if you were) you can just rm -rf /usr/src 05:26:20 /var/db is almost 5GB, which I don't use 05:26:31 ok, so look in /var/db and see what's using the space there 05:27:02 /var/db/freebsd-update is 4.4GB 05:27:40 you can simply delete everything in there, assuming you aren't in the middle of upgrading 05:27:50 excellent 05:27:58 it only stores some files there in case you want to rollback to the previous release 05:31:46 great; now I got it down to 2.3GB so can keep using it years/decades... still 800GB larger than yours but I guess a few things I installed could be bigger (I also have just cleared all the compressed logs) 07:04:15 <|cos|> Today https://bugs.freebsd.org/280186 hit me, again. Would anyone feel up for suggesting how to either improve my patch or suggest some other path to make that part of the handbook more helpful? 07:06:42 |cos|: usually if people ignore your patches the best option is to mail the appropriate mailing list to attract attention -- for src, i would also suggest github, but i don't think doc is using that (yet?) 07:09:30 <|cos|> ivy: that seems like a good idea. thanks! 07:23:05 my jail system blew up again 07:23:16 hate this webchat 07:23:37 luke_jobless_sb: you know you don't need a webchat to be here right? you can use a normal irc client 07:24:44 ivy: i mean it is a pretty interface. well-made client but I just like traditional way 07:26:30 ivy: my bouncer is lost in his(her) jail 07:27:15 ah i see 09:03:11 Hello, if I have a server running jails, can I build ports in one jail and in another jail just install the resulting software (i.e. not having to build in the second jail)? 09:03:30 Yes 09:04:18 Pionat: you probably want poudriere for this 09:04:27 dh: is there any guide on how to do this? 09:04:28 it can build packages to a pkg(8) repository that you can serve from any http server 09:05:07 although it's a bit fiddly to get it running in a jail since it uses jails to do the build, i've never tried that (but i know it is possible) 09:06:51 basically everyone who builds from ports source uses poudriere nowadays, except the 3 people who still use portmaster 09:07:19 and those people have grey beards and live in strange huts in the middle of the forest 09:08:30 Well, simple way would be 1) build and install packages in one jail 2) run "pkg create -a" on that jail 3) copy created package files to other jail 4) install packages in the other jail 09:30:02 Spent two hours tinkering with podman on FreeBSD inside a jail, to find out it can't run inside a jail because it uses jails itself. Poo. :°) 09:34:33 Alver: i don't know anything about podman but nested jails are a thing, just not enabled by default 09:34:41 (if you know that and it still doesn't work, no idea) 09:35:13 ivy: I did not know that (apart from a vague suspicion based on a single comment on a forum) but I don't think I'm in any position to dive into that :) 09:35:40 podman on FBSD is already pretty experimental from what I read, so adding another level of complexity wouldn't be a smart thing to do I think 09:36:38 Podman already requires the host server to have the various linux-compat kernel modules loaded which makes me uneasy enough as it is 09:37:02 oh is that for running linux containers? i thought podman was freebsd native but maybe i'm thinking of something else 09:37:25 Yes, it allows to run unmodified Linux container images 09:37:55 Which would be a nice thing to have - but not if I have to do it straight on the host that also runs the jails with my "important" services 11:29:03 podman does not need to load the linux kmod unless you want to run linux containers 12:05:06 maybe one day I'll know how to use xargs without looking up the man page every single time 12:13:14 darwin: make sure you empty /var/cache/pkg/ in particular (IIRC its `pkg clean -a` but I just `rm -rf` it) this can waste a lot of space 12:43:49 Hmhm. So nested jails are a thing, and I'm trying to get podman to play inside one. I cannot get my jail to be able to manage a ZFS dataset, though. 12:44:22 I've added the mount.zfs and related options; statfs=1; devfs_ruleset=4. 12:45:02 Still getting permission denied when trying to zfs create something inside the jail. 12:46:29 zfs jail myjail path/to/dataset too in exec.created. 12:48:33 Alver: post your config? I think you need to have devfs expose /dev/zfs* stuff or similar too 12:48:55 dch: yes, that's through the devfs_ruleset=4 12:49:33 But I think I've got a lead (mounted status preventing jailed=on to be set, possibly) 12:50:32 no thats not required 12:50:32 https://git.sr.ht/~dch/ansible-jails/tree/main/item/templates/instance.conf.j2.default#L26 12:50:38 this is what I use in production 12:51:33 and look at the end of https://git.sr.ht/~dch/ansible-jails/tree/main/item/README.md for how the datasets are created 12:52:36 IIRC you can create them ready jailed, `doas zfs create -o jailed=on -o mountpoint=/var/db/eden zroot/jailed/eden` for example 12:55:26 Alver: just make sure that you actually have devfs mounted inside the jail(s) 12:58:32 dch: yeah, that was done. It appears that bastille isn't keen on doing jailed=on on datasets 13:00:04 If bastille sees the jail, the dataset is mounted and I can't set jailed=on. If I set jailed=on manually, bastille forgets the jail exists. 13:01:54 Guess I can try with a separate dataset. 13:46:57 kevans: our lord and saviour Sir Mark Johnston fixed my vtnet bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168 13:52:57 ivy: woot 13:55:59 but as usual the fix came while i'm in the middle of a ports build so i can't test it 13:59:02 wonder why poudriere is building qt6 14:50:51 when you have pourdriere build ports do you build them all? 14:51:34 i had this idea. if you could somehow create a graph of like "most used packages" in ports. So then you could build those packages only, that way building most packages would be fast 14:54:00 johnjaye: you can build small amount, or only one port with poudriere, but all the depencies will be built too, so it won't be one pakcate 14:54:09 *package 14:55:09 ah right. 14:55:19 i guess my idea was like. common libraries everything uses and just build those 14:55:35 johnjaye: why would you build "most used packages" when you could just build the packages you want? 14:55:40 is there no command to build the deps of a project? 14:55:49 linux has something like that called build-dep weirdly 14:56:06 ivy: to make it fastest to build a random package i suppose. 15:03:53 johnjaye: I don't know what are you going to do, but poudriere wants just a list of ports. If one of them was dependent on for example devel/cmake-core, then extending this list by another port requring this tool will use already built devel/cmake-core 15:05:24 right. i was thinking of a pkg type command from linux land that installs prereqs 15:05:35 so basically for package X you get all the prereqs you need to build package X 15:06:40 hm... are we talking about pkg(8) command or poudriere builtds ? 15:17:36 mzar: what he is trying to explain is a function of apt & dpkg in the debian world 15:18:06 build-dep is a build dependency step of package building 15:18:44 it is not "linux" specific as much as it is dpkg/apt 15:21:38 So it sounds like to me poudriere already has that depemdency functionality built in when building a package 15:21:55 s/depemdency/dependency 15:22:36 (I haven't used poudriere in years so I can't remember personally) 15:57:09 Tenkawa: I am not much Linux user, but it works for me. Thank you for the explanation 15:59:09 johnjaye: yes, with poudriere you can build and commit to the repo all the dependencies but not package itself using command poudriere testport. Does it fulfil you needs ? 16:12:47 kevans: am i doing phabricator wrong, i had to download the raw patch and apply it to my source tree using patch(1)? 16:12:59 i mean that's okay but this is an odd workflow when git is involved 16:15:19 i do like how quickly bhyve+nvme writes crash dumps 16:16:41 ivy: there's arcanist and some tooling that markj wrote around it called git-arc that might be helpful here 16:16:57 devel/freebsd-git-devtools 16:16:58 oh i know about that but i didn't know it could do this 16:17:08 i only used it to submit phab reviews 16:17:27 can't we just use github smh my tree 16:17:27 you're specifically looking for arc-patch/git-arc-patch 16:21:24 patch is broken 16:21:27 /data/build/src/freebsd/lf/main/sys/kern/subr_bus.c:2579:20: error: incomplete definition of type 'struct prison' 16:21:27 2579 | CURVNET_SET_QUIET(TD_TO_VNET(curthread)); 16:21:27 | ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~ 16:25:10 (updated the PR)