Hi, I recall someone here told me he use fish shell, wonder what is the analog of "!!" in fish

If I have two exec.start within my myjail { exec.start = "/usr/local/mytool1"; and exec.start = "/usr/local/mytool2"; } let's say, would both work at each start of Jail?

(in jail.conf)

tercaL: look for += in jail.conf(5)

would symlinking /etc/localtime to the correct zoneinfo file cause issues? I notices that my current /etc/localtime was a file dated 2017

I believe tzsetup copies the file

it's usually much better not to have an /etc/localtime at all, and just set TZ in the environment as needed

though that does mean the system will run on UTC except when specified

the only way anything would ever care about whether /etc/localtime is a symlink or not is if / and /usr are separate filesystems

and if anything accesses it before /usr is mounted

everything ZFS on one tank, nothing fancy

so a different subvolume, but on the same device

all the rc.d scripts relevant to timekeeping seem to depend on FILESYSTEMS so won't be run until /usr is mounted anyway

awesome. But it's weird though that there's no automatic update of that file, or that FreeBSD is the only OS where /etc/localtime is a file (and not a symlink)

looks like tzsetup will copy the file if it doesn't exist, but if it's already a symlink, it'll create a new symlink instead of copying

if I have 10 GB data and make a zfs snapshot, need the snapshot also 10 GB?

miromoto, That will depend on how much data is changed since the creation of a snapshot.

I create a new boot environment from a snapshot of a current one. I am seeing ~200-300 MB taken by the snapshot after updating the OS via source & may be after updating packages.

Oh the size of a boot environment is usually ~6.5 GB

... compressed with compression=zstd-15.

parv: so it works as differential backup, right? If I lost my harddrive and have only the snapshot, it isn't useful

miromoto, Say a snapshot is copied to a files via " zfs send x@y >| file.x-y". Then can create a new dataset from that file.

s/files/files/

🤦🏽‍♂️ s/files/file/

Feel free to replace the file with back up of the original dataset on another dataset

parv: thank you for your answer, the best is, I test it :)

Indeed

If this is the correct place to submit web site typos, section 4.4.1 of the handbook says the first-run output of pkg should be

Do you want to fetch and install it not? [y/N]

Obviously the "not" should be "now".

snorkcamp: is "Reported by: snorkcamp on libera-chat IRC" good as part of a commit message?

Absolutely, thanks dstolfa! :-)

snorkcamp: emaste will push it at some point :). thanks!

fixed, should be on the website in a few mins

thanks for reporting it

Sorry, didn't have a chance to check until just now... looks good. Thanks emaste :-)

what languages support sctp?

(is there a better channel for this?)

is the beta available for freebsd-update? the site seems to say yes, but it doesn't work when i do it. first time, so could be user error

imgur.com/8hp9RZJ.png  but libvirtd is running

any clue/

markmcb: i haven't seen any emails about betas yet, but, i assume, from this, freshbsd.org/freebsd/src/branch/releng/14.0 that builds have started

Title: FreeBSD / src - FreshBSD

can you use kqueue with sctp?

Beladona: could you please just paste in the actual error message. it's really hard to read in that picture, and i can't scroll in the pictured window to see it in full

SoniEx2: i reckon freebsd-hackers@, freebsd-net@, or freebsd-arch@ might be able to answer your questions

usually, i would start by looking at docs and code

but, right now, all i want is to sleep, and I still have about 3 hours before my kid will allow me to do that, so diving into code i know nothing about is fraught with dangers

first stab at BETA builds was broken if cgit.freebsd.org/src/commit/?id=4e0…ca1514fc5c8d4720bec5a1ac6c71888aa38 is to be believed, I imagine he tried again after that

Title: src - FreeBSD source tree

I don't think there's a process for incrementally redoing a build like that, so we're probably looking at the full build time following that before there's a chance of availability

how long does that usually take?

I don't recall, but I would imagine not more than a day or so; iirc he does a little more Q/A on BETA/RC builds to make sure they're not fundamentally hosed

*nod*

does it make sense to use BETA/RC builds for new software?

as in, as a basis for your own platform?

or are we talking that concept in a release process in general?

SoniEx2: is you're developing Software that will be finished in two years from now, it makes sense to go with main, imo. otherwise, stick to something more stable. or even STABLE.

yeah like uh we're trying to make this cursed reverse proxy thingy

we have no code so far, so does it make sense to start writing it at a BETA/RC or stick to STABLE?

depends on how long you think it's gonna take

six months or less? RELEASE. a year or two? STABLE. two or three or more? why not sick with CURRENT, if you're already that deep in the mud?

if I were the one deciding, I'd stick to -stable in many cases and main the rest

wait which one is STABLE again

but I also have the advantage of being able to take errata fixes to stable branches personally if I need to

there you go. two almost equally qualified people issuing almost the same statement

in general, if you have a problem in base it's both quicker and easier to get it fixed in a stable/ branch than in a release

ah, STABLE is dev branch for RELEASE basically?

sort of. it's a branch where no breaking changes are merged into

*nod*

until eventually a new release is cut from it

and BETA/RC is what?

that's pre releases, before a new RELEASE is cut

beta/rc are generally along the release ("releng" branches) lineage

hmm, but there's no 14.0-STABLE until there's a 14.0-RELEASE?

it's 14-STABLE, because all 14.x releases are cut from it, not just 14.0 and it's patches

why are we explaining this? don't we have a document that explains it better than we can?

koobs had a good diagram somewhere

so where does one download 14-STABLE?

snapshots will start after the 14.0 release

otherwise you'd have to grab src and build your own

SoniEx2: the time around a RELEASE is very busy, so many things are disrupted

that reminds me, i need to test Colin's new 14.0 images with cloud-init

alright, so there is no 14-STABLE until there's a 14.0-RELEASE we guess

So much to do

it does exist, it's just that re only builds one set of snapshots from a given major branch series at a time

oh okay

stable/ branch always gets created first, then releng/ from that

as soon as releng/ branches, stable/ is open again and renamed to 14-STABLE, which kust jappened

so it's probably fine to go with the BETA (once that's built) for developing our software?

since that's gonna become a RELEASE in a couple of months

it's is a couple of months, that might mean 14.1, so, I would still stick with STABLE

hey there; what system specifics do you fine-tune, services you disable, etc., right after creating a new jail?

veg: generally, network, cron, and syslog, because i do network from the jail startup, and i don't want cron to run periodic scripts (i guess i could just disable periodic?), and i do syslog from unter outside, too

pthanks meena, that sounds reasonable

meena: do you disable cron as a whole though?

hey quick question i made the changes in the /boot/load.conf to change the colors of the kernel messages during boot up of freebsd 13.2 my question is how do i change the console colors during boot is this also done in the boot/loader.conf or do i need to recompile the kernel and if so what option do i need to put in the new kernel file ?

markmcb: fyi, announcement mail for BETA1 just dropped