07:43:41 * RhodiumToad wtfs
07:44:11 <RhodiumToad> so autofs/special_media works by parsing kern.conf.geomdot?
07:46:39 <RhodiumToad> kern.geom.confdot
07:49:17 <parv> .oO( That's a new-to-me MIB )
08:01:02 <meena> if we had a dot or xml parser in base
08:02:54 <RhodiumToad> I was trying to figure out why it showed me some labels but not others; it turns out it ignores glabel and uses the labels obtained via fstyp instead
08:03:32 <RhodiumToad> kern.geom.confdot is actually pretty awesome; feed it into dot and convert to svg and you get a diagram of your entire geom topology
08:04:01 <RhodiumToad> but parsing it in a shell script is a bit ... eww
08:04:17 <meena> but we don't have dot in base, yes, that
08:04:55 <RhodiumToad> right, you want the graphviz package for that
08:05:34 <meena> that the only thing that can deal with the dot format?
08:06:20 <RhodiumToad> no idea
08:07:03 <meena> if there was a lua parser that would be cool
08:07:10 <meena> extremely cool
08:23:25 <meena> I wonder how hard it would be to implement
08:23:56 <RhodiumToad> parsing in lua without lpeg is a bit of a pain
08:24:47 <RhodiumToad> I don't know anything about how easy dot is to parse
08:25:39 <paulf> probably not difficult but what are you going to do with it once parsed?
08:26:03 <meena> there's a bunch of xml parsers.
08:26:20 <meena> paulf: imagine this: doing things in not sh
08:27:04 <paulf> would rather use sh than write a graph router
20:41:56 <beladona> Hi
20:42:04 <beladona> I cannot boot. Disk got full. I rebooted. It now says  zroot got unrecoverable errors and has been suspended. What can be done here?
20:52:16 <V_PauAmma_V> Boot installation media, then choose the "live" option. That will give you a root shell in which you can enter troubleshooting commands to narrow down the cause, then (hopefully) recovery commands to fix whatever caused it.
20:53:56 <beladona> Ok.. doing
20:54:01 <rwp> beladona, Should as assume this is a single disk zfs installation?
20:54:15 <V_PauAmma_V> (Someone with more ZFS experience than me may be able to guide you through troubleshooting.)
20:54:29 <beladona> Encrypted raid. Will use geli
20:54:30 <rwp> +1 for V_PauAmma_V's suggestion to boot a live boot and then assemble it.  I had to do that myself recently.
21:14:10 <beladona> V_PauAmma_V rwp It was raid 0. How to decrypt via geli and live cd?
21:15:05 <rtprio> you would need to attach the geli volume and import the pool by hand
21:24:09 <beladona> rtprio which vol? I have 2 drives on raid 0
21:24:28 <rtprio> you'd need both, obviously. also raid0"
21:24:38 <rtprio> is probably why it failed
21:25:59 <RhodiumToad> you can use  gpart show   to list all partitions on all drives
21:27:09 <RhodiumToad> then use   geli attach daNpX   on each one that needs decrypting
21:27:40 <rtprio> if you're going to use geli you should really be comfortable with this process
21:28:39 <RhodiumToad> hm. well, the installer does offer an option to use geli encrypted zfs.
21:28:51 <RhodiumToad> so you can get to this point without knowing the geli commands
21:29:10 <rtprio> that's a news to me. but raid0... i hope there's nothing important on this system
21:32:57 <uskerine> Is there any ongoing conversation on how the fact that FreeBSD has zero capabilities in the HPC and AI area might impact its future capacity to survive?
21:33:27 <uskerine> I know it is an old fact, but this year seems that there is sort kind of turning point on that
21:33:45 <rtprio> i doubt very much if anyone cares
21:34:23 <uskerine> I am asking because I am assuming -maybe wrongly= that in this channel there will be people who really drive the path of FreeBSD
21:34:29 <uskerine> not just mere users like I am
21:34:45 <rtprio> for ai. as for HPC... how do yo ucome to the conclusion that there are 'zero capabilities'
21:35:03 <uskerine> well, the HPC is migrating to GPU computing
21:35:17 <uskerine> AI is all about DeepLearning and now LLMs, which again is GPU
21:35:26 <uskerine> NVIDIAs are not supported (for CUDA) in FreeBSD
21:35:34 <rtprio> fuck llms. next question.
21:35:41 <uskerine> so essentially anyone who would want to use FreeBSD as a platform for AI can't
21:35:56 <RhodiumToad> iirc, the lack of cuda support in freebsd is up to nvidia, who supply the driver
21:36:02 <rtprio> people here aren't going to drive nvidia to support cuda.
21:36:38 <uskerine> RhodiumToad: I think that NVIDIA has released the drivers as open source, so it would be adapting them, so I am not 100% sure that what you are describing is the case. However this seems fuzzy to me
21:37:07 <uskerine> I might be totally wrong, I am just unsure on what is missing/needed
21:37:50 <rtprio> nvidia to release working drivers. people who care enough about llms to get them working on freebsd to put some time into making them work.
21:39:36 <uskerine> https://github.com/NVIDIA/open-gpu-kernel-modules
21:39:37 <VimDiesel> Title: GitHub - NVIDIA/open-gpu-kernel-modules: NVIDIA Linux open GPU kernel module source
21:39:37 <rtprio> and freebsd will survive if regardless of it supporting ai/hpc
21:40:20 <rtprio> you can't just slap a linux driver in freebsd an expect it to work
21:40:45 <uskerine> RhodiumToad: I do not know if you are curious enough to have had a look to that github, but it seems that the "information" -for Linux- is there, so it would be a porting effort (something which obviously is not at reach of all mortals)
21:41:25 <uskerine> I know that rtprio, I was just asking if there was such discussion now, I have read in google that it has been discussed in the past
21:42:04 <RhodiumToad> video driver porting is not something I have either the time or the facilities for
21:42:30 <uskerine> I am by no means asking you to port RhodiumToad , it was a general question, not a request
21:43:06 <uskerine> petition or suggerence, why shall I do that? My contribution to FreeBSD is inexistant, I am a mere user
21:44:04 <rtprio> maybe ask in -drivers or -hackers if that open-gpu is of any use to kernel developers
21:45:03 <uskerine> well I am sure they are aware of the existence
21:45:27 <RhodiumToad> afaik, at one time someone was working on cuda support, I don't know how far it got
21:45:47 <uskerine> I guess either is a very complex task to be done by just one person or there has not been the combination of someone with the skills and the interests for having NVIDIA GPUs working
21:46:42 <uskerine> the point is that no matter how hype on LLMs there is, it is clear that DeepLearning has arrived to stay and likely grow
21:46:45 <rtprio> ask adrian about where he got in cuda: https://wiki.freebsd.org/DevSummit/201810?highlight=%28cuda%29
21:46:46 <VimDiesel> Title: DevSummit/201810 - FreeBSD Wiki
21:46:53 <markmcb> new to compiling my own ports. i noticed in a lot of people's make.conf files they have a OPTIONS_SET item, but i don't see this mentioned in make.conf(5). am i looking in the right place?
21:47:15 <RhodiumToad> markmcb: it's described in one of the ports makefiles
21:47:45 <markmcb> thanks
21:47:47 <RhodiumToad> see ports/Mk/bsd.options.mk
21:48:17 <RhodiumToad> note that some OPTIONS_* vars are only supposed to be set by the port itself, while others are only supposed to be set in make.conf
21:48:55 <markmcb> appreciate the direction, i'll check it out
21:50:23 <RhodiumToad> personally I use the cat_port_OPTIONS_[UN]SET vars exclusively to configure ports, rather than using the options dialog
21:50:59 <RhodiumToad> er, cat_port_[UN]SET= etc.
21:53:49 <RhodiumToad> I once wrote a make command line to output the cat_port_SET= settings for a list of ports, but I don't think I have it now; I lost a bunch of old irc logs to a thumb drive that scragged itself