08-25-2015
AIX firmware password woes!!
Hi Blackrageous, Is it simply a case of setting the switch and then I have a machine I can switch on, set a new firmware password and up and away re-install AIX? The machine isn't currently networked and when I set it up it will just be to an internet router.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Have a Sun CDROM connected to a Ultra machine .
Problem is it is not recognizing the drive being connected to it ...
When i put the CD in the drive it accepts the CD and zooms initially then quitens out ..
The devices drivers are also not created for it ...
Any ideas anyone ... I am... (4 Replies)
Discussion started by: Jai
4 Replies
2. Solaris
Good Day,
I've remotely mounted a cdrom (no problems theere). The kicker is I can see the directories on the remote CD bout I can't see the files. What am I doing wrong? I'm logged in as root on both systems. All the permissions seem okay - what am I missing? Thanks (2 Replies)
Discussion started by: greg69
2 Replies
3. Solaris
Morning all,
I am attempting to load a package from a Solaris 8 CDROM.
This fails with the error :
"pkgadd: ERROR: unable to access pkgmap file </cdrom/ .........../SUNWlibC/pkgmap>
No changes were made to the system"
Any help would be appreciated
Andy (6 Replies)
Discussion started by: AndyD
6 Replies
4. Solaris
version of solaris: SunOS 5.8 Generic-117350-39 sun4u sparc SUNW,Netra-240
version of SSH: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006
Task:
I need to have another Machine ssh into my machine, by either RSA authentication or username/pass authentication.
History:
In the begining my... (4 Replies)
Discussion started by: EWTGPAC
4 Replies
5. Solaris
Hi:
I have a Sun Blade 1500 and when I do the Jumpstart with
command "boot net - install" asking for the password of the firmware
and I was not that password. There any way to reset this password.
Thank you very much (7 Replies)
Discussion started by: ea1fch
7 Replies
6. Solaris
So in the group of boxes I've inherited, I have one that has a firmware password. I do not know the root password of the machine nor the firmware password. I've tried several things already, such as: removing BIOS battery, double tap the power switch, and several variants of the STOP-A on a PC... (2 Replies)
Discussion started by: adelsin
2 Replies
7. Solaris
Greetings Forumers!
I've been fighting a locale problem on a v490 running Solaris 10 u4 (8/07). When I login to the system, I get several "locale" error messages:
user1's password:
Last login: Wed May 26 2010 09:14:13 -0400 from system1
You have mail.
couldn't set locale correctly
couldn't... (0 Replies)
Discussion started by: bluescreen
0 Replies
8. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
9. Solaris
Hey,
I have been battling with jumpstart for the past few days. Interface nxge0 is set on a vlan:
nxge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 0.0.0.0 netmask ff000000
ether 0:21:28:3c:a0:6
nxge998000:... (0 Replies)
Discussion started by: stantonnet
0 Replies
10. AIX
Hi all
With the recent virus attacks we have been tasked with upgrading Samba to a "secure" version. Currently running 3.0.29a and looking to put the latest version down 4.6.5.
Being a lazy bod I have only ever installed this, a long time ago, when you could get it in BFF filesets. Have... (6 Replies)
Discussion started by: splattty
6 Replies
LEARN ABOUT POSIX
systemd-machine-id-setup
SYSTEMD-MACHINE-ID-SETUP(1) systemd-machine-id-setup SYSTEMD-MACHINE-ID-SETUP(1)
NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id
SYNOPSIS
systemd-machine-id-setup
DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with
a provisioned or randomly generated ID. See machine-id(5) for more information about this file.
If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty.
The new machine ID will be acquired in the following fashion:
1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID
in /etc/machine-id.
2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID.
The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM.
3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the
machine ID. For details, see the documentation of the Container Interface[1].
4. Otherwise, a new ID is randomly generated.
The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below.
Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images.
OPTIONS
The following options are understood:
--root=root
Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for
/etc/machine-id itself.
--commit
Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient
machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of
the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point.
This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The
command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure
that this file is always valid and accessible for other processes.
This command is primarily used by the systemd-machine-id-commit.service(8) early boot service.
--print
Print the machine ID generated or committed after the operation is complete.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1)
NOTES
1. Container Interface
https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)