Ray Muno wrote:
>
> Thanks, three replies in very short order.
>
> I ran the fix-perms script and that is fine.
>
> I am a little confused about the updates disk. I am using kickstart to
> do the installs. How do I incorporate the update floppy in to that
> procedure? I boot from the SGI XFS 1.01 install CD and do a "linux ks".
I think you can add the fix-perms script to run in the post-install section of
the kickstart?
> If this is truly a problem with the underlying kernel, will it cause
> problems beyond install time? I see that Redhat explicitly sets umask
> to 022 in /etc/rc.d/init.d/functions and calls that in the init scripts.
> Is there a danger of other things running as root creating files that
> are mode 666? Is there a kernel patch to fix the problem for the running
> machines.
Since the umask is explicitly set on a normal bootup, you shouldn't run into
problems down the line. The installer was not doing this, so files created
during the install had the wrong perms.
The bug was fixed in 2.4.7-pre7, I'm not sure where the fix was or where a patch
might be.
-Eric
----
We ran a test program out of xinetd that just touched a file in /tmp.
The file that was created was mode 666. We tested this on an Debian 2.2
machine, 2.2.17 kernel, and the file was 644. It seems clear that this is
a big issue for things that are not explicitly run from init.d.
=============================================================================
Ray Muno http://www.aem.umn.edu/people/staff/muno
University of Minnesota e-mail: muno@xxxxxxxxxxx
Aerospace Engineering and Mechanics Phone: (612) 625-9531
110 Union St. S.E. FAX: (612) 626-1558
Minneapolis, Mn 55455
=============================================================================
|