On Fri, Feb 16, 2001 at 02:13:30AM -0800, David Peet wrote:
> IT looks like RPM did not complete the install. Each file that is installed
> is specified to have a particular ownership and group. In the case of
> "mountc" it is "root" and "bin", and most of the rest of the files
> (all but four) have owner bin, group bin. If they are not that then
> RPM screwed up.
>
> -David
>
> Jeffrey Ebert wrote:
> >
> > Can anybody explain these uid and gid numbers in the latest version of
> > win4lin?
> >
> > # ls -l opt/win4lin/bin/mountc
> > -r-sr-xr-x 1 6319 124 17600 Feb 16 00:01
> > opt/win4lin/bin/mountc
> >
> > I'm betting that it should be root:root, and that mountc is suid root,
> > but I thought I'd ask.
> >
> > By the way, the whole distribution has that ownership, not just the
> > mountc file.
I have the same owner/group issues in a Debian install, although I
haven't noticed any detrimental effects. But...
What is the effect of the incomplete install? And what exactly did
rpm not do? Is there a way (a script?) to make it complete the
install? Would it be a good idea to change these file owners/groups
to the correct ones? If so, is there a list somewhere of the correct
ones?
This raises more questions than it answers.
--
Martin Hillyer
Powered by Debian GNU/Linux 2.2.18
Communications by mutt-1.3.12i
~~~~~~~~~~~~~~
QOTD:
The tree in which the sap is stagnant remains fruitless.
-- Hosea Ballou
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
