01-09-2018
AIX 6.1, POWER5 and Spectre/Meltdown
Apologies for this newbie question. We have inherited an IBM p5 520 (9111-520) running AIX 6.1.0.0 which seems to be the base install and no further patches installed.
Is this vulnerable to the Spectre/Meltdown threat?
Are patches available?
Looks like AIX 6.1.0.0 went 'end of support' in April last year so are there even patches available for this new threat and can I get them for free or does the system need subscribing to IBM at a cost?
7 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I had an issue with a second hard disk in my machine. I have a sparc station running solaris 7. It was working fine but now it wont mount on boot up and when you try to mount it manually it gives an I/O error. I tried a different disk as a control which was fine. What I want to know is if my... (3 Replies)
Discussion started by: Henrik
3 Replies
2. AIX
Hi all,
I have a AIX 5.3 Installation on the Power5 processor. I am using the knlist API for getting the details of the CPU details like user cpu, kernel cpu, idle cpu and wait cpu. My code is working fine on other Installations of AIX like PowerPC_POWER4 but it is giving wrong values on Power5... (0 Replies)
Discussion started by: rajesht
0 Replies
3. AIX
I have a power5 that I would like to update and bring everything forward.
I am wondering about trouble-free upgrades. Is it better to go 5.3 -> 7 or 5.3 ->6 ->7?
The power5 box is behind and hopefully can learn from experiences here.
Thanks. (6 Replies)
Discussion started by: redi
6 Replies
4. AIX
Hello,
What is wattage of POWER5+ 2.1Gz CPU ?
It's dual-core 90nm chip.
At least approximately ?
thanks,
Vilius (1 Reply)
Discussion started by: vilius
1 Replies
5. AIX
Hello all, I am hoping someone can point me in the right direction here.
We had a machine running AIX 6.1 that someone completely corrupted, so we decided to re-load it from media. I was able to boot into DVD media, select options for complete (destructive) install, AIX standard, etc. The... (0 Replies)
Discussion started by: JamesNJ
0 Replies
6. War Stories
Apologies if this is the wrong forum but...
...This is hard hitting stuff.
LKML: Linus Torvalds: Re: x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation (5 Replies)
Discussion started by: wisecracker
5 Replies
7. What is on Your Mind?
This seems a bit serious:
Meltdown, Spectre: The password theft bugs at the heart of Intel CPUs • The Register
Vulnerability Note VU#584653 - CPU hardware vulnerable to side-channel attacks
Project Zero: Reading privileged memory with a side-channel (8 Replies)
Discussion started by: Scrutinizer
8 Replies
LEARN ABOUT DEBIAN
stg-squash
STG-SQUASH(1) StGit Manual STG-SQUASH(1)
NAME
stg-squash - Squash two or more patches into one
SYNOPSIS
stg squash [options] <patches>
DESCRIPTION
Squash two or more patches, creating one big patch that contains all their changes. In more detail:
1. Pop all the given patches, plus any other patches on top of them.
2. Push the given patches in the order they were given on the command line.
3. Squash the given patches into one big patch.
4. Allow the user to edit the commit message of the new patch interactively.
5. Push the other patches that were popped in step (1).
Conflicts can occur whenever we push a patch; that is, in step (2) and (5). If there are conflicts, the command will stop so that you can
resolve them.
OPTIONS
-n NAME, --name NAME
Name of squashed patch.
-m MESSAGE, --message MESSAGE
Use MESSAGE instead of invoking the editor.
-f FILE, --file FILE
Use the contents of FILE instead of invoking the editor. (If FILE is "-", write to stdout.)
--save-template FILE
Instead of running the command, just write the message template to FILE, and exit. (If FILE is "-", write to stdout.)
When driving StGit from another program, it is often useful to first call a command with --save-template, then let the user edit the
message, and then call the same command with --file.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SQUASH(1)