BPi-M3 (A83T based) under stable/11 -r308135: powerd? (cpufreq?)
https://wiki.freebsd.org/FreeBSD/arm/Allwinner reports "yes" for "cpufreq / DVFS" for A83T (and A64 and H3). But under stable/11 -r308135 powerd on a BPI-M3 (A83T) reports: powerd: no cpufreq(4) support -- aborting: No such file or directory sysctl -a does not seem to have the items for the subject area. It leaves me wondering if trying -j 5 buildworld buildkernel all the way through would be safe on the BPI-M3 (heat sink and fan in use). I use such long running sustained activity for a stability test, among other things. > # uname -apKU > FreeBSD bpim3 11.0-STABLE FreeBSD 11.0-STABLE #1 r308135M: Tue Nov 1 > 22:07:22 PDT 2016 > markmi@FreeBSDx64:/usr/obj/bpim3_clang/arm.armv6/usr/src/sys/BPIM3-NODBG arm > armv6 1100506 1100506 As far as BPIM3-NODBG goes for my context: include "ALLWINNER" ident BPIM3-NODBG makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options ALT_BREAK_TO_DEBUGGER options KDB # Enable kernel debugger support # For minimum debugger support (stable branch) use: options KDB_TRACE # Print a stack trace for a panic options DDB # Enable the kernel debugger # Extra stuff: #optionsVERBOSE_SYSINIT # Enable verbose sysinit messages #optionsBOOTVERBOSE=1 #optionsBOOTHOWTO=RB_VERBOSE #optionsKTR #optionsKTR_MASK=KTR_TRAP ##options KTR_CPUMASK=0xF #optionsKTR_VERBOSE # Disable any extra checking for. . . nooptions DEADLKRES # Enable the deadlock resolver nooptions INVARIANTS # Enable calls of extra sanity checking nooptions INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect deadlocks and cycles nooptions WITNESS_SKIPSPIN# Don't run witness on spinlocks for speed nooptions DIAGNOSTIC nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones === Mark Millard markmi at dsl-only.net ___ 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"
ath0 associated, wlan0 not associated
Originally posted to freebsd-wireless; no solution yet so I thought I'd try here. After booting up, my ath0 interface says it is associated, but my wlan0 says it is not: FreeBSD 10.3-RELEASE-p11 wpa_supplicant v2.0 Copyright (c) 2003-2012, Jouni Malinen and contributors ath0@pci0:2:0:0:class=0x028000 card=0x064211ad chip=0x0036168c rev=0x01 hdr=0x00 vendor = 'Qualcomm Atheros' device = 'QCA9565 / AR9565 Wireless Network Adapter' class = network grep wlan /etc/rc.conf: create_args_wlan0="country US" ifconfig_wlan0="WPA DHCP" wlans_ath0="wlan0" And the result is: ifconfig wlan0: wlan0: flags=8c43 metric 0 mtu 1500 ether d0:53:49:91:6f:a1 inet6 fe80::d253:49ff:fe91:6fa1%wlan0 prefixlen 64 scopeid 0x4 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=23 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 2 (2417 MHz 11g ht/40+) regdomain FCC country US indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF txpower 30 bmiss 7 scanvalid 60 protmode CTS ampdulimit 8k ampdudensity 8 shortgi wme burst roaming MANUAL ifconfig ath0: ath0: flags=8843 metric 0 mtu 2290 ether d0:53:49:91:6f:a1 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: associated grep wpa /var/log/messages: ov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz) Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: Associated with 60:e3:27:7b:e8:42 Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed [id=1 id_str=] Nov 1 09:16:55 haymarket wpa_supplicant[389]: wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] Nov 1 09:16:56 haymarket wpa_supplicant[389]: wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] Nov 1 09:16:57 haymarket wpa_supplicant[389]: wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] Nov 1 09:16:57 haymarket wpa_supplicant[389]: wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=0 Nov 1 09:16:59 haymarket wpa_supplicant[389]: wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz) Nov 1 09:17:09 haymarket wpa_supplicant[389]: wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out. Nov 1 09:17:09 haymarket wpa_supplicant[389]: wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx2 reason=3 locally_generated=1 Nov 1 09:18:13 haymarket wpa_supplicant[389]: wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz etc. So how does ath0 get associated but not wlan0? -- George ___ 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: huge nanosleep variance on 11-stable
On Wed, 2 Nov 2016 10:23:24 -0400 George Mitchell wrote: >On 11/01/16 23:45, Kevin Oberman wrote: >> On Tue, Nov 1, 2016 at 2:36 PM, Jason Harmening >> wrote: >> >>> Sorry, that should be ~*30ms* to get 30fps, though the variance is still >>> up to 500ms for me either way. >>> >>> On 11/01/16 14:29, Jason Harmening wrote: repro code is at http://pastebin.com/B68N4AFY if anyone's interested. On 11/01/16 13:58, Jason Harmening wrote: > Hi everyone, > > I recently upgraded my main amd64 server from 10.3-stable (r302011) to > 11.0-stable (r308099). It went smoothly except for one big issue: > certain applications (but not the system as a whole) respond very > sluggishly, and video playback of any kind is extremely choppy. > > [...] >> I eliminated the annoyance by change scheduler from ULE to 4BSD. That was >> it, but I have not seen the issue since. I'd be very interested in whether >> the scheduler is somehow impacting timing functions or it's s different >> issue. I've felt that there was something off in ULE for some time, but it >> was not until these annoying hiccups convinced me to try going back to >> 4BSD. >> >> Tip o' the hat to Doug B. for his suggestions that ULE may have issues that >> impacted interactivity. >> [...] > >Not to beat a dead horse, but I've been a non-fan of SCHED_ULE since >it was first introduced, and I don't like it even today. I run the >distributed.net client on my machines, but even without that, ULE >screws interactive behavior. With distributed.net running and ULE, >a make buildworld/make buildkernel takes 10 2/3 hours on 10.3-RELEASE >on a 6-CPU machine versus 2 1/2 hours on the same machine with 4BSD >and distributed.net running. I'm told that SCHED_ULE is the greatest >thing since sliced bread for some compute load or other (details are >scarce), but I (fortunately) don't often have to run heavy server >type loads; and for everyday use (even without distributed.net >running), SCHED_4BSD is my choice by far. It's too bad I can't run >freebsd_update with it, though. > I gave up on ULE during 8-STABLE. I had tried tinkering with kern.sched.preempt_thresh as recommended, as well as some more extreme values, but I couldn't see any improvement. Some values may have made performance even worse. The last straw for me, however, was when I discovered that ULE happily scheduled *idle* priority processes at times when both CPU threads on a P4 Prescott were tied up by 100% CPU-bound (mprime) threads at normal priority niced to 20. Idle priority tasks should *only* run when no higher priority tasks are available to run for all CPU threads. The 4BSD scheduler handles this situation properly. Now I'm running 10.3-STABLE on a QX9650, and I haven't tested ULE on it to see whether it's still as flawed. If and when I get a machine with a multi-cored, hyperthreaded CPU or perhaps a board with multiple CPU chips, then I may worry about the multi-level affinity stuff that ULE was supposedly designed for enough to bother testing it. But for now, I can't see any advantage in it for my current machine. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * ** * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ 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: ath0 associated, wlan0 not associated
hi, can you please try freebsd-11.0 ? I fixed a whole bunch of bugs in the AR9380 HAL and it may have improved that device. Thanks! -a On 3 November 2016 at 07:09, George Mitchell wrote: > Originally posted to freebsd-wireless; no solution yet so I thought > I'd try here. After booting up, my ath0 interface says it is > associated, but my wlan0 says it is not: > > > FreeBSD 10.3-RELEASE-p11 > wpa_supplicant v2.0 > Copyright (c) 2003-2012, Jouni Malinen and contributors > > ath0@pci0:2:0:0:class=0x028000 card=0x064211ad chip=0x0036168c > rev=0x01 > hdr=0x00 > vendor = 'Qualcomm Atheros' > device = 'QCA9565 / AR9565 Wireless Network Adapter' > class = network > > grep wlan /etc/rc.conf: > create_args_wlan0="country US" > ifconfig_wlan0="WPA DHCP" > wlans_ath0="wlan0" > > And the result is: > > ifconfig wlan0: > wlan0: flags=8c43 metric > 0 mtu 1500 > ether d0:53:49:91:6f:a1 > inet6 fe80::d253:49ff:fe91:6fa1%wlan0 prefixlen 64 scopeid 0x4 > inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 > nd6 options=23 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 2 (2417 MHz 11g ht/40+) > regdomain FCC country US indoor ecm authmode WPA2/802.11i privacy ON > deftxkey UNDEF txpower 30 bmiss 7 scanvalid 60 protmode CTS > ampdulimit 8k ampdudensity 8 shortgi wme burst roaming MANUAL > > ifconfig ath0: > ath0: flags=8843 metric 0 mtu 2290 > ether d0:53:49:91:6f:a1 > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng > status: associated > > grep wpa /var/log/messages: > ov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: Trying to associate > with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz) > Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: Associated with > 60:e3:27:7b:e8:42 > Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: WPA: Key > negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] > Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: > CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed [id=1 > id_str=] > Nov 1 09:16:55 haymarket wpa_supplicant[389]: wlan0: WPA: Key > negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] > Nov 1 09:16:56 haymarket wpa_supplicant[389]: wlan0: WPA: Key > negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] > Nov 1 09:16:57 haymarket wpa_supplicant[389]: wlan0: WPA: Key > negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] > Nov 1 09:16:57 haymarket wpa_supplicant[389]: wlan0: > CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=0 > Nov 1 09:16:59 haymarket wpa_supplicant[389]: wlan0: Trying to > associate with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz) > Nov 1 09:17:09 haymarket wpa_supplicant[389]: wlan0: Authentication > with xx:xx:xx:xx:xx:xx timed out. > Nov 1 09:17:09 haymarket wpa_supplicant[389]: wlan0: > CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx2 reason=3 > locally_generated=1 > Nov 1 09:18:13 haymarket wpa_supplicant[389]: wlan0: Trying to > associate with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz > > etc. > > So how does ath0 get associated but not wlan0? -- George > > ___ > 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" ___ 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: zfs receive leads to a stuck server
> Am 01.10.2016 um 18:02 schrieb Rainer Duffner : > > Hi, > > I posted this before, but I didn’t really get an answer and I’m still looking > for ways to debug this. > > I have to servers (HP DL 380 Gen8, 192 GB RAM, 6C CPU). > I’ve outfitted them with HP’s H22x cards (really OEMed 9207-8x, three > altogether) that I recently cross-flashed to LSI’s latest firmware. And it turns out, using anything branded by HP is just asking for ulcers and headaches. We replaced said HBAs with LSI^WAvago^WBroadcom HBAs - and everything started working as it should. There are still hangs at 03:00 and 04:00 (when the snapshots that got deleted on the master get deleted on the slave) - but that's not really a problem because they are much shorter than before and nobody is using the system at that time. So, while the H22x-cards are „close enough to a LSI2308-based card so that the driver actually thinks it’s a 2308 - they are in fact not. Also, with the original LSI cards, you can use LSI’s FreeBSD flash utility and have a far better life overall. ___ 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: ath0 associated, wlan0 not associated
Thanks for the suggestion. I won't be able to try it until after a business trip next week. Any patches available that apply to 10.3? -- George On 11/03/16 18:48, Adrian Chadd wrote: > hi, > > can you please try freebsd-11.0 ? I fixed a whole bunch of bugs in the > AR9380 HAL and it may have improved that device. > > Thanks! > > > -a > > > On 3 November 2016 at 07:09, George Mitchell wrote: >> Originally posted to freebsd-wireless; no solution yet so I thought >> I'd try here. After booting up, my ath0 interface says it is >> associated, but my wlan0 says it is not: >> >> >> FreeBSD 10.3-RELEASE-p11 >> wpa_supplicant v2.0 >> Copyright (c) 2003-2012, Jouni Malinen and contributors >> >> ath0@pci0:2:0:0:class=0x028000 card=0x064211ad chip=0x0036168c >> rev=0x01 >> hdr=0x00 >> vendor = 'Qualcomm Atheros' >> device = 'QCA9565 / AR9565 Wireless Network Adapter' >> class = network >> >> grep wlan /etc/rc.conf: >> create_args_wlan0="country US" >> ifconfig_wlan0="WPA DHCP" >> wlans_ath0="wlan0" >> >> And the result is: >> >> ifconfig wlan0: >> wlan0: flags=8c43 metric >> 0 mtu 1500 >> ether d0:53:49:91:6f:a1 >> inet6 fe80::d253:49ff:fe91:6fa1%wlan0 prefixlen 64 scopeid 0x4 >> inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 >> nd6 options=23 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> ssid "" channel 2 (2417 MHz 11g ht/40+) >> regdomain FCC country US indoor ecm authmode WPA2/802.11i privacy ON >> deftxkey UNDEF txpower 30 bmiss 7 scanvalid 60 protmode CTS >> ampdulimit 8k ampdudensity 8 shortgi wme burst roaming MANUAL >> >> ifconfig ath0: >> ath0: flags=8843 metric 0 mtu 2290 >> ether d0:53:49:91:6f:a1 >> nd6 options=21 >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng >> status: associated >> >> grep wpa /var/log/messages: >> ov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: Trying to associate >> with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz) >> Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: Associated with >> 60:e3:27:7b:e8:42 >> Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: WPA: Key >> negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] >> Nov 1 09:16:54 haymarket wpa_supplicant[389]: wlan0: >> CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed [id=1 >> id_str=] >> Nov 1 09:16:55 haymarket wpa_supplicant[389]: wlan0: WPA: Key >> negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] >> Nov 1 09:16:56 haymarket wpa_supplicant[389]: wlan0: WPA: Key >> negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] >> Nov 1 09:16:57 haymarket wpa_supplicant[389]: wlan0: WPA: Key >> negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP] >> Nov 1 09:16:57 haymarket wpa_supplicant[389]: wlan0: >> CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=0 >> Nov 1 09:16:59 haymarket wpa_supplicant[389]: wlan0: Trying to >> associate with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz) >> Nov 1 09:17:09 haymarket wpa_supplicant[389]: wlan0: Authentication >> with xx:xx:xx:xx:xx:xx timed out. >> Nov 1 09:17:09 haymarket wpa_supplicant[389]: wlan0: >> CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx2 reason=3 >> locally_generated=1 >> Nov 1 09:18:13 haymarket wpa_supplicant[389]: wlan0: Trying to >> associate with xx:xx:xx:xx:xx:xx (SSID='yy' freq=2417 MHz >> >> etc. >> >> So how does ath0 get associated but not wlan0? -- George >> >> ___ >> 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" > ___ > 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" > ___ 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"
Use of env SRC_ENV_CONF=. . . for buildworld does not override/avoid use of /etc/src.conf : Intentional?
I just had a case of "odd" command text in a buildworld that was based on (in part) env SRC_ENV_CONF=. . . env __MAKE_CONF=. . . does not get the kind of behavior reported below for /etc/src.conf . Overall this means that even with an explicit env SRC_ENV_CONF=. . . one must separately prevent /etc/src.conf from contributing if the SRC_ENV_CONF file is intended to cover everything. Looking in the log from a failure that resulted shows that .MAKE.MAKEFILES shows both the SRC_ENV_CONF expansion and also a /etc/src.conf as well (formatted to make the /etc/src.conf and such stand out: separate lines wiht whitespace before and after and with just one path on the line for such file paths): > Script started on Thu Nov 3 16:37:26 2016 > Command: env __MAKE_CONF=/root/src.configs/make.conf > SRC_ENV_CONF=/root/src.configs/src.conf.powerpc64-xtoolchain.amd64-host > WITH_META_MODE=yes MAKEOBJDIRPREFIX=/usr/obj/powerpc64vtsc_xtoolchain make -j > 5 buildworld buildkernel . . . > .MAKE.MAKEFILES='/usr/src/share/mk/sys.mk /usr/src/share/mk/local.sys.env.mk > /usr/src/share/mk/src.sys.env.mk > /root/src.configs/src.conf.powerpc64-xtoolchain.amd64-host > /usr/src/share/mk/bsd.mkopt.mk /usr/src/share/mk/bsd.suffixes.mk > /root/src.configs/make.conf > /usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk > /etc/src.conf > /usr/src/include/rpcsvc/Makefile /usr/src/share/mk/bsd.prog.mk > /usr/src/share/mk/bsd.init.mk /usr/src/share/mk/bsd.opts.mk > /usr/src/share/mk/bsd.cpu.mk /usr/src/share/mk/local.init.mk > /usr/src/share/mk/src.init > .mk /usr/src/share/mk/bsd.own.mk /usr/src/share/mk/bsd.compiler.mk > /usr/src/share/mk/bsd.compiler.mk /usr/src/share/mk/bsd.libnames.mk > /usr/src/share/mk/src.libnames.mk /usr/src/share/mk/src.opts.mk > /usr/src/share/mk/bsd.nls.mk /usr/src/share/mk/bsd.confs.mk /usr/src/share > /mk/bsd.files.mk /usr/src/share/mk/bsd.incs.mk /usr/src/share/mk/bsd.links.mk > /usr/src/share/mk/bsd.man.mk /usr/src/share/mk/bsd.dep.mk > /usr/src/share/mk/bsd.clang-analyze.mk /usr/src/share/mk/bsd.obj.mk > /usr/src/share/mk/bsd.subdir.mk /usr/src/share/mk/bsd.sys.mk' > .PATH='. /usr/src/include/rpcsvc' Note: > # grep src.conf /root/src.configs/src.conf.powerpc64-xtoolchain.amd64-host > # The context I was under was: > # uname -apKU > FreeBSD FreeBSDx64 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r308247M: Thu Nov 3 > 04:05:55 PDT 2016 > markmi@FreeBSDx64:/usr/obj/amd64_clang/amd64.amd64/usr/src/sys/GENERIC-NODBG > amd64 amd64 1200014 1200014 I'd just cloned and switched from a stable/11 context to head (12-CURRENT). If this is intentional then I think the man src.conf references and such should be explicit about the /etc/make.conf vs. /etc/src.conf distinction for __MAKE_CONF= vs. SRC_ENV_CONF= . === Mark Millard markmi at dsl-only.net ___ 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: pax(1) needs to learn POSIX-pax format (by libarchive(3)?)
On Nov 1, 2016, at 13:44, Harry Schmalzbauer wrote: > Has anyone ever thought about? Unfortunately I'm lacking skills and time :-( You’ll want to talk to the folks here: http://libarchive.org That is the upstream project. It actually started on FreeBSD over a decade ago but spun off on its own, and is used by a wider audience nowadays. I provided some sample Solaris-ACL files early in the development. If you provide some problematic files I’m sure they’ll be willing to help. Regards, David ___ 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"
