08-24-2006
Quote:
Originally Posted by System Shock
You can only have one Linux running at a time.
You are going to need 3 different boxes to do this.
So? You can still have 3 distros on one box, they just can't all run at the same time.
10 More Discussions You Might Find Interesting
1. Red Hat
i need to convert my centos 5.2 to fedora 10 with no losing data . !! but how ?
can someone help !!?
cheers
Chang-Lee (1 Reply)
Discussion started by: chang-lee
1 Replies
2. Linux
Hello,
Can anyone please explain HOW Crontab i.e. job scheduling daemon works in Fedora and CentOS or any Linux platform(Ubuntu)....
What are the points that i have to take care of if have to include a script to be run at a specific scheduled time.
URGENT reply requested. Please help (1 Reply)
Discussion started by: Vabiosis
1 Replies
3. Virtualization and Cloud Computing
Hi,
I have installed VirtualBox, downloaded CentOS 5.5 and created a VirtualMachine where i have installed the 'server' versión of CentOS 5.5
As I installed Virtual Box a new network device appeared '192.16.1.250' in my 'real' machine. I was unable to reach my webserver so i istalled CentOS once... (5 Replies)
Discussion started by: motoko
5 Replies
4. Red Hat
Hi, I want to install the wmii window manager on my redhat. is there any package for it? anybody has any idea?
I googled it but did not find a good answer.
thanks.
Double post, continued here (0 Replies)
Discussion started by: messi777
0 Replies
5. Red Hat
Hi,
can i say technically there is no difference in:
package management (installation/removal/updating)
commands
between redhat and fedora?
in redhat if I am not a official subscriber, I can never do commands like:
yum search/update/install... unless I have the license
how does... (4 Replies)
Discussion started by: messi777
4 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I have following problem. I have Centos 5.8 ( Final ) on Virtual Box.
I noticed very strange behavior of the terminals when resizing them.
My default shell is tcsh .
Let's assume that we have trial script try.csh with text in it:
#! /bin/tcsh -f
# Trial script
echo... (4 Replies)
Discussion started by: tyanata
4 Replies
7. IP Networking
Guide on how to disable ipv6 for Centos and RedHat
1) Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and change:
NETWORKING_IPV6=yes to NETWORKING_IPV6=no
2) Edit /etc/modprobe.conf and add these lines:
alias net-pf-10 off
alias ipv6 off
3) Stop the ipv6tables service:
... (0 Replies)
Discussion started by: zanna91
0 Replies
8. Red Hat
Hi
I have a linux box and need to access from windows graphically
# uname -a
Linux pc-l416116 2.6.18-155.el5 #1 SMP Fri Jun 19 17:06:47 EDT 2009 i686 i686 i386 GNU/Linux
What components do I need to install on Linux and windows to do that?
TIA (6 Replies)
Discussion started by: magnus29
6 Replies
9. Red Hat
HI,
I have a Centos linux box and there is interface connect to internet.
I stop the iptables in this box .
After a few day , I find the linux box have been hacked and install some perl script into the box .
Could anyone tell me how the hacker can login into the centos box without knowing... (1 Reply)
Discussion started by: chuikingman
1 Replies
10. IP Networking
Hello my dears,
I preparing system running linux. I found that team is advantage than bond with the option "load-balancing for LACP support" and some minor advantages.
8.3. Comparison of Network Teaming to Bonding - Red Hat Customer Portal.
But what exactly meaning of this option I don't... (1 Reply)
Discussion started by: tien86
1 Replies
LEARN ABOUT MOJAVE
s390_runtime_instr
S390_RUNTIME_INSTR(2) System Calls Manual S390_RUNTIME_INSTR(2)
NAME
s390_runtime_instr - enable/disable s390 CPU run-time instrumentation
SYNOPSIS
#include <asm/runtime_instr.h>
int s390_runtime_instr(int command, int signum);
DESCRIPTION
The s390_runtime_instr() system call starts or stops CPU run-time instrumentation for the calling thread.
The command argument controls whether run-time instrumentation is started (S390_RUNTIME_INSTR_START, 1) or stopped (S390_RUN-
TIME_INSTR_STOP, 2) for the calling thread.
The signum argument specifies the number of a real-time signal. The real-time signal is sent to the thread if the run-time instrumentation
buffer is full or if the run-time-instrumentation-halted interrupt occurred.
RETURN VALUE
On success, s390_runtime_instr() returns 0 and enables the thread for run-time instrumentation by assigning the thread a default run-time
instrumentation control block. The caller can then read and modify the control block and start the run-time instrumentation. On error, -1
is returned and errno is set to one of the error codes listed below.
ERRORS
EINVAL The value specified in command is not a valid command or the value specified in signum is not a real-time signal number.
ENOMEM Allocating memory for the run-time instrumentation control block failed.
EOPNOTSUPP
The run-time instrumentation facility is not available.
VERSIONS
This system call is available since Linux 3.7.
CONFORMING TO
This Linux-specific system call is available only on the s390 architecture. The run-time instrumentation facility is available beginning
with System z EC12.
NOTES
Glibc does not provide a wrapper for this system call, use syscall(2) to call it.
SEE ALSO
syscall(2), signal(7)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux Programmer's Manual 2017-09-15 S390_RUNTIME_INSTR(2)