Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Mar 2011 14:38:12 GMT
From:      Lance Leger <laleger@gmail.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   misc/156092: pw user flag -m does not respect custom home directory locations
Message-ID:  <201103311438.p2VEcC1j050385@red.freebsd.org>
Resent-Message-ID: <201103311440.p2VEeA4N056810@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         156092
>Category:       misc
>Synopsis:       pw user flag -m does not respect custom home directory locations
>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:   Thu Mar 31 14:40:09 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Lance Leger
>Release:        8.1-RELEASE-p2
>Organization:
>Environment:
>Description:
I've got an installation running from mfsroot with custom home directory locations on a seperate ufs filesystem and when I attempt to issue a "pw user mod <username> -m" command, pw gives me the following error:

pw: mkdir '/home': Read-only file system

Two issues here:

1) /home does not even exist on my system
2) the users custom home directory location is clearly defined in /etc/passwd

Now if I re-mount my mfsroot filesystem read-write, issue mkdir /home, then attempt to issue same command again it creates my users custom home directory (i.e. /d/home/user)

Another observation. If I leave the /home directory in place, re-mount my mfsroot filesystem read-only again, then attempt to issue the same command again it works (even though it has a reason now to complain that /home is read-only)
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201103311438.p2VEcC1j050385>