00:04:26 <idwer> rwp: iirc ntpd opens a port, as well, https://cgit.freebsd.org/src/tree/libexec/rc/rc.conf#n408
00:04:27 <VimDiesel> Title: rc.conf « rc « libexec - src - FreeBSD source tree
00:09:28 <rwp> I am not sure which detail from that file you wanted to call my attention to. I'll need to buy a clue? Thanks.
00:09:54 <rwp> By default ntpd is peer-to-peer in that it will share time by default.  That's usually desirable.  So it will normally open UDP port 119.
00:10:48 <rwp> On a large machine collection site I recommend selection three stable well connected systems and having them peer time among themselves and pool from the outside Internet WAN.
00:11:15 <rwp> Then have all other systems on that site use those three LAN systems to serve time to the LAN.
00:11:34 <idwer> aiui ntpdate is used to consume ntp, and ntpd can serve and consume ntp?
00:11:52 <rwp> The LAN will have low latency and jitter and then all LAN systems will have a good common shared time base.  And the global servers never see too large of a load on them.
00:12:27 <rwp> Yes.  Local ntpdate would connect to a remote ntpd to sync the time.
00:13:01 <rwp> And ntpd is peer-to-peer with other ntpd.  And other time daemon programs implementing NTP too.
00:59:06 * wikan waves
01:08:35 <wikan> i wonder if you know how people whom use i3/awesome/qtile/icewm may change mouse cursor.
01:09:06 <wikan> i have tried via Xresources, gtk2 and gtk3 config - only firefox use my  cursor theme
01:11:00 <yuripv> do you xrdb your .Xresources?
01:11:50 <yuripv> (I do remember issues with i3 and mouse cursor in the root window, don't remember the solution though)
01:12:27 <wikan> as i said i have tried
01:12:55 <wikan> xrdb -merge didn't do anything after relogin
01:13:27 <wikan> Xcursor.theme: VS11
01:15:18 <wikan> xrdb -merge is in xinitrc
01:15:33 <rwp> I use i3 and the mouse cursor is chosen by the window with focus. That is, XTerm gives me a "I" pointer and Firefox changes that to an Arrow pointer and so forth.
01:16:56 <rwp> i3 itself uses a pointer icon for the pointer.
01:17:53 <wikan> in icewm it dowsnt work, i will check in fluxbox
01:18:02 * wikan relogins
01:20:41 <wikan> weird it works with icewm
01:21:07 <wikan> so, question 2: how can I change theme on the fly without relogin?
01:22:18 <wikan> previously I put X settins to ~/.Xdefaults and cursor theme to ~/.Xresources
01:22:33 <wikan> I xrdb -merge `d both files from xinitrc
01:22:38 <wikan> and it didn't work
01:22:52 <wikan> I moved theme to ~/.Xdefaults and it works
01:23:07 <wikan> maybe xinitrc script has misspelling
01:27:25 <wikan> nope it is good
01:37:06 * wikan vommits
01:37:15 * wikan vommited
01:38:42 * wikan thinks: fucking radiotheraphy
01:40:26 <Kalten> `.xinitrc` (dot at the start)
01:41:06 <wikan> yea, but it would be gread to change cursor theme on the fly without relogin
01:41:20 <wikan> i have no idea how lxapperance does it
01:41:41 <Kalten> and out of some reason symbolic link `.xsession` to it, i.e. `ln -s .xinitrc .xsession`
01:41:55 <wikan> i am looking for solution to change all themes (gtk2, gtk3 and cursors) just on fly from script
01:45:08 <Kalten> maybe restarting the windowmanager without closing programs (sometimes programs do close though) `icewm --restart` it seems to be
01:45:49 <Kalten> (might have to do with the session leader of such processes)
01:46:06 <wikan> nope
01:46:27 <wikan> Xinitrc does not affect already launched apps
01:46:33 <wikan> so root window too
01:46:59 <wikan> and root window is not from wm but X
01:53:55 <Kalten> ROTFL!!! icewm theme https://user-images.githubusercontent.com/7656607/32042698-002e773c-ba6b-11e7-8e6a-29da6f910ec2.png
01:54:25 <wikan> downloaded, ugly ;)
03:42:57 <parv> "icewm" already does gives very strong impression of a "Windows" theme even without going through the effort to create a even stronger resemblance
03:43:29 <parv> Then again there is helloSystems so🤷‍♂️
03:46:39 <CCFL_Man> is there a command line utility that uses cdparanoia and cd-discid to make cd rips automatically naming files to cddb track listings?
03:49:15 <parv> s/Systems/System/
03:53:03 <CCFL_Man> looks like
03:53:06 <CCFL_Man> https://www.freebsd.org/cgi/man.cgi?query=cdrdao&apropos=0&sektion=1&manpath=FreeBSD+Ports&format=html
03:53:07 <VimDiesel> Title: cdrdao(1)
03:58:25 <rtprio> i think i used abcde for that in like, 2003
03:58:33 * rtprio wonders if that port still exists.
03:58:52 <rtprio> uh, i'll be damned
05:12:20 <parv> Re icewm theme: https://mastodon.social/@thelinuxcast⊙fo/109736687459889165
05:12:22 <VimDiesel> Title: The Linux Cast :fedora: :xfce:: "You know, it's hilarious. Some of the most upvote…" - Fosstodon
08:19:36 <yourfate> rwp: thanks for the insights!
11:05:58 <pertho> what scripts can be configured to run after resume from suspend to S3?
11:08:18 <idwer> you mean to S0
11:11:52 <pertho> yeah I noticed.. 13.1 laptop.. you suspend it to S3.. leave it overnight.. resume in the morning and the clock stays at the old time.
11:12:05 <pertho> I had to run ntpdate to fix the clock
11:18:56 <meena> pertho: https://lists.freebsd.org/archives/freebsd-virtualization/2022-December/001073.html
11:18:57 <VimDiesel> Title: VM Wakeup Events
11:19:49 <meena> not the same thing, but, rc.resume(8) should be what you're looking for
11:20:04 <pertho> found this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264729
11:20:06 <VimDiesel> Title: 264729 – RTC clock is set incorrectly upon resume if NTP is in use
11:20:12 <pertho> but I'm running openntpd not base ntpd
11:20:56 <V_PauAmma_V> pertho, I think any rc.d script with "KEYWORD: resume" will be run on resume, but I'm not sure you can tell from which suspend state within the script. So check /usr/local/etc/rc.d/* or add a custom script there.
11:23:36 <pertho> thanks I'll do some investigation.. I wonder if ntpdate needs to run on resume regardless.. ntpd may not be enough to correctly 'skew' the clock
11:25:53 <pertho> anyway I think that bug I linked above is what happened
11:26:48 <idwer> I'd compare, have not and never before looked at this, linux code and (open)BSD code
11:27:05 <idwer> like, does openbsd store suspend and resume timestamps in RAM?
11:29:14 <meena> pertho: by default, ntpd refuses to correct a big skew, maybe just changing the flags could fix the issue
11:30:05 <meena> openntpd can be compelled to correct the skew on restart, but it seems it'll happily sit there for hours doing nothing about it
11:31:24 <deeaitch> morning all
11:33:47 <pertho> FreeBSD's base ntpd has a ton of options, but.. it's not clear which one to use
11:34:25 <pertho> e.g. -x, --slew  : Slew up to 600 seconds. <- Won't that only be useful if your clock is under 10 minutes difference?
11:35:28 <pertho> looks like it might be -g
11:35:39 <yuripv> just restart ntpd service?
11:35:55 <idwer> https://github.com/openbsd/src/blob/master/sys/arch/amd64/amd64/acpi_wakecode.S
11:35:56 <VimDiesel> Title: src/acpi_wakecode.S at master · openbsd/src · GitHub
11:35:58 <yuripv> (having ntpd_sync_on_start="YES" in rc.conf)
11:46:25 <pertho> yuripv: does having ntpd_sync_on_start="YES" mean ntpd_enabled="YES" has to be in there too?
11:46:35 <pertho> or does the sync on start just run ntpd once and quit?
11:48:43 <idwer> pertho: pgrep is your friend
12:09:21 <micttyl> hello
12:09:39 <micttyl> is there any rc that meant to be run for each login?
12:10:09 <micttyl> which is not user specific rc. i mean admin-configured rc but for each login
13:54:33 <lucas-arg> hey all... got a problem with freebsd 13.1, i have a lenovo 14p laptop, and my touchpad doesnt work, added moused_enable and dbus etc to /etc/rc.conf and still does not work... installed xorg etc nothing makes it work... went back t linux and touchpad works ok...
13:55:43 <lucas-arg> need help dont know  what else i should do
13:59:22 <paulf> use an external mouse?
14:00:02 <lucas-arg> would be a simple solution, but want to use bsd on my laptop
14:01:20 <vkarlsen> Is this a non-Thinkpad Lenovo?
14:02:46 <lucas-arg> yeah
14:02:58 <lucas-arg> lenovo 14p
14:02:59 <lucas-arg> it is
14:03:19 <lucas-arg> tried with synaptic and libinput but no luck
14:04:25 <vkarlsen> I don't know about those regular ones. They might contain whatever hardware. I've never had problems with that on the Thinkpads.
14:05:34 <lucas-arg> :(
14:07:08 <vkarlsen> Have you tried running hw-probe on it?
14:07:59 <lucas-arg> nope
14:08:12 <lucas-arg> will do so
14:18:13 <micttyl> is the portsnap volunrability resolve? if not, is this why new handbook does not introduce portsnap?
16:15:53 <V_PauAmma_V> micttyl, portsnap is being deprecated. Plans are for it to go away, but I'm not sure in which major version.
16:34:29 <ixmpp> everyone just using git instead now?
16:52:40 <Kalten> ixmpp: likely
16:52:52 <ixmpp> good 🙂
18:18:40 <pertho> meena: I think you're right.. openntpd does absolutely nothing until you restart
18:18:55 <pertho> at least as far as time skew
18:23:30 <rwp> I don't happen to have a laptop capable of resuming with FreeBSD at the moment. My Thinkpad x201 has the black display after resume problem.
18:24:09 <rwp> But if it were me I would configure such that "service ntpd restart" happened after resume so that the clock would get updated.
18:24:19 <ixmpp> i wish i had a freebsd laptop, mine doesn't work because no touchpad drivers
18:25:02 <pertho> well.. /etc/rc.d/ntpd only has KEYWORD: nojail shutdown
18:25:11 <rwp> You might find this funny but I can't remember if my x201 is the model with or without the touchpad. :-)
18:26:14 <ixmpp> that simplifies things :p
18:27:57 <pertho> rwp: have you tried sysctl hw.acpi.reset_video=1 ?
18:29:12 <rwp> I have not.  Looking up the details of it now...
18:29:25 <pertho> acpi(4)
18:29:42 <rwp> Also I found description of it in https://docs.freebsd.org/en/books/handbook/config/
18:29:43 <VimDiesel> Title: Chapter 13. Configuration and Tuning | FreeBSD Documentation Portal
18:32:16 <rwp> Thank you for the acpi(4) reference.  I had not looked at it before.  The combination of documentation is very useful!
18:34:22 <pertho> rwp: give it a whirl see if it works on your thinkpad! :)
18:35:59 <rwp> I just finished reading the first pass through the various docs.  I'll boot it up and give it a try right now.
18:36:37 <rwp> So far I have just been doing a full shutdown and boot on the laptop.  But suspend-resume is one of the things needed to really make it useful.
18:41:16 <pertho> does hibernate (I think that's 'S5'?) work at all?
18:42:09 <pertho> I don't think FreeBSD has 'ZZZ'
18:46:40 <V_PauAmma_V> It has zzz (all lowercase)
18:47:54 <meena> rwp: in theory, rc.resume should work
18:55:23 <rtprio> pertho: it does; /usr/sbin/zzz
19:31:13 <rwp> pertho, Unfortunately reset_video=1 causes it to never wake up from sleep.  (I typo'd that as zleep, corrected it but zleep might become a new favorite word for me now.)
19:32:26 <rwp> meena, The difference between theory and practice is the difference between theory and practice.  :-)
19:36:05 <rwp> pertho, Suspend S4 appears to hibernate to disk and shutdown okay but upon boot does not resume the previous state.
19:36:51 <rwp> Suspend S5 says it is not supported.  Though hw.acpi.supported_sleep_state reports S3 S4 S5
19:37:56 <rwp> This laptop OS image is slightly behind at 13.1-RELEASE-p2 so I will upgrade it now to the latest and test again.
19:37:57 <rtprio> i haven't figured out my thinkpad sleep either :|
19:40:16 <rwp> I am running zfs on this laptop.  With the iwn wifi driver. There are only 10 drivers listed in kldstat that are not iwn and none appear to me to be video drivers.
19:50:28 <rtprio> rwp: sometimes i kldload a glob in /boot/kernel just to see what lands
19:55:27 <rwp> I wasn't planning on debugging the laptop issues today.  Though when help is available one should take it!
19:55:37 <rwp> I'll take all of this down in my notes and return to the problem later.  I have to do some $WORK for a bit.
20:34:49 <Yoohoo999> anyone here?
20:40:02 <rtprio> looks like 650 people are, my dude
20:44:18 <thumbs> Yoohoo999: you generally want to ask the actual question first.
21:16:17 <Yoohoo999> thumbs: I'm entirely new to freebsd. I have windows on my computer. I shrank my C: drive partition to give about 32 gb to freebsd, and then I installed freebsd 13.1 from the amd64 memstick img. When I boot my computer, it goes to the freebsd logo screen and there I can select "boot multiuser".
21:16:49 <Yoohoo999> thumbs: However, I want to see the boot0 boot manager and select between windows 11 and freebsd.
21:17:47 <Yoohoo999> thumbs: I ran "boot0cfg -B [whatever my disk was called]", but it still won't show the boot0 boot screen.
21:18:08 <thumbs> Yoohoo999: right, but you don't need to keep addressing me; address the channel in general.
21:18:18 <Yoohoo999> thumbs: ok
21:20:20 <Yoohoo999> Hey, boot0 isn't showing on startup of my computer. I just installed freebsd on a computer with windows 11 and want to see the boot manager so I can boot either os easily. However, it just goes to the freebsd and I have to select exit to boot loader and then type "quit" to get to windows. I
21:20:20 <Yoohoo999> installed boot0 with boot0cfg, what could be wrong?
21:22:36 <rtprio> Yoohoo999: is your system uefi?
21:23:00 <Yoohoo999> yes, unfortuneately
21:24:25 <rtprio> you can add windows back with efibootmgr
21:24:28 <rtprio> and use it to select
21:25:18 <drg99> hi, how can I find the service file for a running process?
21:26:13 <Yoohoo999> rtprio: ok
21:26:29 <rtprio> drg99: either /etc/rc.d or /usr/local/etc/rc.d
21:27:58 <drg99> rtprio thanks
21:30:48 <cpet> Man sysrc as well
21:31:39 <drg99> I was looking into ps aux and service status but could not find
21:32:46 <cpet> services -l
21:33:24 <drg99> cpet: I am looking for something like systemd, where I see the path of service definition in status
21:33:48 <drg99> not so important, but would be nice if there is some way of doing it
21:33:49 <cpet> We don’t have systemd
21:34:31 <cpet> Luckily we only have two locations  system and ports
21:35:06 <drg99> i am still learning freebsd and its not yet natural for me to know the paths
21:38:55 <rtprio> drg99: it takes some time
21:40:23 <drg99> rtprio: yes, but it worth's the time, I like it so much
21:40:40 <cpet> Yeah
21:59:40 <Yoohoo999> rtprio: i used efibootmgr to make sure that windows was in the boot order, and running "boot0cfg -v [my disk]" let me know that boo0 has the 0xf mask, which means it should see all 4 partitions. Any ideas as to why the boot0 boot manager isn't showing a menu on startup?
22:00:13 <rtprio> when i dualboot i have to hit f12 to override the boot device
22:00:32 <daemon> ^ what I do too, everything else seemed to not work with UEFI
22:00:39 <Yoohoo999> rtprio: that works :(
22:00:40 <daemon> and windows
22:00:43 <rtprio> but it does list the items in efiboot, in my case windows and freebsd (or fedora when i had it)
22:00:43 <daemon> I mean
22:00:45 <daemon> uefi menu
22:00:47 <daemon> f12 boot menu
22:00:50 <daemon> is it really any different?
22:00:58 <Yoohoo999> ?
22:01:12 <rtprio> i have in the past put freebsd into the windows boot menu
22:01:31 <rtprio> but all this is generally why i'm not super keen on dualboot
22:01:59 <daemon> you could with dnsmasq PXE for pretty much everything not windows
22:03:51 <rtprio> i was playing with that idea too
22:04:02 <Yoohoo999> I have a mediatek wifi card that freebsd apparently doesnt support, and I want to connect my machine to my wireless network, so I'm thinking of using a VM with freebsd and internet access to fetch the package 'net/wifibox' which supports my card, and then putting that package on a usb drive so my
22:04:02 <Yoohoo999> non-network-connected freebsd machine can access it.
22:04:02 <Yoohoo999>  is this a good idea?
22:04:12 <daemon> it is not actually to bad to get working, few hours cocking about
22:05:38 <daemon> Yoohoo999, depends on budget, if you have a few spare quad/dollar, try a powerline adapter or a ethernet/wireless converter; if you have no spare <currency> then yeah you can vm something that supports the card and as long as the bios supports vt-d pass through the wifi card to the guest vm and use the bridge network to get out via it
22:06:53 <Yoohoo999> er, i have a uefi only computer. would 'wifibox' or another service where a linux vm manages my wifi work
22:07:16 <Yoohoo999> what is vt-d?
22:07:40 <daemon> its a way to pass through hardware to a vm, its more the underlying technology required
22:08:04 <rtprio> * a cpu flag
22:08:23 <Yoohoo999> ok
22:08:35 <Yoohoo999> is that a hypervisor setting or a bios setting
22:08:59 <rtprio> it's a capability of a cpu
22:09:05 <Yoohoo999> ok
22:10:00 <nacelle> to be fair though, the answer is yes
22:10:10 <nacelle> (its both a hypervisor setting and a bios setting, generally)
22:10:39 <nacelle> if you're at the point of doing that, get a new nic, they're cheap.
22:11:06 <rtprio> yeah, a new nic would be better
22:11:19 <rtprio> ndiswrapper was bad an i can't imagine wifibox being that much better
22:12:12 <LxGHTNxNG> it could be okay?
22:12:14 <LxGHTNxNG> for some
22:12:25 <nacelle> not really
22:12:39 <nacelle> its generally pretty unstable, which is the opposite of what you want out of networking
22:13:34 <nacelle> I mean, granted, its been a while since i've done it, but ... dont do it. its a nightmare in the end when something goes wrong.  troubleshooting has a lot of extra layers, where each extra layer multiplies the things you have to think about when something breaks.
22:14:12 <Yoohoo999> ok, i have an amd ryzen 5000 series processor, and that seems to support amd-vi
22:14:40 <Yoohoo999> will amd's virtualization thingy work just as well as vt-d?
22:19:00 <daemon> new nic = yes, but ethernet/wireless converter box == absolute yes
22:19:06 <daemon> they are a god send when you are in a pickle
22:19:17 <daemon> and should be in everyones toolbox
22:23:45 <rtprio> i had a usb nic which was handy. slow, but handy
22:25:09 <daemon> got a few of them ;D
22:25:25 <daemon> 10M is awesome when your only other option is ppp etc :P
22:27:12 <debdrup> Yoohoo999: AMD came up with it first, so yes
22:27:32 <debdrup> Wait, I think you're mixing terms.
22:27:41 <CCFL_Man> Yoohoo999 has some big dreams, for sure
22:28:04 <Yoohoo999> i just want what's possible with linux
22:28:07 <Yoohoo999> :)
22:28:31 <debdrup> AMD-V, the vendor-specific implementation of hardware-assisted virtualization for x86, is the equivalent of VT-x on Intel CPUs.
22:28:37 <Yoohoo999> ok
22:28:45 <Yoohoo999> i deduced that from the product page
22:28:52 <debdrup> VT-d is IOMMU.
22:29:04 <Yoohoo999> so bhyve supports this?
22:29:07 <LxGHTNxNG> is it different? or do they use the same instructions
22:29:20 <daemon> Yoohoo999, from the setup you are describing, it sounds like you would be better getting a freebsd VM or server and running linux on that wireless system
22:29:26 <debdrup> Yoohoo999: functionally identical from the point of view of the OS, as far as I know.
22:29:35 <Yoohoo999> good point
22:29:51 <CCFL_Man> Yoohoo999: well, this ain't linux. it's FreeBSD. you should just use windows and be done with it
22:29:57 <daemon> freebsd and wireless / webcams are not really a thing
22:30:02 <daemon> freebsd is better for servers and such
22:30:06 <debdrup> daemon: wemcams work fine.
22:30:12 <rtprio> my first freebsd box was a bunch of hand-me down parts, in a full tower case that was missing the cover
22:30:22 <debdrup> How do you think I've been participating in the last many FreeBSD devsummits?
22:30:28 <rtprio> some webcams work fine
22:30:33 <debdrup> Most webcams work fine.
22:30:35 <Yoohoo999> er, so yall wouldnt recommend a laptop freebsd setup
22:30:42 <debdrup> Yoohoo999: it depends.
22:30:46 <debdrup> Are you a FreeBSD power user?
22:30:47 <daemon> debdrup, fair point; but even so that does not excuse wireless :)
22:30:56 <Yoohoo999> no, im new to freebsd
22:31:05 <Yoohoo999> i saw it has a linux alternative
22:31:05 <debdrup> daemon: proprietary interfaces is why FreeBSD is lacking behind in that area.
22:31:09 <LxGHTNxNG> i used freebsd on my old hp elitebook 2760p, named schoenefeld
22:31:13 <CCFL_Man> daemon: FreeBSD is good with a lot of hardware. it's system agnostic and is not a "server os" or "desktop os"
22:31:18 <debdrup> Yoohoo999: then I wouldn't recommend it.
22:31:29 <daemon> CCFL_Man, but it really does better in a server type enviroment
22:31:32 <Yoohoo999> debdrup: ok
22:31:40 <LxGHTNxNG> i think the only thing which didn't work was bluetooth audio, and the touchscreen
22:31:41 <Yoohoo999> hmmmm
22:32:00 <debdrup> FreeBSD _can_ be used as a desktop OS.
22:32:03 <CCFL_Man> Yoohoo999 is one of those "linux users" akin to a windows user when linux required brains to use
22:32:03 <daemon> Yoohoo999, note, no one here is saying you should not get into freebsd, you can get vm's or dedicates all over the place
22:32:15 <Yoohoo999> im not a linux user
22:32:17 <CCFL_Man> daemon: it works great as a desktop too
22:32:36 <LxGHTNxNG> CCFL_Man: please don't be like this
22:32:41 <daemon> CCFL_Man, not in my opinion; but that is personal taste
22:32:43 <debdrup> Yoohoo999: I started out using FreeBSD in 2000, after having been a Windows user up until that point - s o it's possible.
22:33:11 <Yoohoo999> well, i also have a freebsd im trying to set up on my windows machine, but that crashes
22:33:26 <daemon> in a vm? or is that the dual boot one
22:33:31 <Yoohoo999> in a vm
22:33:34 <Yoohoo999> in virtualbox
22:33:42 <daemon> it works perfectly well in hper-v and virtualbox
22:33:45 <LxGHTNxNG> Yoohoo999: You should start with linux honestly. FreeBSD is promising for some who are new from Windows NT, but Linux derivatives are easier to work for those new to UNIX
22:33:53 <LxGHTNxNG> daemon: it should*
22:33:54 <Yoohoo999> ok
22:33:55 <CCFL_Man> Yoohoo999: ubuntu linux user, right?
22:33:56 <daemon> it does
22:34:18 <LxGHTNxNG> daemon: Should. Yoohoo999 is reporting it Does Not work for them.
22:34:25 <daemon> Yoohoo999, https://i.imgur.com/93OtAL4.png
22:34:28 <Yoohoo999> CCFL_Man: I'm not a dedicated linux user in any respect, I just use WSL2 a lot and want it to be separate from windows
22:34:31 <daemon> try hyper-v as a one off
22:34:33 <debdrup> LxGHTNxNG: instead of telling them to use something else, help them figure out the problem and solve it.
22:34:34 <LxGHTNxNG> Yoohoo999: Can you help us understand how "it crashes" in your virtualbox?
22:34:47 <Yoohoo999> sorry, lemme explain
22:34:48 <LxGHTNxNG> FreeBSD *is* *not* Linux.
22:34:58 <Yoohoo999> i know
22:35:21 <Yoohoo999> lemme recreate the virtual box error so i can give details
22:35:22 <LxGHTNxNG> debdrup: they are already overwhelmed with CCFL_Man disparaging them and calling them a linux user as an insurt.
22:35:40 <daemon> Yoohoo999, run it and take a screenshot alt-printscreen then paste it ctrl-v into imgur
22:35:44 <Yoohoo999> "linux users" deserve to be insulted
22:35:54 <daemon> lets no be rude now
22:36:02 <Yoohoo999> but calling someone a "linux user" who isn't is just rude
22:36:02 <LxGHTNxNG> Yoohoo999: No?
22:36:04 <daemon> every os has its strength
22:36:15 <CCFL_Man> the bummer is that earthworm does not compile without significant source code edits
22:36:25 <LxGHTNxNG> I used to be an anti-linux elitist for a while too
22:36:31 <CCFL_Man> is "linux user" an insult these days?
22:36:38 <daemon> I suppose we all did that at some point
22:36:39 <Yoohoo999> yes
22:36:43 <LxGHTNxNG> you seem to be using it as one ccfl
22:36:51 <Yoohoo999> due to reddit linux users all wear fedoras now
22:37:00 <LxGHTNxNG> Yoohoo999: how old are you?
22:37:05 <Yoohoo999> like 12
22:37:17 <daemon> and playing with freebsd, grats
22:37:31 <Yoohoo999> no, i just dont tell ppl personal info
22:37:34 <Yoohoo999> sorry
22:37:40 <LxGHTNxNG> I don't think I was that young when I first mucked with FreeBSD
22:37:41 <daemon> ok dokey
22:37:44 <Yoohoo999> cant convey sarcasm in irc
22:37:46 <LxGHTNxNG> your age is not personal info. ]
22:37:53 <Yoohoo999> what is it then?
22:38:00 <ixmpp> LxGHTNxNG, i mean, it is
22:38:01 <CCFL_Man> LxGHTNxNG: linux has it's place. the scientific software i use interfaces with hardware best on linux, particularly alsa audio
22:38:22 <LxGHTNxNG> dr shelton, get me the cyanide
22:38:27 <LxGHTNxNG> i'm out.
22:38:30 <CCFL_Man> and in embedded systems, linux is often a better choice to to hardware support
22:38:53 <ixmpp> and honestly, in most situations, linux has better hardware support
22:39:02 <Yoohoo999> I'll be honest I want to install DOS but can't because UEFI only computer
22:39:07 <ixmpp> i would use freebsd on my laptop if i could, i think i said as much earlier today
22:39:12 <daemon> you tend to build systems to have the support for open/free bsd now days
22:39:30 <debdrup> daemon: that's always been the case.
22:40:09 <daemon> debdrup, ~ back in the 4.x days it was not so bad (except sound cardS)
22:40:41 <daemon> where the heck do I remember ./MAKEDEV pcm0 from?
22:40:50 <daemon> or snd0
22:40:53 <daemon> to long ago -_-
22:40:54 <CCFL_Man> Deaygo5: i use freebsd to process scientific data through the terminal and x11 forwarding
22:41:16 <CCFL_Man> daemon: i mean
22:41:44 <CCFL_Man> ffmpeg work too
22:41:59 <daemon> ffmpeg + youtube-dl (awesome app) :)
22:42:04 <Yoohoo999> Anyway, with virtual box when I press "1: boot multiuser" it displays text and then ends with the text "trying to mount root from cd:9660:/dev/iso9660/13_1RELEASE...." before crashing
22:42:32 <CCFL_Man> sounds like a virtual box problem
22:42:34 <daemon> mount the ISO as a sata/IDE optical drive
22:42:35 <Yoohoo999> yep
22:42:53 <Yoohoo999> daemon: ok i willl
22:42:58 <daemon> you can use SCSI or w/e for the drives
22:43:06 <daemon> but make sure the optical media is old school mounted
22:43:31 <Yoohoo999> daemon: the iso is mounted as an ide optical drive
22:43:41 <daemon> then there is no reason it should not work
22:43:46 <Yoohoo999> dang
22:43:56 <Yoohoo999> does hypervisor work for windows?
22:43:56 <daemon> what host os is this?
22:44:02 <daemon> windows whaty
22:44:04 <Yoohoo999> host os is windows 11
22:44:04 <daemon> windows what#*
22:44:12 <daemon> type 'hyper-v' in start menu search
22:44:16 <daemon> and see if it finds anything
22:44:16 <Yoohoo999> almost as bad as windows 8
22:44:21 <daemon> 'hyper-v manager'
22:44:24 <daemon> in particulat
22:44:26 <daemon> in particular
22:44:37 <Yoohoo999> i dont know why ms discontinued win7 support, it was so much better
22:45:01 <daemon> https://i.imgur.com/g4fzxpw.png
22:45:02 <daemon> ^
22:45:05 <daemon> if you see that
22:45:18 <daemon> you have hyper-v enabled which may upset virtualbox
22:45:25 <Yoohoo999> ok
22:45:35 <Yoohoo999> i dont see that
22:45:51 <daemon> that should be totally fine
22:46:09 <daemon> are you sure your system supports any form of virtulization
22:46:16 <Yoohoo999> virtual machine platform is enabled in windows features
22:46:18 <daemon> can you boot anything else; like gentoo etc
22:46:30 <Yoohoo999> i've booted windows 95 and ms-dos 6.0
22:46:38 <daemon> that does not count
22:46:43 <Yoohoo999> damn
22:46:52 <Yoohoo999> uh, no, nothing else
22:47:02 <daemon> try boot ubuntu, gentoo, debian; anything
22:47:15 <daemon> something not in dosbox
22:47:23 <daemon> because virtualbox should be able to handle freebsd with zero problems
22:47:38 <Yoohoo999> when i booted dos and win95 it was on virtualbox
22:47:43 <Yoohoo999> not dosbox
22:48:13 <Yoohoo999> would me having wsl2 enabled be a problem?
22:48:35 <daemon> that is not possible without hyper-v being there
22:49:01 <daemon> go here: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
22:49:11 <daemon> and look for 'Hyper-V Manager'
22:49:32 <daemon> if that exists create the VM there instead
22:53:10 <Yoohoo999> ya i don't have that
22:53:27 <daemon> ok no idea :D
22:53:36 <daemon> might be for #windows
22:53:50 <daemon> but im pretty sure WSL2 infers hyper-v be the tier-0 hypervisor
22:53:56 <daemon> which will impede virtualbox
22:54:33 <daemon> but I can tell you with 100% certainty that both hyper-v and virtual can run freebsd with zero issues
22:55:02 <Yoohoo999> what if i install hyper-v
22:55:06 <Yoohoo999> and then use that
22:55:14 <daemon> works for me
22:55:17 <Yoohoo999> ok
22:55:35 <daemon> get ready for a reboot and some beer time
22:56:36 <Yoohoo999> i have home edition
22:56:43 <Yoohoo999> so i cant just activate it
22:56:50 <Yoohoo999> how do i install it off the web
22:57:13 <daemon> I do not know enough about windows to actually answer you I just installed it (pro version)
22:57:22 <Yoohoo999> nevermind
22:57:26 <Yoohoo999> ill figure it out
22:57:29 <daemon> I honestly think you should head to #windows
22:57:34 <daemon> not being rude here
22:57:48 <daemon> but I think your home version of windows might have some limitations that I am not 100% sure about
22:57:56 <daemon> and certainly do not want to be wrong about
22:58:39 <daemon> I KNOW there is no reason virtualbox should have a problem with freebsd
22:58:49 <daemon> but I also know WSL2 infers hyper-v
22:58:55 <daemon> so ... yeah
22:59:33 <Yoohoo999> ok
22:59:38 <Yoohoo999> ill stop buggin yall
23:00:07 <daemon> until we know more ;)
23:00:14 <Yoohoo999> ;;)
23:31:37 <debdrup> https://www.freshports.org/games/lbreakouthd/ ooo
23:31:39 <VimDiesel> Title: FreshPorts -- games/lbreakouthd: Breakout-style arcade game