[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | The setld and ULTRIX layered product installation/integration conference |
|
| Moderator: | SQM::DUFAULT |
|
| Created: | Thu Feb 08 1990 |
| Last Modified: | Wed Apr 23 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 359 |
| Total number of notes: | 1357 |
358.0. "setld question for Digital UNIX" by REQUE::CHOI (Yung Choi (ZKO2-2/R80 DTN:381-2295)) Tue Mar 11 1997 15:22
A question about setld on Digital UNIX; it is for the file protection
on the kits.
In my kit builder,
# cp -p my_file ./usr/opt/MYKIT300/my_file
# chmod 744 ./usr/opt/MYKIT300/my_file
# ln -s ./usr/opt/MYKIT300/my_file my_file
Then ./usr/opt/MYKIT300/my_file gets different protection for different
OS version of Digital UNIX.
Digital UNIX 3.0 rwxr--r-- ./usr/opt/MYKIT300/my_file
Digital UNIX 3.2C rwxrwxrwx ./usr/opt/MYKIT300/my_file
Digital UNIX 4.0 rwxr--r-- ./usr/opt/MYKIT300/my_file
The linked my_file gets lrwxrwxrwx for all OS versions, and this is what
expected. It is 100744 on the inv file for V3.0 and V4.0, but it is
100777 for V3.2C.
The problem is why 3.2C sets the original file's protection different
from what is asked?
Is there any way to make 3.2C sets proper protection?
Thank you. - Yung
PS: We are now upgrading 3.0 machine to 4.0 and our product should suport
3.2C. So far the kit has been built by 3.0 machine, but after it is
upgraded, 3.2C must be used.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 358.1 | | SEAN::davidson | D. Sean Davidson | Fri Mar 14 1997 13:54 | 15 |
| Re: .0
First off you cannot build a product on V4.0 that is intended to run on V3.2C
because of forward library incompatibilities. The only way to make this work
most of the time is to link any applications static.
This problem with the file showing up with the wrong modes sounds like a bug
in /usr/lbin/invcutter. You can verify this by doing a
echo "0\t./usr/opt/MYKIT300/my_file\tMYKIT300" | /usr/lbin/invcutter
and verify the mode that it reports. If this does report the correct mode
then it is probably a tar bug when loading it onto the system.
Sean
|