01-06-2015
How did you create the virtual machine? We need exact steps.
Is it an LDOM or a zone or VirtualBox?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
There are two servers where my machine is connected. Is there any type of link formed between my machine and server machine? (1 Reply)
Discussion started by: palash2k
1 Replies
2. Solaris
Do we have any Virtual Data Center software as we have Virtual Machine?
I want to practice everything of Solaris practically but i don't have resources like data center which includes Servers, Data storages, switches, and other things. (2 Replies)
Discussion started by: karman0931
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I'm virtualising ubuntu on a mac forum and I get the following error when I run my application...
If I try ping localhost from guest OS, it works...
thanks (0 Replies)
Discussion started by: aneuryzma
0 Replies
4. UNIX for Dummies Questions & Answers
After installing PV (Para virtual drivers) drivers I m not able to check the network speed of my Ethernet port.
Please check the output of mii-tool and ethtool.
# mii-tool eth0
SIOCGMIIPHY on 'eth0' failed: Operation not supported
# ethtool eth0
Settings for eth0:
Link... (2 Replies)
Discussion started by: pinga123
2 Replies
5. Red Hat
Hi All,
In my Org we are using Xen Hypervisor on RHEL 5.Now now the biggest challenge for us is to take online snapshot of running VM Guests.But this feature is not available in Xen.
So i am trying to figure it out with some of the blogs found on net,in one blog its saying to create... (0 Replies)
Discussion started by: ajaincv
0 Replies
6. Solaris
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies
7. Red Hat
My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool
Hi,
I don't seem to have the Virtual Machine Manager Desktop tool set up on my RHEL6 Machine. The Linux machine runs off VMWare player and I'm not sure whether it is a VMWare software issue or a problem with the RHEL6... (2 Replies)
Discussion started by: accipiter1
2 Replies
8. UNIX for Advanced & Expert Users
Can I please get some recommendations on virtual machine software? I am using Fedora. What do you think is the best software and why? I need a windows virtual machine to run some windows software. What do you think is the best Windows version to use and why (xp, vista, 7, 8, 8.1)? Is it hopefully... (2 Replies)
Discussion started by: cokedude
2 Replies
9. AIX
Hi There,
I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available).
Anyone could provide me the following answer -
Can IBM VM been deploy on X86 and X64 (Intel Chip)?
If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
Is there any way I can prioritize my VMs when there is resource crunch in host machine so that some VMs will be allocated more vcpu, more memory than other VMs in kvm/qemu hypervisor based virtual machines?
Lets say in my cloud environment my Ubuntu 16 compute hosts are running some... (0 Replies)
Discussion started by: SanjayK
0 Replies
LEARN ABOUT REDHAT
atalkd
ATALKD(8) System Manager's Manual ATALKD(8)
NAME
atalkd - AppleTalk RTMP, NBP, ZIP, and AEP manager
SYNOPSIS
/usr/sbin/atalkd [ -f configfile ] [ -1 | -2 ]
DESCRIPTION
atalkd is responsible for all user level AppleTalk network management. This includes routing, name registration and lookup, zone lookup,
and the AppleTalk Echo Protocol (similar to ping(8)). atalkd is typically started at boot time, out of /etc/rc. It first reads from its
configuration file, /etc/atalk//atalkd.conf. If there is no configuration file, atalkd will attempt to configure all available interfaces
and will create a configuration file. The file consists of a series of interfaces, one per line. Lines with `#' in the first column are
ignored, as are blank lines. The syntax is
interface [ -seed ] [ -phase number ] [ -net net-range ] [ -addr address ] [ -zone zonename ] ...
Note that all field except the interface are optional. The loopback interface is configured automatically. If -seed is specified, all
other fields must be present. Also, atalkd will exit during bootstrapping, if a router disagrees with its seed information. If -seed is
not given, all other information may be overriden during auto-configuration. If no -phase option is given, the default phase as given on
the command line is used (the default is 2). If -addr is given and -net is not, a net-range of one is assumed.
The first -zone directive for each interface is the ``default'' zone. Under Phase 1, there is only one zone. Under Phase 2, all routers
on the network are configured with the default zone and must agree. atalkd maps ``*'' to the default zone of the first interface. Note:
The default zone for a machine is determined by the configuration of the local routers; to appear in a non-default zone, each service, e.g.
afpd, must individually specify the desired zone. See also nbp_name(3).
ROUTING
If you are connecting a netatalk router to an existing AppleTalk internet, you should first contact your local network administrators to
obtain appropriate network addresses.
atalkd can provide routing between interfaces by configuring multiple interfaces. Each interface must be assigned a unique net-range
between 1 and 65279 (0 and 65535 are illegal, and addresses between 65280 and 65534 are reserved for startup). It is best to choose the
smallest useful net-range, i.e. if you have three machines on an Ethernet, don't chose a net-range of 1000-2000. Each net-range may have
an arbitrary list of zones associated with it.
EXAMPLE
Below is an example configuration file for a sun4/40. The machine has two interfaces, ``le0'' and ``le1''. The ``le0'' interface is con-
figured automatically from other routers on the network. The machine is the only router for the ``le1'' interface.
le0
le1 -seed -net 9461-9471 -zone netatalk -zone Argus
atalkd automatically acts as a router if there is more than one interface.
FILES
/etc/atalk//atalkd.conf configuration file
BUGS
On some systems, atalkd can not be restarted.
netatalk 1.3 17 Nov 1995 ATALKD(8)