cat /proc/cpuinfo
to get centOS unix version
cat /etc/redhat-release



|
cat /proc/cpuinfo to get centOS unix version cat /etc/redhat-release
Check the RHEL repos, but useful cmds include: #lshw
#lspci
#dmidecode
#cat /var/log/dmesg (might be boot.msg or similar)
DMI 2.3 present.
Using APIC driver default
ACPI: RSDP (v002 IBM ) @ 0x000fdfb0
ACPI: XSDT (v001 IBM SERONYXP 0x00001001 IBM 0x45444f43) @ 0xd7fcff00
ACPI: FADT (v002 IBM SERONYXP 0x00001001 IBM 0x45444f43) @ 0xd7fcfe40
ACPI: MADT (v001 IBM SERONYXP 0x00001001 IBM 0x45444f43) @ 0xd7fcfd80
ACPI: MCFG (v001 IBM SERONYXP 0x00001001 IBM 0x45444f43) @ 0xd7fcfd40
ACPI: SSDT (v002 IBM YETA0 0x00001000 INTL 0x20041203) @ 0xd7fcfa40
ACPI: DSDT (v002 IBM SERTURQU 0x00001000 INTL 0x20041203) @ 0x00000000
ACPI: PM-Timer IO Port: 0x588
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
Processor #6 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
Processor #7 15:4 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 14, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x0d] address[0xfec84000] gsi_base[24])
IOAPIC[1]: apic_id 13, version 32, address 0xfec84000, GSI 24-47
ACPI: IOAPIC (id[0x0c] address[0xfec84400] gsi_base[48])
IOAPIC[2]: apic_id 12, version 32, address 0xfec84400, GSI 48-71
ACPI: IOAPIC (id[0x0b] address[0xfec80000] gsi_base[72])
IOAPIC[3]: apic_id 11, version 32, address 0xfec80000, GSI 72-95
ACPI: IOAPIC (id[0x0a] address[0xfec80400] gsi_base[96])
IOAPIC[4]: apic_id 10, version 32, address 0xfec80400, GSI 96-119
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 5 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at dc000000 (gap: d8000000:26c00000)
Detected 3000.370 MHz processor.
Built 1 zonelists. Total pages: 1048576
Kernel command line: ro root=LABEL=/
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
mapped IOAPIC to ffffb000 (fec84000)
mapped IOAPIC to ffffa000 (fec84400)
mapped IOAPIC to ffff9000 (fec80000)
mapped IOAPIC to ffff8000 (fec80400)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
you need to edit this file: etc/resolv.conf #vi /etc/resolv.conf To install a chrooted BIND9, enter the following command: #yum install bind-chroot
There are two separate things keeping track of the date/time in a *nix system:
the hardware clock and the "kernel time". The "date" command is used to access
the kernel time, and the "clock" command is used to access the internal
hardware clock (or CMOS). Problems can arise when the two are not properly
synced. Additionally, there are other files traditionally involved in setting
the local timezone, and even files that can be set to correct for internal
clocks that run a bit fast or slow (see references). All steps below should be
typed on the command line as root.
STEPS:
(1) See what day-date-time-timezone-year the kernel thinks it is. Type:
date
and you should see something like:
Mon Aug 14 11:34:42 HST 2000
(2) If your timezone is not correct, look under /usr/share/zoneinfo/ for a
location near you. To set the timezone you need to make a symbolic link from
the appropriate file to /etc/localtime. For me this looked like:
ln -s /usr/share/zoneinfo/Pacific/Honolulu /etc/localtime
Some representatives from mainland US timezones include:
/usr/share/zoneinfo/America/Los_Angeles
/usr/share/zoneinfo/America/Denver
/usr/share/zoneinfo/America/Chicago
/usr/share/zoneinfo/America/New_York
If /etc/localtime already exists, do this:
mv /etc/localtime /etc/localtimeOLD
and then create the symbolic link.
(3) If the date/time is not accurate, set it using the following options:
date -s 'MM/DD/YYYY HH:MM:SS'
(4) Now set the CMOS (hardware clock) to match the kernel time:
clock -w
(5) If you don't want all this stuff to get messed up again when you reboot,
you need to link the kernel time to the hardware clock. To do this enter:
echo "clock -s" > /sbin/hwclock
chmod +x /sbin/hwclock
Now when /sbin/hwclock is run during the boot sequence it will set the kernel
time to match the CMOS time (which you just set). This fixes an oversight/bug
in LinuxPPC that will hopefully be fixed in future ditributions.
ALTERNATE: If you dual-boot, you can just do steps 1, 2 and 5 above, and then
set your hardware clock using the MacOS date & time control panel. This can be
used as a simple way to sync with a timeserver. |