10-05-2015
Quote:
The first big one was the abandon of PA-RISC...
I find this statement really odd. The reason why people liked RISC chips is because, at one point, they had faster clock speeds that CISC chips. However, since then CISC chips have become significantly faster, run at a higher clock frequency and can do more with each clock cycle. Hence anything RISC is in the past.
I worked in the VAX/Alpha world 20 years ago. That architecture was dying then, and is now all but dead. There is still a local steel mill that uses Alpha processors. But they only use it because they haven't yet rewritten all their old Cobol and Fortran.
I get the argument that cloud computing means fewer tech jobs. But companies will still want some knowledge in house. But maybe not forever.
9 More Discussions You Might Find Interesting
1. Solaris
Hello Guys, im new to this forum. Im from UK and ive recently completed my SCSA I & II and also got trained in Veritas Suite (Veritas Volume Manager and Veritas Clusters, Veritas NetBackup), SAN Configuration. I was trying to get a break as a junior sun solaris admin. I am applying for the jobs... (1 Reply)
Discussion started by: megadeth
1 Replies
2. UNIX for Dummies Questions & Answers
the root shell has been changed in the file /etc/passwd, basically pointing to an incorrect directory. So now every time we login as 'su' I get the message
'su: no shell' so we can't login as superuser.
Is there an easy way to rectify this? please use step by step instructions/commands -
I... (4 Replies)
Discussion started by: homechoice
4 Replies
3. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
4. Solaris
Hi all - I have an issue with our (way old) single processor SunFire 280R, running Solaris 9.0.4.
It won't boot even after multiple power cycles. There was a power outage last week end in the computer room, so this might have to do.
In normal boot mode, the screen shows a single line :
... (5 Replies)
Discussion started by: bostella
5 Replies
5. UNIX for Dummies Questions & Answers
I've screwed something up in my sshd_config apparently, because I can't ssh with root anymore.
I had disabled root login for security reasons, but then my ssh credentials with full administrative privelges stopped working. So then I reenabled root login (and reset ssh), but root now isn't... (3 Replies)
Discussion started by: cquarry
3 Replies
6. UNIX for Advanced & Expert Users
Can someone tell me why pkill won't work on firefox anymore? (11 Replies)
Discussion started by: cokedude
11 Replies
7. Slackware
We used to use Slackware, but then moved all our servers to Ubuntu Linux.
Does anyone use Slackware anymore? (8 Replies)
Discussion started by: Neo
8 Replies
8. Programming
(Apologies for any typos.)
OSX 10.12.3 AND Windows 10.
This is for the serious Python experts on at least 3.5.x and above...
In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly.
Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 Replies
9. UNIX for Beginners Questions & Answers
Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
3 Replies
LEARN ABOUT FREEBSD
clocks
CLOCKS(7) BSD Miscellaneous Information Manual CLOCKS(7)
NAME
clocks -- various system timers
SYNOPSIS
#include <time.h>
DESCRIPTION
HZ is not part of the application interface in BSD.
There are many different real and virtual (timekeeping) clocks with different frequencies:
o The scheduling clock. This is a real clock with frequency that happens to be 100. It is not available to applications.
o The statistics clock. This is a real clock with frequency that happens to be 128. It is not directly available to applications.
o The clock reported by clock(3). This is a virtual clock with a frequency that happens to be 128. Its actual frequency is given by the
macro CLOCKS_PER_SEC. Note that CLOCKS_PER_SEC may be floating point. Do not use clock(3) in new programs under FreeBSD. It is feeble
compared with getrusage(2). It is provided for ANSI conformance. It is implemented by calling getrusage(2) and throwing away informa-
tion and resolution.
o The clock reported by times(3). This is a virtual clock with a frequency that happens to be 128. Its actual frequency is given by the
macro CLK_TCK (deprecated; do not use) and by sysconf(_SC_CLK_TCK) and by sysctl(3). Note that its frequency may be different from
CLOCKS_PER_SEC. Do not use times(3) in new programs under FreeBSD. It is feeble compared with gettimeofday(2) together with
getrusage(2). It is provided for POSIX conformance. It is implemented by calling gettimeofday(2) and getrusage(2) and throwing away
information and resolution.
o The profiling clock. This is a real clock with frequency 1024. It is used mainly by moncontrol(3), kgmon(8) and gprof(1). Applications
should determine its actual frequency using sysctl(3) or by reading it from the header in the profiling data file.
o The mc146818a clock. This is a real clock with a nominal frequency of 32768. It is divided down to give the statistic clock and the
profiling clock. It is not available to applications.
o The microseconds clock. This is a virtual clock with frequency 1000000. It is used for most timekeeping in BSD and is exported to
applications in getrusage(2), gettimeofday(2), select(2), getitimer(2), etc. This is the clock that should normally be used by BSD
applications.
o The i8254 clock. This is a real clock/timer with a nominal frequency of 1193182. It has three independent time counters to be used. It
is divided down to give the scheduling clock. It is not available to applications.
o The TSC clock (64-bit register) on fifth-generation or later x86 systems. This is a real clock with a frequency that is equivalent to
the number of cycles per second of the CPU(s). Its frequency can be found using the machdep.tsc_freq sysctl, if it is available. It is
used to interpolate between values of the scheduling clock. It can be accessed using the PMIOTSTAMP request of perfmon(4).
o The ACPI clock. This is a real clock/timer with a nominal frequency of 3579545. It is accessed via a 24 or 32 bit register. Unlike the
TSC clock, it maintains a constant tick rate even when the CPU sleeps or its clock rate changes. It is not available to applications.
Summary: if HZ is not 1000000 then the application is probably using the wrong clock.
SEE ALSO
gprof(1), clock_gettime(2), getitimer(2), getrusage(2), gettimeofday(2), select(2), clock(3), moncontrol(3), times(3)
AUTHORS
This manual page was written by Jorg Wunsch after a description posted by Bruce Evans.
BSD
January 18, 2008 BSD