Sponsored Content
The Lounge What is on Your Mind? They won't need so many sys admins anymore Post 302956937 by Corona688 on Monday 5th of October 2015 11:12:22 AM
Old 10-05-2015
Quote:
Originally Posted by gandolf989
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.
Which is why the average North American now carries one or more RISC processors at all times, has several more in their home, and is increasingly using them for all computing.
 

9 More Discussions You Might Find Interesting

1. Solaris

Any sys admins from uk?

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

Can't login as SU anymore - SU: NO SHELL

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

won't mount /usr...won't boot fully

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

Sun Fire won't boot anymore

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

Can't SSH as root anymore!

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

pkill won't work on firefox anymore

Can someone tell me why pkill won't work on firefox anymore? (11 Replies)
Discussion started by: cokedude
11 Replies

7. Slackware

Anyone Using Slackware Anymore?

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

Interactive Python 3.5+ sys.stdout.write() AND sys.stderr.write() bug?

(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

Bash script won't run because hardware won't produce display

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
normality(5)							File Formats Manual						      normality(5)

NAME
normality - definition of what types of normalities different users may have. SYNOPSIS
/etc/normality DESCRIPTION
The normality configuration file has a rather simple syntax, as shown in the diagram in the next section. Some things to remember is that the normality file's influence is inversely proportional to the user's cluefulness and that, in certain cirumstances, modification of the normality file can and will be considered immoral. NORMALITY GRAMMAR
<normality file> := <normality file> <line> | ; <line> := <normality type> ': ' <userlist> | <normality type> '! ' <userlist> | <normality type> '= ' <normality tags> | <comment> <normality type> := [A-Z][a-zA-Z0-9]+ <userlist> := <username> ', ' <userlist> ';0 | <username> ';0 <normality tags> := <normality tag> ', ' <normality tags> ';0 | <normality tag> ';0 <normality tag> := 'marriage' | 'love-relation' | 'nice-job' | 'money' | 'spare-time' | 'friends' | 'no-pager' | 'vacation' <comment> := '#' .* '0 SEMANTICS
It is expected that you specify all normality types before you start assigning (or disassigning) users to (or from) them. That is so the system can do an easier consistency check of the specification. Let's say that we have a system with three normality types, foo, bar and gazonk and two users, cucumber and onion. Now, a line like "foo! onion;" would exclude onion from having any of the real-life things specified by the foo type, even if that (or those) things appear in another normality type. So, the disallow syntax overrides the allow syntax (specified by "<type>: <username>..."). There is always an implicit type named ``all'', that contains all normality tags. For all system administrators, you have an implicit rule, "all! asr". EXAMPLES
# Normality file for a sad system # Our users are onion, cucumber, jdoe, jrl and washu animetype= love-relation, nice-job, friends, spare-time; notworst= love-relation, nice-job, friends; sysadm= friends; # All normality types we will use are declared # Now let's do the magic stuff... all: jdoe, jrl; animetype: washu; sysadm: cucumber; all! onion; # Now, this is fairly easy, OK? WARNINGS AND BUGS
This file messes with the real world, so a bit of caution is recommended. Newer versions of the chastise(3) library function modifies this file on-the-fly. Has a tendecy to create small discontinuities in the velvet of reality whenever there are syntax errors in the normality file. AUTHOR
This sick idea was put down in *roff format by Ingvar Mattsson, as a contribution to the alt.sysadmin.recovery man page collection. 4th Berkeley Distribution Release 0.001 alpha normality(5)
All times are GMT -4. The time now is 08:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy