00:05:24 <lw> can anyone connect to fuchsia.eden.le-fay.org port 25?  i've not seen any SMTP traffic all day and find this very suspicious
00:09:51 <jgh> gives a banner just fine
00:10:12 <jgh> hmm, one sec
00:10:31 <jgh> ah, ok
00:10:41 <jgh> a delay in the banner
00:14:28 <tmp_> Apparently, Cisco firewall choke on banner delays unless they've been configured not to.
00:15:19 <lw> jgh: thanks
00:28:37 <lw> i just noticed logrotate was only an hour ago (how time flies) so maybe that explains it
00:53:46 <lw> sigh now what
00:53:55 <lw> pkg remove FreeBSD-ntp just hangs forever
01:34:03 <polarian> Hello, I have FreeBSD on an E6430, the laptop has a rf switch, however it doesn't appear to work on FreeBSD, is there anything I can do to try to get it to work, or is rf switches simply not supported?
01:34:34 <lw> "rf switch" might be exposed via acpi, you can try filing a bug
01:34:46 <lw> polarian: do i know you from #a&a?
01:34:53 <polarian> lw: yes.
01:34:55 <lw> ah
01:35:06 <polarian> dammit.. how come I am always recognised :(
01:35:17 <lw> well, you do use the same nick everywhere :-P
01:35:29 <polarian> true...
01:35:42 <lw> or if you don't want to file a bug, try asking questions@
01:35:58 <polarian> hm... thanks for the advice :)
01:36:07 <polarian> its 3am I will do that tomorrow
01:36:19 <lw> 2:36AM
01:36:30 <lw> you have 24 minues to test it
01:36:36 <lw> then you turn into a pumpkin
01:37:31 <polarian> O.O
01:37:47 <polarian> wait my email isn't setup on this laptop yet ugh
01:38:45 <lw> pray to Ms. Thatcher
01:45:05 <polarian> lw: she long dead :/
01:45:15 <lw> :-)
01:45:22 <lw> rest in pieces
01:45:48 <lw> (but seriously, this is a good candicate for a mail to questions@)
05:28:52 <ke5c2fin25> How do I get this ifconfig to work in my rc.conf? ifconfig_em0="promisc -tso -lro -rxcsum, -txcsum, -rxcsum6, -txcsum6 -vlanmtu, -vlanhwtag, -vlanhwfilter, -vlanhwcsum, -vlanhwtso"
05:29:39 <ke5c2fin25> Each command, eg `ifconfig em0 -tso` works, but when put in rc.conf they do not work.
05:39:48 <concussious> ke5c2fin25: not sure but do they work without the hyphens?
05:43:56 <ke5c2fin25> if I use just `ifconfig_em0="promisc` it turns promisc on. Everything else in the list is enabled by default and I am trying to turn them off.
05:51:01 <concussious> what about "s/-/no/"?
09:21:23 <dch> got a weird problem. I swapped out my (old!) NVIDIA 1650 gpu for a new NVIDIA 3050
09:21:28 <dch> its a dual monitor setup
09:21:37 <dch> but the 2nd monitor just goes to sleep
09:21:59 <dch> nvidia-settings knows the screen is there, but there's nothing on the monitor
09:24:50 <dch> xorg.conf has `Option         "metamodes" "DP-0: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +2560+0"`
09:26:06 <dch> on the old card it was a dual DP output, but this one now is 1x DP and 1x HDMI
09:36:35 <dch> weird, I move it all to 2nd HDMI output on the monitor, and it just works. go figure.
13:59:34 <polarian> To avoid me making a fool of myself, I am not too sure why FreeBSD ports have weird updates
14:03:08 <polarian> Openfire is still at 4.7.5, which is new enough, but there was an entire network stack rewrite to fix tons of bugs which is the 4.8.x releases... but Openfire doesn't get updated. And then I go to use gajim yesterday and i realise the port for it is 1.3.3, and still being patched, while the latest version is 1.8.4, 1.3.3 was released on 9th October 2021. I believe FreeBSD aims to be stable and
14:03:10 <polarian> updates when there is security fixes, or when the newer versions become stable... however both the new versions for both ports have major improvements fixing numerous bugs and are _likely_ more secure... (especially how gajim integrated OMEMO into the main source code, instead of loading it as a plugin, allowing easy use of end to end encryption)
14:03:42 <polarian> Is there a reason they are being held back? or is it just lack of manpower?
14:04:08 <polarian> (probably should ask on mailing list, but again didn't want to make a fool of myself with something simple as "too new" or something)
14:07:08 <realdeimos> for gajim specifically, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274490#c3
14:07:10 <VimDiesel> Title: 274490 – net-im/gajim: update to 1.8.1 reason: OMEMO is broken
14:07:41 <polarian> ah
14:07:46 <polarian> should have searched bugzilla
14:09:59 <polarian> ugh this is why native is better...
14:10:06 <polarian> python and its dependency trees...
14:10:55 * polarian was kiding
14:10:57 <polarian> kidding*
14:13:45 <realdeimos> use dino
14:17:03 <polarian> realdeimos: I am using dino currently
14:17:25 <polarian> but dino misses a lot of features, and since it moved to gtk4, I haven't managed to figure out how to set the gtk theme for it
14:26:12 <realdeimos> but yes, dependencies are a pain, esp python ones
15:26:25 <remiliascarlet> We really need a graphical XMPP client that doesn't suck so bad!
15:27:33 <remiliascarlet> Gajim sucks because of Qt and Python, and Dino sucks because of GTK and Linuxisms.
15:45:51 <realdeimos> i'll get my llm to write one in lisp with zero dependencies
15:50:18 <Dooshki> an amorphous blob of parenthesis where no one will know how it works, just that it does
15:50:43 <realdeimos> sentient parens
17:01:37 <polarian> realdeimos: gajim is gtk
17:01:42 <polarian> gtk3 to be exact
17:01:48 <polarian> dino is gtk4
17:02:04 <polarian> realdeimos: you are kidding right?
17:02:47 <polarian> The issue is Linux is what most XMPP users use... and developing a client solo isn't going to be useful
17:03:53 <CrtxReavr> Is linux really what most XMPP users use?
17:03:57 <polarian> yup...
17:04:01 <polarian> I am 99% sure
17:04:10 <polarian> android and linux users
17:04:19 <CrtxReavr> ARen't there lots of Windows & mobile phone users too?
17:04:33 <polarian> not iOS, android yes. but Windows a little...
17:04:43 <polarian> but the XMPP community is privacy paranoid...
17:04:53 * CrtxReavr wonders if his domain still has the XMPP records.
17:05:31 <rwp> Back in the day I used to use Pidgin but then it became impossible for some reason I forget.  It looks like it is back now though.
17:05:40 <polarian> I don't think any public provider currently runs on BSD
17:06:38 <polarian> theres a few BSD users around...
17:06:40 <unixman_home> For XMPP I use Profanity on FreeBSD.
17:06:41 <CrtxReavr> I guess not.
17:06:43 <rwp> On phones the main thing my associates use xmpp on their phone for is to get automated downtime notifications.
17:06:54 <polarian> rwp: thats clever
17:07:02 <CrtxReavr> I used to have pidget setup with. . . a bunch of services & protocols.
17:07:08 <CrtxReavr> pidgin
17:08:06 <rwp> They have hooks into grafina, prometheus, nagios and an xmpp adaptor and then the xmpp client on Android seems pretty battery efficient so doesn't drain the phone like other notification specific apps.
17:08:17 <unixman_home> If we are talking smartphone and XMPP I use Conversations on Android. I haven't used Pidgin as my primary for XMPP for a long time.
17:08:24 <CrtxReavr> Grafana, you mean?
17:08:37 <rwp> Right.  Grafana.
17:08:37 <polarian> anyways for most there isn't any issues with XMPP, Dino and gajim are both GPL licenced and python has good support on Linux... both work under Arch Linux flawlessly... BSD is too niche to be heard
17:09:03 * rwp is still consuming my morning caffeine...
17:09:22 <polarian> morning? what time zone is that...? New Zealand?
17:09:56 <rwp> It's not yet noon here in Colorado! :-)  TZ is -0600 here.
17:10:03 <polarian> ah...
17:11:28 <rwp> Other than the occasional jitsi use I am not using xmpp for anything these days.  I mean with IRC who needs anything else?  https://xkcd.com/1782/
17:11:29 <VimDiesel> Title: xkcd: Team Chat
17:11:41 <polarian> I use XMPP IRC and email
17:11:46 <polarian> I keep all 3 clients open
17:12:12 <polarian> XMPP is best for 1-1 chats... IRC is best for big channels... and email is best for well... email.
17:14:13 <|cos|> email is great for chat. rfc9078, you know...
17:17:05 <polarian> lets not ruin email :)
17:21:56 <CrtxReavr> They should switch ntalk to TCP & wrap it in TLS.
17:22:59 <rwp> I thought ntalk already used tcp?  No?
17:24:38 <CrtxReavr> grep ntalk /etc/inetd.conf
17:25:30 <rwp> Hmm...  It does also have both tcp and udp service defined in /etc/services too.  But lots of things had both there at one time.
17:25:48 <CrtxReavr> I mean, IANA reserved port 5818 TCP & UDP for it. . . but I'm not aware of a TCP implementation of it.
17:25:54 <rwp> Wikipedia mentions "utalk" as using UDP.
17:26:40 <CrtxReavr> I think IANA's practice for a long time was to just reserve both TCP & UDP for everything, whether it made sense or not.
17:27:25 <rwp> That reservation practice made sense both then and now IMNHO because having different protocols on the same number would be confusing.  And look at the mess of port 465.
17:29:20 <rwp> Hmm...  I this seems to be the project page for ytalk https://ytalk.ourproject.org/
17:29:21 <VimDiesel> Title: YTalk - About
17:29:57 <rwp> And I had not heard of utalk before but https://utalk.ourproject.org/
17:29:59 <VimDiesel> Title: utalk - a UDP-based talk protocol
17:31:46 <rwp> Now that I have learned about utalk I feel I must play with it because it looks interesting.  "utalk uses a protocol, based on UDP, which ensures a quick response even over links with high packet loss, by displaying information as it arrives even if it is out of order. So if you type "hello world" and the "w" is lost, the other party sees "hello  orld", and a few seconds later the "w" pops into place."
17:32:29 <rwp> It must tag each packet with the order count so that loss is known so gaps can be created and then backfilled later.  That could make for an interesting effect! :-)
17:33:34 <rwp> The immediate protocol problem fir UDP though is the same as for mosh in that it is not easily supported via bastion host proxies.  I have been needing a mosh bastion host proxy system forever.
17:46:14 <CrtxReavr> "utalk uses a protocol, based on UDP, which ensures a quick response even over links with high packet loss"
17:46:40 <CrtxReavr> That sounds very much anti-thetical to UDP.
17:47:21 <CrtxReavr> "Hey, I sent a packet!  Do you care?  Did you get it?  How will I ever know?"
18:44:54 <P-NuT> Evening all. I use PF for a firewall on a website serving static HTML.
18:45:32 <P-NuT> I have logs full of hackers and even though im not owrried about them doing anything they are annoying and I'd like an automatic way of blocking them with PF.
18:45:45 <P-NuT> Do any solutions exist for this already?
18:48:33 <SponiX> P-NuT: fail2ban is probably available on FreeBSD also (I use it on Linux)
18:49:00 <P-NuT> You use it on linux for blocking people hacking nginx? Or only for SSH trolls?
18:49:55 <SponiX> P-NuT: it can be configured for many services. I normally have it setup for ssh, but it has examples of others included
18:50:32 <phryk> vishwin: hey, i saw you in a mixxx issue of interest to me ( https://github.com/mixxxdj/mixxx/issues/12894 ) and you mentioned being able to sidestep the issue. do you maybe have a working mixxxdb.sqlite lying around, or can you at least tell me where i find those migrations? didn't find them in the output of 'pkg query %Fp mixxx'…
18:50:36 <VimDiesel> Title: Upgrade fail version 2.4.0 - "Unable to upgrade database schema" · Issue #12894 · mixxxdj/mixxx · GitHub
18:50:36 <VimDiesel> 12894 – new port: gyroscope-1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=12894
18:51:45 <P-NuT> Interesting. I will go and check out fail2ban.
18:51:51 <P-NuT> Thanks again!
19:06:57 <phryk> vishwin: just applied your patch from #277728 in case that contains a fix, now building, will report back when it's done.
19:09:14 <vishwin> it doesn't have a fix lmao
19:10:32 <phryk> vishwin: thought so, but it was something i could *do*. anyhow forgot at least make makesum after applying the patch so the build failed :D
19:11:12 <vishwin> run all the migrations specified for version 7 except for the DELETE FROM queries
19:11:31 <phryk> vishwin: ye, but where do i find the migrations?
19:11:43 <vishwin> res/schema.xml
19:12:20 <vishwin> let mixxx run normally on the first run, which should give you that error dialog
19:12:38 <vishwin> it will have you close the program
19:13:08 <vishwin> then inspect the sqlite db manually, it should be at version 6 because none of the version 7 queries were committed
19:13:08 <phryk> yes, and after that, i get a ~/.mixxx directory. no schema.xml anywhere in there, tho.
19:13:21 <vishwin> because the sqlite db had been created by then
19:13:32 <vishwin> you need to open the sqlite db manually
19:13:43 <phryk> on a sqlite repl right now. :)
19:13:50 <phryk> yep, schema is version 6.
19:14:18 <vishwin> run all the version 7 queries except for the DELETEs, then bump schema version to 7
19:15:11 <vishwin> commit, then run mixxx again from there
19:15:39 <phryk> Ah, found schema.xml in the mixxx repo. thought it would be part of the package. :)
19:19:19 <phryk> okay, applied queries, updated all 3 schema version settings to 7. now i just rerun mixxx and it does the rest?
19:20:19 <phryk> ah, i should read :D
19:20:58 <phryk> yus, it worked, thanks a bunch, vishwin :)
19:50:29 <jbo> lw
20:08:02 <zBeeble> It seems to me that we maintin the BSD make and one problem (for both GNU and BSD makes) is that you can start a make -j, and you could theroretically inherit some portion of a j, but we don't do that --- and so (say) a make -j40 in /usr/src on a 40 cpu machine ... does not run along at a concurrentcy of 40 for all it's journey --- it depends on each subdirectory's concurrency.
20:08:38 <zBeeble> ... almost like a make allow job server would be the ideal solution.
20:09:42 <zBeeble> ... similarly for poudriere, you can set the number of jobs, but then the jobs themselves default to a conncurrency of ncpu --- which means that you get number of jobs * number of cpu busy tasks ... sometimes.  about half that mostly.
20:11:02 <zBeeble> putting on my thinking hat, jobd and job ... job communicating with jobd as when to run... that would allow fairly easy deployment to all sorts of different makes (by seting $CC and whatnot appropriatly)
20:11:49 <zBeeble> yes?  no?  run it up the flagpole?  I could pretty easily write this... if it was going to be used.
20:25:02 <zBeeble> yes/no/maybe/
20:25:06 <zBeeble> ???
20:26:04 <Carbon666> Hello everyone! I am still trying to boot FreeBSD Iso Installation disk via GRUB from the HDD. I want to boot the installation with some sorts of loop sintax, under GRUB, any light? Please help me if you have the chance!
20:28:54 <Carbon666> can I paste a 10 line 40_custom grub entry in here? Directly, I mean
20:31:51 <Carbon666> brb
20:45:07 <markmcb> is there a way to make a repo searchable but disabled? like i'd like to be able to pkg search the default repo easily, but have it disabled use my own local repos (with far less packages) when doing anything other than search.
20:45:20 <markmcb> or a better way to accomplish the same thing?
20:52:25 <Carbon666> alright! I am back
20:52:33 <Carbon666> I have this so far:
20:52:38 <Carbon666> menuentry "FreeBSD" --class freebsd --class bsd --class os {
20:52:38 <Carbon666>   insmod ufs2
20:52:38 <Carbon666>   insmod bsd
20:52:38 <Carbon666>   set isofile="/home/carbon/Boot/Iso/freebsd.iso"
20:52:38 <Carbon666>   set root=(hd0,gpt5)
20:52:39 <Carbon666>   loopback loop (hd0,gpt5)$isofile
20:52:41 <Carbon666>   kfreebsd (loop)/boot/kernel/kernel
20:52:43 <Carbon666>   kfreebsd_loadenv (loop)/boot/device.hints
20:52:45 <Carbon666>   set kFreeBSD.vfs.root.mountfrom=ufs:/dev/ada0s1a
20:52:47 <Carbon666>   set kFreeBSD.vfs.root.mountfrom.options=rw
20:52:49 <Carbon666>   set kFreeBSD.hw.psm.synaptics_support=1
20:52:53 <Carbon666> }
20:54:19 <Carbon666> the ada0s1a reference changes nothing if removed entirely, in fact, if I remove all the sets it will render an instant reboot
20:55:00 <Carbon666> please try to enlighten me on how to boot the Iso from the hdd via Grub
20:59:38 <Carbon666> rwp, hello mate!
21:00:08 <rwp> Carbon666, I don't know but I would have assumed that one would chainload from GRUB to the FreeBSD loader.  That would have been my assumption.
21:00:20 <rwp> Obviously I am not actively doing this and so I am just brainstorming here.
21:00:52 <Carbon666> Would it help if I dd the Iso to an actual partition?
21:01:02 <rwp> Usually when one has booted a bootloader like GRUB and then want to boot another system which has their own boot loader then one would use the chainload functionality to chain from GRUB to the other boot loader.
21:01:06 <Carbon666> maybe, right?
21:01:26 <rwp> You haven't already made a dd image copy to the hdd?  I had assumed that you had already.
21:01:26 <Carbon666> Oh, I see!
21:02:45 <Carbon666> I haven't, I was trying to use loop in order to mimic an actual dvd-drive, but without speed limitations
21:02:46 <rwp> For example Windows (blech! /me spits in the dirt) has its own boot loader.  So one will usually chainload it.  https://www.gnu.org/software/grub/manual/grub/html_node/Chain_002dloading.html
21:02:47 <VimDiesel> Title: GNU GRUB Manual 2.12: Chain-loading
21:03:51 <rwp> I am making an assumption here but I think chainloading the FreeBSD bootloader would be the desired thing.  Because then the FreeBSD loader knows about the kernels and boot environments and options and one gets the interface to interact with it at boot time.
21:04:20 <Carbon666> yes, but I can boot most linux dist with a loop interface under grub...
21:04:36 <rwp> GRUB is designed to boot linux kernels.
21:04:58 <Carbon666> ok, so I will dd it to a partition and try to, maybe os-probe it
21:05:03 <Carbon666> let me do it
21:05:33 <Carbon666> yes, that's why I need your help to try to boot it with the right calls
21:05:49 <Carbon666> it provides the kfreebsd keyword
21:05:54 <rwp> Back during the transition from GRUBv1 to GRUBv2 GRUBv2 was defaulted (on Debian at least) to chainloading the previous GRUBv1 loader as a safety precaution because some systems had required custom parameters set that was hard to automatically transfer to the new system.
21:06:01 <Carbon666> so, it must be capable of booting it
21:06:14 <Carbon666> I mean, it IS fully capable of booting it
21:06:35 <rwp> kfrebsd was a Debian project to boot Debian using the FreeBSD kernel.  https://wiki.debian.org/Debian_GNU/kFreeBSD
21:06:38 <VimDiesel> Title: Debian_GNU/kFreeBSD - Debian Wiki
21:06:56 <rwp> s/kfrebsd/kFreeBSD/ as that was just a typo there.
21:07:14 <Carbon666> Oh, so maybe that's why I get an instant restart using it!!!
21:07:45 <Carbon666> ok, let met prepare a partition and all, gonna dd and let's see what happens
21:08:07 <Carbon666> brb
21:08:08 <rwp> Debian kfreebsd had some grip and forward movement but the all encompassing systemd movement killed it as it is counter to the new GNU/systemd system they are building.
21:08:33 <Carbon666> OHHHHHHH
21:08:45 <Carbon666> that's wonderful talk
21:09:06 <rwp> If nothing else I believe it would be easier to chainload to the FreeBSD boot loader and get that working as I think that should Just Work.  And then you can try to get it to boot natively.  I think I might have heard about people doing it.
21:09:07 <Carbon666> let's try to have that talk anytime, if you wish
21:09:26 <rwp> What's a wonderful talk?  What talk?  Did I miss someone giving a talk that I would be interested in?
21:09:48 <Carbon666> ỹes, the GNU/systemd talk
21:10:42 <Carbon666> not gonna lie, this is the first time I will try to use dd without wiping my system
21:10:56 <Carbon666> there goes well 20 years since the last time :P
21:12:43 <Carbon666> rwp, ifI dd, I should use the memstick image?
21:13:40 <Carbon666> gonna go with the full release
21:14:15 <rwp> I think you are just saying that what I am saying about GNU/systemd is my own talk?  Uhm...  Okay.  Sure.  I definitely have opinions. :-/
21:14:33 <Carbon666> maybe I am mixing linux systems and all, I am trying to find MY system yet
21:14:53 <rwp> We do jokingly call dd the disk destroyer because if one gets the destination wrong then it will wipe over a system faster than any other method.  But it won't destroy the disk.  The the OS on it.
21:15:18 <Carbon666> haha
21:15:30 <Carbon666> now I am less blind
21:15:52 <rwp> For FreeBSD I would boot the full install image.  That's just easiest.  And it isn't too terrible.  The FreeBSD-14.0-RELEASE-amd64-disc1.iso is 1.1GB!  It has been growing!
21:15:57 <Carbon666> I can reason to use lsblk nowadays hehe
21:16:30 <Carbon666> WE LOVE IT BIG! rofl, just kidding
21:16:30 <jmnbtslsQE> markmcb: maybe you can pass a special config file in your pkg search command, with this special confnig enabling the default repo. (so maybe best suited for a command alias)
21:17:05 <jmnbtslsQE> ah hmm, this is wrong, nevermind
21:17:15 <rwp> I personally recommend against multi-boot systems.  Because the machine is always booted in the */other/* OS than the one you want to be running.  Instead I find virtual machines to be more useful on current hardware with just a little bit of RAM to support it.  And FreeBSD jails are very light weight for FreeBSD containers.
21:17:36 <jmnbtslsQE> markmcb: i meant repository file, but i don't know if that is supported...i'm curious so i will check
21:18:51 <Carbon666> dude, isn't the: "-memstick.img: This file contains all of the files needed to install FreeBSD, its source, and the Ports Collection. Write this file to a USB stick as shown in Writing an Image File to USB."
21:19:07 <Carbon666> the one to use with dd ?
21:19:25 <Carbon666> let's try
21:19:31 <Carbon666> the full dvd first
21:19:34 <markmcb> jmnbtslsQE: that's what i was thinking, but didn't see a way to pass that to pkg search
21:20:01 <jmnbtslsQE> markmcb: hmm, maybe you can just set REPOS_DIR... so: REPOS_DIR=/etc/pkg pkg search -r FreeBSD $package
21:20:48 <jmnbtslsQE> (that's for the default FreeBSD repo, if it's a different one, then i guess you would want a separate directory with just that repo in it)
21:21:42 <markmcb> i'll give that a shot
21:22:31 <Carbon666> dd started, rofl
21:22:41 <Carbon666> holy mother
21:25:11 <Carbon666> os-probe saw nothing
21:27:41 <Carbon666> it seems I can't see the fs from linux in here
21:27:52 <Carbon666> I am not sure on how to call the kernel
21:28:40 <Carbon666> so far I have: menuentry "FreeBSD ISO" {
21:28:40 <Carbon666>   insmod ufs2
21:28:40 <Carbon666>   set root=(hd0,gpt3)
21:28:40 <Carbon666>   chainloader
21:28:40 <Carbon666> }
21:29:06 <rwp> I don't know much about os-probe but again isn't that a Linux & Windows specific probing?  (It tries to mount file systems and see what is there.  Which can be a problem for people with VMs active on the partition which is getting mounted.  I always remove os-prober.)
21:29:15 <Carbon666> the "ISO" is so that I know it is the install boot
21:29:32 <rwp> There is a forgotten +1 on the chainloader line: https://www.gnu.org/software/grub/manual/grub/html_node/Chain_002dloading.html
21:29:33 <VimDiesel> Title: GNU GRUB Manual 2.12: Chain-loading
21:29:44 <rwp> https://www.gnu.org/software/grub/manual/grub/html_node/chainloader.html#chainloader
21:29:45 <VimDiesel> Title: GNU GRUB Manual 2.12: chainloader
21:30:56 <rwp> I have already told you more than I know.  You will have surpassed my experience on this if get it to work.
21:31:19 <Carbon666> yes, but, I can't see the fs dd created at that partition, I should chainload to /boot/kernel/kernel ?
21:31:54 <Carbon666> let's make it happen!!!!
21:32:34 <rwp> I must do two other higher priority things first.  But since I am curious after I do those things I will try setting up a test on my workbench system and see if I can figure it out.  Don't hold your breath though as it might be a while.
21:33:05 <Carbon666> sure
21:33:20 <Carbon666> I already told you once: you are a live saviour!
21:33:39 <Carbon666> this notebook I have is pretty old
21:33:58 <Carbon666> and that's the only thing I possess right now
21:34:34 <Carbon666> #menuentry "FreeBSD 14 iso" {
21:34:34 <Carbon666> #	insmod bsd
21:34:34 <Carbon666> #	set isofile="/home/lightac/Boot/Iso/freebsd.iso"
21:34:34 <Carbon666> #	loopback loop (hd0,gpt4)$isofile
21:34:34 <Carbon666> #	kfreebsd  (loop)/boot/kernel/kernel -v
21:34:35 <Carbon666> #	kfreebsd_module  (loop)/boot/device.hints
21:34:37 <Carbon666> #	set FreeBSD.vfs.root.mountfrom=cd9660:/dev/md0
21:34:39 <Carbon666> #	set FreeBSD.vfs.root.mountfrom.options=rw
21:34:41 <Carbon666> #}
21:35:17 <Carbon666> this one had positive feedback, but I was unable to install, gotta retry it to refresh my memory
21:37:42 <Carbon666> This is what I will attempt right now:
21:37:44 <Carbon666> menuentry "FreeBSD ISO" {
21:37:44 <Carbon666>   insmod ufs2
21:37:44 <Carbon666>   set root=(hd0,gpt3)
21:37:44 <Carbon666>   chainloader +1 /boot/kernel/kernel
21:37:44 <Carbon666> }
21:38:24 <Carbon666> brb
21:40:37 <Carbon666> rwp, just updated my grub entries with that menuconfig and got this:
21:40:40 <Carbon666> Warning: os-prober will be executed to detect other bootable partitions.
21:40:40 <Carbon666> Its output will be used to detect bootable binaries on them and create new boot entries.
21:40:40 <Carbon666> Found unknown Linux distribution on /dev/sda3
21:40:40 <Carbon666> Found Slackware 15.0 x86_64 on /dev/sda4
21:40:50 <Carbon666> got unknown linux
21:41:00 <Carbon666> let's see
21:41:01 <Carbon666> brb
21:46:57 <Carbon666> I am back. and it says "Missing Boot Loader"
21:47:12 <Carbon666> I will try getting the memstick image
21:54:15 <Carbon666> I am trying to get it by magnet, but, nothing so far
21:54:32 <Carbon666> magnet:?xt=urn:btih:487b456b4a4c5c020644ebb255f5c5b80ebc2bc9&dn=FreeBSD-14.0-RELEASE-amd64-memstick.img
21:57:53 <Carbon666> magnet:?xt=urn:btih:9db64a46d5630912d24bd7bc811b862d6c84dc4b&dn=FreeBSD-14.0-RELEASE-amd64-memstick.img.xz
21:58:01 <Carbon666> this one seems also dead
21:58:35 <Carbon666> not anymore
21:58:45 <Carbon666> 13mb/s
22:00:26 <Carbon666> let's dd it
22:03:01 <Carbon666> now, gonna attempt the same chainloader argument
22:03:06 <Carbon666> brb
22:18:51 <Carbon666> nothing, same thing
22:51:51 <bsd4me> Carbon666: try this line: chainloader (hd0,gpt10)/EFI/FreeBSD/loader.efi
22:52:18 <Carbon666> alright
22:52:24 <bsd4me> change hd0,gpt10 to what you have of course :)
22:52:45 <Carbon666> sure
22:52:55 <Carbon666> but should I provide a +1?
22:53:04 <bsd4me> just like that
22:54:07 <Carbon666> right, brb
23:00:44 <Carbon666> bsd4me, it says: Unknown file system. I tried adding: insmod bsd and it didn't help
23:01:16 <Carbon666> I will dd the full dvd back again, since that was the mem stick img
23:03:57 <bsd4me> insmod ufs2
23:04:26 <Carbon666> that I had on
23:04:32 <Carbon666> ok, dd complete
23:04:58 <Carbon666> menuentry "FreeBSD ISO" {
23:04:58 <Carbon666>   insmod ufs2
23:04:58 <Carbon666>   set root=(hd0,gpt3)
23:04:58 <Carbon666>   chainloader (hd0,gpt3)/EFI/FreeBSD/loader.efi
23:04:58 <Carbon666> }
23:05:17 <Carbon666> that's what I've got
23:05:22 <Carbon666> ok, rebooting
23:22:21 <Carbon666> Hey!!! bsd4me, rwp, we did it!
23:23:42 <Carbon666> menuentry 'FreeBSD ISO' {
23:23:43 <Carbon666>     set root='hd0,gpt3'
23:23:43 <Carbon666>     kfreebsd /boot/loader
23:23:43 <Carbon666> }
23:24:09 <Carbon666> this is the correct entry after dd'ing the full dvd iso to a given partition
23:24:16 <bsd4me> congrats :)
23:24:26 <Carbon666> I gotta go to bed now
23:24:39 <Carbon666> but tomorrow I know what to do :D
23:25:01 <bsd4me> great job :)
23:25:03 <bsd4me> gn
23:25:05 <Carbon666> gn everyone, thank you for everything so far