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

• 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
• no Internet access
• /etc/rc.firewall

2 more annotations...

• Re: Feb 19 meeting actions, discussion, notes, and recording
• Gleb Popov
• arrowd
• 05 Mar 2025
• Ed Maste
• wrote:
• 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
• bhyvemgr looks nice
• too simplistic
• 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
• much more like what we need
• https://invent.kde.org/sitter/karton/
• early stage
• general direction
• improve bhyve
• improve bhyve support in libvirt
• either writing it
• GUI frontend
• or chiming into Karton
• 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

• Popularity contest statistics for gnome-shell,kde-plasma-desktop

• Popularity contest statistics for gnome-panel,gnome-shell,kde-runtime,xfce4-panel,lxpanel,kde-plasma-desktop

• complexd 

   

   

               
• WIP
• A complex of daemons for FreeBSD implementing systemd/freedesktop D-Bus APIs required by desktop environments
• targeting FreeBSD

2 more annotations...

• HT and VHT testing for modern iwlwifi chipsets (notes about others)
• Bjoern A. Zeeb
• 28 Feb 2025
• rtw88/rtw89 and older iwlwifi chipsets all need more work
• modern iwlwifi chipsets will need a net80211 change for a clean solution which is currently hardcoed in LinuxKPI
• rtw88/rtw89 need LinuxKPI and net80211 changes
• older iwlwifi chipsets still need driver changes due to GPL-only code
• iwlwifi AX2xx or BExxx
• HW_CYRPTO
• test a first cut of HT20/40 and VHT20/40/80 (no 160 yet)
• loader.conf
• compat.linuxkpi.iwlwifi_11n_disable=0 compat.linuxkpi.iwlwifi_disable_11ac=0
• without the hw_crypto tunable
• it'll fail
• test that (independently) *first*
• If things work the thanks should go to The FreeBSD Foundation, if things don't work the problem reports go to me.
• Happy testing and a blessed weekend
• https://cgit.freebsd.org/src/commit/?id=2c44f1ff6935e93f7774e526f2f1ab0a2812eab5

16 more annotations...