Re: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd))
On 12/01/12 22:53, Chris Rees wrote: On 1 Dec 2012 21:51, Andreas Tobler andreast-l...@fgznet.ch wrote: On 01.12.12 16:15, Robert Watson wrote: Dear all: I've now committed the build glue required to install the recently merged Audit Distribution Daemon (auditdistd) contributed by the Pawel Dawidek, and sponsored by the FreeBSD Foundation. This allows individual hosts generating audit trails to submit trails to a central audit server for review and safe keeping. Part of the goal is to ensure that a host submitting trail data can't later modify the trails. Pawel uses a variety of useful security- and resilience-related features such as TLS, Capsicum, etc, in auditdistd. As the recent security incident in the FreeBSD.org cluster illustrated, having reliable and detailed audit trails makes a big difference in forensic work, and hopefully this will allow the FreeBSD Project (and our users) to do that better in the future. Aehm, hope it is ok to 'complain' here. Happens when installing world. cd /export/devel/fbsd/head/src; /usr/obj/export/devel/fbsd/head/src/make.amd64/make -f Makefile.inc1 LOCAL_MTREE= hierarchy cd /export/devel/fbsd/head/src/etc; /usr/obj/export/devel/fbsd/head/src/make.amd64/make distrib-dirs mtree -eU -f /export/devel/fbsd/head/src/etc/mtree/BSD.root.dist -p / mtree -eU -f /export/devel/fbsd/head/src/etc/mtree/BSD.var.dist -p /var mtree: line 22: unknown user auditdistd *** [distrib-dirs] Error code 1 Does mergemaster -p help? Chris I had the very same problem and complained about it on current@. mergemaster -p definitely helped for me and I was given the advise to use mergemaster -p prior to every make installworld. Oliver signature.asc Description: OpenPGP digital signature
Re: RFC: sysctl -f filename
On Sun, Dec 02, 2012 at 01:50:48AM +0900, Hiroki Sato wrote:
I would like comments about the attached patch for sysctl(8) to add a
new option -f filename. It supports reading of a file with
key=value lines.
As you probably know, we already have /etc/sysctl.conf and it is
processed by rc.d/sysctl shell script in a line-by-line basis. The
problem I want to fix is a confusing syntax of /etc/sysctl.conf. The
file supports a typical configuration file syntax but problematic in
some cases. For example:
kern.coredump=1
works well in /etc/sysctl.conf, but
kern.coredump=1
does not work. Similarly, it is difficult to use whitespaces and #
in the value:
OK: kern.domainname=domain\ name\ with\ spaces
NG: kern.domainname=domain name with spaces
NG: kern.domainname=domain\ name\ including\ #\ character
NG: kern.domainname=domain\ name\ including\ \#\ character
The attached patch solves them, and in addition it displays an error
message with a line number if there is something wrong in the file
like this:
% cat -n /etc/sysctl.conf
...
10 kern.coredump=1
11 kern.coredump2=1
...
% /etc/rc.d/sysctl start
sysctl: kern.coredump at line 10: Operation not permitted
sysctl: unknown oid 'kern.coredump2' at line 11
# /etc/rc.d/sysctl start
kern.coredump: 1 - 1
sysctl: unknown oid 'kern.coredump2' at line 11
Any comments are welcome.
The idea is OK but the format of the file is messy. Further comments
inline.
Index: sbin/sysctl/sysctl.8
===
--- sbin/sysctl/sysctl.8 (revision 243756)
+++ sbin/sysctl/sysctl.8 (working copy)
@@ -28,7 +28,7 @@
.\ From: @(#)sysctl.8 8.1 (Berkeley) 6/6/93
.\ $FreeBSD$
.\
-.Dd January 17, 2011
+.Dd November 22, 2012
.Dt SYSCTL 8
.Os
.Sh NAME
@@ -37,6 +37,7 @@
.Sh SYNOPSIS
.Nm
.Op Fl bdehiNnoqx
+.Op Fl f Ar filename
.Ar name Ns Op = Ns Ar value
.Ar ...
.Nm
@@ -80,6 +81,11 @@
or
.Fl n
is specified, or a variable is being set.
+.It Fl f Ar filename
+Specify a file which contains a pair of name and value in each line.
+.Nm
+reads and processes the specified file first and then processes the name
+and value pairs in the command line argument.
The file format is not described.
.It Fl h
Format output for human, rather than machine, readability.
.It Fl i
Index: sbin/sysctl/sysctl.c
===
--- sbin/sysctl/sysctl.c (revision 243756)
+++ sbin/sysctl/sysctl.c (working copy)
@@ -56,13 +56,16 @@
#include stdio.h
#include stdlib.h
#include string.h
+#include sysexits.h
#include unistd.h
+static const char *conffile;
static int aflag, bflag, dflag, eflag, hflag, iflag;
-static int Nflag, nflag, oflag, qflag, xflag, warncount;
+static int Nflag, nflag, oflag, qflag, xflag;
static int oidfmt(int *, int, char *, u_int *);
-static void parse(char *);
+static int parsefile(const char *);
+static int parse(char *, int);
static int show_var(int *, int);
static int sysctl_all(int *oid, int len);
static int name2oid(char *, int *);
@@ -74,7 +77,7 @@
{
(void)fprintf(stderr, %s\n%s\n,
- usage: sysctl [-bdehiNnoqx] name[=value] ...,
+ usage: sysctl [-bdehiNnoqx] [-f filename] name[=value] ...,
sysctl [-bdehNnoqx] -a);
exit(1);
}
@@ -83,12 +86,13 @@
main(int argc, char **argv)
{
int ch;
+ int warncount = 0;
setlocale(LC_NUMERIC, );
setbuf(stdout,0);
setbuf(stderr,0);
- while ((ch = getopt(argc, argv, AabdehiNnoqwxX)) != -1) {
+ while ((ch = getopt(argc, argv, Aabdef:hiNnoqwxX)) != -1) {
switch (ch) {
case 'A':
/* compatibility */
@@ -106,6 +110,9 @@
case 'e':
eflag = 1;
break;
+ case 'f':
+ conffile = strdup(optarg);
+ break;
case 'h':
hflag = 1;
break;
@@ -146,13 +153,15 @@
usage();
if (aflag argc == 0)
exit(sysctl_all(0, 0));
- if (argc == 0)
+ if (argc == 0 conffile == NULL)
usage();
-
warncount = 0;
+ if (conffile != NULL)
+ warncount += parsefile(conffile);
while (argc-- 0)
- parse(*argv++);
- exit(warncount);
+ warncount += parse(*argv++, 0);
+
+ return (warncount);
}
/*
@@ -160,8 +169,8 @@
* Lookup and print out the MIB entry if it exists.
* Set a new value if requested.
*/
-static void
-parse(char *string)
+static int
+parse(char *string, int lineno)
{
int len, i, j;
void *newval = 0;
@@ -173,17 +182,30 @@
int64_t i64val;
uint64_t u64val;
int
Re: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd))
On Sun, 2 Dec 2012, O. Hartmann wrote: Does mergemaster -p help? I had the very same problem and complained about it on current@. mergemaster -p definitely helped for me and I was given the advise to use mergemaster -p prior to every make installworld. Just to follow up on this thread, since the question has come up a number of times. mergemaser -p should be run prior to installworld always, but most of the time will do very little. One of its responsibilities is to add any necessary accounts and groups depended on by base system components -- e.g., that will be referenced during installworld as part of setting file ownership and groups. One of the primary sources of new users and groups has been chroot/etc sandboxes -- independent from the role of a daemon as a file owner. My hope is that this will reduce over time with increasing use Capsicum sandboxes, which don't require custom UIDs/GIDs. However, there are still cases where you want a daemon, for reasons of file and group ownership, to run as a specific user, as is the case with auditdistd, which does support Capsicum (where enabled). Robert ___ 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: gcc46: .././../gcc-4.6-20121123/gcc/rtl.h:2105:31: error: use of undeclared identifier 'FIRST_PSEUDO_REGISTER', rtx x_initial_regno_reg_rtx[FIRST_PSEUDO_REGISTER];
On 2012-12-01 13:18, O. Hartmann wrote: On exactly ONE FreeBSD 10.0-CURRENT box, out of a couple, all the same OS version (most recent sources/buildworld with CLANG and ports tree always up to date) I get this nasty error shown below. ... In file included from .././../gcc-4.6-20121123/gcc/genflags.c:28: .././../gcc-4.6-20121123/gcc/rtl.h:1989:13: warning: ISO C forbids forward references to 'enum' types [-Wpedantic] extern enum reg_class reg_preferred_class (int); ^ .././../gcc-4.6-20121123/gcc/rtl.h:2105:31: error: use of undeclared identifier 'FIRST_PSEUDO_REGISTER' rtx x_initial_regno_reg_rtx[FIRST_PSEUDO_REGISTER]; ^ .././../gcc-4.6-20121123/gcc/rtl.h:2112:31: error: use of undeclared identifier 'FIRST_PSEUDO_REGISTER' rtx x_static_reg_base_value[FIRST_PSEUDO_REGISTER]; ^ Can you post the full build log somewhere? ___ 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: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd))
Robert Watson wrote: Dear all: I've now committed the build glue required to install the recently merged Audit Distribution Daemon (auditdistd) contributed by the Pawel Dawidek, and sponsored by the FreeBSD Foundation. This allows individual hosts generating audit trails to submit trails to a central audit server for review and safe keeping. Part of the goal is to ensure that a host submitting trail data can't later modify the trails. Pawel uses a variety of useful security- and resilience-related features such as TLS, Capsicum, etc, in auditdistd. As the recent security incident in the FreeBSD.org cluster illustrated, having reliable and detailed audit trails makes a big difference in forensic work, and hopefully this will allow the FreeBSD Project (and our users) to do that better in the future. Robert N M Watson Computer Laboratory University of Cambridge Is auditdistd going to be included in the base system as of 10.0-RELEASE or be a port that runs on 10.0-RELEASE and newer? ___ 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: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd))
On 2 Dec 2012, at 14:21, Fbsd8 wrote: I've now committed the build glue required to install the recently merged Audit Distribution Daemon (auditdistd) contributed by the Pawel Dawidek, and sponsored by the FreeBSD Foundation. This allows individual hosts generating audit trails to submit trails to a central audit server for review and safe keeping. Part of the goal is to ensure that a host submitting trail data can't later modify the trails. Pawel uses a variety of useful security- and resilience-related features such as TLS, Capsicum, etc, in auditdistd. As the recent security incident in the FreeBSD.org cluster illustrated, having reliable and detailed audit trails makes a big difference in forensic work, and hopefully this will allow the FreeBSD Project (and our users) to do that better in the future. Is auditdistd going to be included in the base system as of 10.0-RELEASE or be a port that runs on 10.0-RELEASE and newer? The plan is that auditdistd will be included in the base operating system for FreeBSD 10.0, and it is now integrated into the development branch that will naturally lead to that outcome; I would like to get it merged to stable/9 for inclusion in a future 9.2 release as well, but that will require a bit more work. I'll plan to let it shake out in 10-CURRENT for at least a few weeks, and let more users report on their experiences, before looking at a merge to 9.x. Robert ___ 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: New jail does not understand nullfs
On Sun, 2012-12-02 at 01:17 -0600, Matt Donovan wrote:
When attempting to start the jail in question the following happens
server# jail -c poudriere
jail: poudriere: unknown parameter: allow.mount.nullfs
Below is my jail.conf
poudriere {
name=poudriere;
host.hostname=poudriere;
ip4.addr=192.168.1.30;
persist;
children.max=10;
allow.mount;
mount.devfs;
allow.mount.nullfs;
allow.raw_sockets;
allow.socket_af;
allow.sysvipc;
enforce_statfs=1;
path=/newsystem/jail/poudriere;
exec.stop=umount -a;
}
Does the switch not work yet? As I am using CURRENT with the latest
revision.
That mount.devfs doesn't look right, should that have allow. on the
front? I wonder if that's the problem and the error report is off by
one line or something?
-- 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: 9.1-RC3 default Linux ALSA configuration
Or maybe there is another way to set /dev/dsp to be /dev/dsp0 (or
others) at system level? That would be even better that setting every
config file by hand, just to point to the default dsp device :-)
On Fri, Nov 30, 2012 at 2:45 PM, CeDeROM cede...@tlen.pl wrote:
I have installed and started Skype (2.1 and 2.2 devel) with success
using Linux binaries provided in port tree. However there is an issue
with default ALSA configuration and sound/calls does not work properly
off out the box. I suggest to set /dev/dsp0 and /dev/mixer0 as default
devices in the alsa configuration, so the sound works on the default
audio device. Right now it does not work at all.
# pcm-oss plugin configuration
pcm.oss {
type oss
device /dev/dsp0
hint {
description Open Sound System
}
}
ctl.oss {
type oss
device /dev/mixer0
hint {
description Open Sound System
}
}
Best regards :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
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: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd))
On Sun, Dec 2, 2012 at 8:05 AM, Robert Watson rwat...@freebsd.org wrote: Just to follow up on this thread, since the question has come up a number of times. mergemaser -p should be run prior to installworld always, but most of the time will do very little. One of its responsibilities is to add any necessary accounts and groups depended on by base system components -- e.g., that will be referenced during installworld as part of setting file ownership and groups. I often use make installworld installkernel distribution DESTDIR=... to create bootable images (e.g. for a USB stick). What's the recommendation for that case? Manually create the auditdistd user on the build host? ___ 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: A suspicious warning in sys/boot/zfs/zfsimpl.c
On 2012-12-01 12:05, Andriy Gapon wrote: on 01/12/2012 12:59 Garrett Cooper said the following: On Mon, Jul 2, 2012 at 6:21 PM, Taku YAMAMOTO t...@tackymt.homeip.net wrote: When I built the world as of r237813, clang reported a warning which caught my attention. === sys/boot/zfs (all) clang -O2 -pipe -march=pentium4 -DBOOTPROG=\zfsloader\ -I/usr/src/sys/boot/zfs/../common -I/usr/src/sys/boot/zfs/../.. -I. -I/usr/src/sys/boot/zfs/../../../lib/libstand -I/usr/src/sys/boot/zfs/../../cddl/boot/zfs -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -Wformat -Wall -DNDEBUG -std=gnu99 -Qunused-arguments -c /usr/src/sys/boot/zfs/zfs.c -o zfs.o In file included from /usr/src/sys/boot/zfs/zfs.c:48: /usr/src/sys/boot/zfs/zfsimpl.c:2033:19: warning: array index 264 is past the end of the array (which contains 192 elements) [-Warray-bounds] memcpy(path, dn.dn_bonus[sizeof(znode_phys_t)], ^ /usr/src/sys/boot/zfs/../../cddl/boot/zfs/zfsimpl.h:788:2: note: array 'dn_bonus' declared here uint8_t dn_bonus[DN_MAX_BONUSLEN - sizeof (blkptr_t)]; ^ I don't have a zfs-powered machine, so I'm not sure whether this warning is false-positive or not. I'm seeing the same warnings trying to build HEAD r242903 with clang on amd64. Andriy CCed. I believe that there is no actual problem there. Indeed. The ZFS code seems to be using the dnode_phys_t::dn_bonus field as a sort of flexible struct member. These specific warnings can be ignored, or turned off. ___ 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: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd))
On 2 Dec 2012, at 15:34, Ryan Stone wrote: On Sun, Dec 2, 2012 at 8:05 AM, Robert Watson rwat...@freebsd.org wrote: Just to follow up on this thread, since the question has come up a number of times. mergemaser -p should be run prior to installworld always, but most of the time will do very little. One of its responsibilities is to add any necessary accounts and groups depended on by base system components -- e.g., that will be referenced during installworld as part of setting file ownership and groups. I often use make installworld installkernel distribution DESTDIR=... to create bootable images (e.g. for a USB stick). What's the recommendation for that case? Manually create the auditdistd user on the build host? Yes, that's probably the best short-term bet. In the longer term, it would be nice of installworld could not only generate an mtree on the side rather than directly chmod/chowning the files (Brooks Davis has patches for this), but also use UIDs/GIDs from a user database directly rather than assuming that the host where you are constructing the image has the same notion of users and groups. This is especially important if we want to support cross-building embedded images from Linux, Mac OS X, etc, in the future. Robert ___ 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: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd))
On 2 Dec 2012 15:34, Ryan Stone ryst...@gmail.com wrote: On Sun, Dec 2, 2012 at 8:05 AM, Robert Watson rwat...@freebsd.org wrote: Just to follow up on this thread, since the question has come up a number of times. mergemaser -p should be run prior to installworld always, but most of the time will do very little. One of its responsibilities is to add any necessary accounts and groups depended on by base system components -- e.g., that will be referenced during installworld as part of setting file ownership and groups. I often use make installworld installkernel distribution DESTDIR=... to create bootable images (e.g. for a USB stick). What's the recommendation for that case? Manually create the auditdistd user on the build host? You could run mergemaster -p; it doesn't do anything that would hurt your running system; just adds important users etc. Chris ___ 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: A suspicious warning in sys/boot/zfs/zfsimpl.c
On 2012-12-02 01:37, Garrett Cooper wrote: On Sat, Dec 1, 2012 at 3:05 AM, Andriy Gapon a...@freebsd.org wrote: I believe that there is no actual problem there. It's probably bugs with clang dealing with alignment problems. Which bugs? These warnings (and others) go largely unnoticed because of the fact that -Werror isn't on on sys/boot. I filed kern/173932 for that and have been grinding away on warnings for the past couple days in my spare time -- with my local modifications sys/boot compiles with -Werror now with gcc, but not clang. Thanks, -Garrett /store/freebsd/head/sys/boot/i386/zfsboot/zfsboot.c:101:24: error: tentative definition of variable with internal linkage has incomplete non-array type 'struct zfsmount' [-Werror,-Wtentative-definition-incomplete-type] static struct zfsmount zfsmount; ^ /store/freebsd/head/sys/boot/i386/zfsboot/zfsboot.c:101:15: note: forward declaration of 'struct zfsmount' static struct zfsmount zfsmount; ^ This is just a programming error: struct zfsmount is declared in zfsimpl.c, but that file is included on line 151, so 50 lines after the static variable definition. Either the include should be moved up, or the definition moved down. In file included from /store/freebsd/head/sys/boot/i386/zfsboot/zfsboot.c:151: In file included from /store/freebsd/head/sys/boot/i386/zfsboot/../../zfs/zfsimpl.c:38: /store/freebsd/head/sys/boot/i386/zfsboot/../../../cddl/boot/zfs/zfssubr.c:207:9: error: cast from 'char *' to 'zio_eck_t *' (aka 'struct zio_eck *') increases required alignment from 1 to 4 [-Werror,-Wcast-align] eck = (zio_eck_t *)((char *)data + size) - 1; ^~ Clang is right here, the alignment *is* being increased. However, on x86, there is no problem with it, so the warning can be ignored. On the other hand, if the code should be portable to alignment-sensitive arches, the code should be fixed. The same holds for all the other alignment warnings. The difference between gcc and clang is that gcc never seems to warn about alignment issues on x86. You must compile the code with a gcc targeting an alignment-sensitive arch, to get any warnings. Clang always warns, when using -Wcast-align. ___ 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: 9.1-RC3 default Linux ALSA configuration
02.12.2012 19:20, CeDeROM пишет:
On Fri, Nov 30, 2012 at 2:45 PM, CeDeROM cede...@tlen.pl wrote:
I have installed and started Skype (2.1 and 2.2 devel) with success
using Linux binaries provided in port tree. However there is an issue
with default ALSA configuration and sound/calls does not work properly
off out the box. I suggest to set /dev/dsp0 and /dev/mixer0 as default
devices in the alsa configuration, so the sound works on the default
audio device. Right now it does not work at all.
# pcm-oss plugin configuration
pcm.oss {
type oss
device /dev/dsp0
hint {
description Open Sound System
}
}
ctl.oss {
type oss
device /dev/mixer0
hint {
description Open Sound System
}
}
Or maybe there is another way to set /dev/dsp to be /dev/dsp0 (or
others) at system level? That would be even better that setting every
config file by hand, just to point to the default dsp device :-)
I've just committed a fix to linux-f10-alsa-lib port. The port now
creates a soft link to the native FreeBSD configuration file at
LINUXBASE. That may help here.
--
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: Is cross-world building broken?
On Fri, 2012-11-30 at 14:16 -0800, Garrett Cooper wrote: On Nov 30, 2012, at 10:14 AM, Ian Lepore free...@damnhippie.dyndns.org wrote: On Fri, 2012-11-30 at 09:36 -0800, Simon J. Gerraty wrote: On Fri, 30 Nov 2012 08:15:03 -0700, Ian Lepore writes: So when did this break, and why can't it be fixed? I've been using Sorry I missed the begining of this thread, is anything broken? Apparently the only thing that's broken is the original implication in this mail thread that something is broken, and also the advice that DESTDIR must not be specified on a make command line for targets other than installworld, installkernel, or distribute. (To be fair, the original was more of a question, but then what followed were replies that reinforced an implication that something is really wrong.) I finally got updated with -current this morning and I find that my cross-build scripts which just blindly always pass DESTDIR=somepath on the make command line regardless of the targets being built still work fine, like they always have. I haven't experienced anything myself, I assumed because I've been too busy to update any of my -current sandboxes for weeks. I was just going by the earlier messages in this thread, which were roughly A cross-build breaks early in the process if DESTDIR is set followed by DESTDIR must only be set for installworld, buildworld, and distribute targets. s/buildworld/installkernel/ Oops, indeed; sorry for contributing to the confusion. -- 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: 9.1-RC3 default Linux ALSA configuration
On Sun, Dec 2, 2012 at 5:44 PM, Boris Samorodov b...@passap.ru wrote:
I've just committed a fix to linux-f10-alsa-lib port. The port now
creates a soft link to the native FreeBSD configuration file at
LINUXBASE. That may help here.
Hey Boris :-) What is the native configuration file location? I only
have /compat/linux/etc/alsa/pcm/pcm-oss.conf file.
What is more, according to
http://www.freebsd.org/cgi/man.cgi?query=pcmsektion=4
hw.snd.default_unit
Default sound card for systems with multiple sound cards. When
using devfs(5), the default device for /dev/dsp. Equivalent to a
symlink from /dev/dsp to /dev/dsp${hw.snd.default_unit}.
But this does not solve the alsa issue for linux even if my default
device is 0, so the /dev/dsp should point to /dev/dsp0 (?) or
/dev/dsp.0.0 (?).
On another machine with SB Audigy I have no sound at all, but the
calls are ongoing (no audio device problem). Any suggestions? :-)
Thanks :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
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: 9.1-RC3 default Linux ALSA configuration
Hi Tomek, 03.12.2012 01:08, CeDeROM пишет: What is the native configuration file location? I only have /compat/linux/etc/alsa/pcm/pcm-oss.conf file. It's the configuration file that is installed by audio/alsa-lib: LOCALBASE/etc/asound.conf. As for the rest, I'm not an expert with sound, sorry. :-( Hope somebody else may help you. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: 9.1-RC3 default Linux ALSA configuration
On Sun, Dec 2, 2012 at 10:26 PM, Boris Samorodov b...@passap.ru wrote: 03.12.2012 01:08, CeDeROM пишет: It's the configuration file that is installed by audio/alsa-lib: LOCALBASE/etc/asound.conf. Perfect solution! Replacing /compat/linux/etc/asound.conf with /usr/local/etc/asound.conf (or using the symlink as you suggeted) also solved my issue on the other machine :-) The configuration for 7.1 sound is more complex and valid for native alsa-lib on FreeBSD, this good configuration also propagates on Linux emulation :-) THANKS A LOT BORIS!!! :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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
looking for help from ppp users
Hey all, I'm working on a project to review the FAQ: http://wiki.freebsd.org/ThwackAFAQ I need volunteers to question through the questions starting userppp through desperation and review them. If you don't have time to go through them all, just pick one and make this a group process. Is it factually correct? Does it use deprecated functionality? Is it completely outdated to the point we should remove it? Does it need better examples? Is it clear and concise? Typos and spelling mistakes It isn't that hard and would be a great help! -- Eitan Adler ___ 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: New jail does not understand nullfs
On Sun, Dec 02, 2012 at 08:09:39AM -0700, Ian Lepore wrote:
On Sun, 2012-12-02 at 01:17 -0600, Matt Donovan wrote:
When attempting to start the jail in question the following happens
server# jail -c poudriere
jail: poudriere: unknown parameter: allow.mount.nullfs
Below is my jail.conf
poudriere {
name=poudriere;
host.hostname=poudriere;
ip4.addr=192.168.1.30;
persist;
children.max=10;
allow.mount;
mount.devfs;
allow.mount.nullfs;
allow.raw_sockets;
allow.socket_af;
allow.sysvipc;
enforce_statfs=1;
path=/newsystem/jail/poudriere;
exec.stop=umount -a;
}
Does the switch not work yet? As I am using CURRENT with the latest
revision.
That mount.devfs doesn't look right, should that have allow. on the
front? I wonder if that's the problem and the error report is off by
one line or something?
mount.devfs means mount devfs :)
However, it indeed may be some issue with config parsing, e.g. some
mishandled whitespace.
Matt, in general this should work just fine. What revision are you using
to test? Can you attach this config instead of copy-pasting it?
--
Mateusz Guzik mjguzik gmail.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: New jail does not understand nullfs
Attached is my jail.conf. according to my logs I am using r243464. Going to
do another svn update and try again as well.
On Dec 2, 2012 7:12 PM, Mateusz Guzik mjgu...@gmail.com wrote:
On Sun, Dec 02, 2012 at 08:09:39AM -0700, Ian Lepore wrote:
On Sun, 2012-12-02 at 01:17 -0600, Matt Donovan wrote:
When attempting to start the jail in question the following happens
server# jail -c poudriere
jail: poudriere: unknown parameter: allow.mount.nullfs
Below is my jail.conf
poudriere {
name=poudriere;
host.hostname=poudriere;
ip4.addr=192.168.1.30;
persist;
children.max=10;
allow.mount;
mount.devfs;
allow.mount.nullfs;
allow.raw_sockets;
allow.socket_af;
allow.sysvipc;
enforce_statfs=1;
path=/newsystem/jail/poudriere;
exec.stop=umount -a;
}
Does the switch not work yet? As I am using CURRENT with the latest
revision.
That mount.devfs doesn't look right, should that have allow. on the
front? I wonder if that's the problem and the error report is off by
one line or something?
mount.devfs means mount devfs :)
However, it indeed may be some issue with config parsing, e.g. some
mishandled whitespace.
Matt, in general this should work just fine. What revision are you using
to test? Can you attach this config instead of copy-pasting it?
--
Mateusz Guzik mjguzik gmail.com
jail.conf
Description: Binary data
___
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: looking for help from ppp users
On 03/12/2012, at 9:49, Eitan Adler li...@eitanadler.com wrote: I'm working on a project to review the FAQ: http://wiki.freebsd.org/ThwackAFAQ I need volunteers to question through the questions starting userppp through desperation and review them. If you don't have time to go through them all, just pick one and make this a group process. Is it factually correct? Does it use deprecated functionality? Is it completely outdated to the point we should remove it? Does it need better examples? Is it clear and concise? Typos and spelling mistakes It isn't that hard and would be a great help! 14.6 should probably read.. If you have Link Quality Reporting (LQR) configured, it is possible that too many LQR packets are lost between your machine and the peer. The ppp(8) program deduces that the line must therefore be bad, and disconnects. Prior to FreeBSD version 2.2.5, LQR was enabled by default. It is now disabled by default. LQR can be enabled with the following line: enable lqr [ie demonstrate how to enable it since it's off by default] Is Brian Somers still a FreeBSD committer? Section 14.9 has his email address and suggests you contact him under some circumstances. I would delete 14.11 because openmode is now the default and 14.12 mentions how and why you should disable it. Section 14.20 says that PPP doesn't dump core because it is run as root, this is incorrect - it doesn't dump core because it is set UID. Section 14.22 could basically be replaced with use 'nat same_ports yes', or suggest the user use PF for NAT and run the miniupnpd port. Certainly these days games (and every other network app) are much more NAT savvy due to its prevalence. I would also add a section about MTU - I expect the dominant use case for PPP is ADSL these days. In this case the MTU is usually limited to 1492 bytes (1500 byte ethernet frame minus PPP framing overhead). If all ICMP is blocked at some part of the link then packet fragmentation doesn't work properly and you end up with symptoms like interactive SSH logins work but bulk SCP or FTPs don't. I hope that helps! -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Re: looking for help from ppp users
On 2 December 2012 21:43, Daniel O'Connor docon...@gsoft.com.au wrote: ... I've marked the appropriate sections as red on the http://wiki.freebsd.org/ThwackAFAQ page. Should I mark the rest green or were they unreviewed? Either way the feedback so far will be taken into account. I would also add a section about MTU - I expect the dominant use case for PPP is ADSL these days. In this case the MTU is usually limited to 1492 bytes (1500 byte ethernet frame minus PPP framing overhead). If all ICMP is blocked at some part of the link then packet fragmentation doesn't work properly and you end up with symptoms like interactive SSH logins work but bulk SCP or FTPs don't. I've added this to http://wiki.freebsd.org/NewFAQs I hope that helps! It was very useful - thank you! Myself, or another volunteer should get to them in due time. At the moment I'm just trying to get triage done. -- Eitan Adler ___ 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
problem with keyboard during installation
I am trying to install a new system using FreeBSD-10.0-CURRENT-amd64-release.iso.xz (from https://snapshots.glenbarber.us/Latest/). I am having a problem with the keyboard. I have tried all possible options of US keyboards, and also the option not to change the keyboard. The problem specifically is that when I try to change the amount of space of a partition I am unable to navigate using the arrow keys. When I try to use the right arrow key to move the cursor, it moves the cursor to the OK button. But that is not what I want to do. I want to setup the partitions manually, but the keys will not allow me to. I know there have been a lot of changes to the install code recently, has anyone else seen this behavior? I have tried wired and wireless USB keyboards, I am currently typing this from the wireless keyboard. so I know it works. There was some discussion concerning this here: http://comments.gmane.org/gmane.os.freebsd.current/135395 Any help would be appreciated. Thanks in advance. ___ 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
please add auditdistd user/group to -stable and the 9.1-release?
Hi, Would you guys please add the auditdistd user/group info to 9.1-release, so people doing crossbuilds of -HEAD on a fresh 9.1-RELEASE won't get an install error? Thanks, Adrian ___ 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: please add auditdistd user/group to -stable and the 9.1-release?
On Sun, Dec 2, 2012 at 9:08 PM, Adrian Chadd adr...@freebsd.org wrote: Hi, Would you guys please add the auditdistd user/group info to 9.1-release, so people doing crossbuilds of -HEAD on a fresh 9.1-RELEASE won't get an install error? Or mtree could just use -w instead in Makefile.inc1 and distribute. Let me do some investigation to determine whether or not this is a valid solution to this problem. -Garrett ___ 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: looking for help from ppp users
On 03/12/2012, at 13:52, Eitan Adler li...@eitanadler.com wrote: On 2 December 2012 21:43, Daniel O'Connor docon...@gsoft.com.au wrote: ... I've marked the appropriate sections as red on the http://wiki.freebsd.org/ThwackAFAQ page. Should I mark the rest green or were they unreviewed? Either way the feedback so far will be taken into account. I eyeballed all of the PPP FAQ entries and I couldn't find anything else wrong. I didn't try them though and only relied on my memory. For 14.17 and 14.23 I didn't really know about the gory details so I just assumed it was correct.. I would also add a section about MTU - I expect the dominant use case for PPP is ADSL these days. In this case the MTU is usually limited to 1492 bytes (1500 byte ethernet frame minus PPP framing overhead). If all ICMP is blocked at some part of the link then packet fragmentation doesn't work properly and you end up with symptoms like interactive SSH logins work but bulk SCP or FTPs don't. I've added this to http://wiki.freebsd.org/NewFAQs I hope that helps! It was very useful - thank you! Myself, or another volunteer should get to them in due time. At the moment I'm just trying to get triage done. OK thanks for your efforts! BTW I see the serial port section is similarly stale (it still mentions sio instead of uart) and as the wiki page says, it doesn't mention any USB to RS232 adapters (which are likely to be what most people see on modern systems). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Re: please add auditdistd user/group to -stable and the 9.1-release?
On Sun, Dec 2, 2012 at 9:20 PM, Garrett Cooper yaneg...@gmail.com wrote:
On Sun, Dec 2, 2012 at 9:08 PM, Adrian Chadd adr...@freebsd.org wrote:
Hi,
Would you guys please add the auditdistd user/group info to
9.1-release, so people doing crossbuilds of -HEAD on a fresh
9.1-RELEASE won't get an install error?
Or mtree could just use -w instead in Makefile.inc1 and distribute.
Let me do some investigation to determine whether or not this is a
valid solution to this problem.
I've done some digging in the source tree and this seems like a
potentially workable solution for the issue reported -- in part
because auditdistd is only present in BSD.var.dist, /etc/rc.d/var runs
BSD.var.dist at boot, etc:
Index: etc/Makefile
===
--- etc/Makefile(revision 243802)
+++ etc/Makefile(working copy)
@@ -293,7 +293,7 @@
distrib-dirs:
mtree -eU ${MTREE_FOLLOWS_SYMLINKS} -f
${.CURDIR}/mtree/BSD.root.dist -p ${DESTDIR}/
- mtree -eU ${MTREE_FOLLOWS_SYMLINKS} -f
${.CURDIR}/mtree/BSD.var.dist -p ${DESTDIR}/var
+ mtree -eUw ${MTREE_FOLLOWS_SYMLINKS} -f
${.CURDIR}/mtree/BSD.var.dist -p ${DESTDIR}/var
mtree -eU ${MTREE_FOLLOWS_SYMLINKS} -f
${.CURDIR}/mtree/BSD.usr.dist -p ${DESTDIR}/usr
mtree -eU ${MTREE_FOLLOWS_SYMLINKS} -f
${.CURDIR}/mtree/BSD.include.dist \
-p ${DESTDIR}/usr/include
I'm running a build still to confirm this.
I'll look into a more generic solution, but this should get people
past r243752 without having to install a master.passwd file everywhere
with auditdistd in it. A better solution would potentially be to delay
processing the mtree files until later and run it via another script
which could handle sequencing things properly (either directly via
mtree, or better, via a make target). I have other ideas for this but
I need to sleep on them because they might not seem workable later.
Thanks,
-Garrett
___
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
