Search results

With a run that's not dry, ten ports are ignored: root@mowa219-gjp4-zbook-freebsd:~ # grep ALLOW_MAKE_JOBS\= /usr/local/etc/poudriere.conf ALLOW_MAKE_JOBS=no root@mowa219-gjp4-zbook-freebsd:~ # sed -i '' s/ALLOW_MAKE_JOBS=no/ALLOW_MAKE_JOBS=yes/g /usr/local/etc/poudriere.conf...

FreshPorts lists files (without focusing on directories alone), for example:

I can't always blame the cats for wreckage when I'm too careless to lock the screen whilst I'm away from the nice, warm keyboard of a toasty ten-year-old ZBook. Sometimes it's just me asleep at the keyboard. Shift, and the two adjacent keys: Does NomadBSD count?

I do … Hint: -n for a dry run will not necessarily forewarn of things about which you would like to be warned. That's not to suggest that pkg-upgrade(8) is dumb. It's as good as what it's given by the end user. I learnt the hard way :)

Yes; <https://forums.freebsd.org/posts/547912> above was in 2021. From the manual page for make.conf: "… the list of ports you wish to rebuild every time the kernel is built." That's what I wanted, and src.conf was effective. I can't remember where or when I adopted the habit, but I know...

KODIR was mentioned in UPDATING in 2005: HTH

It can be, I mean, it did work for me …

True, if the user allows the generic zroot name for the pool. With a distinctively-named pool and a descriptively-named boot environment (1500025-013-base): % zpool get bootfs august NAME PROPERTY VALUE SOURCE august bootfs august/ROOT/1500025-013-base local %

freebsd-version -kru ; uname -aKU pkg -vv | grep -B 1 -e url -e priority – what are the details? Something might be missing from the beginning of that line. For reference: root@fourteen-pkgbase:~ # pkg provides /usr/local/lib/libpopt.so.0 Name : popt-1.19_1 Comment : Getopt(3) like...

Nope. The failure above was no problem, because I made the boot environment only temporarily active before the boot. root@mowa219-gjp4-zbook-freebsd:~ # history | grep 'bectl activate' | tail -n 3 1990 14:28 bectl activate -t 1500025-013-base 2010 17:02 history | grep 'bectl...

Incidentally, stable/14 has the same capability. splash(4) for FreeBSD-STABLE describes how to use the FreeBSD-provided red image of the orb. Never any show-stopper. https://forums.freebsd.org/threads/living-on-the-edge.92135/

Thanks, that's consistent with none for the mountpoint property, however (for example) zroot/ROOT/default would be mounted at: / – not under /boot

A custom splash screen with vt(4) and FreeBSD 15.0-CURRENT With a PNG that was probably too large: – but then boot does not proceed. No splash screen, and so on. With a smaller PNG (366.1 KiB): two frames from a screen recording Pre-vt 2008 (around five years before vt)...

Can you describe the file, or its path? Maybe relevant, from fsck_ffs(8) (for option -z): "… unused directory space. The cleared space includes deleted file names and name padding."

From which version, exactly?

According to groff_mdoc(7), a Bugs section should be used for blatant problems. No such section in bsdinstall(8). Probably relevant to parts of this topic (not the dual boot aspect): https://forums.freebsd.org/threads/installing-freebsd-auto-zfs-mbr-bios-missing-operating-system.87118/#post-588154

I found myself here via bug 212258, which (glancing at 267843) might have been overcome by events … Please, are you certain? For me, the boot environment is mounted at the root / of the file system (not under /boot). % bectl list -c creation | tail -n 7 1500025-006-base-ports - -...

On the other hand, IIRC (before I switched to pkgbase) I made minimal use of PORTS_MODULES because some modules made builds frustratingly slow. Nowadays I use poudriere-devel to build the modules.

Condensed: From src.conf(5) DESCRIPTION: src.conf may be a better place for GPU-related PORTS_MODULES such as x11/nvidia-driver-470 …