00:00:04 i still wish firefox had the damn onenote clipper plugin 00:00:04 errr 00:00:12 but it is /sbin/mount_msdosfs 00:01:07 what is? 00:01:23 mount -tmsdos goes to mount_msdosfs? 00:02:01 at least now i can get back to my manual pages work effort.. after this slight detour 00:02:58 manual page of mount_msdosfs says in HISTORY: “mount_msdos was renamed to the more aptly-named mount_msdosfs in FreeBSD 5.0.” 00:04:05 voy4g3r2: To tell you the truth, lately I just use the normal installer. But I think it's useful to see the moving parts. 00:04:27 So I'll keep the thing up to date generally. 00:08:32 this was great for the use of cloning a drive too 00:08:46 which was my use case.. and learned do NOT do a dd on a zfs partition.. that is no bueno 02:50:54 Hi all. if freebsd's onboard IKEv2 VPN racoon? 02:51:03 Is there any benefit to it over strongswan? 02:58:59 Wife just caught me on https://man.freebsd.org/cgi/man.cgi?ftp(3) and thought it was BDSM pr0n 02:59:00 Title: ftp(3) 03:03:12 SamuelMarks: Tell her no, just daemons. 03:07:00 😈 09:21:24 on FreeBSD UNIX 14 I have a mouse pointer showing on the console/terminal that isn't movable, so how do I either get rid of it or turn it into a one-character bright rectangle like it maybe should look on command-line? 09:33:33 darwin: Sounds like you enabled `moused` during the installation. So just do `service moused stop`, and remove it from `/etc/rc.conf`. 09:34:37 I don't really understand what the point of it is, but it's there. 09:34:42 I guess. 09:48:35 thanks 09:49:28 i used it in the past but guess it doesn't work with that trackpad... and always was too hard to copy & paste with moused more than gpm 10:18:09 Yeah, I fell for the same problem when I installed my first few FreeBSD servers, but I figured it's an option you can set during the installation a few installations later. 13:36:43 HELO 13:37:08 What is the correct way to mount a USB flash drive now on FreeBSD? 13:37:37 I have just installed it as of two days ago and have not seen FreebSD for many years 13:37:43 I love it laready 13:37:50 *already 13:38:00 You can just mount it with: mount /dev/ /mnt 13:38:08 ok 13:38:17 What device would I be looking for? 13:38:32 usb? 13:39:06 cd usb 13:39:10 oops 13:40:54 welcome: gpart show shows all the devices and names for the names. Then you can use something like mount /dev/da0p1 /mnt 13:41:19 thankyou very much 13:41:21 replace the da0p1 whith what your device identifier is 13:41:30 yes, ok 13:42:35 lw 14:51:24 jbo: hi 14:55:22 lw, did you get the e-mail? 14:55:45 about wine? yes, ty 14:56:01 ack 14:56:51 lw, another example of showing that maintainers are supposed to do lots of work :p 15:15:24 jbo: i was already think about that stuff when i made the request, i just think it's better for a port to have *a* maintainer than none 15:15:47 lw, only if that maintainer is actually being a maintainer. otherwise I not really :) 15:15:56 lw, so, you're going for it? :) 15:19:35 it might make more to look for someone who wants to maintain both wine and wine-devel 15:20:06 why not you? 15:21:11 emulators/wine is a much more important and widely used package, i don't know if i want that much responsibility (or would have the time for it at least right now) 15:21:35 I assume if you can handle wine-devel (on the technical side) you can also handle wine? :) 15:24:23 emulators/wine is out of date anyway, maybe i'll start by updating that 15:24:36 that would be very appreciated 15:25:54 one problem with wine is new updates sometimes break existing software, which doesn't really matter for wine-devel, but i wonder if it makes sense to keep the existing port as emulators/wine80 15:26:08 and/or add the new one as emulators/wine90 and have a knob to select the version 15:49:12 that is a common discussion, yeah. 15:49:23 I'd recommend going with wine9 instead of wine90 tho 16:06:42 Errr.. help? I have two FreeBSD systems that are the same HW configuration-wise. Rebooted both. One came up fine, the other one failed to find my main ZFS data zpool. I tried some stuff, but noticed that I see the /dev/nvd devices and /dev/nvme devices, but not the partitions. `smartctl -a` identifies them and they look sane. Trying to `dd` data from the /dev/nvd fails. 16:07:19 pgib: do the disks show up in 'camcontrol devlist' and does 'zpool import' show any pools? 16:08:18 So I rebooted again and watched the console. I am getting a ton of "UNRECOVERED READ ERROR" across all of those drives. But a failure of the whole PCIe/NVMe hardware seems unlikely to me and it was reading and writing just fine prior to the reboot. 16:09:37 bad/loose cable (if they're not an M.2 slot)? although odd that a reboot would trigger that 16:10:22 can you show the entire text of one of the read errors? 16:11:16 They do not show in `camcontrol devlist`, but they also do not show in the functioning system. They are 10 U.2 drives. The nvd and nvme devfiles show, smartctl identifies the device, `nvmecontrol devlist` lists them. 16:16:04 lw, thanks for the help so far. Here are the boot time errors from /var/log/messages: https://bpa.st/TCNA 16:16:05 Title: View paste TCNA 16:18:53 pgib: unfortunately that's probably as much as i can help, i was hoping the read error might be more informative 16:46:21 Sheesh all 10 of these drives have errors according to smartctl. How would they all fail simultaneously? It can't be a "controller" right, as each drive is basically its own PCIe "controller"? 19:25:00 I feel silly suggesting this, but can you try cold power off, unplug for a minute, and then try again? 19:32:17 are the U.2 ports mounted on the motherboard? i have had PCI-X backplanes fail before, so i assume the same could happen to PCIe, although that wouldn't be my first assumption 19:51:13 I don't recall. It is a backplane of some sort at least. Both servers are Cisco UCS C225 M6. For funsies, I did an nvme reformat on one drive with `nvmecontrol /dev/nvme0`, and the drive is responsive again (albeit with no data on it unless you really like zeroes) 19:54:04 The drive was previously formatted with IDEMA LBA mode 3 (which is 4096B sectors with T10-PI protection). I'm trying mode 1 this time around (plain 4096B sectors) and will see what that yields. I doubt that is the problem though - isn't all that stuff handled on the drive itself? 19:57:52 is the disk firmware up to date? 20:05:58 Don't know. Would have to put them in a windows system or something to run the utils I think 20:07:40 you could probably pass them through to a bhyve vm temporarily 23:52:34 jbo: i realised what's going on with not being able to mail gerald@, it's because freebsd.org's mailer doesn't rewrite sender addresses for spf. i might ask postmaster@ about that... 23:53:49 lw i love freebsd lol 23:53:56 i feel pc runs smoother and faster 23:54:00 than linux 23:58:06 warsoul: did you fix your problem with hexchat? 23:58:15 yep 23:58:31 what irc client you use? 23:59:51 ircII-EPIC (irc/epic5 in ports) 23:59:56 lw heh