07-31-2001
???
nonbarye
I switched the machine on again today and it gave the same error messages, only now it also promted a few configuration changes that it is doing. Then it just continued to start up and work as normal. I have re-booted it a few times to check and it is working fine.
Do you have a link where I can read up about the PROM parameters, if this should happen again?
Thanks
Orange
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
How do I check my system to see if the graphics are using hardware 3d suport or not. I have a TNT2 on RH 7.1 kernel 2.4.9-?(can't remember off top of my head)I'm running all the latest updates from RH. Also I now have a dvd drive and I am trying to find a player that will play all movies and not... (1 Reply)
Discussion started by: MaxCat
1 Replies
2. UNIX for Dummies Questions & Answers
Is it possible to use Perl to work with hardware? Or is it strictly for text processing. (1 Reply)
Discussion started by: Luftwaffe
1 Replies
3. Filesystems, Disks and Memory
Does anyone know a good script/tool for remote identification of hardware on a linux-based system (RH9/NLD) ?
I'd like to know all the specifics like amount of memory, motherboard vendor, chipset and so on.... (0 Replies)
Discussion started by: patrickb
0 Replies
4. HP-UX
My J-Class system seems to have killed its onboard NIC. Does anyone have any good suggestions for a *cost effective* :p NIC for this machine? I am currently running 11i v1 on it, and have available PCI-X 5v slots.
Alternatively, perhaps someone knows of where I might find a list of supported... (1 Reply)
Discussion started by: ipaddict
1 Replies
5. UNIX Benchmarks
CPU: 1 x PA8600, 440MHz
RAM: 1GB
Hardware model: 9000/800/N4000-44
BYTE UNIX Benchmarks (Version 3.11)
System -- HP-UX xxx B.11.11 U 9000/800 615379343 unlimited-user license
Start Benchmark Run: Tue Apr 4 05:43:42 IST 2006
1 interactive users.
Dhrystone 2 without register... (0 Replies)
Discussion started by: blowtorch
0 Replies
6. Programming
How would I write a program in C that prints out the hardware the current computer has? And what about information about it?
Thank you for your time. (4 Replies)
Discussion started by: cubics
4 Replies
7. Programming
Hello !
I have a friend , in one day he tell me this : some guy made a cool program in C , for some sort or hardware control . I say : wow !
Maybe someone , can give me an example , how can C control hardware so good ( as I hear ) , and maybe some cool information , where to learn the idea ,... (1 Reply)
Discussion started by: !_30
1 Replies
8. Solaris
Hi,
I'm looking to run Sun Solaris 8 or 9, but have been running windows :mad: .can anyone give me advice about the hardware needed for solaris and possably any software i may need, the type of model and where i may be able to buy these within the uk. :confused:
... (3 Replies)
Discussion started by: franz
3 Replies
9. AIX
Can someone help me with what I am guessing is a simple job for an AIX admin. However I am 100% HP-UX and not touched AIX before the start of this week.
I am trying to connect an IBM Blade (JS22) to our HP Enterprise Tape Library. I have done all the SAN zoning and this appears to be happy... (5 Replies)
Discussion started by: Andyp2704
5 Replies
10. Solaris
Hi folk,
I have this hardware faunty message, but dont know which hardware is this ? can you guide me ?
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
LEARN ABOUT OPENDARWIN
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)