Re: PACKAGESITE spam
The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. -adrian On 21 December 2013 15:49, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Sat, Dec 21, 2013 at 06:47:01PM -0500, Glen Barber wrote: On Sat, Dec 21, 2013 at 03:44:11PM -0800, Steve Kargl wrote: On Sat, Dec 21, 2013 at 06:29:17PM -0500, Garrett Wollman wrote: In article 20131221230448.ga61...@troutmask.apl.washington.edu, Steve Kargl writes: Other than the noise in /var/log/message, what does this provide that 'pkg info' doesn't! A record of when packages were installed and removed. The date/time a package is installed should be recorded in the pkg database and be available with 'pkg info -f'. Of course, it appeat that this information s not properly recorded. Because databases are never corruptible? /var/log/message never gets corrupted? -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
Steve, On Sat, Dec 21, 2013 at 12:14:03PM -0800, Steve Kargl wrote: S It did not ask how to stop this stupidity. I asked to have S this stupidity stopped by default. The spewing of this S information in /var/log/messages provides NOTHING. Please S turn it off by default. I am really suprised that someone might want to see this off by default. -- Totus tuus, Glebius. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Build failure on mips64/octeon
Hello, I'm trying to compile the current tree for my octeon device and
get the following error:
cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
-Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I.
-I/usr/home/m/Ubiquity/10/sys -I/usr/home/m/Ubiquity/10/sys/contrib/altq
-I/usr/home/m/Ubiquity/10/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
-finline-limit=8000 --param inline-unit-growth=1 --param
large-function-growth=10 --param max-inline-insns-single=1
-fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x8010
-march=octeon -mabi=64 -msoft-float -ffreestanding -Werror vnode_if.c
${NORMAL_CTFCONVERT} expands to empty string
: hack.c
cc -shared -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x8010
-march=octeon -mabi=64 -nostdlib hack.c -o hack.So
rm -f hack.c
sed s/KERNLOADADDR/0x8010/g
/usr/home/m/Ubiquity/10/sys/conf/ldscript.mips.octeon1
ldscript.mips.octeon1
MAKE=make sh /usr/home/m/Ubiquity/10/sys/conf/newvers.sh OCTEON1
cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
-Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I.
-I/usr/home/m/Ubiquity/10/sys -I/usr/home/m/Ubiquity/10/sys/contrib/altq
-I/usr/home/m/Ubiquity/10/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
-finline-limit=8000 --param inline-unit-growth=1 --param
large-function-growth=10 --param max-inline-insns-single=1
-fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x8010
-march=octeon -mabi=64 -msoft-float -ffreestanding -Werror vers.c
${NORMAL_CTFCONVERT} expands to empty string
linking kernel.debug
hack.So: could not read symbols: File in wrong format
*** [kernel.debug] Error code 1
Stop in /usr/home/m/Ubiquity/obj/mips.mips/usr/home/m/Ubiquity/10/sys/M.
*** [buildkernel] Error code 1
Stop in /usr/home/m/Ubiquity/10.
*** [buildkernel] Error code 1
Stop in /usr/home/m/Ubiquity/10.
I build with TARGET=mips and TARGET_ARCH=mipseb.
My kernel config:
#
# OCTEON1 -- Generic kernel configuration file for FreeBSD/MIPS on
Cavium Octeon
#
# For more information on this file, please read the config(5) manual page,
# and/or the handbook section on Kernel Configuration Files:
#
#
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: stable/10/sys/mips/conf/OCTEON1 253845 2013-07-31 17:21:18Z
obrien $
ident OCTEON1
makeoptions ARCH_FLAGS=-march=octeon -mabi=64
makeoptions LDSCRIPT_NAME=ldscript.mips.octeon1
# Don't build any modules yet.
makeoptions MODULES_OVERRIDE=
makeoptions KERNLOADADDR=0x8010
# We don't need to build a trampolined version of the kernel.
makeoptions WITHOUT_KERNEL_TRAMPOLINE=1
include ../cavium/std.octeon1
hints OCTEON1.hints #Default places to look for devices.
makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols
# Board-specific support that cannot be auto-detected at runtime.
#optionsOCTEON_VENDOR_LANNER# Support for Lanner boards.
#optionsOCTEON_VENDOR_RADISYS # Support for Radisys boards.
options OCTEON_VENDOR_UBIQUITI # Support for Ubiquiti boards.
#optionsOCTEON_VENDOR_GEFES # Support for GE LANIC boards
#optionsOCTEON_BOARD_CAPK_0100ND# Support for CAPK-0100nd.
# Compile for a specified Octeon model. If not specified, support for
# detection at runtime will be used instead, which may give inferior
# performance.
#
# See sys/contrib/octeon-sdk/octeon-model.h for possible values.
#optionsOCTEON_MODEL=OCTEON_CN58XX_PASS1_1
options SCHED_ULE # ULE scheduler
options PREEMPTION # Enable kernel thread preemption
options INET# InterNETworking
options INET6 # IPv6 communications protocols
options SCTP# Stream Control Transmission Protocol
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control
Re: PACKAGESITE spam
On Sat, 21 Dec 2013, Steve Kargl wrote: On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Yeah, I noticed that spam along with the spam that is being spewed to /var/log/messaage, e.g., Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed Can you (portmgr) please mute these messages? -- Steve This received several responses. Greg Rivers said: Do you really feel that strongly about it? Having a record of changes to the system has always seemed like a feature to me... Baptiste Daroussin said: this has been done and activated for reason, first for lot of companies, it is important (PCI DSS requirement for example), secondly I receive tons of request to actiavte on by default while you are the first to request it off by default Adrian Chadd said: The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. My thought: Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? As for this message: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Glen Barber replied: echo 'SYSLOG: no' /usr/local/etc/pkg.conf And Shane Ambler: now we can turn it off which I don't think we could before. Me again: Where is this documented? /root # man pkg.conf No manual entry for pkg.conf ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
On Sun, Dec 22, 2013 at 09:00:42AM -0500, Frank Seltzer wrote: On Sat, 21 Dec 2013, Steve Kargl wrote: On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Yeah, I noticed that spam along with the spam that is being spewed to /var/log/messaage, e.g., Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed Can you (portmgr) please mute these messages? -- Steve This received several responses. Greg Rivers said: Do you really feel that strongly about it? Having a record of changes to the system has always seemed like a feature to me... Baptiste Daroussin said: this has been done and activated for reason, first for lot of companies, it is important (PCI DSS requirement for example), secondly I receive tons of request to actiavte on by default while you are the first to request it off by default Adrian Chadd said: The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. My thought: Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? As for this message: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Glen Barber replied: echo 'SYSLOG: no' /usr/local/etc/pkg.conf And Shane Ambler: now we can turn it off which I don't think we could before. Me again: Where is this documented? /root # man pkg.conf No manual entry for pkg.conf pkg.conf man pages comes with pkg itself, just bootstrap it and you will get the manpage :) regards, Bapt pgppN2wGUhy2L.pgp Description: PGP signature
iwn trouble
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Hi, I'm running current and iwn fails to load. branch user/ed/newcons (from github) with latest commit: commit d16cc4039855b100f5b3e966a43dabe2028f2b57 Author: emaste ema...@freebsd.org Date: Fri Dec 6 13:58:23 2013 + Make Newcons options clear in GENERIC on the project branch My intel card is the following (pciconf -lv): iwn0@pci0:3:0:0:class=0x028000 card=0x13118086 chip=0x00898086 rev=0x5e hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Advanced-N + WiMAX 6250 [Kilmer Peak]' class = network dmesg has the following information: iwn0: Intel Centrino Advanced-N + WiMAX 6250 mem 0xf250-0xf2501fff irq 17 at device 0.0 on pci3 [and after service wpa_supplicant start wlan0] iwn0: iwn_config: could not configure runtime calibration iwn0: iwn_init_locked: could not configure device, error 35 An earlier kernel (from mid November) from the same branch works like a charm. Any hints? Is there more debug output I can provide to track this down? Cheers and thanks, Hannes -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBCQAGBQJStvZUAAoJELyJZYjffCjupYoP/j3SLrU21mSmydo6AxJaaBA3 +1I79QyyGoz6Kp3ea4sxSVMrnuWK3J6NKO5YCf0b10gjISA/iYOoHNh12Vltch3g x30+APbFtOq5IswO66HY816LOzYDo2fXGxMk/CZhspyOhJptC4bZWb9nrSoEQHEI UvjysflDUUDTa+vs/1CQ0Rall7FVmNSr7eeNdTCHhgV0xF7F7IqyUW6JbnDaYQEA mDwi5cxQNVhOeHjMd0wACO5rf09/bMdvo4m4DNnQNWrg9oPtbuWdRLMRtPZ0UC8W 4w+2ETWYgMCMiZO3kmwG76NI2jzXKHYwQO2/RrTahyWWcWuDzeJm5tK5PjxoN+JB B4B7AB/DIUQsUmBUhjZHTvg+U9Qa37wCWYGN5UO3aM4BEp4FTR4lsp80oEbt5/bt axOi1QVtZl1ZPOgZaoCXFiW4SQKA568uAiX8hlxfs2W1yAJ7CU4bfRyCugUVhBBK ZQAS1hX2sxXJHddrJwNNmAJ2/x+5NcYvzf4ij4hSIk5Gw4oP280rp/u2QIzCyhKx x8c5aPpJgIw/UNHYrBjAoHj+t5qHYANtgqLQUk3BEGOAoCsR2LzgBxObIZn+wRLv aS8qjC3NCknZLNuWPWdrQBleQV9EkqlJ7ODcgv82bqFUdNMwSKcmcX4TmLIvigDH CD+7c6uMkJB681a/IHTX =h++r -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
On 2013-12-22 15:00, Frank Seltzer wrote: On Sat, 21 Dec 2013, Steve Kargl wrote: On Sat, Dec 21, 2013 at 07:35:56PM +0100, d...@gmx.com wrote: I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Yeah, I noticed that spam along with the spam that is being spewed to /var/log/messaage, e.g., Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed Can you (portmgr) please mute these messages? -- Steve This received several responses. Greg Rivers said: Do you really feel that strongly about it? Having a record of changes to the system has always seemed like a feature to me... Baptiste Daroussin said: this has been done and activated for reason, first for lot of companies, it is important (PCI DSS requirement for example), secondly I receive tons of request to actiavte on by default while you are the first to request it off by default Adrian Chadd said: The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. My thought: Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? As for this message: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Glen Barber replied: echo 'SYSLOG: no' /usr/local/etc/pkg.conf And Shane Ambler: now we can turn it off which I don't think we could before. Me again: Where is this documented? /root # man pkg.conf No manual entry for pkg.conf Hm, on all my systems I have a man page for pkg.conf Here is the referenced passage from man 5 pkg.conf OPTIONS The following options can be defined in pkg.conf: ... SYSLOG: booleanThis option is enabled by default, log all the installation/deinstallation/upgrade oper- ation via syslog(3) What I agree is having it would be nice to have dedicated syslog (like yum.log) instead /var/log/messages since this is already spammed by most every process. -- olli ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
On 22/12/2013 14:55, olli hauer wrote: What I agree is having it would be nice to have dedicated syslog (like yum.log) instead /var/log/messages since this is already spammed by most every process. Add something like this to /etc/syslog.conf: !pkg *.* /var/log/pkg.log Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: PACKAGESITE spam
On 22/12/2013 16:08, Matthew Seaman wrote: On 22/12/2013 14:55, olli hauer wrote: What I agree is having it would be nice to have dedicated syslog (like yum.log) instead /var/log/messages since this is already spammed by most every process. Add something like this to /etc/syslog.conf: !pkg *.* /var/log/pkg.log ... although, yes, it's a bit archaic that there are as standard LOG_UUCP and LOG_NEWS facilities in syslog(3) -- neither of which are much used nowadays -- while there is only the generic LOG_DAEMON for things like webservers, LDAP, XMPP, PPP and many other network services, and nothing at all for system maintenance type things like updating packages. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: PACKAGESITE spam
On Sat, 2013-12-21 at 15:25 -0800, Steve Kargl wrote: On Sun, Dec 22, 2013 at 12:16:00AM +0100, Julien Laffaye wrote: On 12/22/2013 12:04 AM, Steve Kargl wrote: On Sat, Dec 21, 2013 at 11:14:39PM +0100, Baptiste Daroussin wrote: this has been done and activated for reason, first for lot of companies, companies can turn it on it they want it. And if you want to save the few extra kB, you can turn it off... I have turned it off. secondly I receive tons of request to actiavte on by default while you are the first to request it off by default I certainly can't refute 'tons of [private] requests'. There is no discussing of such logging in freebsd-current, freebsd-hackers, or freebsd-ports lists. Other than the noise in /var/log/message, what does this provide that 'pkg info' doesn't! Please turn of this feature by default. Actually, you are the one making noise... What does this logging in /var/log/message provide that is not provided by 'pkg info'? It is useless noise. Useless noise is what you get when someone holds an opinion that clearly nobody else agrees with, and yet they somehow think that just saying it over and over again will change peoples' minds. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
On Sun, 22 Dec 2013, Baptiste Daroussin wrote: On Sun, Dec 22, 2013 at 09:00:42AM -0500, Frank Seltzer wrote: /root # man pkg.conf No manual entry for pkg.conf pkg.conf man pages comes with pkg itself, just bootstrap it and you will get the manpage :) regards, Bapt OK, my bad, I did this on a 9.2-STABLE system by mistake. This question still stands. Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
On Sun, 22 Dec 2013 15:48:49 +0400, Gleb Smirnoff wrote: Steve, On Sat, Dec 21, 2013 at 12:14:03PM -0800, Steve Kargl wrote: S It did not ask how to stop this stupidity. I asked to have S this stupidity stopped by default. The spewing of this S information in /var/log/messages provides NOTHING. Please S turn it off by default. I am really suprised that someone might want to see this off by default. I concur. pkg info provides details of *currently installed* packages, whereas the information in syslog yields a *history*. This arrangement seems eminently reasonable to me. It all seems a bit of a storm in a teacup anyway, given that the logging can be directed to another file or turned off altogether, depending on requirements. My vote: Maintainers, thanks for your efforts and please keep it as it is. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
vfs_bio.c revision 259200 breaks writing to tape drive on current
The change to vfs_bio.c in revision 259200 breaks writing to scsi tape drive on i386 and sparc64 on current. I don't have any other machines to test on. here is example: r259199: (/)4794}mt rew (/)4795}tar cvf /dev/sa0 kernel a kernel r259200: (/)4781}mt rew (/)4782}tar cvf /dev/sa0 kernel a kerneltar: Write error the changes between the two revisions: line 3682 removed: bp-b_resid = bip-bio_resid; /* XXX: remove */ I noticed this when trying to do a dump and getting end of tape error. tried different tape drives , different cables no change. backed out r259200 to 259199 and everything works as before. Manfred || n...@pozo.com || || || ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
Frank Seltzer wrote, On 12/22/2013 15:00: Greg Rivers said: Do you really feel that strongly about it? Having a record of changes to the system has always seemed like a feature to me... Baptiste Daroussin said: this has been done and activated for reason, first for lot of companies, it is important (PCI DSS requirement for example), secondly I receive tons of request to actiavte on by default while you are the first to request it off by default Adrian Chadd said: The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. My thought: Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? As for this message: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file Glen Barber replied: echo 'SYSLOG: no' /usr/local/etc/pkg.conf And Shane Ambler: now we can turn it off which I don't think we could before. All of this is mostly off-topic. I haven't had any opposition to logging. Instead, I originally thought that the PACKAGESITE spam was a result of a bug, because -- the spam appeared with a recent installworld; -- there were like 50 consecutive messages every now and then; -- I don't recall ever setting up any PACKAGESITE-related variables (the timestamp on the file is 2013-04-05, so I could be WRONG); -- I looked for pkg.conf (only) in /etc, and didn't find it there; -- neither of the UPDATING files contain instructions regarding pkg.conf; -- I haven't payed too much attention to HEADSUP mails in the last few weeks (what relevant things did I miss?). Why is pkg.conf in /usr/local/etc instead of /etc? By contrast, why does the sample configuration file (/usr/local/etc/pkg.conf.sample) contain a line that links to a file in /etc, namely #PUBKEY : /etc/ssl/pkg.conf? The pkg.conf of a -RELEASE won't be as empty as mine is currently (causing PACKAGESITE spam), will it? If not (obviously), then what will it look like? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
GHCi vs iconv_open
After a recent installworld, GHCi (``ghc -i'' from lang/ghc) fails like so: % ghci GHCi, version 7.6.3: http://www.haskell.org/ghc/ :? for help Loading package ghc-prim ... linking ... done. Loading package integer-gmp ... linking ... done. Loading package base ... linking ... ghc: /usr/local/lib/ghc-7.6.3/base-4.6.0.1/HSbase-4.6.0.1.o: unknown symbol `iconv_open' ghc: unable to load package `base' Running portupgrade to rebuild all (most) ports didn't help. Where's the issue / Do what? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PACKAGESITE spam
On 12/22/2013 6:00 AM, Frank Seltzer wrote: Adrian Chadd said: The point is that some people like an audit trail. The audit trail for some people involves remote logging of syslog messages to a log host. This would include when packages are installed. There are two more: 1. When a port was deinstalled 2. History of a port (previous installs/deinstalls) For example, my logs have: Sep 9 16:05:28 chombo pkg-static: postfix-2.10.0,1 deinstalled Sep 9 16:05:36 chombo pkg-static: postfix-2.10.0,1 installed Nov 30 00:25:02 chombo pkg: postfix-2.10.0,1 deinstalled Nov 30 00:25:09 chombo pkg-static: postfix-2.10.2,1 installed Which tells me I recompiled postfix on Sept 9 (this would have been when I changed it over to openssl from ports) and updated it to 2.10.2 on Nov 30 using portmaster. How do I know that? Because of that deinstall log. When you use `pkg install` to upgrade a port, you get something like this: Jul 10 23:06:40 chombo pkg-static: ca_root_nss-3.15.1 installed Nov 29 15:04:52 chombo pkg: ca_root_nss reinstalled: 3.15.2_1 That information does not exist in the pkg database. My thought: Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? I have never understood why anyone would enable the use of syslog without also providing a way of specifying the facility and level. I'd much rather do stuff like this: local0.*/var/log/dovecot.log local1.*/var/log/postgres.log local2.*/var/log/php-fpm.log ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on i386/pc98
TB --- 2013-12-23 00:54:12 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-23 00:54:12 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-12-23 00:54:12 - starting HEAD tinderbox run for i386/pc98 TB --- 2013-12-23 00:54:12 - cleaning the object tree TB --- 2013-12-23 00:54:12 - /usr/local/bin/svn stat /src TB --- 2013-12-23 00:54:40 - At svn revision 259736 TB --- 2013-12-23 00:54:41 - building world TB --- 2013-12-23 00:54:41 - CROSS_BUILD_TESTING=YES TB --- 2013-12-23 00:54:41 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-23 00:54:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-23 00:54:41 - SRCCONF=/dev/null TB --- 2013-12-23 00:54:41 - TARGET=pc98 TB --- 2013-12-23 00:54:41 - TARGET_ARCH=i386 TB --- 2013-12-23 00:54:41 - TZ=UTC TB --- 2013-12-23 00:54:41 - __MAKE_CONF=/dev/null TB --- 2013-12-23 00:54:41 - cd /src TB --- 2013-12-23 00:54:41 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Mon Dec 23 00:54:50 UTC 2013 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools [...] c++ -O2 -pipe -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/include -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/lib/Transforms/Utils -I. -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd11.0\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd11.0\ -DDEFAULT_SYSROOT=\/obj/pc98.i386/src/tmp\ -I/obj/pc98.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libllvmtransformutils/../../../contrib/llvm/lib/Transforms/Utils/SimplifyIndVar.cpp -o SimplifyIndVar.o c++ -O2 -pipe -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/include -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/lib/Transforms/Utils -I. -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd11.0\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd11.0\ -DDEFAULT_SYSROOT=\/obj/pc98.i386/src/tmp\ -I/obj/pc98.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libllvmtransformutils/../../../contrib/llvm/lib/Transforms/Utils/SimplifyInstructions.cpp -o SimplifyInstructions.o c++ -O2 -pipe -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/include -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/lib/Transforms/Utils -I. -I/src/lib/clang/libllvmtransformutils/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\i386-unknown-freebsd11.0\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd11.0\ -DDEFAULT_SYSROOT=\/obj/pc98.i386/src/tmp\ -I/obj/pc98.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libllvmtransformutils/../../../contrib/llvm/lib/Transforms/Utils/SimplifyLibCalls.cpp -o SimplifyLibCalls.o /src/lib/clang/libllvmtransformutils/../../../contrib/llvm/lib/Transforms/Utils/SimplifyLibCalls.cpp: In member function 'virtual llvm::Value*unnamed::PrintFOpt::callOptimizer(llvm::Function*, llvm::CallInst*, llvm::IRBuildertrue, llvm::ConstantFolder, llvm::IRBuilderDefaultInsertertrue )': /src/lib/clang/libllvmtransformutils/../../../contrib/llvm/lib/Transforms/Utils/SimplifyLibCalls.cpp:1393: internal compiler error: Bus error: 10 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop. bmake[3]: stopped in /src/lib/clang/libllvmtransformutils *** Error code 1 Stop. bmake[2]: stopped in /src/lib/clang *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-12-23 01:54:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-12-23 01:54:53 - ERROR: failed to build world TB --- 2013-12-23 01:54:53 - 3147.52 user 342.38 system 3641.85 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-pc98.full ___ freebsd-current@freebsd.org mailing list
Re: ral(4) panic. head, r257837
ni is NULL, so it's probably line 1475.
On 19 Dec 2013, at 16:02, Adrian Chadd adr...@freebsd.org wrote:
Well there's a null node pointer. Need to figure out why. Its totally legit
to have them too, so the code has to cope.
Grr.
Adrian
On Dec 19, 2013 2:07 AM, Sergey V. Dyatko sergey.dya...@gmail.com wrote:
On Wed, 18 Dec 2013 23:40:23 -0800
Adrian Chadd adr...@freebsd.org wrote:
What's at frame 10?
And list the IP, ie:
list *0x817da911
(kgdb) f 10
#10 0x817da911 in rt2860_tx (sc=0xfe9bd000,
m=0xf80004c6dd00, ni=0x0)
at /usr/src/sys/modules/ral/../../dev/ral/rt2860.c:1472 1472{
Current language: auto; currently minimal
(kgdb) list *0x817da911
0x817da911 is in rt2860_tx
(/usr/src/sys/modules/ral/../../dev/ral/rt2860.c:1475). 1470static
int 1471rt2860_tx(struct rt2860_softc *sc, struct mbuf *m, struct
ieee80211_node *ni) 1472{
1473struct ifnet *ifp = sc-sc_ifp;
1474struct ieee80211com *ic = ifp-if_l2com;
1475struct ieee80211vap *vap = ni-ni_vap;
1476struct rt2860_tx_ring *ring;
1477struct rt2860_tx_data *data;
1478struct rt2860_txd *txd;
1479struct rt2860_txwi *txwi;
-a
On 18 December 2013 23:04, Sergey V. Dyatko sergey.dya...@gmail.com
wrote:
Hi,
I have following setup:
wlans_ral0=wlan0
ifconfig_wlan0=WPA
cloned_interfaces=lagg0 bridge0 tap0
ifconfig_lagg0=laggproto failover laggport alc0 laggport wlan0
DHCP ifconfig_bridge0=addm tap0 addm lagg0
When system boot I have reproducible panic after messages
Waiting 30s for the default route interface: .
ral0: need multicast update callback
ral0: need multicast update callback
:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x0
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x817da911
stack pointer = 0x28:0xfe011fe61da0
frame pointer = 0x28:0xfe011fe62630
118.
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1815 (dhclient)
Reading symbols from /boot/kernel/zfs.ko.symbols...done.
Loaded symbols for /boot/kernel/zfs.ko.symbols
Reading symbols from /boot/kernel/opensolaris.ko.symbols...done.
Loaded symbols for /boot/kernel/opensolaris.ko.symbols
Reading symbols from /boot/kernel/linux.ko.symbols...done.
Loaded symbols for /boot/kernel/linux.ko.symbols
Reading symbols from /boot/kernel/if_alc.ko.symbols...done.
Loaded symbols for /boot/kernel/if_alc.ko.symbols
Reading symbols from /boot/kernel/if_ral.ko.symbols...done.
Loaded symbols for /boot/kernel/if_ral.ko.symbols
Reading symbols from /boot/kernel/snd_hda.ko.symbols...done.
Loaded symbols for /boot/kernel/snd_hda.ko.symbols
Reading symbols from /boot/kernel/sound.ko.symbols...done.
Loaded symbols for /boot/kernel/sound.ko.symbols
Reading symbols from /boot/kernel/acpi_video.ko.symbols...done.
Loaded symbols for /boot/kernel/acpi_video.ko.symbols
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from /boot/modules/cuse4bsd.ko...done.
Loaded symbols for /boot/modules/cuse4bsd.ko
Reading symbols from /boot/kernel/sem.ko.symbols...done.
Loaded symbols for /boot/kernel/sem.ko.symbols
Reading symbols from /boot/kernel/linprocfs.ko.symbols...done.
Loaded symbols for /boot/kernel/linprocfs.ko.symbols
Reading symbols from /boot/kernel/if_lagg.ko.symbols...done.
Loaded symbols for /boot/kernel/if_lagg.ko.symbols
Reading symbols from /boot/kernel/if_bridge.ko.symbols...done.
Loaded symbols for /boot/kernel/if_bridge.ko.symbols
Reading symbols from /boot/kernel/bridgestp.ko.symbols...done.
Loaded symbols for /boot/kernel/bridgestp.ko.symbols
Reading symbols from /boot/kernel/if_tap.ko.symbols...done.
Loaded symbols for /boot/kernel/if_tap.ko.symbols
#0 doadump (textdump=0) at pcpu.h:219
219 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) #0 doadump (textdump=0) at pcpu.h:219
#1 0x803023ae in db_dump (dummy=value optimized out,
dummy2=0, dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:543
#2 0x80301e8d in db_command (cmd_table=value optimized
out) at /usr/src/sys/ddb/db_command.c:449
#3 0x80301c04 in db_command_loop ()
at /usr/src/sys/ddb/db_command.c:502
#4 0x80304570 in db_trap (type=value optimized out,
code=0) at /usr/src/sys/ddb/db_main.c:231
#5 0x8072e9d3 in kdb_trap (type=12, code=0, tf=value
optimized out) at /usr/src/sys/kern/subr_kdb.c:656
#6 0x80a81bb2 in trap_fatal (frame=0xfe011fe61cf0,
eva=value optimized out)
at /usr/src/sys/amd64/amd64/trap.c:870 #7 0x80a81ec9 in
Re: vfs_bio.c revision 259200 breaks writing to tape drive on current
On Sun, Dec 22, 2013 at 09:54:49AM -0800, Manfred Antar wrote: The change to vfs_bio.c in revision 259200 breaks writing to scsi tape drive on i386 and sparc64 on current. I don't have any other machines to test on. here is example: r259199: (/)4794}mt rew (/)4795}tar cvf /dev/sa0 kernel a kernel r259200: (/)4781}mt rew (/)4782}tar cvf /dev/sa0 kernel a kerneltar: Write error the changes between the two revisions: line 3682 removed: bp-b_resid = bip-bio_resid; /* XXX: remove */ I noticed this when trying to do a dump and getting end of tape error. tried different tape drives , different cables no change. backed out r259200 to 259199 and everything works as before. Manfred Show me the kdump of the tar commands on both revisions. pgpwAjgIAoPZD.pgp Description: PGP signature
