bin/65693: wildcarded device names in /etc/devfs.conf break /etc/rc.d/devfs

Conrad J. Sabatier conrads at cox.net
Sat Apr 17 20:50:27 PDT 2004


>Number:         65693
>Category:       bin
>Synopsis:       wildcarded device names in /etc/devfs.conf break /etc/rc.d/devfs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr 17 20:50:22 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Conrad J. Sabatier
>Release:        FreeBSD 5.2-CURRENT i386
>Organization:
None
>Environment:

System: FreeBSD ip68-14-60-78.no.no.cox.net 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Fri Apr 16 12:21:57 CDT 2004 conrads at ip68-14-60-78.no.no.cox.net:/usr/obj/usr/src/sys/MYKERNEL i386

>Description:

Adding the following line to /etc/devfs.conf causes the /etc/rc.d/devfs
script to fail:

perm 	acd*	0666

Trace output (truncated, from sh -x devfs start):

+ read action device parameter
+ [ -c acd0 acd0t01 acd0t02 acd0t03 acd0t04 acd0t05 acd0t06 acd0t07 acd0t08 acd0t09 
acd0t10 acd0t11 acd0t12 acd0t13 acd0t14 acd1 ]
[: acd0: unexpected operator
+ read action device parameter
+ _return=0
+ [ 0 -ne 0 ]
+ [ -n  ]
+ return 0

>How-To-Repeat:

Use wildcard device name in /etc/devfs.conf and watch the fun.  :-)

>Fix:

None at hand, but obviously the script needs to differentiate between single device 
names and lists of device names.  Wildcarding device names is just too convenient to 
sacrifice for the sake of a non-robust script.  :-)
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list