01:22:10 <white-wolf> Salut
01:23:42 <white-wolf> Comment je définis mon code pin dans une session ppp ?
01:29:06 <white-wolf> hi
01:30:33 <white-wolf> How can I specifying my pin code on lte 4G card ?
01:34:22 <white-wolf> Oh 3h33 all sleeping
05:32:20 <grahamperrin> rwp: output from geom -t is OK, but is far from the at-a-glance overview that I sometimes/often want.
05:32:27 * grahamperrin wishes for lsblk in base
05:34:19 <rwp> To my eyes it is more useful than the ports version of lsblk.  The Linux version of lsblk -f though is better.
05:35:59 <Koston> uh.. FreeBSD doesn't *have* block devices
05:36:12 <Koston> hasn't had since the 90s
05:36:17 <rwp> My status on that project is that I need two more disks to arrive before I can try assembling all on the replacement disks.  Delivery slipped a day too.  Maybe Wednesday delivery now. (shrug)
05:38:33 <grahamperrin> hjf: IIRC vboxdrv.ko built on 13.1 _did_ load on 13.2-RELEASE. I see that it does not load on 13.2-RELEASE-p1.
05:45:08 <BraveheartBSD> Anyone good with zfs? I'm currently in #zfs, but it's pretty quiet in there
05:46:49 <Koston> BraveheartBSD: try 'ZFS' and 'Advanced ZFS' books from the FreeBSD Mastery series
05:59:33 <rwp> BraveheartBSD, If you have a question it is best just to ask it and if someone knows something they will respond.
06:01:58 <BraveheartBSD> I'm getting an All Block Copies Unavailable: unable to read MOS on zroot pool. The system then boots normally.
06:03:03 <BraveheartBSD> Freebsd is installed on a 250gb ssd, with a seperate 20tb data pool
06:18:29 <Koston> BraveheartBSD: do you have any idea what changes have been made between last boot without the problem and first boot with it?
06:21:09 <BraveheartBSD> No. The server was running Ubuntu server, which failed. New install on the same ssd, data pool imported with no issues. zpool status shows no errors on boot drive or data pool.
06:21:48 <Koston> can you elaborate on the ubuntu failure?
06:22:04 <Koston> specifically, could there be a lurking hardware failure
06:23:34 <BraveheartBSD> Ubuntu updated, I then had a txg_sync error which resulted in zpool being stalled.
06:26:28 <Koston> have you tried pursuing the problem as a hardware failure?
06:26:54 <kenrap> Hey folks, sorry if this is a stupid question, I'm looking for confirmation to this assumption I have. I decided to ride on the 14-CURRENT wave and I was wondering by the time the devs create the stable/14 branch, can I then switch to that branch and roll from there without issues?
06:28:21 <BraveheartBSD> The server is old, it a Dell T610. The controller card is a Perc H700 which is not a happy thing to use with ZFS, I'm waiting delivery on a new HBA card.
06:28:32 <Koston> kenrap: STABLE is the development branch based on RELEASE, not CURRENT. so, no, that's not going to work.
06:29:18 <Koston> BraveheartBSD: is this one of the cards that don't have raw device passthrough and you're forced to use hardware RAID on top?
06:30:23 <BraveheartBSD> Koston: yes. It's why I've sourced a new HBA that does IT mode
06:32:15 <Koston> I suggest not spending any more time on it before you can present ZFS with physical devices. FWIW, you might check https://fohdeesha.com/docs/perc.html if your adapter firmware can be "downgraded" to plain LSI (which it probably is)
06:32:16 <VimDiesel> Title: Introduction - Fohdeesha Docs
06:34:28 <Koston> I recently did this for two PERC H710P Minis and at least FreeBSD on ZFS installed fine
06:36:42 <BraveheartBSD> H700 can't be flashed, unfortunately. It truly is a dinosaur
06:38:57 <Koston> then just wait for the new HBA, you'll have to reinstall everything from scratch anyway
06:40:27 <BraveheartBSD> Yup. FreeBSD handles this card/drive array better than Ubuntu, but it's still the weak point with ZFS.
06:40:44 <Koston> it's the weak point with your hardware, not ZFS
06:41:46 <Koston> one of the major benefits of ZFS is precisely not being married to a particular brand and model hardware to access your data
06:41:52 <BraveheartBSD> Exactly
06:43:05 <BraveheartBSD> It's an old server i'm using as a samba share with Windows 11, still learning.
06:45:37 <Koston> if you want to learn a lot about ZFS, I'd reiterate my earlier book recommendation. learning Samba is a lot bigger hurdle, imho
08:57:21 <cpet> Freedom!!!
13:00:32 <kenrap> huh, the new rewritten mixer(8) utility in CURRENT made manually switching to my uaudio device actually work when using the `-d` switch, very neat. Fighting with sysctl (and with pulseaudio because KDE) was not a fun experience.
16:06:23 <CrtxReavr> Something's wrong when #freebsd-irc is more active than this one.
16:07:09 <CrtxReavr> Maybe requiring nick registration to be in here should be reconsidered.
16:08:08 <CrtxReavr> TIL that newer versions of Gnu man(1) support a "feature" that lets you use "man crontab.5" in place of the original "man 5 crontab" syntax for specifing manpage sections.
16:13:58 <CmdLnKid> i think you could attribute that to the unknowledge search engine users thinking that irc and freebsd are one.
16:14:35 <debdrup> Nah, it's more that nobody's telling people to move to #FreeBSD.
16:14:59 <CmdLnKid> there is always many factors
16:15:13 <cpet> So let's make someone register for a nick to join a channel to ask why x11 fails to load up
16:15:18 <cpet> Genius !!
16:15:22 <CmdLnKid> its usally the first thing that someone finds that they go for.
16:17:17 <CmdLnKid> freebsd-irc should most likely be forwarded here. but freebsd.org historically has not supported irc as a medium
16:17:50 <debdrup> The only officially supported communication medium we have is mailing lists, and there's several good reasons for that.
16:18:03 <CmdLnKid> think it may be the opposite now with the knowledge that its not officially supported as a support channel
16:18:13 <CrtxReavr> Soemtimes you want/need something closer to realtime support.
16:18:16 <debdrup> Some of them are properties that IRC share, but others are basically only found on mail.
16:18:40 <CrtxReavr> Or, sometimes you just wanna hang out with people interested in the same thing.
16:18:44 <debdrup> CrtxReavr: For support, sure.
16:19:02 <CmdLnKid> send me mail about freebsd im not supporting it... now email is a diff story
16:19:52 <CmdLnKid> my mail box is officially solicited
16:20:16 <CmdLnKid> and goes into recycleable bags
16:20:21 <debdrup> I'm not saying IRC isn't good (I've been on it since 1992, so that'd be a tiny bit weird if I did..), just that mailing lists and email are the only project-supported communication forms for reasons.
16:20:27 <debdrup> s/are/is/
16:20:49 <CmdLnKid> 96 myself
16:21:15 <cpet> It's 2023 ML had there place stopped using them years ago the only one I still actively use is the OpenBsd mai ly because watching theo curse someone off is hilarious
16:21:35 <nerozero> Hello, A short story. I had an issue with manageable switch at my work, which routes couple vlans.
16:21:37 <debdrup> CmdLnKid: milter/sieve and multiple mailboxes/addresses with a catch-all are the way to go.
16:21:38 <CrtxReavr> Discord seems to be taking over the role of IRC.
16:21:40 <CmdLnKid> lol
16:22:06 <cpet> Discord has a nice web client
16:22:07 <debdrup> CrtxReavr: doubtful, in the long run. I can't count the number of realtime communication systems that've come and gone, and IRC is still here.
16:22:10 <CmdLnKid> not talking about email with that. physical "mail"
16:22:13 <debdrup> cpet: disagree hard.
16:22:23 <CmdLnKid> lets not get distracted
16:22:27 <nerozero> Discord is evil
16:22:29 <debdrup> CmdLnKid: ah, right. Snailmail isn't really a thing in my world.
16:22:43 <CrtxReavr> debdrup, the internet will never catch on.  It's a fad!
16:22:46 <cpet> Uh well
16:22:46 <debdrup> I'm neutral torwards discord, but I don't expect it to be The Next Best thing that some people seem to be predicting.
16:22:50 <CmdLnKid> we shouldn't ever consider "email" ... mail
16:23:11 <nerozero> KISS - Keep It Simple, Stupid
16:23:20 <CmdLnKid> postal services deserve as much respect as email
16:23:25 <CrtxReavr> debdrup, have you used Discord?  Seen all the features it supports?  All the shit it does for free?
16:24:01 <aquamo4k> can you connect to discord with a cli client ?
16:24:07 <CrtxReavr> It started out "serverless voice chat for gaming" and just exploded into so much more from there.
16:24:10 <CmdLnKid> without the internet "mail will survive at minimal by horseback"
16:25:20 <debdrup> CrtxReavr: I'm on it right now (on about as many instances as I'm on different irc networks, so +30), and yes. And for free is precisely the problem; Discord will run out of VC funding eventually and either want to IPO or will start seriously going after its users to get them to pay (You think Nitro is bad now, just wait and see). Or they'll run out of VC money and cash out by selling to
16:25:26 <debdrup> Amazon/Microsoft/Alphabet.
16:25:40 <nerozero> so much offtop
16:25:54 <debdrup> aquamo4k: sort-of; it's unsupported and there's a non-zero chance it'll get your account banned.
16:26:13 <aquamo4k> good point debdrup , eventually they will want to reap benefit from all the userids and emails theyve collected.
16:26:46 <nerozero> the things are not that simple.
16:26:52 <debdrup> Nevermind the userIDs and emails, all the quite personal details they'll have from logs is worth a significant chunk of money to the right buyer.
16:27:17 <CrtxReavr> debdrup, but they're monitizing it too. . . there's lots of addon & upgraded features that businesses, software publishers, etc. are taking huge advantage of.
16:27:20 <debdrup> All it takes is one scrupulous techbro who wants money more than he wants self-respect.
16:27:25 <aquamo4k> i use it for some gaming groups but only on my windows game pc.   it's a huge window with lots of space and images all over the place ... it's a good app but not what I like to use for chatting
16:27:48 <debdrup> circuitbone: nitro ain't paying for the business of running the servers or getting enough bandwidth to host something at this scale.
16:27:51 <nerozero> we all already become cattles in comfortable stables
16:28:21 <CmdLnKid> ++
16:28:35 <CrtxReavr> aquamo4k, I too preferr mumble/murmur, overwhelmingly, the gaming world doesn't care what I want for that.
16:28:36 <debdrup> Remember, Discord isn't eventually-consistent like Twitter is (that was one of their strengths in terms of scale-out vs load).
16:29:28 <debdrup> Even if they aren't paying for the bandwidth to do the actual peer-to-peer voice/video stuff, it's still a big chunk of cash to run the infrastructure for something like Discord.
16:30:20 <debdrup> And they won't benefit from elastic infrastructure so butt solutions are just going to be more expensive in the long run.
16:30:42 <debdrup> Anyway, my dinner's finished cooking, so I'll be back in a while.
16:30:55 <CrtxReavr> I think they could with some slight re-focus in marketing, they could easily supplant, Slack, Zoom, WebEx, Et al.
16:31:06 <CmdLnKid> dinner ... wtf timezone are you in
16:31:21 <CrtxReavr> The gamers that grew-up with it enter the job market. . . and keep gaming.
16:42:32 <debdrup> CmdLnKid: Denmark.
16:42:47 <CmdLnKid> k
16:42:53 <CmdLnKid> makes sense now
16:42:55 <debdrup> :)
16:43:01 <CmdLnKid> thnkxx
16:43:10 <debdrup> What, you think I was Usanian?
16:43:30 <CmdLnKid> nah dude im in the us in WI
16:43:43 <CmdLnKid> just need a reminder sometimes
16:44:08 <CmdLnKid> not even ready for a beer yet
16:44:20 <CmdLnKid> 17:00 somewhere
16:44:35 <debdrup> It's kinda funny to me that Usanians can't do timezones outside of Usania, considering they're a Usanian invention.
16:45:31 <CmdLnKid> can't even come to comprehend that most times as business takes most of the time
16:46:01 <CmdLnKid> <- result of the us dumb market
16:47:02 <debdrup> Usania doesn't have a monopoly on dumb, though. The rest of the world is just as capable.
16:47:33 <CmdLnKid> might have to move myself
16:49:47 <CmdLnKid> e.g. out of the US
16:49:59 <CmdLnKid> shits got really stupid
16:50:49 <CmdLnKid> anyway though. back on to the freebsd subject line
16:51:41 <debdrup> Yeah, politics is probably best avoided.
17:00:41 <meena> nerozero: so what was und story with the switch?
17:01:25 <cpet> Usania ?
17:06:22 <nerozero> meena there where so many offtop, that I thought my question will drown in the messages. Thanks for reply
17:07:05 <nerozero> So,I made a quick solution to route vilans
17:07:28 <nerozero> I have a 4ethernet board pc with BSD installed
17:07:58 <cpet> vi for lans vilan
17:08:10 <nerozero> cpet, wait ...
17:08:13 <nerozero> typing
17:08:46 <nerozero> the quick solution was to connect tagged iface to one port and bridge vlan interface with specific ports
17:09:22 <meena> cpet: you can head on over to #freebsd-social for all off topic chatter. tho it is often quite quiet
17:09:24 <nerozero> everything is working, but my question, what could go wrong ?
17:10:27 <meena> How's the thru put? is it reboot safe?
17:10:46 <nerozero> yes. everything done in rc.conf
17:11:02 <nerozero> I mean, the security things ...
17:11:14 <nerozero> leaking packets ... etc .
17:11:25 <nerozero> this is a first time I did that
17:11:41 <nerozero> was thinking on the fly how to quickly address this issue
17:13:24 <cpet> What exactly is the issue or doni need to go-to #freebad-issues ?
17:14:59 <cpet> debdrup: yeah you tend to disagree a lot but think ML lost there tick
17:17:17 <CmdLnKid> cpet, you may want to lay off the phsylobins
17:17:25 <CmdLnKid> ;-)
17:17:33 <CmdLnKid> just giving you shit
17:17:49 <cpet> Thank you
17:18:39 <cpet> But please take this to #freebsd-social you may talk shit there
17:18:41 <CmdLnKid> just trying to keep it interesting
17:19:24 <CmdLnKid> gotacha. didn't ever hear about it before so thank man
17:19:28 <cpet> Also take that to #freebsd-interesting and #freebsd-physylobins
17:19:37 <CmdLnKid> lol
17:19:55 <cpet> Don't forget #freebsd-lol
17:20:22 <cpet> Let's make it like Twitter with hashtags
17:20:31 <CmdLnKid> haha
17:21:15 * CmdLnKid high fives cpet 
17:28:27 <Beladona> do I need ECC and server grade hardware to run web server + postgres on freebsd or any pc would do?
17:29:24 <CmdLnKid> no
17:29:47 <CmdLnKid> that only suppliments your monnitoring
17:30:10 <meena> Beladona: depends on how critical the data is, re ECC
17:30:19 <CmdLnKid> less than 1%
17:30:33 <CmdLnKid> just good practice
17:30:52 <meena> the only times I've heard people lose data on ZFS was without ECC RAM
17:31:45 * Beladona wonder how much extra will it cost
17:31:45 <CmdLnKid> meena, unless you can predict the replacement cycle which could ultimately cost you your bottom line
17:32:35 <Beladona> but isn't what zfs already does and no need for ECC? zfs is pretty good about avoiding corruption because it manually checksums everything multiple times along the way. Like its using your CPU to do that, but its not a big deal
17:33:45 <meena> CmdLnKid:  I'm not sure i understand that sentence
17:34:01 <CmdLnKid> ECC is your bottom line. if youve ever seen your files been written in american all the way to japanese. you probably want ecc
17:34:43 <Beladona> CmdLnKid ok but isn't that zfs thing already?
17:35:02 <CmdLnKid> intel only perspective but it can effect everything
17:35:20 <Beladona> pardon? intel what?
17:36:04 <CmdLnKid> it goes further than that but my involvement is intel centric
17:37:18 <CmdLnKid> when your ram goes bad or your cpu and your .bashrc looks like chinese ECC may be your problem
17:37:46 <CmdLnKid> not neccesarily ecc but ram in general or your cpu
17:38:32 <CmdLnKid> keep in mind ive noticed this only once on intel
17:39:05 <CmdLnKid> never minded to look further than just replacing and restoring the data
17:39:35 <meena> CmdLnKid: can you please sort your thoughts out first, then sort the words in the sentences you write to make sense to more people people than just you
17:40:09 <CmdLnKid> meena, thanks. ill take a further look at it
17:41:15 <CmdLnKid> or deeper
17:41:53 <cpet> Remember #freebsd-grammar
17:42:17 <CmdLnKid> recusing myself
17:42:32 <CmdLnKid> forgive the spelling
17:43:18 <meena> Beladona: ZFS checksumming protects data on the disk, but it can't do that in RAM
17:44:36 <cpet> CmdLnKid: meena seems to think he she is special so it's ok
17:44:45 <cpet> #freebsd-special
17:45:02 <cpet> ECC does
17:45:15 <meena> gives you one bit
17:45:47 <cpet> It should as it hogs it all
17:46:01 <CmdLnKid> i woudln't call it that. meena seems to keep me in check and i respect that much like yourself.
17:47:01 <CmdLnKid> anyway like i said earlier before i injected some bs freebsd centric stuff should reside here
17:47:40 <CmdLnKid> screw reside i mean someyhing else
17:47:58 <CmdLnKid> im out
17:48:26 <cpet> Later
17:49:08 <CmdLnKid> later guys
17:49:16 <CmdLnKid> or girls
17:54:43 <cpet> Nice save
18:03:20 <CmdLnKid> just tryinng to keep up with the times without all the bullshit
18:18:51 <cpet> Buts it's still all bullshit
18:20:04 <cpet> Should change my email and add in the pronoun of BFM
18:20:15 <cpet> But it may confuse with BDSM
18:20:50 <cpet> Hopefully current doesn't fail to build
18:21:11 <cpet> So when I get home it's just a reboot and a installworld
19:17:12 <puddinghead> Hey, I’ve been trying to build Xfce again from poudriere after reinstalling FreeBSD (this time as the only OS as opposed to a dual boot) and when poudriere tries to build rust it fails leading to poudriere e to stop
19:17:41 <puddinghead> I’ve read that it might be due to the tmpfs storage limit (I have it at 8gib), but what else could it be?
19:20:22 <costly> 8gib seems a bit tight indeed
19:20:42 <cpet> If you have no rams can't make tnpfs bigger
19:20:58 <cpet> Xfce is small don't really need tmpfs
19:21:14 <cpet> Or is that mpfs
19:21:40 <cpet> I don't know shouldn't have to create a whole build system to build custom ports
19:30:38 <puddinghead> Yeah, I have 16gb so I might as well disable tempfs then
19:30:57 <puddinghead> And it’s not xfce which is unable to be built by poudriere but rust lol
19:31:16 <puddinghead> Which xfce now pulls in as a build depeedency
19:31:36 <cpet> There's an option to use pkg for deps
19:31:44 <cpet> And builds the requested port
19:31:58 <cpet> Saves ya the time for rust
19:32:03 <puddinghead> I see
19:32:22 <puddinghead> Personally I don’t mind the compile times, though, so that means I’m best off just disabling tempfs right
19:33:23 <cpet> However you chose to do it I'm sure that doesn't require a response from here
19:33:33 <cpet> Ccache is another
19:33:56 <puddinghead> I see, that’s cool!
19:35:51 <puddinghead> I feel like making all the dependencies be downloaded from pkg isn’t for me since I’d like to have a local copy of all the packages
19:36:25 <puddinghead> I don’t remember there being any freebsd package servers in Peru and would like to host one once I am able to
19:37:46 <cpet> I get a max speed of 6mbit
19:41:57 <puddinghead> I see
19:42:18 <puddinghead> I get pretty low download speeds compared to when I used Linux but whatever
19:42:42 <cpet> Guess NYI wants it's bw back
19:42:51 <puddinghead> I c
19:43:10 <puddinghead> I personally plan to pretty much use freebsd on all my servers, especially my future home server plans so I might as well get a local pkg repository
19:46:18 <cpet> Like most people do here so yeah
19:47:05 <cpet> If you aren't customizing ports there's no point
19:52:22 <Beladona> meena I see. so ECC is a ram feature and is found in ram only?
20:00:05 <cpet> Beladona: server boards
20:00:58 <Beladona> cpet so ECC is a feature of server board/main board. not ram or both  or ram only?
20:01:23 <cpet> Read about it man
20:01:31 <Beladona> ok
20:01:35 <cpet> Hey Siri ECC ram
20:01:47 <cpet> That simple man
20:46:08 <meena> cpet: can you just tone down the condescension by like five percent?
20:55:39 <meena> Beladona: ECC RAM is a more or less standard feature of server Hardware. There are some AMD consumer motherboards that allow putting in ECC RAM, and apparently no Intel boards, because Intel wants to sell you every single feature for extra money
20:57:24 <Beladona> ya I have x570 asus tuf plus. It has ecc
21:31:23 <cpet> meena: I'll get back to you on that
21:31:35 <cpet> Probable a no though
21:52:51 <puddinghead> One hour and 35 minutes since I started building stuff
21:52:59 <puddinghead> Rust has failed building AGAIN holy shit
21:53:12 <puddinghead> Especially grating since llvm12 just built
21:58:51 <puddinghead> Nvm it was just llvm12, llvm13 failed to compile as well
22:54:55 <cpet> ok guess no logs
23:41:47 <cpet> rust builds fine here