Search results

Exactly. Because of this, for example, gpart has lenovofix attribute for irregular (mostly on Lenovo PCs) firnwares (basically on legacy boot with MBR scheme, though). Boot codes related with ZFS implements codes for non-read-compatible attributes, but it's a filesystem driver, not any of devide...

A simple and humble question. Is CSM (aka legacy boot support) enabled on your UEFI firmware config? If so, does anything change when you disable it? Possibly, some buggy firmwares could apply the same limits, including LBA pointer sizes, as legacy (aka BIOS) boot, which cannot boot over 2TB.

In many cases, FreshPorts is helpful. If you don't want searching there (doesn't support ports origin format, so quite noisy in some cases), you can directly access info for specific port like https://www.freshports.org/x11-wm/picom/ for x11-wm/picom. Unfortunately, for x11-wm/picom, message is...

FYI: I made /usr/local/etc/poudriere.d/options as a symlink which points to /var/db/ports directory to share configrations between bare metal builds and poudriere.

Not sure they're related, but possibly. x11-servers/xorg-server: Add upstream patch for xkbcomp directory 278204

Found this. Doesn't seem to be FreeBSD-specific. I myself was not bitten by this, as I already had devel/dconf-editor installed. should depend on dconf-editor

Maybe I've overlooked, but did you try, for example for nvme0, nvmecontrol logpage -p 1 nvme0? Errors on NVMe cards would usually logged to page 1. See nvmecontrol for details. Example for a card without error:

Found 2024Q2 branch is created. Corresponding annoucement is here. Note that preparation of pkg repo would take a fair amount of time due to toooo heavy ports like www/chromium and so on.

It's worth tracking freebsd-ports ML. Sometimes there are some show-stoppers.

A bit paranoid, but intentionally quote the commit messages, not to confuse future visitors. This is NOT BECAUSE FreeBSD IS AFFECTED. Note that this MFC target is only for stable branches (stable/14 and stable/13), as xz 5.6.0 is not yet MFS (Merge From Stable)'ed into any releng branches, thus...

So it would malfunction or crash without alerts. If there's ECC or something alike, it would be able to keep on running, alerting for error and suggest replacing.

In the introduced thread, thus FreeBSD is not affected. Related post at freebsd-security ML, introduced by Ed Maste on Mastodon.

I believe any apps which requires learning to "use" is not at all worth using in Windoze world. I feel notepad does not require learning to use. ;) (Excluding data, programs, ... created/edited on it.) There's so many "not for use on Windoze" apps, though.

Just a FYI: I cannot recall what actually was, but some ports failed to build when I disabled one of the default option which pulls in unwanted-for-me ports. This seemed to be that there were some implicit dependencies on ports pulled in by disabled option. For these cases, drop the option and...

Simple and dumb question. Is the partition actually formatted? Isn't it just a partition (in FreeBSD world, slice for MBR scheme) is created? Maybe the partition goes into /dev/msdosfs/ if it has any of proper *FAT* partition type.

No. For MBR scheme, exFAT uses the same partition type as HPFS and NTFS, 0x07 (0x17 for hidden partition). For FAT32LBA, partition type is 0x0C (0x1C for hidden partition). FAT32LBA means FAT32 with LBA addressing (in contrast with CHS addressing). See here for details.

And maybe recent lang/gcc* with LTO_BOOTSTRAP enabled? They're quite CPU/Memory/tmp intensive. lang/rust with default option is quete heavy, too.

And would also affects whether ccache/sccache-overlay to be used or not. And if used, how much chache size is given. Note that sccache-overlay often behaves evil, with timeouts. But it would not the problem of sccache-overlay itlself, but poudriere[-devel]. Toooooo few timeouts for high loads...

Exactly. But users of Mate like me is still unhappy, as at least x11-fm/caja still depends on devel/gvfs. Offtopic here: gvfsd-trash should have way to disable on specified (via configuration file) directory and its subdirectories (of course, specifying / completely disallow it to work), or...

Even if you are NOT booting from ZFS pool, you should required to have zfs.ko in /boot/loader.conf[.local] if you want the pool auto-imported stably on boot (via rc.d scripts). So assuming you have zfs_load="YES" in your /boot/loader.conf[.local]. The kernel and in-tree modules are becoming...