I think I'm on to something. I don't think ly launches sway with ck-launch-session but instead just launches it directly?

lw, ping

polyduekes: raw commit info can be got by appending .patch to GitHub commit URLs: freebsd/freebsd-ports 851ec02.patch

I'm wondering about etymology of ports/packages. I think packaged foo is still a port. Does this seem reasonably?

pabs3: thanks for the info

hello

I am trying to forward an X11 session to a FreeBSD chroot jail

problem solved by mounting nullfs with X11-unix, tmpfs in to the compat system and Xauthority copied in to the jail

Yea, that sounds like a pretty standard solution.

I'm hoping to get IPv6 networked on an Azure FreeBSD 14.1 instance - anyone got that working already? /etc/rc.conf settings would be nice. I feel like the handbooki is lacking in that area.

doesn't ifconfig_<interface>_ipv6="inet6 accept_rtadv" work there?

nimaje: I just discovered the first critical bit of information: my default IPv6 gateway. Let's see how this goes...

does azure not do SLAAC? you shouldn't need to know that with SLAAC (and why does the handbook list static ipv6 stuff before dynamic ipv6? in most cases you want dynamic ipv6)

What is useful: for this, do this. Got none of that.

nimaje: I don't know. So far, I've assigned static IPv6 and gateway, can't ping the gateway.... so, I've got that going for me.

I will say: the reboot time for an Azure VM is nice.

dvl, I believe you can thank cperciva for that.

V_PauAmma_V: Agreed. He's been doing some great work on that.

Assumption check: when I "bectl destroy" a boot environment, does it also rollback the underlying ZFS snapshot?

s/rollback/rollback to/

hi, I want to install FreeBSD 14.1 in a Pentium Dual Core, first, I think it is 64 bits, the computer is a dell optiplex 755. The HD is 80Gb and I already have a partition of 512Mb for Windows NT (just for fun). I would like to leave space for another 512Mb partitionn (NTFS or FAT) and the rest for FreeBSD, I always install FreeBSD without sharing with another OSs, so could someone let me know what

shall I do here? thanks

uskerine: I'd first try to boot it from an install cd or usb to verify that it is 64bit

(It might very well be, I'd just want to make sure)

As for the dual-booting part, I'm sure there are folks here who can advice on that. I haven't dual-booted anything in many years.

what should I do to make xdm work?

it runs, but when I log in, the programs complain that they cannot connect to the server

I just upgraded from 13 to 14, and now running `sudo` or `pkg` gets me an error like this:  ld-elf.so.1: Shared object "libssl.so.111" not found, required by "pkg"

what do I do?

did you forget to reinstall your packages when freebsd-update told you to?

I didn't reinstall packages, but I must have missed that instruction, as I don't remember seeing it. Is there no COMPAT to save me? How do I recover from the current state?

when gh00p comes back, tell them pkg-static bootstrap -f && pkg upgrade -f should do the trick

pkg(7), which needs to be involed with the full path when pkg(8) is installed, can also be used instead of pkg-static.

It's good to avoid teaching people the bad habit of using full hard coded paths though. Says me who has been burned many times by hard coded paths.

that's not what i'm doing, though

But "which needs to be involed with the full path when pkg(8) is installed" says it needs to be invoked with a full path.

and what about that says "you need to always do this"?

Where is "you need to always do this" written?

exactly my point.

Okay then.

And now for something completely different; there's been an announcement about the change to the support model for FreeBSD: lists.freebsd.org/archives/freebsd-announce/2024-July/000143.html

looking forward to see how that plays out...

I certainly appreciate the effort

but a minor release every quarter sounds... "interesting"

six months would sound more resonable IMHO

I got the impression they're staggered between major releases, so you effectively get 6 months between minor releaes for the same major.

s/releaes/releases/

I was just about to press enter on a sentence similar to this ^ :)

Only if you've got infrastructure on both RELENG branches will you be updating every quarter.

I can only think of one place where that's the modus operandi.

aye, that makes it the "preferred six months" then :D

I'm a _huge_ fan of the predictable release schedule, personally.

more predictable*

certainly. I just wonder whether releng@ truly has that capacity

I don't doubt that they can pull it off, but can they pull it of consistently over years?

I imagine releng@ to be quite a stressful job.

compared to other freebsd positions that is.

nobody really has to deal with deadlines the way that releng@ does

Well, once it's fully in place, there'll no longer be times when there's 3 supported branches, and one minor release every quarter is less work than they're currently doing now, I think?

possible

just to be clear: I'm not saying it's a bad decision. I'm honestly looking forward seeing how this plays out and surely releng@ knows better than me

Colin as re@ knows better than anyone how to do this kind of thing, I'm pretty sure.

indeed

my wording might have sounded unnecessarily negative/harsh

Eh, no worries.

Also, Colin did an excellent talk at BSDCan this year: youtube.com/watch?v=wrlCxwH6MsA

I get the impression Colin is doing this to make it easier for someone else to take over the job? That's just pure speculation, though.

maybe one day I'll leave my cave to attend a BSD con

Wouldn't that involve touching grass?

oh that's fine. I mainly dislike uncontrolled sunlight

So long as it doesn't try to crawl up my nose before I've had my antihistamines, I'm fine.

Grass does seem fond of nasal spelunking, though.

if you can't fight them - join them

It's even figured out how to be temporarily airborne for the purposes of getting up in peoples business.

surely there is some 420 joke in there somewhere

Oh, almost certainly.

if you can't fight them - joint them?

I'll see myself out.

ok, I have some freebsd vm, where I noticed that the disk space is not enought, so I resized the disk, now of course freebsd thinks the gpt is corrupt, as the backup gpt is where the old end was, not at the end with the new size; so now I should do a gpart recover to correct the gpt then resize the freebsd-zfs partition and then expand the pool to the full partition via setting autoexpand and a

reboot, as it is the root pool?

nimaje: the corrupt gpt is OK, expected, normal, in this situation.

nimaje: so, yes, gpart recover.

thanks vkarlsen

dvl: thanks for confirmation, that I unstand that correct

oh, zpool online -e works too without needing to use offline, so also usable on a single disk root pool while the system is running

What up

Thinking of getting freebsd another shot

Hope my sound card is supported now

nimaje: I have notes on this process at the office, and that's of no use to you until Monday....

everything worked perfectly, that's also why I now know that zpool online -e works on a single disk pool, that is currently in use

anyone here using labwc ?

Hello, all. FreeBSD comes with a vi clone named nvi. Does anybody know how to disable wrappeing it that editor? Setting wm and wl to 0 does not help, the man page does not seem to list any other options related to wrapping, and I see no other documentation for nvi.

wrapping for display, or inserting newlines into the actual file? vi has always done the former

jgh_, I mean wrapping for display, when the lineas are too long. I dont' want it for code and config files.

you want something that isn't vi, then; sorry

jgh_, Hmmm. Do you mean that this simplle behavior <vimdoc.sourceforge.net/htmldoc/options.html#'wrap'> is Vim-only?

^ I mean the behaviro with `nowrap' on.

Viewing code and config files with lines wrapped around the edges of the screen is ugly, and these days many writers do not care about violating the ISO screen limit of 80 characters...

I can't comment on whether it's vim-only, but traditional vi didn't do that

mind you, it's been a long time and lots of different versions. I was brought up on the one on Edition 7, around 1984

Thank you. Am I right, thought, that in the times when traditional vi was young & beautiful, people cared not exceed the 80-characters-per-line limit in all their text files, especailly code and config ones?

Great -- it was more than a year before I was born into this workd.

to some extent. It did help that terminals were that wide; windows were not a thing

(ok, we got a Sun 2 in about 1985... But vt100 was my workhorse

Well, in fact, I like reading text in monospace font at about 60-70 characters per line, and limit my code lines to 80 characters. Hard-wrapped text is a beautuful idea.

VT100 -- a terminal controlled by those ECMA codes: <vt100.net/emu/dec_ansi_parser> .