10-11-2019
no issues but as I said we just reinstalled them a couple of weeks ago to 3.1.0.21 so they are latest and greatest. But so far chef is doing a great job updating the root password, /etc/resolv.conf and other files to our standards - and it has not yet killed a box
I am not sure how a 2000 day old VIOS would behave (not to mention that I am pretty sure that version is no longer supported by IBM since a while anyways - what do you have, 2.5.x?. Do you have any physical box with similar old OS you could try if it would generally work for that OS version? I am more of a chef user, so all I do is install the client software and run it and check afterwards that the initial run did what it was supposed to do
7 More Discussions You Might Find Interesting
1. AIX
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
2. AIX
Hi,
I would like to reboot vio client but I am not able to access vio client(I am not able to get putty) , I am able to get putty of vio server,
is there any command by using which from vio server I can reboot vio client? (3 Replies)
Discussion started by: manoj.solaris
3 Replies
3. AIX
Hi,
I am having single p series blade with Single Physcial CPU with dual core,
on that vio server is installed, I have created vio client allocate 0.9 each cpu , now when I am running prtconf command on vio client it is showing "2" no of processor,
My query using which command it will... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
4. AIX
Hi
I am facing very strange issue on my vio server 5 vio clients are confgured, now I am to connect 3 vio client , i am unable to connect 2 vio client my ip address,subnet mask,gateway is correct.
i have rebooted and reconfigured the ip address, but issue is persists.
Kindly suggest how to... (0 Replies)
Discussion started by: manoj.solaris
0 Replies
5. AIX
Hi
im logged in to the vio servers now.
when i give
# lspv | wc -l
i get the count as 6246
how will i know if a lun has been already mapped to a vio client or it is left free without mapping to any of the vio client ? (1 Reply)
Discussion started by: newtoaixos
1 Replies
6. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
7. AIX
Hi
In my vio server I have the below output
$ lsvopt | grep -i SAPSITGS
sapsitgs_cdrom TL12UP.iso 3182
In my vio client lpar I have the below output
root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server
cd1... (1 Reply)
Discussion started by: newtoaixos
1 Replies
LEARN ABOUT NETBSD
compat_ultrix
COMPAT_ULTRIX(8) BSD System Manager's Manual COMPAT_ULTRIX(8)
NAME
compat_ultrix -- setup procedure for ULTRIX compatibility on MIPS and VAX architectures
DESCRIPTION
NetBSD/mips and NetBSD/vax architectures can run Risc ULTRIX and VAX ULTRIX executables, respectively. However, you have to worry about the
legal issues of ensuring that you have a right to use any ULTRIX binaries on your machine.
Most executables will work. The exceptions include programs that use proprietary, ULTRIX-specific features (LAT, CI support, DECnet support)
and various system calls, ioctl()'s, or ULTRIX kernel semantics that are difficult to emulate (e.g. ULTRIX packetfilter) or buggy (e.g.
ULTRIX NIS).
All ULTRIX executables are static, so no shared libraries are required for ULTRIX compatibility. However, ULTRIX is based on a 4.3BSD alpha
release. ULTRIX commands and libraries are often much older than their NetBSD or even SunOS 4.x equivalents, and may require incompatible
configuration files.
SYSTEM CONFIGURATION FILES
Set up resolv.conf and svc.conf as below:
# mkdir -p /emul/ultrix/etc
# cd /emul/ultrix/etc
# egrep 'domain|nameserver' /etc/resolv.conf > ./resolv.conf
# cp -p /usr/share/examples/emul/ultrix/etc/* ./
/etc/resolv.conf
The ULTRIX resolver library only understands domain and nameserver lines in resolv.conf(5). You should create a copy of /etc/resolv.conf
containing only those commands and put it in /emul/ultrix/etc/resolv.conf. Note that the domain search order used by ULTRIX executables may
not be the same as native binaries; there is no good way around this.
/etc/svc.conf
ULTRIX uses /etc/svc.conf to select an ordered search of NIS, Hesiod, or local flat-file mappings. You should create an
/emul/ultrix/etc/svc.conf specifying either local files or bind (DNS) lookups for all ULTRIX name services.
SEE ALSO
resolv.conf(5)
BUGS
RISC ULTRIX NIS (YP) is known to not work. The ULTRIX NIS libraries have a consistent endian-ness bug. ULTRIX NIS client will not inter-
operate with the NetBSD ypbind(8) process. The only workaround is to use /etc/svc.conf to disable NIS (YP).
The ndbm hashed-password file used by ULTRIX are incompatible with the db hashed-password file used by NetBSD. There is no good solution for
this. NIS would be a good one, if ULTRIX NIS worked.
The API used by Xservers to talk to the kernel is currently compatible with ULTRIX 4.1. An implementation of the ULTRIX 4.2 Xws interface
(used by X11R6) is in progress.
A complete list of things which fail to work in ULTRIX compatibility mode should be added here.
BSD
January 16, 1999 BSD