, not an absolute. I think what we are doing
isn't a problem for 99.999% of use cases.
On the rare occasions where I use sysinstall, I usually find that prompt
annoying... but I almost broke a CD drive once by ejecting the tray
with the enclosure's dust cover half closed.
DES
--
Dag-Erling Smørgrav - d
is device md, but mdconfig(8) will automatically load
the module, so you don't need it.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
is the memchr() that looks for
'\n' in the input buffer.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
Nathan Whitehorn nwhiteh...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
I'm not sure I understand what you mean (or rather, how it would
help the tinderbox). What *would* help would be an easy way to
determine, *before* trying to build it, whether a specific kernel
config
-specific scripting language, not a general-purpose one.
BTW, most of the Perl scripts we had were rewritten in C, not sed / awk.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
the index lists
only files, not exact positions. For anything other than fixed strings,
it reverts to agrep, but I assume (I haven't looked at the code) that if
the regexp has one or more fixed components, it uses those to narrow the
search space before running agrep.
DES
--
Dag-Erling Smørgrav - d
them to exclude
\n: /[^bar]/ becomes /[^bar\n]/, /./ becomes /[^\n]/, etc., and the
FSA will stop if it hits EOL before it reaches an accepting state.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http
Sean C. Farley s...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Aho-Corasick is not really a search algorithm, but an algorithm for
constructing a table-driven finite state machine that will match
either of the search strings you fed it. I believe it is less
efficient
Mike Haertel m...@ducky.net writes:
Dag-Erling Smørgrav d...@des.no writes:
You don't really need to isolate the containing line unless you have
an actual match, do you?
Theoretically no. However, suppose the pattern was /foo.*blah/.
The Boyer-Moore search will be for blah, since that's
b. f. bf1...@googlemail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
Does not seem to work properly is not a very useful statement. The
least you could do is provide an example.
I did provide an example, later in the same sentence that you quoted.
I forgot to answer this part
Dag-Erling Smørgrav d...@des.no writes:
No idea what causes it, but a quick grep (hah!) for qflag turns up the
following horror:
/* Find out the correct return value according to the
results and the command line option. */
exit(c ? (notfound ? (qflag ? 0 : 2) : 0
Can you all please tell me which revision(s) you were running before you
upgraded? Something like bzgrep 11.0-CURRENT /var/log/messages*
should do the trick.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http
O. Hartmann ohart...@zedat.fu-berlin.de writes:
r273800 was the last (obviously) working on one box, r273872 seems to
have the problem:
Are you sure? If I understand Manfred correctly, r273905 was running
fine for him.
DES
--
Dag-Erling Smørgrav - d...@des.no
blocks once
it's seeded, and reading 4096 bytes won't take noticeably longer than
reading 2048 bytes. But it should already be unblocked by then - this
is on shutdown, right?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing
Tomoaki AOKI junch...@dec.sakura.ne.jp writes:
Dag-Erling Smørgrav d...@des.no writes:
Manfred Antar n...@pozo.com writes:
Then for some reason /var started to being mounted mfs. [...] If
I have varmfs=NO and cleanvar_enable=NO everything works fine.
Not really. The default
Ian Lepore i...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
That means we're not getting enough entropy during early boot, or
we're underestimating the amount of entropy we're getting. We added
entropy harvesting to device_attach() about a year ago, which in
most cases
Ian Lepore i...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
I think you misremember. It is impossible to guarantee that the
system will always have enough entropy right from the start.
Servers, desktops and laptops will be fine, but embedded systems and
VMs might
still runs.
*Noticed that r273919 should fix above by your reply, backed out
Manfred's workaround [no other change] and rebooted, can't reproduce
the mfsvar problem anymore!
Yes, that was the idea.
DES
--
Dag-Erling Smørgrav - d...@des.no
. If you need more
time for review, please email me privately and I will make delay.
Please remember to bump __FreeBSD_version.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
, and
keeps the file descriptors open indefinitely.
I know this isn't really germane, but I just couldn't pass up a chance
to complain about HAL.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http
Dag-Erling Smørgrav d...@des.no writes:
Steve Kargl s...@troutmask.apl.washington.edu writes:
I'll try that tomorrow. But, I now know that this is related to using
hal from ports. If I comment out both enable_dbus and enable_hal in
/etc/rc.conf, the system works as I would expect (ie
Jung-uk Kim j...@freebsd.org writes:
A file seems missing. I worked around it like this:
sed -e 's/@ENABLE_DNSTAP@/0/' \
/usr/src/contrib/unbound/dnstap/dnstap_config.h.in \
/usr/src/contrib/unbound/dnstap/dnstap_config.h
Thank you, fixed.
DES
--
Dag-Erling Smørgrav - d...@des.no
was also a
bug in the server-side code (IIRC, one place where it printed only the
hardcoded version instead of the variable string). I'll try again.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.free
e of the few people who need HPN
and lack the CPU power to perform encryption at line speed.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, s
> security/krb5.
We switched from MIT to Heimdal at some point in the past for some
reason I don't remember. MIT and Heimdal are *not* interchangeable at
the source or binary level, so switching back is not trivial.
DES
--
Dag-Erling Smør
another reason why I still
haven't upgraded OpenSSH, but to the best of my knowledge, it is far
less intrusive than HPN.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
Julian Elischer <jul...@freebsd.org> writes:
> Bob Bishop <r...@gid.co.uk> writes:
> > Is removing HPN going to impact the performance of tunnelled X
> > connexions?
> yes if your rtt is greater than about 85 mSec
With an RTT of 85 ms, X is unusable with or wi
sn't
noticed this thread.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
rk, and the server was so old it didn't
> have AESNI and would soon be retired, using the NONE cipher sped up
> the transfer significantly.
In that scenario, you don't need ssh at all. Just set up rsyncd on the
backup server.
DES
--
Dag-Erlin
e with the
latest OpenSSH? And if HPN is so important to you, is there a reason
why you can't use the port?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
to the openssh-portable port, which has
them as a default option. I would also like to remove the NONE cipher
patch, which is also available in the port (off by default, just like in
base).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current
ell
workflow for OpenSSH and apply the output of that workflow to the source
tree instead of working entirely within the source tree.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mail
some spare cycles.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ou mean logging IP addresses instead of hostnames? Just turn off
UseDNS. It is off by default since 6.8.
If you mean adding IP addresses or hostnames to messages that don't
already have them, try suggesting it on the openssh-portable mailing
list (openssh-unix-...@mindrot.org).
DES
--
Dag-Erling Smør
accept changes to the old version that is
> currently in base?
No, why would they do that?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscrib
Willem Jan Withagen <w...@digiware.nl> writes:
> "Dag-Erling Smørgrav" <d...@des.no> writes:
> > Willem Jan Withagen <w...@digiware.nl> writes:
> > > Are they still willing to accept changes to the old version that
> > > is currently in base
EL 7 desktop at work and
FreeBSD 10 desktop at home).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd
NGie Cooper <yaneurab...@gmail.com> writes:
> Dag-Erling Smørgrav <d...@des.no> writes:
> > David Wolfskill <da...@catwhisker.org> writes:
> > > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped)
> > Did you find a solution? [...]
> htt
people are
reporting on freebsd-security@ are related. I vaguely recall hearing
that this had been traced to a pthread bug, but can't find anything
about it in commit logs or mailing list archives.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-curren
with that patch then, but we may have to include
some of the other recent commits to the vm_map.c, which seem (at a quick
glance) to be related.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/m
dvise() returns 22 on EINVAL.
That's how syscalls work.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Konstantin Belousov <kostik...@gmail.com> writes:
> Dag-Erling Smørgrav <d...@des.no> writes:
> > Maxim Sobolev <sobo...@freebsd.org> writes:
> > > Hi, while working on some unrelated feature I've noticed that at least
> > > those two system calls
Julian Elischer <jul...@freebsd.org> writes:
> what is the internal window size in the new ssh?
64 kB.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebs
Kevin Oberman <rkober...@gmail.com> writes:
> Dag-Erling Smørgrav <d...@des.no> writes:
> > Julian Elischer <jul...@freebsd.org> writes:
> > > what is the internal window size in the new ssh?
> > 64 kB.
> Are you sure of this?
Sorry, I was thinking o
ME}" != "${krb5ccuid}" ] ; then
if mv "${KRB5CCNAME}" "${krb5ccuid}" ; then
export KRB5CCNAME="${krb5ccuid}"
else
echo "Unable to rename krb5 credential cache" >&2
fi
fi
unset krb5ccuid
Slawa Olhovchenkov <s...@zxy.spb.ru> writes:
> Dag-Erling Smørgrav <d...@des.no> writes:
> > In the meantime, you can try something like this in .bashrc or
> > whatever:
> Imposible. For accessing .bashrc on kerberoized NFS need correct
> /tmp/krb5cc_.
/etc/p
ack a few years, and
fixed the bug before it affected you. No hard feelings?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
intended to reduce the impact of upstream
changes on existing systems.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "fr
installed. It's been running for ten minutes and has
printed over 90,000 lines, with no end in sight.)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
h no reverse dependencies:
# pkg query -e '%#r == 0' %n-%v
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd
opers, our friends, most of us want nothing to do with you. If
can't live with that, I'm sure you can figure out how to install Linux.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/
ains the code that loads the loader and
should not need updating.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to &
es,
Niclas, Warner and others with a century of combined experience will be
thrilled to see you succeed where they, by your account, have failed.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.or
blubee blubeeme writes:
> You seem to miss the point where the you avoid breaking the system for
> any users not on the bleeding edge.
You seem to miss the point where nobody is interested in anything you
have to say any more.
DES
--
Dag-Erling Smørgrav - d...@
is needed here.
(and libldns probably needs a version bump, but that won't affect this)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
; share ?
# pkg install -y misc/compat9x misc/compat10x misc/compat11x
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
stem. It may delete
files which have been obsoleted by changes you haven't yet built and
installed, to the point where you may be unable to build and install
those changes. In this particular case, it will, at the very least,
break ssh and svn /
Jung-uk Kim writes:
> I forgot to patch one more file, i.e., Makefile.inc1. Please try the
> attached patch instead.
Thanks, I missed that too.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
Rebecca Cran writes:
> After installing 12.0-BETA1, on the first boot I noticed a warning
> about $local_unbound_tls not being set properly.
Ah, I should probably have added it to /etc/defaults/rc.conf. Can you
do that (just set it to “no”) and let me know if it helps?
DES
--
Dag-
he cause, as
it shouldn't break arm32, where time_t *is* 64 bits wide, but it still
needs fixing. Are you getting the exact same error message as Michael?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https:/
Please try the attached patch. I expect it to fix i386. If it also
fixes arm32, all the better, although I don't quite see why it would.
DES
--
Dag-Erling Smørgrav - d...@des.no
Index: crypto/openssh/sshbuf-getput-basic.c
just i386. The quick fix is
to replace size_t with u_int64_t in sshbuf_get_passwd(), on line 513 of
sshbuf-getput-basic.c (with my previous patch applied). I have a full
patch in the pipeline.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org
f.
Then it's useless.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Yuri Pankov writes:
> There's apparently a bug in VMware Workstation NAT implementation,
> [...] The patch itself is attached.
Could you please open a differential and add me as reviewer?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-c
ed Hat does. Advise the customer to use a workaround
> until the other vendor fixes their code.
With respect, that's not your decision. It's mine.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.fr
would not be a viable piece
of software. Wishing they weren't needed is a waste of time and energy.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
devd's aware of. The only way to find out if it's supported is to call
the driver's identify method, which checks the cpuid and creates a
device instance for each reported sensor.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org m
domain setting, so it cannot handle email from cron,
periodic etc. where the recipient is just a user name (usually “root”),
and the devs were not willing to add that feature. I have email as far
back as 2015 on the subject.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Baptiste Daroussin writes:
> Dag-Erling Smørgrav writes:
> > [...] does not have a default domain setting, so it cannot handle
> > email from cron, periodic etc. where the recipient is just a user
> > name (usually “root”) [...]
> This has been fixed since. (not by me)
h a bogus length invokes UB.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Mark Millard writes:
> I'm not aware of there being other documentation for what
> is appropriate for setting up such for kyua runs.
https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test_image-head.sh#L69-L84
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Rainer Hurling writes:
> If I try to build world from todays c1b26df2972d with 15.0-CURRENT
> (main-n265063-e0752f431b01), it aborts with an error.
Either update your source tree or apply aca3bd160257, then build and
install libc before attempting buildworld.
DES
--
Dag-Erling Smørgr
ms to be a recent issue (less than 5 days).
> Hundreds of configure scripts now fail to run on 15-current due to
> this sed failure: [...]
Try adding ARCHLEVEL=scalar to CONFIGURE_ENV on one of these. If that
helps, yell at fuz@ :)
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
sudo make -C lib/libc install
then buildworld as usual.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
uilding libc. If that still
fails, just run buildworld; it will fail in libmagic as before but it
will have built libc before failing, and you can install libc and
restart the build.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
able for file) to fail.
This was fixed in aca3bd160257.
> I am trying to manually compile a working mkmagic and restart the
> build to get unstuck.
mkmagic is fine, just build and install libc.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
eems to give a retval of 1 inside
> certctl.
This only happens if a certificate is listed as both trusted and
untrusted, and I'm pretty sure the previous version would return 1 in
that case as well. Can you check?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Warner Losh writes:
> Do we support any compression on top of that? Has support for
> poudriere been added for it?
Yes (zstd) and no.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
le (of which there are 30k in the
ports tree) is only 200-250 bytes long, but it occupies 512 bytes on an
FFS filesystem, 1 kB in a tarball, and 4 kB on a typical ZFS filesystem.
Note that if the target system is FreeBSD 14 or newer, you can simply
mount the tarball (`sudo mount -rt t
ething wrong?
No, this is definitely something we want to support.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
o you have a FreeBSD branch with your patch applied?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
ches has so far built
2,285 packages without a hitch, whereas normally it would have
deadlocked after well before reaching 500 packages. I'll do another run
without the patches tomorrow just to be sure.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Dag-Erling Smørgrav writes:
> A kernel built from c47116e909 plus these two patches has so far built
> 2,285 packages without a hitch, whereas normally it would have
> deadlocked after well before reaching 500 packages. I'll do another run
> without the patches tomorrow just to be
Dag-Erling Smørgrav writes:
> Plot twist: c47116e909 _without_ the patches also appears to be working
> fine. The last kernel I know for sure deadlocks is b36f469a15, so I'm
> going to test cd25b0f740 and 28d2e3b5de.
c47116e909 with cd25b0f740 and 28d2e3b5de reverted deadlocks, see
Dag-Erling Smørgrav writes:
> c47116e909 with cd25b0f740 and 28d2e3b5de reverted deadlocks, see
> attached ddb.txt. I'm going to see if reverting only 28d2e3b5de but not
> cd25b0f740 changes anything.
c47116e909 with only 28d2e3b5de reverted also deadlocked, but in both
cases it
The attached script successfully deadlocks 9228ac3a69c4.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
#!/bin/sh
: ${n:=$(nproc)}
: ${pool:=zroot}
basefs="${pool}/zfsdl"
set -eu
zfs destroy -r "${basefs}" >/dev/null 2>&1 || true
zfs create -o com.sun:auto-snap
Mateusz Guzik writes:
> Given that the custom reproducer failed I think the most prudent
> course of action is to reproduce again with poudriere, but this time
> arrange to have all stacktraces dumped.
Why? What more information do you need?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Dag-Erling Smørgrav writes:
> I managed to geat a deadlock with 4e8d558c9d1c. Its predecessor
> 5ca7f02946 appears to be working. I'm going to try to come up with a
> more efficient way to reproduce the deadlock than running poudriere.
I wrote a script that creates multiple fi
a random victim
> and whatever the real culprit is deeper.
We already know the real culprit, see upthread.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
I will be removing OPIE from the main branch within the next few days.
It has long outlived its usefulness. Anyone still using it should look
into OATH HOTP / TOTP instead (cf. security/pam_google_authenticator).
https://reviews.freebsd.org/D36592
DES
--
Dag-Erling Smørgrav - d...@des.no
money, and
> those devices all have different threat/failure/admin models
> than simple paper.
Neither HOTP nor TOTP require dedicated devices. HOTP codes are
sequential and can be pre-generated and printed if that's what you
prefer.
DES
--
Dag-Erling Smørgrav - d...@des.no
ecurity/opie). You will have to manually add back the
pam_opie and pam_opieaccess lines in the relevant PAM policies.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
FreeBSD User writes:
> I tried to put the option
>
> WITHOUT_MODULE="an"
it's spelled WITHOUT_MODULES, cf. make.conf(5).
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
assword” upstream (and presumably in the port), while
PermitEmptyPasswords defaults to “no” both in FreeBSD and upstream,
cf. crypto/openssh/servconf.c (search for “permit_root” and
“permit_empty”).
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Tomoaki AOKI writes:
> This can help new installation using release tarballs (official or
> locally built) or upgrading with overwriting using said tarballs, but
> how does freebsd-update?
freebsd-update uses the same release process.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Dag-Erling Smørgrav writes:
> At some point between 42d088299c (4 May) and f0c9703301 (26 June), a
> deadlock was introduced in ZFS.
Trying to narrow this range down, I did not get a deadlock with
4e8d558c9d1c (10 June) but I did with b7198dcfc039 (16 June), albeit
after building ~1800 pa
#14987 Fix memory leak in zil_parse()
Obtained from: OpenZFS
OpenZFS commit: 8e8acabdcaeb831c777f71361722f4235b698a8d
We can't ship 14.0 with this deadlock.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Alan Somers writes:
> Do you have ZFS block cloning enabled on your pool? There were a lot
> of bugs associated with that feature. I think that was merged on
> 3-April.
No, and this deadlock did not appear until May.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
uld I run 'make installkernel' a 2nd time?
'make reinstallkernel' is more appropriate in this case.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
Michael Grimm writes:
> I'm currently in the process to prepare for upcoming 14-STABLE. Thus,
> I upgraded one of my sytems from 13-STABLE to 14-CURRENT.
Did you run etcupdate?
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
301 - 400 of 408 matches
Mail list logo
