03:20:32 kevans: no no, why would you have 13,14,15 kernels with the same rootfs 03:26:32 rtprio: oh, well, good reasons for that sometimes, too. :-) admittedly, the last time I had to it was rerally just bisecting for a kernel bug over a few releases 03:26:41 much easier to just pin userland down low 08:32:01 there is something really weird with jails and IPv6, few weeks ago I spent all night debugging it to find out that when I reloaded the firewall it just worked randomly, now with the same firewall and haven't touched it since, IPv6 now randomly stops workign 08:32:04 * polarian sighs 08:38:39 ndp is working, LLA are working, firewall is passing quick on icmpv6 as the first rule 08:39:31 the *only* thing I can think it could be is the fact I chopped up a /64 into smaller blocks which is not technically standard 08:39:37 but has never caused me issues in the past on other platforms 08:42:52 only SLAAC should stop working if you make a smaller subnet then a /64, if you assign addresses in another way, then any subnet size should be fine 08:43:32 yeah thats what I thought 08:43:42 and no SLAAC isn't used, just chopping up /64 into smaller blocks for lots of jails :) 08:43:55 but something is clearly broken, I think it might be OpenBSD which is the issue (running on the router) 08:44:29 its not responding to NDP for one of the other devices, I can see there is NDP being broadcasting asking who is holding the LLA of the router, and never getting a reply 08:45:38 maybe its address conflict... 08:45:55 but I doubt it 08:46:49 another OpenBSD host keeps spamming the broadcast with NDP, despite the fact that the OpenBSD router can actually ping it, so I am going to take out the other OpenBSD host on the vlan and maybe that might be the problem 08:51:03 this is what happens when you try to use an entirely BSD stack I guess :p 08:51:17 or maybe im just too stupid to do it properly who knows :p 08:56:18 what the fuck: https://bpa.st/Y23Q 08:56:24 this was literally working a few weeks ago 09:03:02 oh wait, the host ndp cant see the address 09:04:03 I figured out the problem :p 09:04:34 iirc to route packets you cant have the same subnet on different interfaces 09:04:46 wait no 09:05:01 it's anycast 09:05:15 what I assumed the problem was is that I am routing packets over LLA but LLA doesnt care about anything else 09:06:11 the inet6 2001:8b0:57a:2391::1:4 prefixlen 128 09:06:14 routed over LLA 09:06:20 afaik this *should* work 09:06:48 but the host is unable to find the address 09:07:02 LLA - like link-local address ? 09:07:06 although its also weird that the host is retrasmitting the packet 50 times until TTL is exceeded and *then* dropping the packet 09:07:08 mzar: yes 09:07:22 LLA communication works fine :) 09:07:39 do you have any ip6 firewall ? 09:07:50 in fact the packet is routed both on the host, and the router as you get the response from google which is what im pinging to test, but the response is then dropped on the host as it cant see the address 09:08:00 mzar: I am passing quick icmpv6 09:08:04 do all icmp6 pass ? 09:08:05 pl 09:08:06 also this is not a firewall issue 09:08:06 ok 09:08:14 as I said 09:08:17 ndp cant see the address 09:08:34 which means there needs to be a route 09:08:38 have an efficient troubleshooting polarian, good luck ! 09:08:40 bbl 09:08:52 I think I just rubberducked this by spamming the channel :p 09:08:59 I bet there is no route and thats why 09:09:30 2001:8b0:57a:2391::1:4 link#6 UHS lo0 09:09:45 oh there is a route, but its loopback, and that explains why the packet is being looped 50 times until dropped due to ttl- 09:10:19 oh shit no thats on the container whoops mixed up the terminals :p 09:12:31 okay this is a routing table issue. 09:12:55 Question I asked a while back though, how do I specify multiple ifconfig commands in rc.conf, I cant seem to assign an IPv6 address AND set a static local link to say fe80::2 09:13:07 fe80::2/64 09:13:15 netif complains its an invalid format 09:13:41 if I use the same ifconfig_ string, and you cant set two of them, it will just execute the last one and ignore the one before it 11:54:39 any recommendations for kvm-over-ip hardware (either dongle or appliance) with solid edid and usb emulation, bios control, and virtual media? 11:57:49 also 2560x1440 rez 12:32:03 kvm-over-ip with 2560x1440 rez ? 12:32:59 promising setup 12:36:04 what do you mean by promising? 12:36:18 i found GL.iNet Comet Pro 12:36:26 has that feature and pretty decent price 12:58:52 mzar 13:05:06 ok 13:05:16 cool great contribution 13:05:35 i guess your job around here is to just dump on ideas then get proven wrong immediately after? 13:06:13 I am not against new ideas 13:07:34 still lagged behind, though 13:08:38 ok 14:14:41 tryin to update jails with bastille. 14:14:53 https://bastille.readthedocs.io/en/latest/chapters/upgrading.html#id4 14:15:10 yet after the steps the jail is still the old release in `bastille list` 14:15:33 and bastille upgrade says the jail is already running the new release 14:17:43 and also packages within the jail are still at 15.0, not 15.1 14:19:59 its just text, you can update what it says in myJail/jail.conf or via bastille edit myJail 14:20:39 osrelease = 15.1-RELEASE; it alrady seems to have the correct value 14:21:50 what it says when you exec in the jail and run freebsd-version is a better indicator 14:23:17 -r is 15.1 (correct) -u is still 15.0 14:23:41 -k is unable to locate kernel (don't know what that's supposed to read) 14:26:12 did i botch the release? 14:26:57 Attempting to update release: 15.1-RELEASE 14:26:58 pkg: Setting ABI requires setting OSVERSION, guessing the OSVERSION as: 1500000 14:27:53 -r asks the running kernel for its version and as a jail doesn't have its own kernel, it probably results in reporting the version of the host, -k tries to read the version from the kernel on the filesystem, but as a jail doesn't have its own kernel, you probably don't have a kernel installed inside the jail 14:28:02 this sounds weird, that should be 1501 something 14:28:43 i don't care about the kernel as much? 14:28:56 but the "bastille upgrade TARGET 15.2-RELEASE" 14:29:00 start the jail 14:29:08 in the instructions didn't actually do the thing 14:50:15 it still mounts to the old thin release 15:03:19 oh maybe it's because etcupdate doesn't work 15:05:15 There's a bug in bastille. I ran into it as well. It's on their tracker. 15:05:37 https://github.com/BastilleBSD/bastille/issues/1560 15:05:55 so if i update the link in /usr/local/bastille/jails/myjail/fstab will that fix it 15:06:06 Aye, that's all you need. 15:06:57 You might also need to edit the jail.conf as well, if it doesn't show the new release. I needed to do that for one or two jails. 15:07:26 oh, they all were showing the new release 15:07:36 Yeah, it was the same for me. 15:07:52 Just the mount in the fstab was wrong for most of them. 15:10:36 yay, that was it 15:12:34 You're welcome. 15:13:04 i'm finding the bastille commandline rather tedious 15:13:56 i get the concepts but he seemed to overload operators in a nonintuitive way 15:20:59 boru / sbr: should pkg be able to 'see' the freebsd-base repo / try to install packages within the jail 15:21:07 or are those hidden as they're part of the jail 17:59:08 hello people 18:04:32 I'm trying to install freebsd on a laptop using the mini-memstick image, I can get to the menu but when I boot, no matter which option I choose, the menu is still there, and the booting/installation screen is appearing very tiny at the top of the screen, repeated 20 times (so I assume it's something like 80x45 pixels). It's so tiny it's unreadable and I can't use it. Has anyone exprienced 18:04:34 something similar ? Thinkpad T520 using HD graphics 18:28:21 http://www.rhizogen.es.eu.org/~ac/bugs/P6270142_shrinked.jpg 18:58:40 I've ended up in charge of a small FreeBSD installation due to the person in charge entering permanent retirement with bad timing. 18:59:57 I presently suspect most executables were being handled via `freebsd-update` while ports were being done via `portmaster` and `gitup`. 19:02:47 what is the output of `history` as root 19:04:13 Fairly long and several invocations of `portmaster -BDg `. 19:04:17 (you don't actually have to send it, you just have to have understood it, because root's history will tell you what the previous admin was doing if they didn't turn it off) 19:05:19 Which is why I saved a copy of .history which has had minimal modification. 19:06:24 good 19:06:59 If git.freebsd.org supports filtering, I suspect `git clone --filter=tree:0` may be preferable to `git clone --depth 1` in section 4.5.1 of the manual. 19:07:53 (alas this was someone older who disliked Git, so I'm worried about whether any packages were modified though `gitup` may handle that) 19:11:00 ah... 19:12:36 I understand the dislike of rename detection, but real world experience suggests it works quite well. 19:13:29 freebsd-update is used for updating the base system (up to the 15 series I believe) 19:14:24 I *think* it was used that way and no customization there, though a customized kernel was built. 19:17:29 ah 19:19:10 The irony is I've been playing with an uncustomized installs and using prebuilt packages, but not doing everything from source. 19:21:03 I've mostly got a plan and I think I know next steps, but I'm nervous. 19:21:29 If you know how FreeBSD generally works, you probably won't break anything too major. 19:22:48 I don't claim that, I've got a decent feel for how most OS setups go, but that means I could severely break things. 19:22:55 what are you trying to do, geometry 19:24:05 Get a package security update done, then I'm thinking about getting things move onto later release of FreeBSD (since this installation is at EoL). 19:26:13 I /think/ the package security update is minor for this installation, but I don't like those being even the slightest bit out of date. 19:26:24 gotcha. I would mainly just be concerned about the kernel. if it has any custom stuff going for hardware or whatever, then make sure to take a note of that 19:26:45 I wouldnt worry much about the pkg upgrades until I did the system upgrade 19:26:52 Looked like a slightly cut-down GENERIC. 19:27:17 I'll strip out Hyper-V since that driver is a pig. 19:27:19 freebsd-update will quite easily update you to the current 15.x branch 19:27:34 then you can handle the packages 19:27:59 Well, the fact they were using portmaster and not pkg makes the assumption that they also needed custom builds for their software. So, you might wanna take a look a the build options for the ports they were installing. 19:28:10 I'd think they would opt for packages if otherwise. 19:28:14 oh yah thats true 19:28:58 It's an easy fix, though. I'd focus on the base/kernel updates first, and the software afterwards. 19:29:15 my own inclination would be to wipe all local packages and upgrade the system. then reset whatever local packages I want and reinstall them 19:29:19 Some of it might also be history, I've got the impression portmaster predates pkg by several years. 19:29:27 You can use "pkg" to upgrade everything and just see what does and does not work. Then rebuild the ports with the custom options (if needed). 19:29:42 I'd also suggest migrating to Poudriere for the custom port builds. 19:29:59 geometry: Yes. Portmaster has been around for a VERY long time. 19:30:31 <3 portmaster 19:32:19 I think moving to prebuilts for most packages would be best, likely there is fairly little customization just the person in charge figured out portmaster when that was the only tool for the job. 19:32:45 at my installation i have dovecot customized 19:38:30 Ah ha, finally found the patches! 19:40:54 :O 19:46:25 geometry: Excellent! 19:46:32 That should make it easier. 19:46:46 Indeed. 20:04:42 nice 20:05:59 ac_laptop: that's very blurry. what is on the top line of the screen, with the blue background 20:07:09 rtprio: I assume it's the installation screen, repeated 20 times. 20:07:40 but it's too small for me to read 20:08:03 but the installer is text, and that still looks like you're in text mode; 20:08:44 if you move the arrows / press enter does it change? what about ^l ? 20:09:02 or alt-f2 to alt-f4 to see if another console comes up 20:11:00 rtprio: Alt-F3 and Alt-F4 indeed show what appears to be an other console 20:11:56 but back to alt-f1 and does it redraw iwth the installer or no 20:13:17 rtprio: yes, Alt-F1 redraws it with the installer 20:25:56 I've been given the impression shallow clones are now sort-of discouraged since filtering works better in most cases. 21:23:41 geometry, Do you have any references for that assertion that git filter is better than shallow clones? Because I don't agree. 21:23:46 Those two things do different things entirely. One is the horizontal. One is the vertical. By analogy anyway. 21:24:17 I prefer shallow. 21:24:40 Well, depending on what I'm doing with that particular ports tree. 21:25:02 ... or src tree. 21:25:12 If nothing and just building? Definitely shallow. 21:25:12 Filtering keeps you synchronized with history so you know where you are when you do updates. 21:26:26 Shallow-clone only downloads the data for a single-commit and loses history and therefore ends up with incorrect commit hashes. 21:26:52 Filtering downloads the history, but none of the files/data attached to those commits. 21:27:35 Isn't vertical versus horizontal, more filtering gets you the entire backbone whereas shallow-clone only gets you a single vertebrae. 21:29:42 Yep. 21:30:12 If I'm only pulling/cloning to build, a single, latest commit gets it done just as I need. I don't need a ton of old data. 21:30:32 Filtering or depth'ing works fine for both. 21:31:18 If I have any reason to have previous commit info, I'll pull the full depth or filter for commit info without the full data. 21:32:08 The strength is more being able to cleanly update to a later revision. 21:33:19 Sure. I just generally need commit hashes for a single thing. So, commit hash history is important on dev systems. On non-dev systems, I just need the base --depth=1. 21:34:15 Like, I'll pull an old commit for a single port. I very rarely need to pull an entire, old ports tree. 21:34:22 But, it has happened! 21:40:18 If someone is just cloning to build something then it should be a shallow clone to avoid the long history and bandwidth consumed by it. If someone is filtering then they will get all of that and will not have the files needed to do a build. 21:41:35 In the end it depends upon what you need and what task you are doing. But I would not say that filtering is preferred over shallow clones. Or people will set up CI/CD services using filtering and that will wasteful of bandwidth and server resources. 22:39:14 ^ Is this about Git? 22:40:01 (now with mandatory depency on Rust) 22:42:04 the corrosion is spreading?????? 22:42:10 kill me now 22:44:43 whatever happened to rust-in-base in regards to fbsd? 22:53:44 Anytime anyone wants to move to fossil then I am supportive. Just say'n! :-) 22:56:40 ... isn't that written by christian fundamentalists? 22:59:01 Did we somehow skip to talking about the King James bible when I wasn't looking? 22:59:59 SQLite has some fanciful comments in the code base that has caused this strange meme but let's say it is true. Does it matter? 23:00:31 No it doesn't matter. 23:04:54 Christians are good peeps 23:06:57 Nearly every religious text is good moral principles. 23:07:38 Then everyone spends centuries or millenia arguing and killing each other about what *exactly* was meant. 23:07:45 I don't judge software based on the beliefs of its creator(s). I judge it on its merits and design. I don't care about the politics of it. I might disagree with them. I might dislike them. But I'll still use it. 23:12:16 I have heard this before that because there are fanciful comments in the code "the blessed artifacts" and other such stylized language that this means something other than bored programmers trying to have fun with it. I mean the language is called "fossil" for goodness sakes! That by itself should lead people to think it is the other direction. 23:12:43 i have verses of the quran in my test suites. 23:14:21 this conversation reminds me of the movie "Pi" .. 23:14:43 I saw a report years ago that Lewis Carroll's books about Alice were the most quoted in code comments. This gives me hope when I read an AI generated something with quotes from Holy Grail. 23:14:56 Then he would have verses of the talmud if it was Pi 23:15:07 Great movie btw 23:17:00 mason, I never figured out what caused freebsd-update to not add the new file sshd-auth (maybe because I had modified the sshd_config?) so in the end I created a new empty Boot Environment, installed a fresh pristine 15.1-RELEASE there, installed the configuration, activated it, booted it, and voila it is upgraded. I might just do that for upgrades from here on forward. It was simple. 23:18:17 The use and coding of computers are esoteric... Look at old games like World Of Warcraft, there was biblical and kabbalistic stuff woven through the stories 23:18:32 Loads of symbolism everywhere 23:18:49 Why do you think there's a bite out of the apple on the Macintosh? 23:19:32 /\ 23:19:43 / o \ 23:19:55 / \ 23:20:27 Freemason btw, tubal cain apprentices 23:21:06 because apples are tasty 23:21:30 Keeps doctors away? 23:21:41 Adam and Eve 23:22:10 Forbidden fruit 23:40:24 objectivist: Based on Jobs' biography, I don't think that is accurate. 23:41:59 But we may also be leaning a bit #freebsd-social at this point. 23:42:22 objectivist: that kinda thinking is not unique or interesting, go to any in-patient mental health clinic and thats all you'll hear, or variations of it, maybe your version is a bit more coherent. its not a healthy way to think. i cant avoid thinking this way, but wouldnt recommend it.