Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Dec 1999 09:02:43 -0500
From:      "Louis A. Mamakos" <louie@TransSys.COM>
To:        "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
Cc:        obrien@NUXI.com, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject:   Re: cvs commit: src/usr.sbin/chown Makefile 
Message-ID:  <199912141402.JAA35445@whizzo.transsys.com>
In-Reply-To: Your message of "Mon, 13 Dec 1999 22:17:50 PST." <199912140617.WAA18057@gndrsh.dnsmgr.net> 
References:  <199912140617.WAA18057@gndrsh.dnsmgr.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
> > On Mon, Dec 13, 1999 at 09:48:55PM -0800, Rodney W. Grimes wrote:
> > > >   Install `chown' into /sbin rather than /usr/sbin as `chown' is needed by
> > > >   `MAKEDEV'.  And one might need to `MAKEDEV' inorder to get a device node
> > > >   in order to mount /usr from.
> > > 
> > > The sources need repo moved from usr.sbin to sbin and this change ripped
> > > out.
> > 
> > Yes.  Patience.  First put the change in usr.sbin/chown/ so it is
> > documented by someone looking there.  Then repo move it to sbin/chown/
> > and clean up the Makefile.  This was how we did usr.sbin/sysctl/ ->
> > sbin/sysctl/ .
> 
> And now that I went digging your going to find that chown/chgrp is not
> the only thing missing to run MAKEDEV.
> 
> printf is _NOT_ a borne shell builtin, so you'll also need /usr/bin/printf,
> used extensivly in MAKEDEV.
> 
> Might I suggest you backthis out (as it creates the mess of folks having
> to remeber to rm /usr/sbin/chown) until you have a _COMPLETE_ set of
> patches that makes /dev/MAKEDEV run without /usr, and have tested that
> set of _COMPLETE_ patches.

So, do we need to wait until the perfect solution until any progress
can be made at all?  The place that I suspect most folks trip across
the chown problem is when making new device nodes for disk devices.
You don't need awk for that particular problem, and given all the flux
in the disk arena these days, it would be nice if unsuspecting users
can unscrew themselves by making (e.g., ad0s1a) device nodes when they
stumble across that change.

louie






To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




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