vermaden

Not sure about NetBSD - but FreeBSD does WINE really well.

Details:

- https://vermaden.wordpress.com/2020/10/14/oldschool-gaming-o...

The details are in other article I linked to - here:

- https://vermaden.wordpress.com/2026/01/18/200-mb-ram-freebsd...

Seems that zVault 'did not make it' - https://zvault.io/ - even the page is gone now.

Lets hope FreeCORE will make it longer.

Some comparison between Linux based TrueNAS SCALE and FreeBSD based TrueNAS CORE here:

- https://vermaden.wordpress.com/2024/04/20/truenas-core-versu...

Regards,

vermaden

Its both actually.

This is strictly the FreeBSD part:

    freebsd # gpart backup ada1 | gpart restore nda0
    
    freebsd # gpart backup ada1 | gpart restore nda1

The ZFS part comes later :)

Regards,

vermaden

The same article for FreeBSD:

- Install FreeBSD in defaults with Auto (ZFS) option.

- Do not thing more.

- You are resilient for power outages.

Regards,

vermaden

Cold migration.

Stop machine, transfer VM to other host, start machine.

Did the fixed [ENTER] (or double-click) in 'Save as...' dialog finally?

> macOS userland tools on FreeBSD kernel

I do not have anything against NextBSD - but that 'macOS userland tools on FreeBSD kernel' term sounds as stupid as it can - knowing that Apple pulled FreeBSD userland as part of creating Mac OS X :D

Which generally means: 'FreeBSD userland tools on FreeBSD kernel' ...

No ZFS no problem :)

Nope.

    frankenpad25 vermaden ~ % uname -prism
    FreeBSD 14.4-RELEASE-p6 amd64 amd64 GENERIC
    
    frankenpad25 vermaden ~ % uptime --libxo=json | jless | jq
    {
      "uptime-information": {
        "time-of-day": "12:50PM",
        "uptime": 790654,
        "days": 9,
        "hours": 3,
        "minutes": 37,
        "seconds": 34,
        "uptime-human": "9 days,  3:38",
        "users": 15,
        "load-average-1": 2.72,
        "load-average-5": 2.54,
        "load-average-15": 2.00
      }
    }

TrueOS does not exists anymore.

Try GhostBSD - it now comes with XLibre X11 and ZSH by default.

Sure.

2011:

- W520/T520 (maximum resolution: 1920x1080)

- T420s (maximum resolution: 1600x900)

- X220 (maximum resolution: 1366x768)

2012:

- W530/T530 (maximum resolution: 1920x1080)

- T430s (maximum resolution: 1600x900)

- X230 (maximum resolution: 1366x768)

2018:

- T480 (maximum resolution: 1920x1080 or more)

2020:

- T14 GEN1 (Intel) (maximum resolution: 1920x1080 or more)

- T14 GEN1 (AMD) (maximum resolution: 1920x1080 or more)

Newer models also work like the light ThinkPad X1 Carbon GEN5/GEN6/GEN7/GEN8/... for example.

The good thing about T530 (and T520) is that You can put there the same Quad Core CPU that W520/W530 has :)

I own these and they also work great with FreeBSD:

ThinkPads:

- W520/W530/T520/T530/X220/X230/T420s

- T480

- T14 GEN1 (Intel)

- T14 GEN1 (AMD)

I needed to replace MediaTek WiFi card on T14 (AMD) into some Intel WiFi one.

Hope that helps.

Regards,

vermaden

No one prevents You from installing Linux in a Bhyve VM and running Docker there.

Overhead of FreeBSD Bhyve Hypervisor is about 0.5% (measured in benchmarks) so You loose nothing.

Here You have easy and complete jumpstart into Bhyve in FreeBSD:

- https://vermaden.wordpress.com/2023/08/18/freebsd-bhyve-virt...

Regards, vermaden

For the record - just tested it on 15.x and `/usr/local/share/wine/pkg32.sh` works well.

By the way - does 32bit packages 'problem' for WINE has been resolved on 15.x series?

On 14.x and older versions WINE brings `/usr/local/share/wine/pkg32.sh` to keep 32bit packages for WINE32 ... but 15.x does not build 32bit packages anymore ...

I also regret that change.

Big downgrade after moving to Linux:

- https://vermaden.wordpress.com/2024/04/20/truenas-core-versu...

Manufacturer/vendor did not provided open source driver with real freedom license (BSD/MIT/...) or documentation on which the driver could be written ... this is the result ... and its still better to overcome a problem in any way then to NOT overcome it at all ... and this driver is just a code - people can look at it and improve it.

    > (are those different?)

Its the same thing - just different naming.

    > I'm running FreeBSD because I prefer it over Linux.

Me too but there are things that will not be ported (at least soon) anyway ... that is where Linux Compat Layer helps. Even simple watching movies with DRM bullshit (Widevine) or using a Brave browser that is not in the FreeBSD Ports ... or running Linux games ... or CUDA workaround ... and no NopeVidia will not provide official CUDA support anytime soon.

Also please remember that entire The Matrix (1999) movie was rendered [1] on FreeBSD machines in Linux Compat Layer because the software used to do that was not natively available on FreeBSD an yet it sill run faster on FreeBSD in Linux Compat Layer then natively on Linux. Let that sink in.

Even today [2] playing Linux games in Linux Compat Layer is faster then natively on Linux - with more FPS and more 'stable' gameplay.

Hope that helps.

[1] https://freebsd.org/press/press-rel-1/

[2] https://youtube.com/watch?v=lK6eRbz9DkM

Thanks.

Me too brother, me too.

I modified the article to copy the keytab using scp(1) instead.

I hope I was clear enough that credit for the solution goes to Christian Hofstede-Kuhn (Larvitz).

I treat my blog also as a place where I keep and maintain my FreeBSD documentation/information.

So there are several motivations for this:

- Keep and maintain personal version with more code snippets that I can copy/paste fast.

- More detailed commands and outputs.

- Some additional improvements that may be useful – like local console login.

Hope that helps.

> Break free from Google

Looks inside.

Only Google phones are supported.

Curtain drops ...

Good point - gonna add a notice about that - thank You.

I also covered Keycloak on FreeBSD in the past - here:

- https://vermaden.wordpress.com/2024/03/10/keycloak-on-freebs...

Hope that helps.

Regards,

vermaden

What I expected - that if I would want to install Openbox - then Xorg will be forced.

I typed:

    # pkg install xlibre 

... and X11 XLibre implementation installed and Openbox installed properly and 'xorg' packages was not forced.

The binaries of XLibre still have the same old 'Xorg' names like 'Xorg' is the server binary name (not 'XLibre') and xinit(1) is still xinit(1) ...

But if you already have 'xorg' package installed and you would like to install 'xlibre' package then there would be conflicts as they install file into the same places - and often with the same names.

Hope that helps.

Thank You :)

    > Do the same for X!

I kinda did ... but for RAM usage and not disk space.

Details here:

- https://vermaden.wordpress.com/2026/01/18/200-mb-ram-freebsd...

Please read entire article (or at least skim read it) because I also cover that part :)