00:00:54 acu, virtualmin appears to be available for FreeBSD as well (in the sysutils category). 00:02:57 V_PauAmma_V: i think we're getting in the way of a good rant 00:04:59 We are? OK. 00:09:31 i dunno--was just trying to be uh 00:09:32 comical 04:00:50 I think FreeBSD continues to be successful because it avoids fashions, like AI. FreeBSD is already credible and sustainable. 04:01:22 *squint* 04:52:12 any mikrotik routeros experts around? 04:52:17 deimosBSD: I highly agree with your opinion 04:52:29 kerneldove: ask, you will receive. 04:52:48 well i don't just have 1 question i need more of a convo 04:53:00 and it's off-topic so i wouldn't wanna spam up the chan 04:53:22 deimosBSD: one of the reasons why I chose fbsd is because it's less popular. i am kind of sorry to say that debian is full of strange people like today's wikipedia 04:53:36 kerneldove: no worry man. i am no expert but welcome all comments. 04:53:45 mind if i pm you? 04:53:50 not at all 04:53:54 tyvm 05:02:42 black, what do you mean by «strange people» 05:03:52 AmyMalik: obscure entities pushing for changes that are strange 05:04:39 but i have to admit that debian is a very good community effort 05:05:08 the purest OS out there more so than Ubuntu and others. however the thing I talked about is a very recent discovery. 05:09:54 there is a certain "hatred" that I feel is amongst certain free software people 05:10:41 proprietary software is fine but there is no reason to prefer to better camp for the hatred of the opponent 05:41:45 black, could you join #freebsd-social and elaborate further? 05:42:17 i am there 05:42:36 sure if you interested 09:51:36 actually that cu/tip/sc bug is cursed one 09:52:13 who would think that consoles or terminals fail 09:52:27 it has to be devices or interfaces 09:52:47 like "it wasn't dns" :p 09:56:53 and within manpage of cu, nothing tells me it's somehow outdated util, even single usage example used usb serials 11:18:24 hello 11:18:47 where can I download packages manually? I used to be able to browse this fairly easily, now I can't find the pkg repos 11:18:51 I need to download wifi drivers 11:20:35 I keep getting 403 forbidden.. 11:20:45 https://pkg.freebsd.org/FreeBSD:14:amd64/kmods_latest_3/All/ 11:20:54 I think would typically list all the packages? 12:22:15 Gud: no, repos have not listed package files for quite a while now in my experience 13:07:05 Gud, in addition to what Remilia said, I'd first use "pkg search" to find the relevant package name(s), then either "pkg install" or "pkg fetch" depending on what you mean by "download". 13:13:46 V_PauAmma_V: I think the machine that needs the drivers has no network connection and the machine that does is not running freebsd 13:24:36 That could be. 13:29:39 ISTR reading that -dvd1 install images (and maybe others) include wifi driver packages these days. If I'm not mistaken, that may be a way around. 14:28:11 V_PauAmma_V: the problem is I don't have networking on that computer 14:28:23 because missing wifi drivers 14:28:33 anyway, sucks I can't browse the packages like how I always could 17:33:42 Quick question, does anyone know of any usb-c wifi dongles that are known to work with wpa(2/3) enterprise with EAP-TLS? (by work I mean not only hardware support but support in freebsd kernel, preferably without having to install separate packages or at very least only things from ports tree) 17:40:02 TIL: cp /long/path/to/file{,.orig} 18:49:21 nxjoseph: With the right shell, yep. Handy stuff. 18:49:52 ek: yes, i use tcsh, tried in sh which is the default, but i use tcsh afterwards 18:49:58 it didn't work in sh 18:50:56 Yeah. sh is pretty limited. 18:51:17 even in it's name, its 2 characters :D 18:51:44 jk, i like tcsh more 18:52:09 i even use it in my scripts (even though it isn't recommended) to learn it more 18:52:56 That's fair. I don't mind (t)csh as a shell. I like the history search defaults and such. But, I always script in sh just to keep it as compatible as possible. 18:53:11 If it's my choice, I use zsh for the shell. Best of all worlds. 18:53:17 i see, yes i like the history defaults too. 18:53:36 i try to avoid bash/zfs/fish for some reason 18:54:28 To each their own. Choices are nice to have. :) 18:54:39 indeed 18:55:06 zsh's first login setup was interesting, didn't go further than that 19:03:57 i was disconnected somehow, did you wrote something? 19:24:11 No one said anything after you did. 19:24:22 ok, ty. 19:32:32 We waited for you to come back 19:32:41 oh, very kind, thanks :) 19:33:39 Haha. 21:05:02 nxjoseph is a good kid, don't bash him 21:05:20 buggers 21:18:01 I'm bad adult 21:19:24 I fully embraced bashism 21:28:01 flatdog: No one was bashing anyone. 22:16:06 I really need to free up some time to become involved in the ports. Because every time I do a pkg upgrade it says stupid things like "You may need to manually remove /usr/local/etc/postfix/main.cf if it is no longer needed." which I find annoying. It always scares me into thinking it has removed the package instead of upgrading it. 22:18:10 rwp: Well, technically, it did remove the package. It just also replaced it with a new one. 22:21:17 It's a useless message that I always have to re-train myself to ignore. Which is a bad thing. 22:22:39 Well, I don't think that has to do with ports directly. It definitely is the way pkg handles things, though. 22:24:23 Only some ports have this problem. Which is why I thought it was a ports problem rather than a pkg problem. But I don't know. As I said I should free up some time to dig into it. 22:32:16 Well, in ports you get the same messages on a deinstall. pkg just prints the deinstall messages as well as the install messages.