06-08-2005
*sigh*
/digressing_mode_on/
back then, in the good old days of the microchannel bus even booting was far easier than it is nowadays.
Who'd have thought back then, that these days will once be regarded as "good" ones, for chrissakes.
/digressing_mode_off/
Here is what you do: Put a monitor or terminal onto your 43P. Put the CD into the drive and switch on. After the IPL (firmware boot) there will ring a sort-of bell and on your screen will appear symbols for RAM, disk, Keyboard, etc. (LFT monitor) or the respective words "RAM", "disk", ... (terminal).
Press F4 *before* the last of the symbols/words appear and you get into a menu where you can select your installation media, etc. You can follow the instruction on the screen from there.
As an additional caveat I'm not sure if you can install 5.2 on a 43P, you *may* need a POWER-4 processor for 5.2, but I don't know that for sure.
Hope this helps.
bakunin
9 More Discussions You Might Find Interesting
1. AIX
:o Unix Sirs,
:eek:RE: IBM RISC/6000 1990
Used on Application:
Image buffer: 3D "Catia" (3D "Autocad" sim.) engineering C.A.D. Written by Deso. Cash prior to main frame dump:cool:
*
:oCan I purchase the oem operating system from you unix people? :cool:
... (1 Reply)
Discussion started by: penguins
1 Replies
2. UNIX for Dummies Questions & Answers
Hi
I am on solaris 8. And using xdm Xsun for X windows capabilities. Is it possible to close port 6000 and still have xdm Xsun for X windows capabilities.
I came across http://www.sunmanagers.org/pipermail/summaries/2004-May/005208.html
and neither i can close off port 6000
Rgds (2 Replies)
Discussion started by: yls177
2 Replies
3. AIX
Hi,
I am new to the AIX environment and am having this major problem,
I need to add a node to the cluster (hacmp) and i don't know how.
I got RS/6000 IBM running AIX 4.3.3
and the HACMP 4.4
any help :o (4 Replies)
Discussion started by: turki_00
4 Replies
4. AIX
On my IBM RS/6000 9114-275 a warning led is burning. It's an orange light with an exclamation mark. It started to burn when I did a reset of the system. What does it mean? How can I get it away? (0 Replies)
Discussion started by: rein
0 Replies
5. AIX
I bought an old IBM RS/6000 9114-275 1,00 GHz + 4 GB with AIX 6 Beta preinstalled. I have a TFT monitor at home. There's no fitting connector on the server for it. Does anyone know what type of monitor, or cable is common for this type of machine? I just never had to deal with things like this at... (4 Replies)
Discussion started by: rein
4 Replies
6. AIX
I have a friend who has the following error message on his LED:
888-102300-0C5
I've tried searching, but can't find anything.
Any ideas?
tks. (4 Replies)
Discussion started by: bbxguy
4 Replies
7. AIX
The 7046-B50, 7025-F50 and 7043-150 could utilize Yellow Dog linux from their initial release. My question is has anyone been able to extend Yellow Dog, or other linux distributions to work on other PPC RS/6000 platforms?
Rick (2 Replies)
Discussion started by: RAVC01
2 Replies
8. Hardware
Some time ago I bought an old microchannel RS/6000 39H as a hobby toy. I mostly deal with newer Sun/Oracle equipment so I'm a bit out of my element.
The machine was running, AIX 4.1.3 I believe. Using it via IBM terminal. I stored it for what was apparently too long, and now it stalls out... (11 Replies)
Discussion started by: drjohnnyfever
11 Replies
9. AIX
I have just purchased an old IBM RS/6000 7026-C2 with the intention of installing AIX 5.2 to do some testing.
I have no AIX or RS/6000 experience, but I have managed to access the console/service menu through a hyper terminal console via the com port.
I get the service processor menu and I can't... (12 Replies)
Discussion started by: AIX5.2
12 Replies
LEARN ABOUT ULTRIX
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk
SYNOPSIS
systemd-machine-id-commit.service
DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
file system. See machine-id(5) for more information about machine IDs.
This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
See systemd-machine-id-setup(1) for details.
The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
make it permanent.
SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)
systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)