Re: kern/172931: Suspen/resume blocks USB mouse
The following reply was made to PR kern/172931; it has been noted by GNATS. From: J B To: bug-follo...@freebsd.org, jb.1234a...@gmail.com Cc: Subject: Re: kern/172931: Suspen/resume blocks USB mouse Date: Sat, 27 Oct 2012 10:06:58 +0200 Supplemental info. I repeated these tests twice. Reboot. 'startx' for XFCE. Before suspend: $ ps auxwww|grep mouse root 1296 0.0 0.1 9608 1456 ?? Is9:26AM 0:00.10 /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid root 1671 0.0 0.1 9608 1500 ?? Ss9:26AM 0:00.01 /usr/sbin/moused -p /dev/psm0 -t auto root 1796 0.0 0.2 12244 3176 ?? I 9:26AM 0:00.02 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy) root 1824 0.0 0.2 12244 3184 ?? I 9:26AM 0:00.01 hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy) Trial 1 --- Suspend (XFCE panel: menu: user JB - Suspend) Resume (power switch ON). After resume: $ ps auxwww|grep mouse root 1671 0.0 0.1 9608 1500 ?? Ss9:27AM 0:00.79 /usr/sbin/moused -p /dev/psm0 -t auto root 1796 0.0 0.2 12244 3176 ?? I 9:27AM 0:00.02 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy) root 2007 0.0 0.1 9608 1556 ?? Is9:32AM 0:00.07 /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid root 2063 0.0 0.2 12244 3452 ?? I 9:33AM 0:00.01 hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy) Note: - first suspend/resume seems to work OK (both mouses work). - the moused PIDs are different for USB mouse (1296 -> 2007) Trial 2 --- Suspend (XFCE panel: menu: user JB - Suspend) Resume (power switch ON). After resume: $ ps auxwww|grep mouse root 1671 0.0 0.1 9608 1500 ?? Ss9:27AM 0:00.93 /usr/sbin/moused -p /dev/psm0 -t auto root 1796 0.0 0.2 12244 3176 ?? I 9:28AM 0:00.02 hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy) Note: - second suspend/resume blocks USB mouse - neither HAL nor moused processes present jb ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/173076: New Port: sysutils/jail another rc-script for jails, this time for jail.conf jails
The following reply was made to PR misc/173076; it has been noted by GNATS.
From: Yamagi Burmeister
To: bug-follo...@freebsd.org, yam...@yamagi.org
Cc:
Subject: Re: misc/173076: New Port: sysutils/jail another rc-script for
jails, this time for jail.conf jails
Date: Sat, 27 Oct 2012 10:43:27 +0200
This is a multi-part message in MIME format.
--Multipart=_Sat__27_Oct_2012_10_43_27_+0200_xtW69zI6H9arjAUK
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sorry, I forgot to remove the .git directory before creating the shar.
New version is attached.
--
Homepage: www.yamagi.org
XMPP: yam...@yamagi.org
GnuPG/GPG: 0xEFBCCBCB
--Multipart=_Sat__27_Oct_2012_10_43_27_+0200_xtW69zI6H9arjAUK
Content-Type: text/plain;
name="jail2.txt"
Content-Disposition: attachment;
filename="jail2.txt"
Content-Transfer-Encoding: 7bit
# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file". Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# jail2
# jail2/files
# jail2/files/jail2.in
# jail2/Makefile
# jail2/pkg-descr
#
echo c - jail2
mkdir -p jail2 > /dev/null 2>&1
echo c - jail2/files
mkdir -p jail2/files > /dev/null 2>&1
echo x - jail2/files/jail2.in
sed 's/^X//' >jail2/files/jail2.in << '16a6c5557e83ea0912b4b8ab95367891'
X#!/bin/sh
X
X# Alternative rc script for jails. This script relies on
X# /etc/jail.conf instead of rc.conf variables. Usage:
X#
X# jail2_enable -> Enables the script
X# jail2_list -> List of jails to be started. The names
X# must match the names in /etc/jail.conf
X# jail2_$name_zfs -> List of ZFS datasets to connect to the
X# jail $name.
X#
X# To manage ZFS datasets within a jail the dataset must have
X# set the parameter "jailed" to 1. Additionally the jail must
X# have set the proberties "allow.mount", "allow.mount.zfs"
X# and "enforce_statfs" to value lesser than 2.
X
X# PROVIDE: jail
X# REQUIRE: LOGIN cleanvar
X# BEFORE: securelevel
X# KEYWORD: shutdown
X
X. /etc/rc.subr
X
Xname="jail2"
Xrcvar=jail2_enable
X
Xstart_cmd="jail2_start"
Xstop_cmd="jail2_stop"
X
Xjail2_start()
X{
X echo -n "Starting jails: "
X
X for _j in ${jail2_list}; do
X echo -n "${_j} "
X
X if [ -e /var/run/jail_${_j}.id ]; then
X echo "${_j} already exists"
X continue
X fi
X
X jail -c -i -J /var/run/jail_${_j}.id ${_j} > /dev/null 2>&1
X
X eval _zfs=\"\${jail2_${_j}_zfs:-}\"
X _jid=`jls -j ${_j} jid 2>/dev/null`
X
X if [ -n "${_zfs}" ]; then
X for _ds in ${_zfs}; do
X _jailed=`zfs get -H jailed ${_ds} 2>/dev/null |
awk '{ print $3 }'`
X if [ "${_jailed}" = "on" ]; then
X echo "zfs jail "${_jid}" ${_ds}
2>/dev/null"
X zfs jail "${_jid}" ${_ds} 2>/dev/null
X fi
X done
X fi
X done
X
X echo
X}
X
Xjail2_stop()
X{
X echo -n "Stopping jails: "
X
X for _j in ${jail2_list}; do
X echo -n "${_j} "
X
X if [ ! -e /var/run/jail_${_j}.id ]; then
X echo "${_j} doesn't exists"
X continue
X fi
X
X eval _zfs=\"\${jail2_${_j}_zfs:-}\"
X _jid=`jls -j ${_j} jid 2>/dev/null`
X
X jail -r -q ${_j} > /dev/null 2>&1
X rm /var/run/jail_${_j}.id
X
X if [ -n "${_zfs}" ]; then
X for _ds in ${_zfs}; do
X _jailed=`zfs get -H jailed ${_ds} 2>/dev/null |
awk '{ print $3 }'`
X if [ "${_jailed}" = "on" ]; then
X echo "zfs unjail "${_jid}" ${_ds}
2>/dev/null"
X zfs unjail "${_jid}" ${_ds} 2>/dev/null
X fi
X done
X fi
X done
X
X echo
X}
X
Xload_rc_config $name
X: ${jail2_enable="NO"}
X
Xcmd="$1"
Xif [ $# -gt 0 ]; then
X shift
Xfi
Xif [ -n "$*" ]; then
X jail2_list="$*"
Xfi
X
Xrun_rc_command "${cmd}"
16a6c5557e83ea0912b4b8ab95367891
echo x - jail2/Makefile
sed 's/^X//' >jail2/Makefile << '244169e487ff8dd224c47b19f508f4f0'
X# New ports collection makefile for: jail2
X# Date created: 21 October 2012
X# Whom: Yamagi Burmeister
X#
X# $FreeBSD$
X#
X
XPORTNAME= jail2
XPORTVERSION= 1.0
XCATEGORIES= sysutils
XMASTER_SITES= #
XDISTFILES=#
X
XM
Re: kern/172931: Suspen/resume blocks USB mouse
The following reply was made to PR kern/172931; it has been noted by GNATS. From: J B To: bug-follo...@freebsd.org, jb.1234a...@gmail.com Cc: Subject: Re: kern/172931: Suspen/resume blocks USB mouse Date: Sat, 27 Oct 2012 13:20:47 +0200 After boot and first (good) suspend: crw-rw-rw- 1 root wheel0, 41 Oct 27 12:35 /dev/psm0 crw-r--r-- 1 root operator0, 130 Oct 27 14:35 /dev/ums0 After second (bad) suspend: $ ls -al /dev/ums0 ls: /dev/ums0: No such file or directory ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
misc/173140: usr.sbin/bsdinstall/scripts/auto awk parameter need from $4 to $8
>Number: 173140
>Category: misc
>Synopsis: usr.sbin/bsdinstall/scripts/auto awk parameter need from $4 to
>$8
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Oct 27 14:20:00 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Hideyuki Hakotani
>Release:-Current r241902
>Organization:
>Environment:
FreeBSD riku.tsr1.dip.jp 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Oct 20
14:47:40 JST 2012 r...@riku.tsr1.dip.jp:/usr/obj/usr/src/sys/AAA amd64
>Description:
DISTMENU=`awk '!/^(kernel|base)/{print $4,$5,$6}' $BSDINSTALL_DISTDIR/MANIFEST`
DISTMENU is bad.
>How-To-Repeat:
>Fix:
DISTMENU=`awk '!/^(kernel|base)/{print $4,$5,$6,$7,$8}'
$BSDINSTALL_DISTDIR/MANIFEST`
>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: bin/173140: bsdinstall(8): scripts/auto awk parameter need from $4 to $8
Old Synopsis: usr.sbin/bsdinstall/scripts/auto awk parameter need from $4 to $8 New Synopsis: bsdinstall(8): scripts/auto awk parameter need from $4 to $8 Responsible-Changed-From-To: freebsd-bugs->freebsd-sysinstall Responsible-Changed-By: eadler Responsible-Changed-When: Sat Oct 27 15:09:12 UTC 2012 Responsible-Changed-Why: fix synopsis and assign http://www.freebsd.org/cgi/query-pr.cgi?pr=173140 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: bin/172965: pw useradd does not allow -g ""
The following reply was made to PR bin/172965; it has been noted by GNATS. From: Eitan Adler To: bug-follo...@freebsd.org Cc: Subject: Re: bin/172965: pw useradd does not allow -g "" Date: Sat, 27 Oct 2012 15:20:09 -0400 -- Forwarded message -- From: J B Date: 26 October 2012 15:00 Subject: Re: misc/172965: pw useradd does not allow -g "" To: freebsd-bugs@freebsd.org The following reply was made to PR misc/172965; it has been noted by GNATS. From: J B To: bug-follo...@freebsd.org, j...@bovine.net Cc: Subject: Re: misc/172965: pw useradd does not allow -g "" Date: Fri, 26 Oct 2012 20:58:46 +0200 I am presenting a summary that would suggest better solution. pw(8): ... USER OPTIONS The following options apply to the useradd and usermod commands: ... -g group Set the account's primary group to the given group. group may be defined by either its name or group number. ... The useradd command also has the ability to set new user and group defaults by using the -D option. Instead of adding a new user, pw writes a new set of defaults to its configuration file, /etc/pw.conf. When using the -D option, you must not use either -n name or -u uid or an error will result. Use of -D changes the meaning of several command line switches in the useradd command. These are: -DSet default values in /etc/pw.conf configuration file, or a different named configuration file if the -C config option is used. ... -g group Set the default group for new users. If a blank group is specified using -g "", then new users will be allocated their own private primary group with the same name as their login name. If a group is supplied, either its name or uid may be given as an argument. ... Now, let's review it once again. # pw useradd moo -g moo pw: group `moo' does not exist # pw useradd moo -g boo pw: group `boo' does not exist # pw useradd moo -g "" pw: group `' is not defined You want to make a one-time override of any default group as established in /etc/pw.conf by "-D -g" options: # pw useradd moo -g "" moo:*:8007:8007:User &:/home/moo:/bin/sh But, the below does the same but by checking if user name/id is equal to primary group name/id as entered: # pw useradd moo -g moo moo:*:8007:8007:User &:/home/moo:/bin/sh which clearly reflects user's intentions as entered. By contrast, your solution is less clear about the user's intentions; also, it introduces blank group specification -g "" to entry whose context is an immediate and particular account setup, but which is specific to -D -g "" type of entry whose context is setting up system defaults for any accounts setup. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org" -- Eitan Adler ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
bin/173144: vidcontrol(1) options parsing problem
>Number: 173144
>Category: bin
>Synopsis: vidcontrol(1) options parsing problem
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Oct 27 23:20:00 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: jb
>Release:reeBSD 9.1-RC2 #0
>Organization:
>Environment:
FreeBSD localhost.localdomain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2
17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
i386
>Description:
In console mode.
# vidcontrol VGA_80x30 -m on
< blank screen >
usage: vidcontrol [-CdHLPpx] [-b color] [-c appearance] [-f [size] file]
[-g geometry] [-h size] [-i adapter | mode] [-l screen_map]
[-M char] [-m on | off] [-r foreground background]
[-S on | off] [-s number] [-T xterm | cons25] [-t N | off]
[mode] [foreground [background]] [show]
#
That usage message indicates some problem with options parsing ("-m on" is
probably not executed).
This entry seems to execute cleanly:
# vidcontrol -m on VGA_80x30
< blank screen >
#
>How-To-Repeat:
as above
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: bin/173005: PW(8) - 'pw usermod' causes Segmentation fault: 11 (core dumped)
The following reply was made to PR bin/173005; it has been noted by GNATS.
From: Mark Johnston
To: bug-follo...@freebsd.org, jb.1234a...@gmail.com, li...@eitanadler.com
Cc:
Subject: Re: bin/173005: PW(8) - 'pw usermod' causes Segmentation
fault: 11 (core dumped)
Date: Sun, 28 Oct 2012 01:36:57 -0400
--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Looks like this was introduced by r63596, which itself was a fix for
bin/5717: http://www.freebsd.org/cgi/query-pr.cgi?pr=5717
Basically, pw(8) allows '-g ""' when setting the default group for new
users; it has a special meaning, described in the man page. I think the
right fix is to check for -D before proceeding when running with -g "".
With the attached patch, 'pw useradd -D -g ""' still does the right
thing, and we also have
# pw usermod mark -g ""
pw: group `' does not exist
#
which I think is the right behaviour.
Thanks,
-Mark
--TB36FDmn/VVEgNH/
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="pw_empty_group.patch"
diff --git a/usr.sbin/pw/pw_user.c b/usr.sbin/pw/pw_user.c
index 1b72cbd..26d13cf 100644
--- a/usr.sbin/pw/pw_user.c
+++ b/usr.sbin/pw/pw_user.c
@@ -228,7 +228,8 @@ pw_user(struct userconf * cnf, int mode, struct cargs *
args)
cnf->password_days = atoi(arg->val);
if ((arg = getarg(args, 'g')) != NULL) {
- if (!*(p = arg->val)) /* Handle empty group list specially */
+ /* Handle empty group list specially when defining a default
group. */
+ if (!*(p = arg->val) && getarg(args, 'D'))
cnf->default_group = "";
else {
if ((grp = GETGRNAM(p)) == NULL) {
--TB36FDmn/VVEgNH/--
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
