• 07 Nov 2023
• Can you explain Xwayland to me using small words?
• used automatically when running x gui apps on a wayland compositor
• used automatically for things that won't run natively
• X server running as a Wayland client
• Environment variables
• force something to run natively or in XWayland

• equivalent of:

    
   
  • XQuartz on macOS / Cocoa
   
  • Xwin / Xming / Xceed on Windows
   
  • Xsdl on Android
   
  • DESQview/X on DOS
   
  • Xephyr on X11
   
  • Xnest on X11
• Xserver which runs (usually as a window)
• X and Wayland are Display Servers
• some programs that heavily rely on how X works won't work on Wayland
• a Wayland extension that runs a little X server
• a compatibility layer for the time being
• X.org server running with no root privileges
• Regular X11 uses your graphics hardware to render its canvas
• using XWayland,

  X11's canvas is Wayland

14 more annotations...

• 29 Jan 2025
• https://wiki.freebsd.org/PkgBase#setup
• /etc/rc.firewall
• no Internet access

2 more annotations...

• Re: Feb 19 meeting actions, discussion, notes, and recording
• arrowd
• Gleb Popov
• 05 Mar 2025
• wrote:
• Ed Maste
• The Foundation is investigating funding some libvirt work
• describe your initial experience with virt-manager/libvirt/bhyve
• bhyve to run a Windows guest completely in the background
• FreeRDP "seamless" mode for most apps
• Moonlight client for games
• moderate success
• serious drawback
• suspend/resume functionality (aka snapshots)
• hoping to bring Vitaly Gusev
• he was developing this feature
• configure bhyve networking in the same way as VirtualBox' "NAT" option
• no network interface or any configuration should be required from the host side
• bhyve running prevents other hypervisors
• like VirtualBox
• our user would need a neat GUI to create and run his own VMs
• too simplistic
• bhyvemgr looks nice
• sudo
• canonical approach for such tasks is to have a daemon running as root
• RPC protocol for non-root client applications
• contemporary desktop environments are using DBus as an RPC bridge and the Polkit framework to define and manage policies for actions requiring escalated privileges
• libvirt
• privileged daemon implementation, a D-Bus API and a GUI
• virt-manager
• too "advanced"
• unnecessary complexity
• patches for libvirt to upstream
• https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/JOZ26QFIU4O3YTDMV7E5JYMGDYC7DZ4H/
• allow configuring passthrough devices
• KDE Karton
• https://invent.kde.org/sitter/karton/
• much more like what we need
• early stage
• general direction
• improve bhyve
• improve bhyve support in libvirt
• or chiming into Karton
• GUI frontend
• either writing it
• improve virt-manager
• "reference" frontend implementation that gives a broader access to libvirt's APIs

45 more annotations...

• Oct 11, 2024
• man.4: Add .Sh HARDWARE for some wireless drivers for release notes
• iwlwifi.4 and rtw88.4 did not show up in the hardware list in the release notes for 13.4
• doc/website/tools/hardware-notes-processor.rb
• parses the .Sh HARDWARE section
• Reported by: re (cperciva), grahamperrin

4 more annotations...

• list the current state of devices supported and which firmware they need
• list is automatically generated based on a sysctl added to the iwlwifi driver