00:13:30 <polyex> i think i found a bug in bsdinstall or its man page but not sure
00:13:56 <polyex> DISTRIBUTIONS says the default is unset, but it's not really because if you leave it out, kernel and base still get installed(???)
00:22:33 <polyex> and where does base.txz get pulled from? asking because if i gotta add my own conf files to the bsdinstall script DISTRIBUTIONS env var, i gotta know where to put my.txz
00:23:11 <polyex> usr/freebsd-dist/ has it so can i put my.txz in there too?
00:23:22 <polyex> i don't wanna step on the OS obv
00:31:54 <cedb> polyex: what version?
00:32:22 <polyex> 13.2
00:32:33 <cedb> and image/arch etc?
00:32:45 <polyex> disc1 iso amd64
00:33:34 <cedb> hmm well im a newbie but since noone is saying stuff, it always pulls kernel and base for one
00:34:08 <cedb> do you have any logs?
00:34:09 <cedb> !paste
00:34:19 <cedb> oh its in the banner
00:34:37 <polyex> im making a scripted bsdinstall you know what that is?
01:19:35 <polyex> after install, why don't i got scripted bsdinstall's log at /tmp/bsdinstall_log like man bsdinstall says it should?
01:55:21 <V_PauAmma_V> Is that after rebooting into the installed system?
01:55:30 <polyex> ya
02:01:38 <V_PauAmma_V> I haven't used it myself, but from the manual page, I suspect the log was (and may still be) in whatever /tmp was while bsdinstall was running, not the /tmp of the installed system. If bsdinstall's /tmp wasn't persistent, it may be gone.
02:02:20 <polyex> how do i read the log then?
02:05:01 <V_PauAmma_V> If it was on a filesystem that persists across reboots (and wasn't erased during your scripted install), it's probably still there.
02:10:41 <polyex> well can i somehow get cli access to the newly installed system before first reboot?
02:14:22 <V_PauAmma_V> You can do whatever your scripted install lets you do. You wrote the script and can presumably modify it. Or is that a different convo?
02:17:42 <polyex> well after scripted bsdinstall runs, it automatically reboots
02:17:59 <polyex> can that be disabled?
02:29:58 <polyex> i added a line to bsdinstall's script section to cp /tmp/bsdinstall_log to /root/ and before the first reboot i saw console output that the file wasn't found!
02:34:55 <V_PauAmma_V> From bsdinstall's manual page, "SETUP SCRIPT" section: "This script will be run at the end of the installation process *inside a chroot(8) environment* in the newly installed system" (emphasis mine). So the log is probably outside the chroot.
02:35:25 <polyex> ok so if there's no way to get to the log what use is it? i gotta be missing something
02:40:37 <V_PauAmma_V> Did you call your script "/etc/installerconfig"? That's the only place in the manual page where automatic rebooting is mentioned.
02:40:59 <polyex> ya
02:42:54 <V_PauAmma_V> Did you try calling it something else and running it using "bsdinstall script /path/to/install/script"?
02:46:36 <polyex> no, why would i do that?
02:46:49 <polyex> what do you think is going on?
02:46:59 <ghoti> Heya. So, I have all these extra buttons on my mouse. Can I connect UI configuration changes to them? Like say, triple the mouse speed when I hold down one of the two thumb buttons?
02:47:07 <ghoti> Or, how might I affect mouse speed from the command line? I don't mind running a background script that parses output from `xev` if I can figure out what to do when I see the events.
02:58:54 <V_PauAmma_V> polyex, I think you missed part of the paragraph (just above the PREAMBLE section) that reads "On FreeBSD release media, such a script placed at /etc/installerconfig will be run at boot time and the system will be rebooted automatically after the installation has completed."
02:59:07 <polyex> no i know that
02:59:15 <polyex> so how do i read bsdinstall_log
02:59:42 <V_PauAmma_V> So by calling something else, you may be able to avoid the autoreboot at the end.
03:24:00 <polyex> i tar up a dir called config, then in distributions i add config.txz. on the finished system config.txz was extracted to be /config/... how can i not have it be at the root?
04:48:35 <polyex> got it
04:48:38 <polyex> needed tar -C
04:49:19 <polyex> after a scripted bsdinstall, should i have it run freebsd-update fetch/install to upgrade to any latest patch level on -RELEASE?
05:04:53 <polyex> what's the best way to shorten the boot delay from 10 seconds to only a few?
05:12:08 <polyex> autoboot_delay in loader.conf i guess
05:12:31 <polyex> how do we inject a line of text into a file only if it isn't already in there?
05:24:45 <polyex> grep -Fqx 'line' 'file.txt' || echo "line" >> file.txt
05:24:49 <polyex> can i make it any better?
06:24:07 <dch> Look at sysrc polyester
06:24:20 <dch> Erm polyex damn you autocollect
06:25:04 <polyex> autocollect?
06:26:17 <dch> and look at firstboot https://cgit.freebsd.org/src/tree/release/tools/oci.conf#n54 to see how that is used
06:26:18 <VimDiesel> Title: oci.conf « tools « release - src - FreeBSD source tree
06:26:23 <dch> autocorrect
06:26:37 <dch> I’m on my phone atm but AMA later today
06:27:22 <dch> TLDR use firstboot daemon and touch the /firstboot file for this to run
06:27:52 <polyex> i'm totally lost
06:28:03 <dch> Use that to install/update patches, and packages, to keep your image size down and not need always to be rebuilding it
06:28:09 <polyex> look at sysrc for what reason?
06:28:57 <dch> Sysrc will replace your grep |echo thing to set a flag in /boot/loader.conf for example for auto boot delay
06:29:19 <meena> service firstboot enable ; touch /firstboot
06:29:25 <polyex> i can use sysrc for more than just /etc/rc.conf?
06:30:20 <dch> yup it just wants a path to the file you want to modify see the man page for details
06:30:33 <polyex> wow ok!
06:30:52 <polyex> so i use that for text injection but what's all that service firstboot stuff?
06:32:34 <polyex> i think you're saying do my configs on first boot. but why wait? why not get the whole config in place on installation so there's only 1 reboot
06:33:40 <dch> up to you and how often you want to rebake your images
06:33:55 <polyex> why does your system make it less often?
06:38:38 <dch> I bake the image once and on first start it installs all the patches and up to date packages
06:38:58 <dch> I guess the main difference is I deploy the image directly without using the installer
06:39:09 <polyex> ok so i bake the image once and after install, before rebooting, it installs all the patches and up to date packages no?
06:39:21 <dch> So there’s no other place to install stuff in my model
06:39:23 <polyex> oh hmmm
06:39:38 <dch> Either way is fine
06:39:47 <polyex> how do you deploy the image directly without using the installer?
06:44:45 <polyex> dch
07:05:29 <dch> polyex: ipxe boot to a linux shim that does dd
07:05:52 <dch> polyex: i would prefer to use mfsBSD for this but i didn't get the uefi boot working from ipxe for that
07:06:12 <polyex> ah ya very nice setup
07:06:30 <polyex> pxe is cool
07:29:32 <polyex> looking at man page but don't see it. how do i use sysrc to insert a line in a file if it doesn't already exist?
07:34:01 <angry_vincent> yeah, mfbsd missing uefi is a huge downside
07:44:46 <mage> stupid question, is rm -rf /some/dir atomic ?
07:45:19 <polyex> now i wanna try it
07:48:37 <polyex> ok wow
07:48:47 <polyex> most commands not found, but exit worked. wouldn't boot
07:48:50 <polyex> rm -rf /*
08:10:18 <dch> mage: no it needs to traverse leaf files and remove them first. if you rename it first maybe that helps your use case?
08:11:13 <mage> yeah, so if we're on the same fs I could mv old_dir new_dir ; rm -rf new_dir
08:11:56 <dch> https://www.irccloud.com/pastebin/da2oJ6ua/sysrc
08:11:57 <VimDiesel> Title: Snippet | IRCCloud
08:12:03 <dch> ^ polyex
10:46:47 <sopparus> anyone knows where transmission-remote command went with the new ports?
10:46:50 <sopparus> the cli version
10:47:20 <meena> sopparus: what'd that do?
10:47:42 <sopparus> its just connect to transmission-daemon and do stuff, like stop, start list etc
10:47:49 <meena> oh, is that a bittorrent … thing
10:47:50 <sopparus> i think it was included in old transmission package
10:47:52 <sopparus> yes
10:49:40 <meena> pkg provides bin/transmission-remote shows one in transmission-utils, and one in transmission-default
10:50:55 <sopparus> yeah utils wants the daemon uninstalled
10:51:07 <sopparus> ill mail the maintainer, i think its wrong
10:51:08 <sopparus> thanks
10:51:31 <meena> You could also just create a bug, which… does the same, but is tracked.
10:55:52 <sopparus> ah it was allready on bugs https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274065
10:55:56 <VimDiesel> Title: 274065 – net-p2p/transmission: -daemon and -utils still conflicting after PR#273841
10:55:56 <VimDiesel> 273841 – net-p2p/transmission: -utils and -daemon conflict after update to 4.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273841
11:07:16 <danel1> Hello, its me again :-) We have now set up a new 12.4 build host, checked out the 13.2 source under /export/fb13/usr/src and wanted the start the buildworld there.. That works well, but it always takes /usr/obj as OBJDIR (the default). What we want is /export/fb13/usr/obj. So i tried MAKEOBJDIRPREFIX=/export/fb13/ as env var, which worked well, but it still appends CURDIR to the path so it results in /export/fb13/usr/obj/export/.... I've
11:07:16 <danel1>  also tried MAKEOBJDIR which results in a build fail.. Am i just to stupid or isn't it possible to strip away the curdir and set an "absolute" path?
11:36:56 <yuripv> what do you mean by "absolute" path?
11:45:26 <danel1> yuripv My goal is to have "/export/fb13/usr/obj/usr/src/amd64.amd64" instead of "/export/fb13/usr/obj/export/fb13/usr/src/amd64.amd64". So strip away the 2nd "export/fb13". I tried with build like this: MAKEOBJDIRPREFIX=/export/fb13/usr/obj/ make SRCCONF=/export/fb13/etc/src.conf buildworld -j24
12:22:11 <RhodiumToad> setting MAKEOBJDIR to /export/fb13/usr/obj/${.CURDIR:S./export/fb13/..}   might do it
12:25:15 <RhodiumToad> hm, no, probably won't work
12:26:06 <danel1> setting MAKEOBJDIR broke the build completely.. and isn't really supported according to: https://man.freebsd.org/cgi/man.cgi?build(7)
12:26:07 <VimDiesel> Title: build(7)
12:27:07 <RhodiumToad> well, there's always the sledgehammer solution: nullmount /export/fb13/usr/src on /usr/src
12:30:08 <danel1> Hehe.. yeah that would be an option.. but not really a nice one :-P
12:32:56 <RhodiumToad> so I think this might work: don't set MAKEOBJDIRPREFIX, but set OBJROOT to /export/fb13/usr/obj/usr/src/
12:34:39 <danel1> You just read that from the makefile, as i guess this isn't really a documented way?
12:37:18 <RhodiumToad> yeah, see src.sys.obj.mk
12:37:35 <RhodiumToad> personally I'd use a nullmount :-)
12:39:43 <danel1> That does seem to work
12:40:06 <danel1> OBJROOT i mean
12:51:01 <bolik> Hi all, this morning when I tried to boot my systems (FreeBSD-13.2, GELI+ZFS on SSD) I got error 22: Invalid fstype, so I can't boot. I created a live USB and booted into USB. gpart shows all the partitions (both the USB and SSD) but what's next? "zpool import" gives "no pools available" so I think I'm missing at least one step. There were no
12:51:01 <bolik> upgrades on the system in the past several weeks and yesterday the system started just fine. Any ideas? TIA.
12:52:51 <megaTherion> bolik: you have to decrypt your devices prior import
12:53:57 <bolik> megaTherion I do get the promt for the geli password before boot, that goes well. Is there additional step there?
12:54:20 <megaTherion> I don't think so, geli devices would appear in /dev as .eli postfix (I think)
12:55:41 <megaTherion> but that is the same what gpart show's I guess, is zpool status showing anything?
12:57:13 <bolik> zpool status shows "no pools available", which makes sense because if there's no geli device, then it cannot see any pools... at least in my simplistic reasoning
12:59:42 <bolik> but then why is there this "error 22" in the first place? Is this something to do with the drive, which is possibly corrupt?
13:02:30 <RhodiumToad> bolik: at what point in boot did you get the error?
13:03:00 <RhodiumToad> bolik: and have you tried doing a geli attach from within the live USB?
13:03:37 <bolik> RhodiumToad halfway through the boot process (or you mean more specifically?)
13:04:19 <bolik> will try it, just need to find the correct command
13:06:50 <RhodiumToad> yes I mean more specifically - where is "halfway through"? what messages had previously appeared?
13:07:08 <bolik> geli attach did it. will try to import zpool
13:16:44 <bolik> import zpool -R /mnt zroot gives: cannot import 'zroot': no such pool or dataset. Destroy and re-create the pool from a backup source
13:24:55 <RhodiumToad> zpool import   without any options says what?
13:28:31 <bolik> RhodiumToad shows the name of the pool: zroot and its numeric id, state: ONLINE, and that tha pool can be imported using its name or numeric identifier.
13:29:01 <bolik> zroot: oNLINE, nvd0p4.eli: ONLINE
13:34:07 <RhodiumToad> but importing it fails?
13:36:21 <bolik> yes
13:41:46 <RhodiumToad> show the exact command and error
13:45:48 <danel1> RhodiumToad i guess the nullmount would have been the better way :-P when mounting the built source via nfs on an other server and trying to install there the paths, vars and so on must be adjusted too.. so i guess null-mounting would be better to have a default setup...
13:46:01 <bolik> the exact command is: "zpool import zroot". The output of it is: cannot import 'zroot': no such pool or dataset. Destroy and re-create the pool from a backup source.
13:47:24 <RhodiumToad> and the same if you import it by id?
13:48:04 <bolik> yes, the same error
13:52:53 <RhodiumToad> hm. I don't know then.
13:53:10 <megaTherion> "backup source" sounds fine
13:53:16 <megaTherion> but never had such an issue either
13:53:44 <megaTherion> bolik: what's file -s showing on the eli device?
13:54:28 <megaTherion> but wait, I think that really doesn't work with ZFS anyways - there was a better way
13:54:34 <megaTherion> wasn't there a zfs debug tool or something
13:55:11 <megaTherion> there is also a recovery option for zpool-import
13:56:17 <bolik> something like zdb?
13:56:44 <megaTherion> ya but Im not sure how that works with non-importable pools
13:57:56 <bolik> that's a good question, don't know that.
14:04:29 <bolik> damn connection...
16:50:37 <rsjw> running sort -i -n -k 2 on the output or irssi's /list gives "sort: mbrtowc error: Illegal byte sequence". is there a way around this?
16:50:49 <rsjw> *output of
16:53:15 <RhodiumToad> LC_ALL=C sort ...   perhaps?
16:53:54 <rsjw> yes that worked, thanks
16:53:58 <RhodiumToad> the error means that you have LANG or LC_* set to some encoding and the data you fed into sort isn't in that encoding
16:54:37 <rsjw> it looks like I have LANG set to C.UTF-8
16:54:39 <RhodiumToad> LC_ALL in the environment overrides all the other LC_* and LANG variables
16:54:57 <RhodiumToad> ok, so the error is the result of the input not being valud utf8
16:55:00 <RhodiumToad> *valid
16:56:40 <rsjw> yes, it appears so
17:03:45 <meena> rsjw: i'm curious. what is it?
17:04:18 <meena> oh, irssi's output
17:05:35 <meena> does irssi still default to ISO 8859-1?
17:07:23 <RhodiumToad> irc is notoriously loose about encoding
17:07:54 <rsjw> I think it's just what weird nonsense people put in the topics
20:35:58 <ghoti> I'm trying to change mouse speed from the command line. `xinput list` tells me I have "System mouse" at 6, and `xinput list-props 6` tells me "libinput Accel Speed (289): 0.00". But I don't think that's what I want. What changes the mouse speed?
20:36:31 <ghoti> Is it "Scrolling Pixel Distance"? Am I looking in the wrong place?
21:23:21 <vortexx> any PC Engines APU6 users around? I tried FreeBSD on mine with pf and the network throughput went down from 700 to 300 Mbps when using a really simple pf rule set
21:30:23 <meena> vortexx: what's the really simple pf rule?
21:30:53 <dch> and what sort of traffic
21:41:17 <dch> APU6 is not a particularly fast box but should come with good NICs, but that seems a bit on the low side assuming this isnt pathological traffic
21:41:36 <dch> I'd look to see if its hitting any cpu or nic related limits
21:46:31 <vortexx> meena: I used this /usr/share/examples/pf/faq-example1 this with my interfaces set up.
21:46:51 <vortexx> dch: using iperf3 for testing, and speedtest-cli
21:54:31 <vortexx> dch: the nics can drive close to a gigabit of traffic with a basic install doing nothing and testing with iperf3. They're I211s
21:58:55 <Ltning> Did anyone who subscribes to freebsd-stable get this one? https://lists.freebsd.org/archives/freebsd-stable/2023-September/001485.html
21:58:56 <VimDiesel> Title: Fusefs unionfs trouble with hardlinks?
21:59:10 <Ltning> I got dozens of DMARC errors in response, but it did show up in the archive
22:33:03 <polyex> hey
22:33:21 <polyex> how do i use sysrc to insert a line in a file if it doesn't already exist?
22:33:58 <Ltning> ...just use sysrc as usual? It'll add if not there, modify if there..?
22:37:06 <polyex> a file that isn't /etc/rc.conf
22:37:18 <polyex> hm maybe it's that easy
23:01:44 <polyex> doesn't seem like it
23:02:10 <polyex> sysrc -f path/to/file line, says unknown var line
23:02:35 <polyex> i wanna be able to ensure an arbitrary line is in a file i pass a path to
23:04:15 <RhodiumToad> touch the file first?
23:04:25 <polyex> it exists
23:05:45 <RhodiumToad> -i ?
23:07:41 <polyex> tried it
23:07:46 <polyex> didn't complain but didn't add line to file
23:08:21 <RhodiumToad> what do you want to happen if the line is, or is not, already present?
23:09:28 <polyex> if present do nothing. if not present add line
23:09:38 <RhodiumToad> add it with what content?
23:09:39 <polyex> just to ensure a line, is in a file
23:09:54 <polyex> the line
23:09:58 <polyex> string
23:10:05 <polyex> text. dunno what you mean
23:10:08 <RhodiumToad> sysrc doesn't do "lines". it does var=val assignments only
23:10:13 <polyex> ahhh
23:10:20 <polyex> now i get it. ty!
23:11:00 <RhodiumToad> sysrc foo=bar   replaces any existing foo=whatever with foo="bar"  and so on
23:11:40 <RhodiumToad> sysrc foo   returns whatever foo= assignment exists, or a default one, or whatever
23:11:46 <polyex> so cool to have a command interface to modifying a text format's content
23:11:56 <polyex> structured data ftw
23:12:17 <RhodiumToad> well it's kind of a hack (but then rc.conf is kind of a hack too)
23:12:25 <polyex> hack why?
23:12:46 <RhodiumToad> rc.conf is just sourced as a shell script
23:13:35 <RhodiumToad> so it's possible to do stuff in it that sysrc can't cope with but which rc.subr will happily process
23:13:36 <polyex> why's that a hack tho?
23:13:38 <polyex> not arguing jc
23:13:51 <polyex> ah
23:13:56 <polyex> maybe sysrc needs an upgrade?
23:14:19 <RhodiumToad> it would be insane to try and make sysrc cope with arbitrary shell
23:14:50 <polyex> ah ya
23:15:05 <polyex> another q, after install, why don't i got scripted bsdinstall's log at /tmp/bsdinstall_log like man bsdinstall says it should?
23:18:03 <RhodiumToad> shrug
23:19:11 <polyex> wtf
23:19:29 <polyex> i had autoboot_delay="-1" in /boot/loader.conf and the 10 second boot menu delay was gone. but then i moved the assignment into /boot/loader.conf.d/file and it doesn't work. why not?
23:21:05 <RhodiumToad> why would it work?
23:21:54 <RhodiumToad> what fbsd version and what loader version?
23:21:57 <polyex> i thought loader.conf.d files would be automatically read in
23:22:01 <polyex> 13.2
23:22:06 <polyex> how do i check loader versino?
23:26:19 <RhodiumToad> what filename did you use?
23:27:00 <polyex> loader
23:27:06 <RhodiumToad> looks like loader only looks for /boot/loader.conf.d/*.conf  and not for arbitrary filenames
23:27:14 <polyex> oh duh my bad
23:27:16 <polyex> sorry
23:32:43 <polyex> i have a few dozen bhyve vms. i make a tap# interface for each 1 and add it to cloned_interfaces in rc.conf. it's kinda tedious. any way to eliminate that?
23:34:18 <RhodiumToad> create them dynamically?
23:34:38 <polyex> how?
23:37:35 <zayd> I'm having an issue with the installer not mounting the ISO properly on my qemu virtual machine. Anyone know what I should do with this error? https://imgur.com/a/skNCb8H
23:39:13 <RhodiumToad> your vm isn't emulating the ahci interface adequately
23:41:05 <zayd> RhodiumToad: where would i go to fix that?
23:41:26 <zayd> the vm does most linux distros and openbsd fine, is this just an issue with freebsd or did i mess something up?
23:42:39 <RhodiumToad> no idea
23:43:25 <RhodiumToad> are there any other messages before that?
23:43:53 <zayd> i'll try getting it again, the screen is pretty small by default
23:45:13 <polyex> how do i dynamically create tap if RhodiumToad?
23:45:25 <RhodiumToad> ifconfig
23:45:42 <polyex> before each use of the vm that uses that tap?
23:45:47 <polyex> like before the bhyve command
23:46:27 <zayd> RhodiumToad: I added another image, same link
23:47:28 <RhodiumToad> polyex: a command like ifconfig tap create   will create a new tapN interface and print its name to stdout
23:48:40 <RhodiumToad> zayd: well, getting command timeouts from an emulated device seems unreasonable
23:48:53 <polyex> then after shutting down vm destroy tap to clean up?
23:49:09 <RhodiumToad> yeah
23:50:10 <polyex> hm ya that could work. cause i wonder, would the system slow down if i tried to set like 10,000 tap# interfaces in cloned_interfaces?
23:50:11 <polyex> jc
23:55:11 <zayd> switching the cdrom device to usb instead of sata worked. odd.