GhostBSD IRC channel?

jgaz

I know Discord is all the rage these days, but it looks like there is also an IRC-based GhostBSD community on libra.chat. I'm curious why the GhostBSD website doesn't mention it. FreeBSD, upon which GhostBSD is based, has a huge following the same IRC server. It seems like hanging out in the same virtual watering hole would be useful. Am I missing something?

brianthehughes

It’s really quiet on irc. I hung there for about 6 months last year. Telegram has general and developer groups. IRC becomes just another narrow band communication channel. Just a few thoughts. I’m a fan of irc, nostalgic vibes of a simpler time.

vimanuelt

Telegram feels a bit like IRC, only with faces, colors, and the grace to fix our small mistakes. Yet both can grow quiet, with many watching and only a few speaking.

I’ve seen more real conversations take root on GitHub, where words become work and work becomes service.

ericbsd

@jgaz I used to be active on IRC, but with the lack of interaction, I have stopped being active there. I don't use IRC much, even though I have Quassel server set up on my TrueNAS system.

zephyrus

Hello everyone! 🙂

I think we should start a little experiment where a few of us find a common time slot and get together for a ₃₀ minute chat. Nothing too formal, just a handful of like-minded GhostBSD users hanging out and talking about whatever comes up.

Maybe we could start with once a month at a set time, see how it goes, and take it from there?

Would anyone be interested in trying this out?

vimanuelt

I really like the idea of an online meetup! 😊 I think using Jitsi could work better for most of us since real-time conversation makes communication easier and more natural — we can usually cover more in a 30-minute chat than through typing alone.

If we do decide to stick with text, Telegram might be simpler — plus, we can still share short voice messages there. I’m just not sure what the advantage of using IRC would be in this case, but I’m open to giving it a try!

How about we plan for 8:30 PM ADT (Canada) / 23:30 UTC?

zephyrus

vimanuelt
That time slot works but let's schedule this for next Sunday? I'm in Vancouver and your suggestion is a bit tight for today.
Let us know which medium would work best. I haven't used IRC since the 90s, still, I am OK if we start off simple and move to a more suitable platform when convenient.

vimanuelt

Perhaps I’m biased, but I’ve lost count for the friends I once chatted with on IRC who are no longer here. Sometimes, it feels like IRC became a kind of digital Death Note.

zephyrus

vimanuelt
You are right but many things became digital death notes.
I set up IRC and if you have time this coming Sunday,8:30 PM ADT (Canada) / 23:30 UTC, let's do it?

zephyrus

TODAY is the day! 🙂
I will be in the ghostBSD (FreeNode) IRC channel around 2:00 PM Pacific Time.

vimanuelt

I was online at 8:30 PM ADT / 23:30 UTC. I posted for comments, but it seemed only a few were around; mostly news hounds waiting for a morsel, not a conversation.

zephyrus

vimanuelt
I am sorry (really am), I screwed up. When I posted a few days ago, I completely forgot that we were invited for a Thanksgiving BBQ. f
Let's pick up the pieces and salvage this. I will drip in next Sunday at 4:30 PM Pacific Time / 8:30 PM your time.

brianthehughes

True IRC legends idle endlessly.

zephyrus

brianthehughes
Indeed!

I need to pick your brain. During our chat, you mentioned virtual machines. If you happen to run GhostBSD also as a VM, do you have network access? For some reason, I installed Virtmanager on CachyOS and there are issues with an inactive network. I also struggle to get a better then 1280x720 resolution.

If you have time tomorrow (same time as last time), we could have a quick IRC chat?

brianthehughes

zephyrus
In VirtualBox, I generally enable two network interfaces.

Host Only Network 192.168.56.*
This one provides access from the Host to the Machine but also between guest virtual machines on the host.
NAT 10.0.3.*
This one provides Internet to the guest virtual machines. In essence the Host acts like a router for the guest VMs.
Bridging -
I experimented with Bridging the guest and host network to enable my LAN addressing to show up in the guest virtual machine network but found performance to be inconsistent.

A core motivation was to NOT manually configure networking on guest VMs but utilize DHCP. With an array of brian@brian-ghostbsd machines for the series of testing VMs I recognized that enabling the guests to show up in my primary LAN did not add value to existing monitoring and actually added a noisy mess of VMs into the 30-50 client devices that the home/property already supports.

vimanuelt

Yes, I see their is a need for a new feature. You can submit a feature request to have it implemented. ghostbsd/issuesissues/new?assignees=&labels=feature&template=feature_request.yaml

# Treat virt-manager as QEMU. KVM vendor covers QEMU family.
  if [ "$hv" = "KVM" ] || [ "$gpu" = "qemu" ]; then
    setup_qemu
  else
    case "$gpu" in
      intel)  setup_intel ;;
      amd)    setup_amd ;;
      nvidia) setup_nvidia ;;
      scfb)   setup_scfb ;;
      unknown) setup_vesa ;;
      *) setup_vesa ;;
    esac
  fi

zephyrus

Clever detection logic. This one deserves a pull request plaque.

vimanuelt

s/their/there
:-)

zephyrus

Thank you @brianthehughes

Two days ago, I did the unthinkable and installed W11 Pro on my laptop. Then Virtualbox, and GhostBSD. No issues. I can even go fullscreen (3440 x 1440) and drag content from host > guest.

If you have time, we can chat some more about "this and that" in the ghost hangout 😉