jra at baylink
Mar 26, 2012, 1:44 PM
Post #1 of 1
(119 views)
Permalink
|
|
Folo: Building rt4 while logged in as an AD user
|
|
----- Original Message -----
> From: "Jay Ashworth" <jra [at] baylink>
> Ok, that was stupid. That *was* testdeps telling me, clearly. Fixdeps
> is cleaning up (most, if not all) of that,
It was; everything is installed now.
> but the first part of my inquiry
> stands: it appears that the build scripts do not expect that the user
> and group names may contain non-magic backslashes and spaces, as will be
> the case on a machine where authentication is provided by AD/Samba;
> can anyone confirm or deny?
In addition to:
users:
rt group (GETMOTIVATEDdomain) ...MISSING
bin owner (GETMOTIVATEDjay.ashworth) ...MISSING
libs owner (GETMOTIVATEDjay.ashworth) ...MISSING
libs group (GETMOTIVATEDdomain) ...MISSING
web owner (GETMOTIVATEDjay.ashworth) ...MISSING
web group (GETMOTIVATEDdomain) ...MISSING
I now get, at the end:
/usr/bin/install -c -m 0755 -o GETMOTIVATED\jay.ashworth -g GETMOTIVATED\domain -d /appl/rt405/etc
/usr/bin/install: invalid user `GETMOTIVATEDjay.ashworth'
make: *** [config-install] Error 1
It's relatively clear to me that the build machinery does *not* contemplate
usernames which contain spaces and backslashes, as winbind usernames and
group names will -- and probably not ones which don't exist on the local
machine, either.
I'm not sure what's the best approach to this; I'm probably not competent
to implement a global solution, suitable for a patch; I'm at the edge of my
skillset working in that environment myself.
Suggestions?
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra [at] baylink
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
|
