Sponsored Content
Operating Systems Solaris How to configure Xorg and fvwm on x86 Solaris 10 update 10? Post 303028107 by jlliagre on Monday 31st of December 2018 03:52:44 AM
Old 12-31-2018
What makes you think the script location makes any difference? You can put it in the non-root user's home directory, or almost anywhere (/tmp whould be unwise for example).
 

8 More Discussions You Might Find Interesting

1. Solaris

Cant configure video & nic (solaris 8 on x86)

can someone please through light on how to configure video and nic. Dimension 3000 Series, Intel Pentium 4 Processor at 2.8GHz 256MB DDR SDRAM at 400MHz EA 0.00 0.00 17 in (17 in viewable) E173FP Flat Panel Display EA Integrated Intel Extreme Graphics 2 EA Intel Pro 100M Integrated... (4 Replies)
Discussion started by: Jimmpy
4 Replies

2. Solaris

Where Xorg X-Lock file is located in Solaris?

I am using Xorg server with Solaris 10. After unnormal poweroff dtlogin tells: "The X-server can not be started on display :0" I am absolutelly sure it is because there is still a X-lock file from the previouse X-session somewhere, but I do not know where is it located in Solaris! :confused: (2 Replies)
Discussion started by: eugrus
2 Replies

3. UNIX for Dummies Questions & Answers

Question regarding Solaris 10 x86 Update.

:) I have question regarding Solaris 10 x86 Update ,does it require sunsolve account and if am using Solaris 10 x86 for learning ,how to get sunsolve account with out a contract number .i am very in need for this update . Please if any can help, help is highly appreciated :) (1 Reply)
Discussion started by: ibasit
1 Replies

4. UNIX for Dummies Questions & Answers

Running Solaris Sparc Apps on X86 Solaris

I know that Sun make s a version of Solaris for Sparc platforms and also an x86 (Intel/AMD) release of Solaris. Can an application that runs on Solaris/Sparc also run on a PC running the x86 release of Solaris? Would a different release be required or any re-compling of the application? jim (1 Reply)
Discussion started by: stocksj
1 Replies

5. Linux

Linux ES 4 Update 4 (x86)

I have cdrom with the following files which I copieed on my hard drive. RHEL4-U4-i386-ES-disc1.iso RHEL4-U4-i386-ES-disc4.iso RHEL4-U4-i386-ES-disc2.iso RHEL4-U4-i386-ES-disc5.iso RHEL4-U4-i386-ES-disc3.iso What shell I do now to upgrade linux version. :o Thank you zam (6 Replies)
Discussion started by: zam
6 Replies

6. Solaris

How to Configure NIS Client for Solaris7 x86

HI Unix Gurus i am new to Solaris OS, i want to configure NIS CLient for Solaris 7 x86 Machine. i need what are the step and how to configure it in that machine.. please let me know Thanks in Advance Regards ..kiruba.. (2 Replies)
Discussion started by: nkkirubakaran
2 Replies

7. Windows & DOS: Issues & Discussions

cygwin-x/can't install xorg-x11-f100 & xorg-x11-fnts

Hello All. Really a newbie to Linux/Unix. Trying to get into Linux. Using XP PE currently. Installed cygwin and trying to intall cygwin-x. Everything else is setup nice but i can't seem to install these two packages (without whom xwin won't start) 1. xorg-x11-f100 2. xorg-x11-fnts Tried the... (1 Reply)
Discussion started by: binodbdrchand
1 Replies

8. Solaris

How to configure Proxy Server in Solaris 10 (X86)

Hi , I have installed solaris 10 on x 86 architecture. Now i want to configure this system as Proxy Server. I am new to the solaris. Please help me how can i configure this. Which packages or patches are needed ? or Which files have to be modify ? Please help me to resolve. Thanks and... (0 Replies)
Discussion started by: raviraj001
0 Replies
NAMESPACE.CONF(5)						 Linux-PAM Manual						 NAMESPACE.CONF(5)

NAME
namespace.conf - the namespace configuration file DESCRIPTION
The pam_namespace.so module allows setup of private namespaces with polyinstantiated directories. Directories can be polyinstantiated based on user name or, in the case of SELinux, user name, sensitivity level or complete security context. If an executable script /etc/security/namespace.init exists, it is used to initialize the namespace every time an instance directory is set up and mounted. The script receives the polyinstantiated directory path and the instance directory path as its arguments. The /etc/security/namespace.conf file specifies which directories are polyinstantiated, how they are polyinstantiated, how instance directories would be named, and any users for whom polyinstantiation would not be performed. When someone logs in, the file namespace.conf is scanned. Comments are marked by # characters. Each non comment line represents one polyinstantiated directory. The fields are separated by spaces but can be quoted by " characters also escape sequences , , and are recognized. The fields are as follows: polydir instance_prefix method list_of_uids The first field, polydir, is the absolute pathname of the directory to polyinstantiate. The special string $HOME is replaced with the user's home directory, and $USER with the username. This field cannot be blank. The second field, instance_prefix is the string prefix used to build the pathname for the instantiation of <polydir>. Depending on the polyinstantiation method it is then appended with "instance differentiation string" to generate the final instance directory path. This directory is created if it did not exist already, and is then bind mounted on the <polydir> to provide an instance of <polydir> based on the <method> column. The special string $HOME is replaced with the user's home directory, and $USER with the username. This field cannot be blank. The third field, method, is the method used for polyinstantiation. It can take these values; "user" for polyinstantiation based on user name, "level" for polyinstantiation based on process MLS level and user name, "context" for polyinstantiation based on process security context and user name, "tmpfs" for mounting tmpfs filesystem as an instance dir, and "tmpdir" for creating temporary directory as an instance dir which is removed when the user's session is closed. Methods "context" and "level" are only available with SELinux. This field cannot be blank. The fourth field, list_of_uids, is a comma separated list of user names for whom the polyinstantiation is not performed. If left blank, polyinstantiation will be performed for all users. If the list is preceded with a single "~" character, polyinstantiation is performed only for users in the list. The method field can contain also following optional flags separated by : characters. create=mode,owner,group - create the polyinstantiated directory. The mode, owner and group parameters are optional. The default for mode is determined by umask, the default owner is the user whose session is opened, the default group is the primary group of the user. iscript=path - path to the instance directory init script. The base directory for relative paths is /etc/security/namespace.d. noinit - instance directory init script will not be executed. shared - the instance directories for "context" and "level" methods will not contain the user name and will be shared among all users. The directory where polyinstantiated instances are to be created, must exist and must have, by default, the mode of 0000. The requirement that the instance parent be of mode 0000 can be overridden with the command line option ignore_instance_parent_mode In case of context or level polyinstantiation the SELinux context which is used for polyinstantiation is the context used for executing a new process as obtained by getexeccon. This context must be set by the calling application or pam_selinux.so module. If this context is not set the polyinstatiation will be based just on user name. The "instance differentiation string" is <user name> for "user" method and <user name>_<raw directory context> for "context" and "level" methods. If the whole string is too long the end of it is replaced with md5sum of itself. Also when command line option gen_hash is used the whole string is replaced with md5sum of itself. EXAMPLES
These are some example lines which might be specified in /etc/security/namespace.conf. # The following three lines will polyinstantiate /tmp, # /var/tmp and user's home directories. /tmp and /var/tmp # will be polyinstantiated based on the security level # as well as user name, whereas home directory will be # polyinstantiated based on the full security context and user name. # Polyinstantiation will not be performed for user root # and adm for directories /tmp and /var/tmp, whereas home # directories will be polyinstantiated for all users. # # Note that instance directories do not have to reside inside # the polyinstantiated directory. In the examples below, # instances of /tmp will be created in /tmp-inst directory, # where as instances of /var/tmp and users home directories # will reside within the directories that are being # polyinstantiated. # /tmp /tmp-inst/ level root,adm /var/tmp /var/tmp/tmp-inst/ level root,adm $HOME $HOME/$USER.inst/inst- context For the <service>s you need polyinstantiation (login for example) put the following line in /etc/pam.d/<service> as the last line for session group: session required pam_namespace.so [arguments] This module also depends on pam_selinux.so setting the context. SEE ALSO
pam_namespace(8), pam.d(5), pam(7) AUTHORS
The namespace.conf manual page was written by Janak Desai <janak@us.ibm.com>. More features added by Tomas Mraz <tmraz@redhat.com>. Linux-PAM Manual 06/04/2011 NAMESPACE.CONF(5)
All times are GMT -4. The time now is 05:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy