su - "S"tunted "U"ser?

What gives with me not being able to chown directories in my /usr/
directory? It gives me a “Not supported” message. My /usr/local directory
is owned by some unknown user with a number of 320 and it wont let me change
the freaking owner to root. This is in the latest release of QNX 6. I
installed it last week and there are some really freaky user numbers showing
up as owners to some of the directories. Not a huge problem, USUALLY, but I
can’t change the owner or group of the directory.

Does anyone know how to do this? BTW, I am logged in as root when I am
trying to chown or chgrp.

TIA,

Jim

Jim Lambert <jlambert@futurex.com> wrote:

What gives with me not being able to chown directories in my /usr/
directory? It gives me a “Not supported” message. My /usr/local directory
is owned by some unknown user with a number of 320 and it wont let me change
the freaking owner to root. This is in the latest release of QNX 6. I
installed it last week and there are some really freaky user numbers showing
up as owners to some of the directories. Not a huge problem, USUALLY, but I
can’t change the owner or group of the directory.

Does anyone know how to do this? BTW, I am logged in as root when I am
trying to chown or chgrp.

Administration of these items for now is done at the source
package level. All of your filesystem is virtualized by
the package filesystem with the real files living most
probably in /pkgs/[repository|base]/…

If you are looking for more control over user id’s and
group id’s and other associated permissions, then you need
to change the permissions on these files which will then
be reflected in the virtual view of the filesystem.

The rational here is that package repositories are
read-only and designed to be shared by a large number
of users and set up by a system administrator for a
site. On a single machine you are your own system
administrator and serving the files to your own machine.
As a result you need to do your own administration. A
future version of the package filesystem will allow you
to change directory permissions/ownership but just like
files these items will be “spilled” into local copies
seperate from the original packaged versions.

For more information on the package filesystem take a
read through the past articles on QDN (qdn.qnx.com).
We will be putting more of this type information in the
future releases of the system administrator’s guide.

For now you can find the real location of the files
using pkgctl, though updating all the files in your
repository with your site appropriate permissions
would probably be a good idea.

Thomas

\


Thomas (toe-mah) Fletcher QNX Software Systems
thomasf@qnx.com Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf

<thomasf@qnx.com> wrote in message news:9j3vf2$85f$1@nntp.qnx.com

Jim Lambert <> jlambert@futurex.com> > wrote:
What gives with me not being able to chown directories in my /usr/
directory? It gives me a “Not supported” message. My /usr/local
directory
is owned by some unknown user with a number of 320 and it wont let me
change
the freaking owner to root. This is in the latest release of QNX 6. I
installed it last week and there are some really freaky user numbers
showing
up as owners to some of the directories. Not a huge problem, USUALLY,
but I
can’t change the owner or group of the directory.

Does anyone know how to do this? BTW, I am logged in as root when I am
trying to chown or chgrp.

Administration of these items for now is done at the source
package level. All of your filesystem is virtualized by
the package filesystem with the real files living most
probably in /pkgs/[repository|base]/…

If you are looking for more control over user id’s and
group id’s and other associated permissions, then you need
to change the permissions on these files which will then
be reflected in the virtual view of the filesystem.

The rational here is that package repositories are
read-only and designed to be shared by a large number
of users and set up by a system administrator for a
site. On a single machine you are your own system
administrator and serving the files to your own machine.
As a result you need to do your own administration. A
future version of the package filesystem will allow you
to change directory permissions/ownership but just like
files these items will be “spilled” into local copies
seperate from the original packaged versions.

For more information on the package filesystem take a
read through the past articles on QDN (qdn.qnx.com).
We will be putting more of this type information in the
future releases of the system administrator’s guide.

For now you can find the real location of the files
using pkgctl, though updating all the files in your
repository with your site appropriate permissions
would probably be a good idea.

Thomas

I hear what you are saying, Thomas. My problem is why do you release QNX 6
with the permissions hosed (messed up, screwed up) to begin with? Should
not the /usr/local directory (and all other files/directories with unknown
users and groups) be modified in your release to be the right permissions?
BTW, I have no idea what ownership or permissions should be on each file in
the OS. I’m hesistant to just go in and assign root:root to each file in
/pkgs and below. It would be much nicer, and make much more sense, if QNX
just released QNX 6 with the ownerships set properly. I mean who in the
@(&# is user 327 and user 320? Am I the only one who has had problems with
this?

As for changing /usr and /usr/local, I have done that and I thank you for
the info on how to do it. But I’m still disappointed that it is being
released with broken ownership on MAJOR system directories. Is QNX
considering releasing a non-virtual version of the fs?

On a better note though, I love this operating system (other than the
“virtual” filesystem :slight_smile: ) and love QNX.

Sincerely,

Jim Lambert
Futurex International

@(&# is user 327 and user 320? Am I the only one who has had
problems with
this?

You are not the only one who has problems with this. Every time I
upgrade I have to go and set all the permissions under /pkgs properly.
I too am puzzled as to why directories and executables can’t be setup to
be read/executable for everyone by default.

On a better note though, I love this operating system (other than the
“virtual” filesystem > :slight_smile: > ) and love QNX.

As you are aware there is really nothing wrong with the package
filesystem (at least I haven’t had any problems with 6.1 yet), but the
underlying files should be setup so that normal users (not just root)
can execute them after install.

Rennie

“Rennie Allen” <RAllen@csical.com> wrote in message

[snipped]

As you are aware there is really nothing wrong with the package
filesystem (at least I haven’t had any problems with 6.1 yet), but the
underlying files should be setup so that normal users (not just root)
can execute them after install.

Actually there may not be problems with the code or the operation of the
fs, but in using it I have already run into problems such as trying to do
find’s from the root directory and getting into infinite loops, speed issues
(takes several seconds to access some directories), files constantly open on
disk so can’t do chkfsys, backup difficulties and other issues.

I just hope that QNX gives us the choice to NOT use the package filesystem.

Jim

Previously, Jim Lambert wrote in qdn.public.qnxrtp.os:

I just hope that QNX gives us the choice to NOT use the package filesystem.

My impression is that not only does QNX does not intend to
force you to use the package filesystem, they assume that
most embedded systems will not use it. It is there for
desktop/development systems to simplify updates. While
a little strange at first, I’ve grown to be be quite
happy with it.



Mitchell Schoenbrun --------- maschoen@pobox.com

Absolutely, the package filesystem is a development system only thingy.
It’s primary design goal being to allow simplified multi-target self
hosted development.

-----Original Message-----
From: Mitchell Schoenbrun [mailto:maschoen@pobox.com]
Posted At: Wednesday, July 18, 2001 3:24 PM
Posted To: os
Conversation: su - "S"tunted "U"ser?
Subject: Re: su - "S"tunted "U"ser?


Previously, Jim Lambert wrote in qdn.public.qnxrtp.os:

I just hope that QNX gives us the choice to NOT use the package
filesystem.

My impression is that not only does QNX does not intend to
force you to use the package filesystem, they assume that
most embedded systems will not use it. It is there for
desktop/development systems to simplify updates. While
a little strange at first, I’ve grown to be be quite
happy with it.



Mitchell Schoenbrun --------- maschoen@pobox.com

Jim Lambert <jlambert@futurex.com> wrote:

[Administration of package filesystem snipped]

I hear what you are saying, Thomas. My problem is why do you release QNX 6
with the permissions hosed (messed up, screwed up) to begin with? Should
not the /usr/local directory (and all other files/directories with unknown
users and groups) be modified in your release to be the right permissions?
BTW, I have no idea what ownership or permissions should be on each file in
the OS. I’m hesistant to just go in and assign root:root to each file in
/pkgs and below. It would be much nicer, and make much more sense, if QNX
just released QNX 6 with the ownerships set properly. I mean who in the
@(&# is user 327 and user 320? Am I the only one who has had problems with
this?

As for changing /usr and /usr/local, I have done that and I thank you for
the info on how to do it. But I’m still disappointed that it is being
released with broken ownership on MAJOR system directories. Is QNX
considering releasing a non-virtual version of the fs?

Yes this is an enormous gaffe on our part, and I appologize
for it. Things will hopefully get better with each release
as we standardize, automate and build better packaging tools.

As for being forced to use the package filesystem … there
would be widespread revolts in the streets if this was the
case. As others have mentioned, the package filesystem is
really targetted at software distribution and the desktop,
and we will be providing tools to “depackagify” packages
in the future. This is already the case for our cross
development Windows and Solaris installations.

Thomas

Thomas (toe-mah) Fletcher QNX Software Systems
thomasf@qnx.com Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf