bsdtar: xz threads support disabled
on Sat Nov 24 08:47:18 UTC 2018 Stefan wrote: > Is there any reason why bsdtar is built without XZ multi-threading support? > It's not documented in the man page, so maybe it's an experimental feature. > Can be tested with this command: > tar -Jcf /dev/null --options xz:threads=4 $HOME > After setting HAVE_LZMA_STREAM_ENCODER_MT, it works as expected: My lord, indeed. A careful inspector you are. This speciality makes an appearance in ports libachive but not libarchive in base. I bet you already had this intuition all along. $ /usr/local/bin/bsdtar cpJ --options xz:threads=2 -f /dev/null temp & $ ps -o pid,user,args -H $! PID USER COMMAND 1655 miltonott /usr/local/bin/bsdtar cpJ --options xz:threads=2 -f /dev/null temp 1655 miltonott /usr/local/bin/bsdtar cpJ --options xz:threads=2 -f /dev/null temp 1655 miltonott /usr/local/bin/bsdtar cpJ --options xz:threads=2 -f /dev/null temp Bah, now I need to research why I see three and not two. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Trap 12 in vm_page_alloc_after()
<
said:
> On Sun, Nov 18, 2018 at 08:24:38PM -0500, Garrett Wollman wrote:
>> Has anyone seen this before? It's on a busy NFS server, but hasn't
>> been observed on any of our other NFS servers.
>>
>>
>> Fatal trap 12: page fault while in kernel mode
>> --- trap 0xc, rip = 0x809a903d, rsp = 0xfe17eb8d0710, rbp =
>> 0xfe17eb8d0750 ---
>> vm_page_alloc_after() at vm_page_alloc_after+0x15d/frame 0xfe17eb8d0750
> What is the line number for vm_page_alloc_after+0x15d ?
> Do you have NUMA enabled on 11 ?
If gdb is to be believed, the trap is at line 1687:
/*
* At this point we had better have found a good page.
*/
KASSERT(m != NULL, ("missing page"));
free_count = vm_phys_freecnt_adj(m, -1);
>> if ((m->flags & PG_ZERO) != 0)
vm_page_zero_count--;
mtx_unlock(_page_queue_free_mtx);
vm_page_alloc_check(m);
The faulting instruction is:
0x809a903d : testb $0x8,0x5a(%r14)
There are no options matching /numa/i in the configuration. (This is
a non-debugging configuration so the KASSERT is inoperative, I
assume.) I have about a dozen other servers with the same kernel and
they're not crashing, but obviously they all have different loads and
sets of active clients.
-GAWollman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic on 11-STABLE with Xen guest
I have the same failure to boot 11-stable as a DomU host on xen_version: 4.4.1 Kernel I was trying was recent, FreeBSD 11.2-STABLE (GENERIC) #23 r334205:340834 commit 340016 for the dynamic IRQ layout seems rather involved and I doubt I could isolate the problem, but maybe it is in 338631: xen: legacy PVH fixes for the new interrupt count Register interrupts using the PIC pic_register_sources method instead of doing it in apic_setup_io. This is now required, since the internal interrupt structures are not yet setup when calling apic_setup_io. -- Richard M. Timoney (richa...@maths.tcd.ie) Tel. +353-1-896 1196 School of Mathematics, Trinity College, Dublin 2, Ireland WWW https://www.maths.tcd.ie/~richardt FAX +353-1-896 2282 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Problem reports for sta...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- New |230620 | "install -d" issue Open|227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock 2 problems total for which you should take action. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic booting 12-RC2 on amd64
26.11.2018 1:26, Christian Ullrich wrote: > I'd really like to upgrade to 12. If anyone can suggest something I can > try, I'll be happy to do experiments. Try verbose boot (boot -v), collect pre-panic output and post it again. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Panic booting 12-RC2 on amd64
Hello, I have a reproducible panic booting 12-RC2 and stable/12, 2cf4a7e0d8 from Friday, on a Jetway JNF9HG board, Celeron N2930 CPU, booting with UEFI. The same box has no problems with stable/11 18f83cbbc9 from Thursday. There is no serial console on the box right now, but the last screenful of boot output is this (from the -RC2; the panic'ing symbol is the same with the stable/12 kernel): random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module [ath_hal] loaded module_register_init: MOD_LOAD (vesa, 0x810f8750, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled cryptosoft0: on motherboard acpi0: <_> on motherboard panic: smp_targeted_tlb_shootdown: interrupts disabled cpuid = 2 time = 1 KDB: stack backtrace: #0 0x80be74a7 at kdb_backtrace+0x67 #1 0x80b9b093 at vpanic+0x1a3 #2 0x80b9aee3 at panic+0x43 #3 0x811eda2f at smp_targeted_tlb_shootdown+0x40f #4 0x811ed60d at smp_masked_invltlb+0x3d #5 0x8105d5c5 at pmap_invalidate_range+0x1b5 #6 0x8106a429 at pmap_change_attr_locked+0x859 #7 0x81069804 at pmap_mapdev_internal+0x424 #8 0x81075ed0 at pcie_cfgregopen+0x60 #9 0x80451f10 at acpi_attach+0x390 #10 0x80bd6efc at device_attach+0x3ec #11 0x80bd81dc at bus_generic_attach+0x5c #12 0x80bd6efc at device_attach+0x3ec [sic!] #13 0x80bd88b8 at bus_generic_new_pass+0x118 #14 0x80bda577 at root_bus_configure+0x77 #15 0x811dbce9 at configure+0x9 #16 0x80b31a78 at mi_startup+0x118 #17 0x8034102c at btext+0x2c Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort If it matters, the build from svn was with CPUTYPE=slm, the -RC2 is FreeBSD-12.0-RC2-amd64-mini-memstick.img, i.e. without CPUTYPE. I have been running stable/11 with CPUTYPE=slm on this and other identical CPUs for a long time with no trouble, so I think it is unrelated. I'd really like to upgrade to 12. If anyone can suggest something I can try, I'll be happy to do experiments. -- Christian ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [UPDATE] Re: FreeBSD 12.0-RC2 Now Available
freebsd-update upgrade -r 12.0-RC2 src component not installed, skipped Looking up update.FreeBSD.org mirrors... 2 mirrors found. Fetching metadata signature for 12.0-RC1 from update4.freebsd.org... done. Fetching metadata index... done. Fetching 3 metadata files... failed. Seems like freebsd-update binary update patches are not available yet... ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 12.0-RC2 Now Available
HI, I went over the release notes and honestly I don't see what 12 brings new.. I remember older versions were big change each in different aspect.. So what is 12-Rel unique aspect VS 11 let's say? Thanks in advance, Sami בתאריך יום א׳, 25 בנוב׳ 2018, 4:04, מאת Glen Barber : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > The second RC build of the 12.0-RELEASE release cycle is now available. > > Installation images are available for: > > o 12.0-RC2 amd64 GENERIC > o 12.0-RC2 i386 GENERIC > o 12.0-RC2 powerpc GENERIC > o 12.0-RC2 powerpc64 GENERIC64 > o 12.0-RC2 powerpcspe MPC85XXSPE > o 12.0-RC2 sparc64 GENERIC > o 12.0-RC2 armv6 RPI-B > o 12.0-RC2 armv7 BANANAPI > o 12.0-RC2 armv7 BEAGLEBONE > o 12.0-RC2 armv7 CUBIEBOARD > o 12.0-RC2 armv7 CUBIEBOARD2 > o 12.0-RC2 armv7 CUBOX-HUMMINGBOARD > o 12.0-RC2 armv7 PANDABOARD > o 12.0-RC2 armv7 WANDBOARD > o 12.0-RC2 armv7 GENERICSD > o 12.0-RC2 aarch64 GENERIC > o 12.0-RC2 aarch64 RPI3 > o 12.0-RC2 aarch64 PINE64 > o 12.0-RC2 aarch64 PINE64-LTS > > Note: The 12.0-RC2 armv7 RPI2 build failed, and the cause is being > investigated. > > Also note, at present, freebsd-update(8) patch builds are still in > progress. A followup email will be sent in reply to this announcement > when they are available. > > Note regarding arm SD card images: For convenience for those without > console access to the system, a freebsd user with a password of > freebsd is available by default for ssh(1) access. Additionally, > the root user password is set to root. It is strongly recommended > to change the password for both users after gaining access to the > system. > > Installer images and memory stick images are available here: > > https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.0/ > > The image checksums follow at the end of this e-mail. > > If you notice problems you can report them through the Bugzilla PR > system or on the -stable mailing list. > > If you would like to use SVN to do a source based update of an existing > system, use the "releng/12.0" branch. > > A summary of changes since 12.0-RC1 includes: > > o Kernel debugging support in various kernel configurations has been > disabled, which was missed when branching releng/12.0 from stable/12. > > o Allow set ether/vlan PCP operation from the VNET jails. > > o Align IA32_ARCH_CAP MSR definitions and use with SDM rev. 068. > > o Several IFLIB-related fixes. > > o Regressions when using 'pciconf -l' were fixed. > > o Handle kernel superpage mappings in pmap_remove_l2(). (PR 233088) > > o Fix /etc/ntp permissions. > > o OpenSSL has been updated to version 1.1.1a. > > o Various fixes to libbe(3) and bectl(8). > > o A src.conf knob to build userland with retpoline was added (off by > default). > > o Various other miscellaneous fixes. > > A list of changes since 11.2-RELEASE is available in the releng/12.0 > release notes: > > https://www.freebsd.org/releases/12.0R/relnotes.html > > Please note, the release notes page is not yet complete, and will be > updated on an ongoing basis as the 12.0-RELEASE cycle progresses. > > === Virtual Machine Disk Images === > > VM disk images are available for the amd64 and i386 architectures. > Disk images may be downloaded from the following URL (or any of the > FreeBSD FTP mirrors): > > https://download.freebsd.org/ftp/releases/VM-IMAGES/12.0-RC2/ > > The partition layout is: > > ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) > ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) > ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) > > The disk images are available in QCOW2, VHD, VMDK, and raw disk image > formats. The image download size is approximately 135 MB and 165 MB > respectively (amd64/i386), decompressing to a 21 GB sparse image. > > Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI > loader file is needed for qemu-system-aarch64 to be able to boot the > virtual machine images. See this page for more information: > > https://wiki.freebsd.org/arm64/QEMU > > To boot the VM image, run: > > % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ > -bios QEMU_EFI.fd -serial telnet::,server -nographic \ > -drive if=none,file=VMDISK,id=hd0 \ > -device virtio-blk-device,drive=hd0 \ > -device virtio-net-device,netdev=net0 \ > -netdev user,id=net0 > > Be sure to replace "VMDISK" with the path to the virtual machine image. > > === Amazon EC2 AMI Images === > > FreeBSD/amd64 EC2 AMIs are available in the following regions: > > ap-south-1 region: ami-0285a4b0c311d9e5e > eu-west-3 region: ami-01989f54cc5fc3425 > eu-west-2 region: ami-0058f626d39ade7dc > eu-west-1 region: ami-07cca4933d62d5d22 > ap-northeast-2 region: ami-084b8fc685e73d718 > ap-northeast-1 region: ami-0fd072608bc5cc041 > sa-east-1 region: ami-0df9e331ad6b563cd > ca-central-1 region: ami-01360ca27677e8deb > ap-southeast-1 region: ami-0dc6b473d0770bd29 >
Re: 12-STABLE source update zoneinfo missing build directories
cd /usr/src <...> && rm -r /usr/share/man && rm -r /usr/share/doc && rm -r /usr/share/examples &&\ make installworld && \ make cleandir && make cleandir && \ rm -rf /usr/obj && \ mergemaster && \ Well, that explains it. I'm not sure mergemaster should depend on a unclean tree. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: freebsd-stable Digest, Vol 798, Issue 7
On Sun, Nov 25, 2018, 05:01 Send freebsd-stable mailing list submissions to > freebsd-stable@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > or, via email, send a message with subject or body 'help' to > freebsd-stable-requ...@freebsd.org > > You can reach the person managing the list at > freebsd-stable-ow...@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-stable digest..." > > > Today's Topics: > >1. Re: 12-STABLE uname -a misses timestamp of the build (Yuri Pankov) >2. Re: 12-STABLE uname -a misses timestamp of the build (Jakub Lach) >3. Re: 12-STABLE uname -a misses timestamp of the build > (Tomoaki AOKI) >4. "sockstat: struct xinpgen size mismatch" in 11.2-p4 jail on > 12-STABLE host (Paul Mather) >5. Re: SCSI and dmesg (Yuri Pankov) >6. FreeBSD 12.0-RC2 Now Available (Glen Barber) >7. [UPDATE] Re: FreeBSD 12.0-RC2 Now Available (Glen Barber) > > > -- > > Message: 1 > Date: Sat, 24 Nov 2018 15:13:15 +0300 > From: Yuri Pankov > To: Jakub Lach , freebsd-stable@freebsd.org > Subject: Re: 12-STABLE uname -a misses timestamp of the build > Message-ID: <183252d3-7080-8747-4534-da0e8b048...@yuripv.net> > Content-Type: text/plain; charset="utf-8" > > Jakub Lach wrote: > > Is there a way to restore it? I liked the old behaviour better, it was > useful > > info for me. > > See 20180913 in UPDATING and WITHOUT_REPRODUCIBLE_BUILD in src.conf(5). > > -- next part -- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 488 bytes > Desc: OpenPGP digital signature > URL: < > http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20181124/eb8724d2/attachment-0001.sig > > > > -- > > Message: 2 > Date: Sat, 24 Nov 2018 05:18:05 -0700 (MST) > From: Jakub Lach > To: freebsd-stable@freebsd.org > Subject: Re: 12-STABLE uname -a misses timestamp of the build > Message-ID: <1543061885192-0.p...@n6.nabble.com> > Content-Type: text/plain; charset=us-ascii > > That was very helpful, thank you very much :) > > > > -- > Sent from: > http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html > > > -- > > Message: 3 > Date: Sat, 24 Nov 2018 21:37:37 +0900 > From: Tomoaki AOKI > To: freebsd-stable@freebsd.org > Subject: Re: 12-STABLE uname -a misses timestamp of the build > Message-ID: <20181124213737.d8128e30920e8de5fcca1...@dec.sakura.ne.jp> > Content-Type: text/plain; charset=US-ASCII > > WITHOUT_REPRODUCIBLE_BUILD should be default for now on stable/12, > as releng/12.0 already branched. > > As I already proposed on -current ML, REPRODUCIBLE_BUILD should be > enabled only for release/* and releng/*. > > > https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071151.html > > I didn't noticed as I have WITHOUT_REPRODUCIBLE_BUILD=yes in src.conf. > > > On Sat, 24 Nov 2018 15:13:15 +0300 > Yuri Pankov wrote: > > > Jakub Lach wrote: > > > Is there a way to restore it? I liked the old behaviour better, it was > useful > > > info for me. > > > > See 20180913 in UPDATING and WITHOUT_REPRODUCIBLE_BUILD in src.conf(5). > > > > > -- > Tomoaki AOKI > > > -- > > Message: 4 > Date: Sat, 24 Nov 2018 09:17:23 -0500 > From: Paul Mather > To: FreeBSD Stable > Subject: "sockstat: struct xinpgen size mismatch" in 11.2-p4 jail on > 12-STABLE host > Message-ID: > Content-Type: text/plain; charset=us-ascii > > I updated a system yesterday to the latest 12-STABLE as part of the > upcoming 12-RELEASE cycle. I've installed several BETA and at least one RC > of 12 since updating from 11-STABLE as part of the 12 cycle and have had no > problems up to now. Currently, I am at FreeBSD 12.0-PRERELEASE r340834 > GENERIC amd64. > > Since the most recent update, I have been getting this error when I invoke > "sockstat" in any of the jails running on the system: > > sockstat: struct xinpgen size mismatch > > The jails are managed via iocage and all are running 11.2-RELEASE-p4, > which is the most up-to-date version of 11.2-RELEASE. > > Has anyone encountered this error? Unfortunately, it means that it breaks > Salt, which is what I use to help manage the jails. Sockstat works fine on > the host, just not in the jails. > > I am using a GENERIC kernel which includes "options COMPAT_FREEBSD11". I > assumed this would allow FreeBSD 11 binaries to work on a FreeBSD 12 > kernel, which it has done up to now. > > Cheers, > > Paul. > > -- > > Message: 5 > Date: Sat, 24 Nov 2018 18:52:40 +0300 > From: Yuri Pankov > To: Warner Losh , FreeBSD-STABLE Mailing List > , FreeBSD Current > > Subject: Re: SCSI and dmesg >
Re: 12-STABLE source update zoneinfo missing build directories
On Sun, Nov 25, 2018 at 07:01:34AM -0700, Jakub Lach wrote: > Thank you for reply. > > Files install fine, it's from mergemaster. > Well, I ran mergemasater as well (as a routine part of the build), but saw no such complaints in the typescript: freebeast(12.0-P)[1] grep 'zoneinfo/builddir: No such file or directory' s3 freebeast(12.0-P)[2] echo $? 1 freebeast(12.0-P)[3] Peace, david -- David H. Wolfskill da...@catwhisker.org No, Mr. Trump, the "disgrace" is your repeated lies and unlawful behavior. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: 12-STABLE source update zoneinfo missing build directories
Thank you for reply. Files install fine, it's from mergemaster. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12-STABLE source update zoneinfo missing build directories
On Sun, Nov 25, 2018 at 06:00:06AM -0700, Jakub Lach wrote: > *** Creating the temporary root environment in /var/tmp/temproot > *** /var/tmp/temproot ready for use > *** Creating and populating directory structure in /var/tmp/temproot > > [Creating objdir /usr/obj/usr/src/amd64.amd64...] > [Creating objdir /usr/obj/usr/src/amd64.amd64/etc...] > cd: /usr/src/share/zoneinfo/builddir: No such file or directory > make[4]: "/usr/src/share/zoneinfo/Makefile" line 104: warning: "cd > /usr/src/share/zoneinfo/builddi > > > *** Beginning comparison > >*** Checking /etc/rc.d for stale files > >*** No stale files found > > <...> > > It looks harmless, I wonder why though? > I don't see that in my typescript from my upgrades from r340851 to r340915 this morning (on either my laptop or my build machine). Indeed: g1-215(11.2-S)[3] grep 'zoneinfo/builddir' s3 | head install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Abidjan /usr/share/zoneinfo/Africa/Abidjan install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Accra /usr/share/zoneinfo/Africa/Accra install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Addis_Ababa /usr/share/zoneinfo/Africa/Addis_Ababa install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Algiers /usr/share/zoneinfo/Africa/Algiers install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Asmara /usr/share/zoneinfo/Africa/Asmara install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Bamako /usr/share/zoneinfo/Africa/Bamako install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Bangui /usr/share/zoneinfo/Africa/Bangui install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Banjul /usr/share/zoneinfo/Africa/Banjul install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Bissau /usr/share/zoneinfo/Africa/Bissau install -o root -g wheel -m 444 /common/S3/obj/usr/src/amd64.amd64/share/zoneinfo/builddir/Africa/Blantyre /usr/share/zoneinfo/Africa/Blantyre g1-215(11.2-S)[4] Peace, david -- David H. Wolfskill da...@catwhisker.org No, Mr. Trump, the "disgrace" is your repeated lies and unlawful behavior. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
12-STABLE source update zoneinfo missing build directories
*** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot [Creating objdir /usr/obj/usr/src/amd64.amd64...] [Creating objdir /usr/obj/usr/src/amd64.amd64/etc...] cd: /usr/src/share/zoneinfo/builddir: No such file or directory make[4]: "/usr/src/share/zoneinfo/Makefile" line 104: warning: "cd /usr/src/share/zoneinfo/builddi *** Beginning comparison *** Checking /etc/rc.d for stale files *** No stale files found <...> It looks harmless, I wonder why though? -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
