06:53:09 Hi, I recall someone here told me he use fish shell, wonder what is the analog of "!!" in fish 07:37:10 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? 07:37:19 (in jail.conf) 08:08:09 tercaL: look for += in jail.conf(5) 08:08:53 would symlinking /etc/localtime to the correct zoneinfo file cause issues? I notices that my current /etc/localtime was a file dated 2017 08:11:35 I believe tzsetup copies the file 08:12:00 it's usually much better not to have an /etc/localtime at all, and just set TZ in the environment as needed 08:12:36 though that does mean the system will run on UTC except when specified 08:15:17 the only way anything would ever care about whether /etc/localtime is a symlink or not is if / and /usr are separate filesystems 08:15:33 and if anything accesses it before /usr is mounted 08:21:58 everything ZFS on one tank, nothing fancy 08:22:30 so a different subvolume, but on the same device 08:29:47 all the rc.d scripts relevant to timekeeping seem to depend on FILESYSTEMS so won't be run until /usr is mounted anyway 08:31:27 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) 08:34:06 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 10:58:19 if I have 10 GB data and make a zfs snapshot, need the snapshot also 10 GB? 11:03:53 miromoto, That will depend on how much data is changed since the creation of a snapshot. 11:07:34 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. 11:13:45 Oh the size of a boot environment is usually ~6.5 GB 11:28:48 ... compressed with compression=zstd-15. 11:41:19 parv: so it works as differential backup, right? If I lost my harddrive and have only the snapshot, it isn't useful 11:43:51 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. 11:45:30 s/files/files/ 11:45:47 🤦🏽‍♂️ s/files/file/ 11:47:11 Feel free to replace the file with back up of the original dataset on another dataset 11:50:29 parv: thank you for your answer, the best is, I test it :) 11:50:39 Indeed 13:49:44 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 13:49:58 Do you want to fetch and install it not? [y/N] 13:50:17 Obviously the "not" should be "now". 13:57:16 snorkcamp: is "Reported by: snorkcamp on libera-chat IRC" good as part of a commit message? 13:57:43 Absolutely, thanks dstolfa! :-) 13:58:21 snorkcamp: emaste will push it at some point :). thanks! 13:58:41 * snorkcamp tips his hat. 14:04:54 fixed, should be on the website in a few mins 14:05:04 thanks for reporting it 15:02:59 Sorry, didn't have a chance to check until just now... looks good. Thanks emaste :-) 16:41:39 what languages support sctp? 16:46:54 (is there a better channel for this?) 17:02:25 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 17:04:21 https://imgur.com/8hp9RZJ.png  but libvirtd is running 17:04:24 any clue/ 17:07:17 markmcb: i haven't seen any emails about betas yet, but, i assume, from this, https://freshbsd.org/freebsd/src/branch/releng/14.0 that builds have started 17:07:18 Title: FreeBSD / src - FreshBSD 17:08:16 can you use kqueue with sctp? 17:08:39 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 17:10:03 SoniEx2: i reckon freebsd-hackers@, freebsd-net@, or freebsd-arch@ might be able to answer your questions 17:10:41 usually, i would start by looking at docs and code 17:22:04 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 17:47:12 first stab at BETA builds was broken if https://cgit.freebsd.org/src/commit/?id=4e027ca1514fc5c8d4720bec5a1ac6c71888aa38 is to be believed, I imagine he tried again after that 17:47:13 Title: src - FreeBSD source tree 17:48:17 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 17:50:30 how long does that usually take? 17:52:28 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 17:53:39 *nod* 17:55:21 does it make sense to use BETA/RC builds for new software? 17:57:56 as in, as a basis for your own platform? 17:58:54 or are we talking that concept in a release process in general? 17:59:00 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. 18:00:44 yeah like uh we're trying to make this cursed reverse proxy thingy 18:01:29 we have no code so far, so does it make sense to start writing it at a BETA/RC or stick to STABLE? 18:02:13 depends on how long you think it's gonna take 18:04:13 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? 18:04:33 if I were the one deciding, I'd stick to -stable in many cases and main the rest 18:05:20 wait which one is STABLE again 18:05:34 but I also have the advantage of being able to take errata fixes to stable branches personally if I need to 18:05:35 there you go. two almost equally qualified people issuing almost the same statement 18:06:56 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 18:07:17 ah, STABLE is dev branch for RELEASE basically? 18:07:58 sort of. it's a branch where no breaking changes are merged into 18:08:09 *nod* 18:08:20 until eventually a new release is cut from it 18:08:24 and BETA/RC is what? 18:08:52 that's pre releases, before a new RELEASE is cut 18:08:54 beta/rc are generally along the release ("releng" branches) lineage 18:10:18 hmm, but there's no 14.0-STABLE until there's a 14.0-RELEASE? 18:11:02 it's 14-STABLE, because all 14.x releases are cut from it, not just 14.0 and it's patches 18:11:34 why are we explaining this? don't we have a document that explains it better than we can? 18:12:29 koobs had a good diagram somewhere 18:13:03 so where does one download 14-STABLE? 18:13:18 snapshots will start after the 14.0 release 18:13:37 otherwise you'd have to grab src and build your own 18:13:56 SoniEx2: the time around a RELEASE is very busy, so many things are disrupted 18:14:41 that reminds me, i need to test Colin's new 14.0 images with cloud-init 18:14:44 alright, so there is no 14-STABLE until there's a 14.0-RELEASE we guess 18:14:45 So much to do 18:14:51 it does exist, it's just that re only builds one set of snapshots from a given major branch series at a time 18:15:45 oh okay 18:16:49 stable/ branch always gets created first, then releng/ from that 18:17:34 as soon as releng/ branches, stable/ is open again and renamed to 14-STABLE, which kust jappened 18:18:31 so it's probably fine to go with the BETA (once that's built) for developing our software? 18:19:35 since that's gonna become a RELEASE in a couple of months 18:24:07 it's is a couple of months, that might mean 14.1, so, I would still stick with STABLE 19:57:28 hey there; what system specifics do you fine-tune, services you disable, etc., right after creating a new jail? 20:11:22 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 20:26:20 pthanks meena, that sounds reasonable 20:30:29 meena: do you disable cron as a whole though? 22:55:29 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 ? 23:49:53 markmcb: fyi, announcement mail for BETA1 just dropped