01:43:58 <warsoul> how can i mine any crypto using freebsd?
01:45:16 <skered> A pick?
01:49:02 <warsoul> skered any
01:53:04 <HER> bsdcoin
01:53:51 <skered> If you mind bsdcoin you can trade it for one commit.
01:53:59 <skered> mine*
01:59:29 <warsoul> how i can do that in freebsd?
01:59:57 <mason> warsoul: If you're lax with security, sometimes people will start mining crypto on your stuff without any intervention.
02:38:57 <warsoul> mason what you mean
02:42:34 <mason> warsoul: https://www.csoonline.com/article/564521/what-is-cryptojacking-how-to-prevent-detect-and-recover-from-it.html
02:42:35 <VimDiesel> Title: Cryptojacking explained: How to prevent, detect, and recover from it | CSO Online
02:47:57 <warsoul> mason how i start mining
03:29:23 <rtprio> warsoul: same as linux
05:29:55 <jauntyd> can anyone verify either way if the Postgresql driver for bacula v15 (from ports) works?
06:28:53 <jauntyd> ;)
07:08:20 <dch> is there a tool that generates htpasswd format files, but with newer algorithms? argon2 would be nice
07:08:36 <dch> the ones in ports look ancient
15:10:29 <voy4g3r2> if i am getting this error: cannot zero first 4096 bytes of '/dev/da0': Device not configured when i try to add a drive to a zfs pool
15:10:35 <voy4g3r2> that means the drive is dead?
15:22:13 <rtprio> that sounds like it's a sd card reader and there isn't a card in it
15:25:03 <voy4g3r2> rtprio: it is a hard drive :)
15:25:13 <voy4g3r2> i am trying ot add it to a zpool
15:25:59 <voy4g3r2> https://dpaste.org/uNzDi
15:26:00 <VimDiesel> Title: dpaste/uNzDi (Plain Text)
15:26:37 <rtprio> but it is a usb drive, eh
15:26:40 <rtprio> 0MB (0 512 byte sectors)
15:26:48 <voy4g3r2> yeah, i think it is dead :(
15:26:48 <voy4g3r2> https://dpaste.org/jVwnb
15:26:50 <VimDiesel> Title: dpaste/jVwnb (Plain Text)
15:26:53 <voy4g3r2> because i am trying to add to this pool
15:27:01 <rtprio> you can't zero the first sector BECAUSE IT DOESN'T HAVE A FIRST SECTOR
15:27:27 <voy4g3r2> so that confirms it is dead
15:27:33 <voy4g3r2> unless some how it "finds" the first sector
15:30:22 <rtprio> you could try a different usb cable but i don't think i'd recommend making a USB zpool
15:31:19 <voy4g3r2> hrm.. i can try the cable, thanks
15:31:34 <voy4g3r2> i understand the risk of usb zpool.. this is just storing backups, it is not being used for production use
15:31:41 <voy4g3r2> that is on a machine that is more equipped for it
15:38:05 <rtprio> okay, but you want to know that the backups are working
15:38:53 <voy4g3r2> yes i test them in a bhyve periodically
15:39:02 <voy4g3r2> zfs send recv
15:39:20 <voy4g3r2> i had a drive laying around and wanted to see if i could expand the pool
15:40:07 <voy4g3r2> https://dpaste.org/kve2J
15:40:08 <VimDiesel> Title: dpaste/kve2J (Plain Code)
15:41:54 <voy4g3r2> i probably should be fine with the 786g left but still do not understand why the whole APFS and timemachine does NOT compress
15:43:14 <voy4g3r2> rtprio: thanks for tips, time to go play
15:56:58 <warsoul> what miner i can use for freebsd
16:05:15 <rtprio> warsoul: move along now,
16:45:58 <angry_vincent> can i add directly devctl reset "devicename" to /etc/rc.resume?
16:46:10 <angry_vincent> or where to put it
17:12:47 <rtprio> angry_vincent: that seems like a fine place for it.
17:17:58 <angry_vincent> ok, i will test
17:23:58 <angry_vincent> maybe it worked
18:58:24 <levitating> So I just installed freebsd on a riscv64 vm
18:58:30 <levitating> and I am running into this:
18:58:31 <levitating> pkg: Error fetching http://pkg.FreeBSD.org/FreeBSD:14:riscv64/quarterly/Latest/pkg.txz: Not Found
18:58:38 <levitating> this seem familiar to anyone?
18:58:45 <levitating> I can't install pkg
18:59:57 <rtprio> risc64 eh
19:00:12 <rtprio> i'm not sure they build packages for that platform
19:00:33 <levitating> So just the base system?
19:00:51 <rtprio> you can build them yourself, using the ports tree
19:01:19 <rtprio> https://docs.freebsd.org/en/books/handbook/ports/
19:01:20 <VimDiesel> Title: Chapter 4. Installing Applications: Packages and Ports | FreeBSD Documentation Portal
19:01:36 <levitating> I don't see a /usr/ports
19:02:49 <rtprio> you might have to download it/ check it out if you didn't add it during the install
19:03:08 <levitating> I didn't install I downloaded a qcow2
19:03:40 <rtprio> oh
19:04:32 <rtprio> download one of these and extract it to /usr/ports:   https://download.freebsd.org/ports/ports/
19:04:33 <VimDiesel> Title: Index of /ports/ports/
19:07:00 <levitating> how do I download it though?
19:08:14 <rtprio> fetch
19:10:59 <levitating> I am still extracing lol
19:11:12 <rtprio> there are a lot of files
19:11:36 <levitating> yes and I am emulating risc64
19:12:15 <levitating> no hardware virtualization
19:12:31 <levitating> or kvm
19:15:14 <levitating> okay we appeared to have hit some bugs
19:15:22 <rtprio> i have no doubts
19:15:25 <rtprio> why are you doing this?
19:15:39 <levitating> curiosity and free time
19:15:59 <levitating> anyway the kernel complained the filesystem got full
19:16:09 <levitating> even though the qcow2 overlay should grow
19:17:17 <rtprio> I stopped using qemu when a number of better alternatives came along.
19:18:25 <levitating> like?
19:19:37 <rtprio> i use hyperv and bhyve
19:20:01 <levitating> I don't use windows
19:20:18 <rtprio> kvm wasn't bad
19:23:03 <levitating> what's even up with having a backwards compatible pkg tool
19:26:39 <rtprio> what do you mean
19:27:32 <levitating> To avoid backwards incompatibility issues, the actual pkg(8) tool is not installed in the base system.  The first time invoked, pkg will bootstrap the real pkg(8) from a remote repository.
19:29:00 <rtprio> yeah, but that doesn't do you any good without risc64 packages
19:29:13 <rtprio> because it's tier 3 or 4
19:30:21 <levitating> It's supposed to be Tier 2
19:30:41 <levitating> https://www.freebsd.org/platforms/#_supported_platforms
19:30:42 <VimDiesel> Title: Platforms | The FreeBSD Project
20:25:23 <yourfate> hey, I'm using wireguard vpn a lot, but now I disabled the VPN and the machien can't resolve DNS anymore. There is a weird server in my resolv.conf which I can't ping
20:25:36 <yourfate> what software usually changes / maintains, resolv.conf?
20:25:41 <yourfate> or should I just set a dns server there?
20:26:41 <yourfate> I have `ifconfig_DEFAULT="DHCP"` in /etc/rc.conf
20:27:02 <yourfate> so I'd assume it would get the defualt DNS server from the dhcp server?
20:28:03 <vstemen> Yes, it does, and it modifies your /etc/resolv.conf.  It is possible that wireguard can also change it but I have no experience with wireguard yet.
20:28:21 <yourfate> can I tell dhcclient to just try and get it again?
20:29:20 <vstemen> yourfate, Probably.  You might try "service dhclient restart"
20:29:44 <yourfate> that says `/etc/rc.d/dhclient: ERROR: /etc/rc.d/dhclient: no interface specified`
20:30:27 <yourfate> ah, I specify the if after the srvice restart command I guess
20:31:18 <vstemen> Yea, I forgot.  I think you do always have to specify the interface on the command line to dhclient.
20:31:40 <yourfate> hmm, it says it can't start b/c its running, but the PID it tells me doesn't exist. I guess there is some pidfile left somewhere
20:32:19 <yourfate> ah no, it tells me a wrong PID in the error lol
20:32:29 <vstemen> Try service dhclient stop.
20:32:29 <vstemen> then you might try /etc/rc.d/dhclint <ifname> start
20:32:36 <yourfate> I tried that start
20:32:38 <yourfate> stop
20:32:46 <yourfate> it said stopping
20:32:48 <yourfate> waiting for pid
20:32:53 <yourfate> then can't start, already running
20:33:01 <yourfate> I had to find the pid using ps, and kill it
20:33:04 <yourfate> then I could start it again
20:33:30 <vstemen> hmm.  I guess it didn't have the correct PID in the /var/run pid file.
20:33:42 <yourfate> hmm, now it runs again, but it didn't fix the resolv.conf
20:34:36 <vstemen> yourfate, strange.  Maybe try renaming resolv.conf and see if it will re-create it.
20:35:33 <yourfate> nope, restarting it does not create a resolv.conf
20:37:48 <vstemen> yourfate, Sorry, I don't have any other ideas off the top of my head.
20:38:03 <yourfate> I'm googling, it seems dhclient itself doesn't maintain the resolv.conf
20:38:24 <yourfate> its maintainged by `resolvconf`
20:38:30 <yourfate> https://man.freebsd.org/cgi/man.cgi?query=resolvconf&sektion=8&apropos=0&manpath=FreeBSD+14.0-RELEASE+and+Ports
20:38:31 <VimDiesel> Title: resolvconf(8)
20:39:37 <vstemen> My machines always seem to setup resolv.conf when I use DHCP on them.  Perhaps dhclient calls on resolvconf, but I don't know why yours would not.
20:44:24 <yourfate> lets try something else: reboot :D
21:15:54 <levitating> adding jobs to make with -j causes some stuff to fail?
21:16:04 <levitating> trying to make a port
21:52:31 <vstemen> yourfate, yea, last resort, like reading the manual :-)
21:52:34 <V_PauAmma_V> Sometimes it can. For elaboration, see #freebsd-ports.
22:40:35 <levitating> are there any desktop environments with wayland support ported?
23:14:37 <SponiX> levitating: Gnome and KDE Plasma