Re: user-directory _is_ home directory

[Luke Kenneth Casson Leighton <lkcl@lkcl.net>]

On Mon, Aug 02, 2004 at 10:06:07AM -0400, Stephen Smalley wrote:
> On Sun, 2004-08-01 at 10:32, Luke Kenneth Casson Leighton wrote:

> > okay, got a good one for you.
> > 
> > ... i notice that genhomedircon is working properly (hurrah)
> > 
> > however, it brings me a slight problem.
> > 
> > i've made /home _the_ home directory: there is one user, it's
> > _the_ user.

> > [... ]

> > my question is: does anyone have any recommendations on how to deal
> > with /home being a mount point, and also being a user's home directory.
> > 
> > naively i removed the HOME_ROOT macro from types.fc, and naturally,
> > the /home mount point doesn't.  mount, that is.
> 
> Quite aside from the issue of whether or not you should directly use
> /home in this manner, 

 *grin*.

> it would be interesting to understand exactly what
> denial you are encountering and whether policy should be adjusted
> accordingly.  e.g. it may well be true that mount is going to need
> permission to directly mount on these directory types anyway for other
> usage scenarios.

 ah.  the problem that i had was that after i removed the line starting
 HOME_ROOT from types.fc, coincidentally, /home would not mount.

 now, whether these two things are interconnected i do not know.

 but it _does_ remind me of an issue that i have tracked down.

 i noticed that pump was not dying on shutdown.

 it was keeping /var from being unmounted at shutdown.

 at boot-up time, /var could NOT BE MOUNTED.

 only after a second shutdown could it be mounted.

 by replacing pump with dhclient3, i got rid of the symptoms, but
 not the problem.


 now, something happened to /home that likewise caused it to not
 be mountable at startup time.

 except that this time it was not clearable by a reboot.

 only by manually mounting it could the problem be cleared.

 subsequently, the problem has gone away.

 .... except it worries me that i might have to wait for it to happen
 again.

 l.



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.