07-25-2016
My first suspicion on it freezing, given old hardware, is graphical incompatibility. Make sure GRUB isn't trying to do anything with a fancy boot overlay screen or anything, just a basic raw text one.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
i'm following the, "How to setup and secure Snort, MySQL and Acid on FreeBSD 4.6 Release" off of the snort.org website.
in the documentation it says snort should be installed through the following:
-----
make -DWITH_MYSQL -DWITH_FLEXRESP ; make install
-----
later it says to do the... (13 Replies)
Discussion started by: xyyz
13 Replies
2. SCO
Hi All,
While installing a Service Pack on my Unix Solaris machine, i got the following error:
UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY
UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME"
UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o... (9 Replies)
Discussion started by: am_yadav
9 Replies
3. Solaris
Hi all,
Previously I had both opensuse 11.3 and Windows XP SP2 on my PC, there was no problem at all.I was able to access all documents in Windows from opensuse.
Now when I wanted to install solaris 10 on the same machine there were 2 problems ...
1. Windows is not accessible from solaris... (3 Replies)
Discussion started by: M.Choudhury
3 Replies
4. HP-UX
I am trying to build a software on HP-UX (HP-UX 11.00). It links against Xerces and Xalan libraries (amongst others).
I am getting the following errors during the final linking phase.
Can somebody help me understand the problem?
I compiled Xerces and Xalan using aCC (
as recommended) while... (1 Reply)
Discussion started by: slash_blog
1 Replies
5. SuSE
Hello,
I have a project that I have compiled on a number of linux systems including CentOS, Ubuntu, and Windows Cygwin. I am trying to build the project under SUSE 12.1. The make file runs allot of the way through, but then throws an error that an included file can't be opened.
This is the... (4 Replies)
Discussion started by: LMHmedchem
4 Replies
6. Red Hat
I am installing RHEL6 on a Cisco UCS blade and the GUI isn't showing up. Curious!!!!! I have installed it on 5 of the other blades and the GUI is there. However, there are many issues that I am having and I am going crazy with this thing. I have issues where the network adapters are not showing... (1 Reply)
Discussion started by: styehimba
1 Replies
7. UNIX for Dummies Questions & Answers
hi guys
right now I have 6 Virtual Machines (VMs) running on Vmware ESXi 5.1 and attached to Storage SAN.
All these run Suse Linux 11 SP1 x64.
All of a sudden 1 of these VMs is running very slow making high CPU usage and I see al wait % kinda high 40-50%. Apparently since I don't own this... (5 Replies)
Discussion started by: karlochacon
5 Replies
8. SuSE
hello All,
good day to you.
could you tell me is there any way I can download SUSE lunux enterprise server trail version ?
I want to install sap application over it.
thanks in advance. (1 Reply)
Discussion started by: Leaner_963
1 Replies
LEARN ABOUT MOJAVE
subdomain.conf
SUBDOMAIN.CONF(5) AppArmor SUBDOMAIN.CONF(5)
NAME
/etc/apparmor/subdomain.conf - configuration file for fine-tuning the behavior of the AppArmor security tool.
DESCRIPTION
The AppArmor security tool can be configured to have certain default behaviors based on configuration options set in subdomain.conf. There
are two variables that can be set in subdomain.conf: SUBDOMAIN_PATH, and SUBDOMAIN_MODULE_PANIC.
SUBDOMAIN_PATH
This variable accepts a string (path), and is by default set to '/etc/apparmor.d/' This variable defines where the AppArmor security tool
looks for its policy definitions (a.k.a. AppArmor profiles).
SUBDOMAIN_MODULE_PANIC
This variable accepts a string that is one of four values: warn, build, panic, or build-panic, and is set by default to warn.
This setting controls the behavior of the AppArmor initscript if it cannot successfully load the AppArmor kernel module on startup. The
four possible settings are:
warn
Log a failure message (the default behavior).
build
Attempt to build the AppArmor module against the currently running kernel. If the compilation is successful, the module will be loaded
and AppArmor started; if the compilation fails, a failure message is logged.
panic
Log a failure message and drop to runlevel 1 (single user).
build-panic
Attempt to build the module against the running kernel (like build) and if the compilation fails, drop to runlevel 1 (single user).
BUGS
Setting the initscript to recompile the module will fail on SUSE, as the module source is no longer installed by default. However, the
module has been included with the SUSE kernel, so no rebuilding should be necessary.
If you find any additional bugs, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>.
SEE ALSO
apparmor(7), apparmor_parser(8), and <http://wiki.apparmor.net>.
AppArmor 2.7.103 2012-06-28 SUBDOMAIN.CONF(5)