Shadow:- groups

pii350mmxpc100 pii350mmxpc100 at
Sun Jan 18 02:27:35 PST 2004

On Sun, Jan 18, 2004 at 20:07:05PM +1030, Greg Schafer wrote:
>On Sun, Jan 18, 2004 at 06:58:18PM +1030, pii350mmxpc100 wrote:
>> Any one who is looking in to Shadow please look at the "groups" with vi.
>> I Think you will see shadow uses it for building it self, not for any other 
>> use.

>Have absolutely no idea what you're gibbering on about there..

 My fault.
 I was Meant to say "groups file", installed by shadow..

>> Now if you all agree too this, can you please take out the comment about 
>> having a choice of removing the groups file.  As this file dose not belong 
>> the system.

>I was only looking at that comment a few hours ago while updating the book
>and testing the new shadow. I agree there should not be a choice. I'll
>change the wording.

>> I think the Coreutils-5.0 "groups" file is the only choice you have got.
>> That is, if you whant a working groups file that is.

>I still dunno what you're talking about there. The groups from shadow does
>work as advertised.
This is part of the groups file Shadow-4.0.3 installed on the my system.
Opened with vim:
#! /bin/sh

# groups - temporary wrapper script for .libs/groups
# Generated by - GNU libtool 1.4.2 (1.922.2.53 2001/09/11 03:18:52)
# The groups program cannot be directly executed until all the libtool
# libraries that it depends on are installed.
# This wrapper script should never be moved out of the build directory.
# If it is, it will not operate correctly.

# Sed substitution that helps us do robust quoting.  It backslashifies
# metacharacters that are still active within double-quoted strings.
Xsed='sed -e 1s/^X//'

# The HP-UX ksh and POSIX shell print the target directory to stdout
# if CDPATH is set.
if test "${CDPATH+set}" = set; then CDPATH=:; export CDPATH; fi

relink_command="cd /usr/local/src/shadow-4.0.3/src; { test -z \"\
${LIBRARY_PATH+set}\" || unset LIBRARY_PATH || { LIBRARY_PATH=; export 
LIBRARY_PATH; }; }; { test -z \"\${COMPILER_PATH+set}\" || unset 
COMPILER_PATH || { COMPILER_PATH=; export COMPILER_PATH; }; }; { test -z \"\
export GCC_EXEC_PREFIX; }; }; { test -z \"\${LD_RUN_PATH+set}\" || unset 
LD_RUN_PATH || { LD_RUN_PATH=; export LD_RUN_PATH; }; }; { test -z \"\
export LD_LIBRARY_PATH; }; }; PATH=\"/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin
\"; export PATH; gcc -O2 -mcpu=athlon-xp -march=athlon-xp -fforce-mem  -s -o \
$progdir/\$file groups.o  ../libmisc/.libs/ ../lib/.libs/ -lcrypt /usr/local/src/shadow-4.0.3/
libmisc/.libs/ -Wl,--rpath -Wl,/usr/local/src/shadow-4.0.3/
libmisc/.libs -Wl,--rpath -Wl,/usr/local/src/shadow-4.0.3/lib/.libs"

Hope this helps



More information about the lfs-dev mailing list