ain and handled separately.
NOTE: I've not checked any context but main. But it may well
be that 14.3-STABLE's PkgBase has some similar issues to what
main has.
===
Mark Millard
marklmi at yahoo.com
g the likes, of, for example, llvm, including the likes
of 20 -> 21 and such? (More generally: Update some contributed
materials that are not normally security updates but tend to get
updates over time, even if not much else changes part of the
time?)
===
Mark Millard
marklmi at yahoo.com
IRPREFIX
changes.
That leads me to expect that it is really setting up overall
use of .MAKE.META.IGNORE* variables that you want to learn about,
with SB_OBJROOT use just being a (new) smaller detail involved in
that.
Sound right?
> Thanks
>
>> Simon J. Gerraty escreveu (terça, 13/05
I normally expand the likes of kernel.txz somewhere
(empty directory) and then mv its boot/kernel to a
/boot/NEWuniqueNAME . Similar issue for
kernel-dbg.txz for its paths involved, matching
NewuniqueNAME . Then I use the name for booting
that specific kernel.
My wording does not get into using zfs to advantage
or the like. [I only use ZFS on the biggest system
configuration (RAM, media capacity, media speed,
FreeBSD-cpus count, and cpu speed combination).]
> Normally, not a problem. Simply rebuild install(1)
> with -static added to CFLAGS. Unfortunately, this
> leads to a bunch of linker errors about relocations
> and rebuilding a few libraries wtih -fPIC.
===
Mark Millard
marklmi at yahoo.com
“comconsole”) if the
/usr/share/man/man8/loader_simp.8.gz: console variable, or set it to serial
console (“comconsole”) if the
/usr/share/man/man5/loader.conf.5.gz: console (“vidconsole”)
“comconsole” selects serial console,
vs. the lack of any reference to eficom:
# man -K efi
WiFi NIC driver
wifi-firmware-mt7601u-kmod-20241017.1500043_2 Firmware modules for the mt7601u
(mt7601u) WiFi NIC driver
wifi-firmware-rtw88-kmod-20241017.1500043_2 Firmware modules for the rtw88
(rtw88) WiFi NIC driver
wifi-firmware-rtw89-kmod-20241017.1500043_2 Firmware modules for the rtw89
(rtw89) WiFi NIC driver
Adding such a package somewhat later after installing
FreeBSD-base, when FreeBSD-base happens to have been
updated between, could be problematical.
===
Mark Millard
marklmi at yahoo.com
On Jun 24, 2025, at 20:08, Mark Millard wrote:
> [This is based on what I eventually noticed in the material
> of my reply to a different message on freebsd-current .]
>
> Modern https://cgit.freebsd.org/src/blame/sys/sys/param.h has:
>
> #define __FreeBSD_version 150004
On Jul 27, 2025, at 15:00, Mark Johnston wrote:
>
> On Sun, Jul 27, 2025 at 02:26:29PM -0700, Mark Millard wrote:
>> I tried a poudriere(-devel) bulk -Ca on the amd64 system that
>> I have access to and a package build used up much of the
>> RAM+SWAP == 704 GiBytes befor
On Jul 27, 2025, at 15:25, Mark Millard wrote:
> On Jul 27, 2025, at 15:00, Mark Johnston wrote:
>>
>> On Sun, Jul 27, 2025 at 02:26:29PM -0700, Mark Millard wrote:
>>> I tried a poudriere(-devel) bulk -Ca on the amd64 system that
>>> I have access to and a
t such paths work in my
context.
===
Mark Millard
marklmi at yahoo.com
bug builds panicking
before.) The more timely package distributions would
help with having more timely security updates available
for main-amd64 packages as well.
Odd idea relative to the just above?:
Something for beefy17 to be involved in when it stops
being the port-package builder for main-i386?
oice between a thing that works for users, or something that *can*
> work for users but comes with a bunch of footguns that they need to avoid,
> I’d pick the former.
>
> David
>
> [1] I’ve noticed on fresh installs, the default shell no longer has working
> persistent history, which is a *big* POLA violation, if people want to
> complain about something.
>
===
Mark Millard
marklmi at yahoo.com
^~~
/wrkdirs/usr/ports/devel/llvm13/work/llvm-project-13.0.0.src/flang/runtime/misc-intrinsic.cpp:50:27:
note: insert an explicit cast to silence this issue
std::size_t resultBytes{size * elementBytes};
^~~
2*1378 == 2756 total to also have a separate one for
stable/13 in, say, /usr/fbsd/stable-13-shallow/ .
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org
On 2021-Jan-24, at 23:37, Mark Millard wrote:
>
>> How cat one track multiple branches with git without keeping entirely
>> separate trees?
>
> There are multiple possibilities here and it is not
> clear which you are hoping for.
>
> A) You could be trying to
names like main-armv7 ,
main-armv6 , main-mips , or main-mip64 . So I assume
that those are not being experimented with yet.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
f . . .
(So if there was a problem about a month ago, there may be another
problem as well as the above that was something else, the above just
happens first now.)
Looks like emulators/virtualbox-ose-kmod needs to track the kernel
change(s).
===
Mark Mill
pears to be the same type of "UNEXPECTED
SOFT UPDATE INCONSISTENCY" issue on an old
2-socket/2-cores-each PowerMac G5 powerpc64
configuration that was running main from after
5cc52631b3b8 .
So, in this case, I do not expect that the problem
is special to Ryzen or related CPUs.
===
Mark Mill
On 2021-Jan-23, at 21:37, Mark Millard wrote:
> On 2021-Jan-22, at 01:45, Mark Millard wrote:
>
>> Given an already built, installed and booted system version, I've
>> noted a big difference for META_MODE in 2 rebuild contexts (no
>> source updates involved
8 or 7 growfs
related activity being involved might avoid later getting cylinder
checksum failure notices.
I hope this proves of some help, but, if it is not, I'm unlikely
to have more information, sorry.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
44523-e124d7d5fc88
GENERIC-NODBG amd64 amd64 1400003 143
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To uns
BSDmacch 14.0-CURRENT FreeBSD 14.0-CURRENT mm-src-n244686-c1845d00f818
GENERIC-NODBG arm64 aarch64 144 144
and had no troubles doing so.
The other systems will all be updated to be based on
the 3acea07c1873 source code vintage.
===
Mark Millard
marklmi at yahoo.com
( dsl-on
a context that supplies the "?h=stable/12&".
Repeating with the one that has "?h=stable/12&" shows stable/12
in the upper right and copy/ptase of the commit link show does
include "?h=stable/12&" text. Further activity from there
continues to have the text
as it saying
"main" in the upper right when what was being looked at was
from stable/12 after it was branched (or some other such
mis-matched example) and that he was indicating that the
mismatches are misleading, especially if one does not know to
expect them.
Part of the issue is th
0004
But this is not a new thing, more of a "still true"
thing.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-curr
So I need to find such a drive another way, something
I was not even trying to do.
That answers my question. Thanks.
Mark
>> On Sat, Feb 13, 2021, 4:41 PM Mark Millard via freebsd-current
>> wrote:
>> I plugged in a new Optane and booted FreeBSD on the
>> ThreadRipper 1
On 2021-Feb-13, at 17:38, Warner Losh wrote:
> On Sat, Feb 13, 2021, 6:36 PM Mark Millard wrote:
>
> On 2021-Feb-13, at 16:40, Warner Losh wrote:
>
> > Are you aware of gpart create?
> >
> > Warner
>
> From which I derive that I had an implicit, incorrec
well, core-avx2, broadwell,
skylake, skylake-avx512, skx, cascadelake, cooperlake, cannonlake,
icelake-client, icelake-server, tigerlake, knl, knm, k8, athlon64, athlon-fx,
opteron, k8-sse3, athlon64-sse3, opteron-sse3, amdfam10, barcelona, btver1,
btver2, bdver1, bdver2, bdver3, bdver4, znver1, zn
On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote:
> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
>> On 2021-Feb-13, at 16:40, Warner Losh wrote:
>>
>>> Are you aware of gpart create?
>>>
>>> Warner
>> From which I derive
On 2021-Feb-16, at 02:22, Harry Schmalzbauer wrote:
> Am 16.02.2021 um 11:08 schrieb Mark Millard:
>> On 2021-Feb-16, at 00:48, Harry Schmalzbauer wrote:
>>> Am 14.02.2021 um 02:36 schrieb Mark Millard via freebsd-current:
>>>> On 2021-Feb-13, at 16:40, Warner Lo
-ports/2021-February/120154.html
Steve Kargl:
https://lists.freebsd.org/pipermail/freebsd-ports/2021-February/120298.html
https://lists.freebsd.org/pipermail/freebsd-ports/2021-February/120314.html
(The last for Steve K. is about how solved.)
But I cannot not tell if there is a common cause or a co
release/release.sh would have to contribute
as a side effect of its prior use in some way for that
sequence, if I understand right.
>
> On Tue, Feb 16, 2021, at 12:20 PM, Mark Millard wrote:
>> There are other reports of a:
>>
>> pkg: Warning: Major OS version upgrade detec
BSD_version
-#define__FreeBSD_version 110
+#define__FreeBSD_version 130
#include
#include
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists
rc) mm-src snapshot for mm's patched build in git
context.
3acea07c1873 (pure-src) Restore the augmented strlen commentary
FreeBSD FBSDFHUGE 14.0-CURRENT FreeBSD 14.0-CURRENT mm-src-n244686-c1845d00f818
GENERIC-NODBG amd64 amd64 144 144
===
Mark Millard
marklmi at yahoo.com
( dsl-onl
On 2021-Feb-16, at 15:37, Mark Millard wrote:
> On 2021-Feb-16, at 11:49, Brandon Bergren wrote:
>
>> It looks like there were recently some fixes to release.sh, that just got
>> backported to 13. I wonder if the problem is the packages themselves being
>>
On 2021-Feb-17, at 01:29, Hans Petter Selasky wrote:
> On 2/17/21 1:58 AM, Mark Millard via freebsd-current wrote:
>> stand/kshim/bsd_kernel.h has its own define of __FreeBSD_version and
>> seems to have last had it changed in the main branch as shown below.
>> Is it as
On 2021-Feb-17, at 11:44, Kyle Evans wrote:
> On Tue, Feb 16, 2021 at 7:29 PM Kyle Evans wrote:
>>
>> On Tue, Feb 16, 2021 at 7:23 PM Mark Millard via freebsd-current
>> wrote:
>>>
>>> I historically on occasion have done something like:
>>>
context I'm using for this:
# sysctl -ad | wc
11153 57922 604736
# sysctl -a | wc
13080 29457 449667
So: not a trivial amount of material.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-cu
natives [ACPI-fast(900)
i8254(0) TSC-low(-100) dummy(-100)] failed to make a
usable environment.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org
On 2021-Mar-5, at 17:35, Mark Millard wrote:
> Yasuhiro Kimura yasu at utahime.org wrote on
> Fri Mar 5 23:34:59 UTC 2021 :
>
>> From: Konstantin Belousov
>> Subject: Re: Waiting for bufdaemon
>> Date: Fri, 5 Mar 2021 22:43:58 +0200
>>
>>> My b
rc, main) [PowerPC] Fix AP
bringup on 32-bit AIM SMP
FreeBSD FBSDmacch 14.0-CURRENT FreeBSD 14.0-CURRENT mm-src-n245316-e48a1c379bfc
GENERIC-NODBG arm armv7 145 145
The host system reports:
# ~/fbsd-based-on-what-freebsd-main.sh
merge-base: bad9fa56620eb82395c5ab66d300e91a0222dde2
merge-base
On 2021-Mar-9, at 15:39, Mark Millard wrote:
> After using poudriere to build ports for native cortex-a72
> on the MACCHIATObin Double Shot (and similarly for
> cortex-a57 on the OverDrive 1000) I attempted to do my
> usual bulk build targeting cortex-a7 via poudriere-devel:
>
On 2021-Mar-9, at 17:18, Mark Millard wrote:
> On 2021-Mar-9, at 15:39, Mark Millard wrote:
>
>> After using poudriere to build ports for native cortex-a72
>> on the MACCHIATObin Double Shot (and similarly for
>> cortex-a57 on the OverDrive 1000) I attempted to d
LL 4 --
83316 100123: #4(0x1,0x403ef000,0x2e)= 46 (0x2e)
-- UNKNOWN FreeBSD32 SYSCALL 542 --
83316 100123: #542(0xcd54,0x0) = 0 (0x0)
-- UNKNOWN FreeBSD32 SYSCALL 2 --
83842 100199:
83316 100123: #2()
On 2021-Mar-9, at 19:17, Mark Millard wrote:
[My only testing context for this has been main, not 13.0.
But it might be a 13.0 worry.]
> Using the quickest to so-far-reliably-fail type of example from
> another thread I used truss to see what happens, here filtered
> down to two proce
On 2021-Mar-9, at 21:11, Mark Millard wrote:
> On 2021-Mar-9, at 19:17, Mark Millard wrote:
>
> [My only testing context for this has been main, not 13.0.
> But it might be a 13.0 worry.]
>
>> Using the quickest to so-far-reliably-fail type of example from
>> ano
On 2021-Mar-9, at 22:00, Mark Millard wrote:
[Trying to be timely about reporting new information
because of 13.0 not having much time left.]
> On 2021-Mar-9, at 21:11, Mark Millard wrote:
>
>> On 2021-Mar-9, at 19:17, Mark Millard wrote:
>>
>> [My only testing c
On 2021-Mar-10, at 10:09, Olivier Houchard wrote:
> On Tue, Mar 09, 2021 at 03:39:42PM -0800, Mark Millard via freebsd-arm wrote:
>> After using poudriere to build ports for native cortex-a72
>> on the MACCHIATObin Double Shot (and similarly for
>> cortex-a57 on
-r--r-- 1 root wheel 26552108 Apr 9 07:39:21 2021 kernel.txz
# ls -Tla /usr/freebsd-dist/
ls: /usr/freebsd-dist/: No such file or directory
NOTE: creating /usr/freebsd-dist/ with a copy of the MANIFEST
file in it was enough to get past this issue: it is doing
Archive Extraction now.
===
Mark Mi
ng / writable at this
stage either.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
on would be more independent of dates possibly
being touched on the file server and would make time ordered
finding of things (such as for build-less approximate bisecting)
far more reasonable.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
__
j/DESTDIRs/13_0R-CA7-for-chroot/var/db/etcupdate/
I have not checked on if "etcupdate build" has a similar issue
vs. not.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing
On 2021-Apr-25, at 08:14, Graham Perrin wrote:
> On 23/04/2021 08:39, Mark Millard via freebsd-current wrote:
>
>> [3]
>
>
> With regard to mounting ZFS file systems in single user mode
>
> What's currently footnote 3 will pr
ht notice and care about such differences.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send an
parated so the ZFS versioning is independent
between 13 and 14.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscr
[Just a resend: asking the question on the list
less than an hour before the UTC month change
might not be all that effective relative to
those that just web browse the list to read it.]
On 2021-Apr-30, at 16:21, Mark Millard wrote:
> Context . . .
>
> I've been experimentin
printf("\n%23s %012jx %012jx %08jx ", type,
+ (uintmax_t)map->md_phys, (uintmax_t)map->md_virt,
(uintmax_t)map->md_pages);
if (map->md_attr & EFI_MD_ATTR_UC)
printf("UC ");
===
Ma
On 2021-May-3, at 07:47, Ed Maste wrote:
> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
> wrote:
>>
>> Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and
>> /usr/obj/DESTDIRs/13_0R-CA7-poud/sbin/ping differ
>> Files /usr/obj/DESTDIRs/1
On 2021-May-3, at 10:51, Mark Millard wrote:
> On 2021-May-3, at 07:47, Ed Maste wrote:
>
>> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
>> wrote:
>>>
>>> Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and
>>> /usr
On 2021-May-3, at 19:26, Mark Millard wrote:
> On 2021-May-3, at 10:51, Mark Millard wrote:
>
>> On 2021-May-3, at 07:47, Ed Maste wrote:
>>
>>> On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current
>>> wrote:
>>>>
>>>
On 2021-May-3, at 21:27, Mark Millard wrote:
> On 2021-May-3, at 19:26, Mark Millard wrote:
>
>> On 2021-May-3, at 10:51, Mark Millard wrote:
>>
>>> On 2021-May-3, at 07:47, Ed Maste wrote:
>>>
>>>> On Thu, 29 Apr 2021 at 02:
On 2021-May-4, at 06:01, Ed Maste wrote:
> On Mon, 3 May 2021 at 22:26, Mark Millard wrote:
>>
>> But I'll note that I've built and stalled py37-diffoscope
>> (new to me). A basic quick test showed that it reports:
>>
>> W: diffoscope.main: Fuzzy-
On 2021-May-4, at 08:51, Mark Millard wrote:
> On 2021-May-4, at 06:01, Ed Maste wrote:
>
>> On Mon, 3 May 2021 at 22:26, Mark Millard wrote:
>>>
>>> But I'll note that I've built and stalled py37-diffoscope
>>> (new to me). A ba
[Just adding readelf -S info since it seems to show more.]
On 2021-May-4, at 10:01, Mark Millard wrote:
> On 2021-May-4, at 08:51, Mark Millard wrote:
>
>> On 2021-May-4, at 06:01, Ed Maste wrote:
>>
>>> On Mon, 3 May 2021 at 22:26, Mark Millard wrote:
>>
.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
line 293, in load
return loads(fp.read(),
File "/usr/local/lib/python3.7/codecs.py", line 504, in read
newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 18:
invalid start byte
Not exactly an obvious erro
[The first buidlworld is still in process. So while waiting . . .]
On 2021-May-4, at 10:31, Mark Millard wrote:
> I probably know why the huge count of differences this time
> unlike the original report . . .
>
> Previously I built based on a checked-in branch as part of
> m
; root at generic
> :~ #
>
> worth submitting a PR? or is bsdinstall legacy and I need to use some
> other method. I've not tried releng/12.2 yet.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
For reference:
# uname -apKU
FreeBSD CA72_4c8G_ZFS 13.0-RELEASE FreeBSD 13.0-RELEASE #0
releng/13.0-n244733-ea31abc261ff-dirty: Thu Apr 29 21:53:20 PDT 2021
root@CA72_4c8G_ZFS:/usr/obj/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
arm64 aarch64 1300139 1300
On 2021-May-4, at 13:38, Mark Millard wrote:
> [The first buidlworld is still in process. So while waiting . . .]
>
> On 2021-May-4, at 10:31, Mark Millard wrote:
>
>> I probably know why the huge count of differences this time
>> unlike the original report . . .
&
On 2021-May-5, at 02:47, Andriy Gapon wrote:
> On 05/05/2021 01:59, Mark Millard via freebsd-current wrote:
>> I had a:
>> # zfs list -tall
>> NAME USED AVAIL REFER MOUNTPOINT
>> . . .
>> zroot/DESTDIRs/13_0R-CA72
On 2021-May-4, at 20:26, Mark Millard wrote:
> On 2021-May-4, at 13:38, Mark Millard wrote:
>
>> [The first buidlworld is still in process. So while waiting . . .]
>>
>> On 2021-May-4, at 10:31, Mark Millard wrote:
>>
>>> I probably know why
On 2021-May-5, at 05:28, Mark Millard wrote:
> On 2021-May-5, at 02:47, Andriy Gapon wrote:
>
>> On 05/05/2021 01:59, Mark Millard via freebsd-current wrote:
>>> I had a:
>>> # zfs list -tall
>>> NAME USED AVAIL
19:52:14 2021
config:
NAMESTATE READ WRITE CKSUM
zroot ONLINE 0 0 0
da0p3 ONLINE 0 0 0
errors: No known data errors
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in e
On 2021-May-5, at 17:01, Yuri Pankov wrote:
> Mark Millard via freebsd-current wrote:
>> Context:
>>
>> # gpart show -pl da0
>> => 40 468862048da0 GPT (224G)
>> 40 532480 da0p1 efiboot0 (260M)
>> 532520 2
shot for mm's patched build in git
context.
merge-base: 7381bbee29df959e88ec59866cf2878263e7f3b2
merge-base: CommitDate: 2021-03-12 20:29:42 +
7381bbee29df (freebsd/main, freebsd/HEAD, pure-src, main) cam: Run all
XPT_ASYNC ccbs in a dedicated thread
n245444 (--first-parent --count for merge-base)
n to completion.
>>
>> When I retried after rebooting and scrubbing (no
>> problems found), the problem did not repeat.
>>
>> I do not have more information nor a way to repeat
>> the problem on demand, unfortunately.
>>
>> Details of the vintage of the
done
Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaemon-3' to stop... done
Waiting (max 60 seconds) for system thread `bufspacedaem
USB3 SSD was the only storage media present.
Port 3 apparently had the USB3 SSD boot media (the
same media that the FreeBSD loader got the kernel
from before the above).
Cutting power and starting over did not get the
problem again (so far).
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
0-CURRENT #1
main-n246854-03b0505b8fe8-dirty: Sat May 22 16:25:04 PDT 2021
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-dbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-DBG-CA72
arm64 aarch64 1400013 1400013
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
On 2021-May-22, at 22:16, Warner Losh wrote:
> On Sat, May 22, 2021 at 10:44 PM Mark Millard via freebsd-arm
> wrote:
> # mount -onoatime 192.168.1.187:/usr/ports/ /mnt/
> # diff -r /usr/ports/ /mnt/ | more
> nvme0: cpl does not map to outstanding cmd
> cdw0: sqhd:
On 2021-May-23, at 00:08, Mark Millard via freebsd-current wrote:
> On 2021-May-22, at 22:16, Warner Losh wrote:
>
>> On Sat, May 22, 2021 at 10:44 PM Mark Millard via freebsd-arm
>> wrote:
>> # mount -onoatime 192.168.1.187:/usr/ports/ /mnt/
>> # diff -r /us
On 2021-May-23, at 00:46, Mark Millard via freebsd-current wrote:
> On 2021-May-23, at 00:08, Mark Millard via freebsd-current at freebsd.org> wrote:
>
>> On 2021-May-22, at 22:16, Warner Losh wrote:
>>
>>> On Sat, May 22, 2021 at 10:44 PM Mark Milla
On 2021-May-29, at 01:15, Mark Millard wrote:
> On 2021-May-23, at 00:46, Mark Millard via freebsd-current at freebsd.org> wrote:
>
>> On 2021-May-23, at 00:08, Mark Millard via freebsd-current > at freebsd.org> wrote:
>>
>>> On 2021-May-22, at 22:16,
gging symbols found in /usr/obj/usr/src/amd64.amd64/usr.sbin/wpa/wp=
> > a_supplicant/wpa_supplicant)
So it was apparently a non-debug build without symbols, limiting
the information that is available.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
months available in
https://lists.freebsd.org/archives/ or show at least just:
• Other: [ Actives mailing lists ] [ Archives from mailman's time ]
when no prior months are available there.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
On 2021-Jun-6, at 13:25, Mark Millard wrote:
> Baptiste Daroussin wrote on
> Date: Sun, 6 Jun 2021 10:53:49 +0200 :
>
>> What has happended:
>> plan A: we migrated everything off mailman/pipermail seamlessly with
>> redirection
>> and so on. We patched the
. . .
Local branches configured for 'git pull':
mainmerges with remote main
releng/13.0 merges with remote releng/13.0
stable/13 merges with remote stable/13
So I'm not sure if I have anything that is messed up
or not. Nothing looks odd to me, other than the
new (next fetch will store in
remotes/freebsd)
vendor/openzfs/master new (next fetch will store in
remotes/freebsd)
vendor/openzfs/zfs-2.1-release new (next fetch will store in
remotes/freebsd)
. . .
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
ebsd-numerics ? (Or may be it happened and I just do not
remember. Or may be it would take special enabling of the
alternate ABI's use and not be a default configuration.)
(i386 only has "12", not "16", for its "80 bit", so 96 bits:
less pad.)
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
o the HoneyComb.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
On 2021-Jul-2, at 08:38, Chuck Tuffli wrote:
> On Thu, Jun 24, 2021 at 11:50 PM Mark Millard via freebsd-current
> wrote:
>>
>> I've given up on figuring any useful out for this example.
>> I've also not had a repeat so far.
>>
>> I
oot -g wheel -m 444 apmd.8.gz /mnt/usr/share/man/man8/
. . .
--- realinstall_subdir_usr.sbin ---
install: apmd.8.gz: No such file or directory
. . .
--- realinstall_subdir_usr.sbin ---
*** [maninstall] Error code 71
. . .
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
On 2021-Jul-4, at 19:59, Mark Millard wrote:
> The following commit seems to have proken installation
> by being incomplete:
>
> . . .
> committer Fernando Apesteguía 2021-06-30
> 07:57:51 +
> commit0a0f7486413c147d56808b38055c40c64cff61f5 (patch)
On 2021-Jul-5, at 13:29, Fernando Apesteguía wrote:
> On Mon, Jul 5, 2021 at 8:48 AM Fernando Apesteguía
> wrote:
>>
>>
>>
>> El lun., 5 jul. 2021 4:59, Mark Millard escribió:
>>>
>>> The following commit seems to
t; integration from the compile_commands.json, reuse LLVM's (and any other
> contrib things that use CMake) build system without having to recreate
> it, and be able to use ninja, to build.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
IC-NODBG-CA72
arm64 aarch64 1400032 1400032
after reaching this state. It behaves the same.
The text presented by:
https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-5E
does not deal with what is happening overall.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
On 2021-Sep-16, at 13:01, Mark Millard wrote:
> What do I go about:
>
> QUOTE
> # zpool import
> pool: zopt0
> id: 18166787938870325966
> state: FAULTED
> status: One or more devices contains corrupted data.
> action: The pool cannot be imported due to damag
On 2021-Sep-16, at 13:39, Alan Somers wrote:
> On Thu, Sep 16, 2021 at 2:04 PM Mark Millard via freebsd-current
> wrote:
> What do I go about:
>
> QUOTE
> # zpool import
>pool: zopt0
> id: 18166787938870325966
> state: FAULTED
> status: One or m
> j...@via.net
> 650-207-0372 cell
> 650-213-1302 office
> 650-969-2124 fax
>
>
>
>> On Sep 16, 2021, at 1:01 PM, Mark Millard via freebsd-current
>> wrote:
>>
>> What do I go about:
>>
>> QUOTE
>> # zpool import
>> pool:
1301 - 1400 of 1468 matches
Mail list logo
