02-01-2007
Quote:
Originally Posted by sb008
echo $((RANDOM%100+1))
That is a poor method since it will return a random number in the range 1..68 more often than 69..100.
8 More Discussions You Might Find Interesting
1. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
2. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
3. AIX
Hi,
How can i check that i am using RAW devices for storage in my AIX machine...
Also after adding a LUN from storage to a aix host, when i check /dev in the host, i can see both rhdisk and hdisk with same number
eg:
dcback1(root):/dev>ls -lrt | grep disk12
crw------- 1 root ... (4 Replies)
Discussion started by: jibujacob
4 Replies
4. AIX
Hello AIXians,
I can't boot my AIX, it hangs and stops at the code error: 0518
After searching google, I knew the problem is due to problems in File Systems.
So the solution is booting from any bootable media, then run these commands in maintenance mode:
#fsck -y /dev/hd4
#fsck -y... (3 Replies)
Discussion started by: Mohannad
3 Replies
5. Shell Programming and Scripting
Objective: To recreate the partitioning setup of /dev/sda on /dev/sdc
How would I parse the below information and initialize variables
(an array?) that can be used to build sgdisk commands in a script, regardless of the number of partitions?
Something along the lines of:
sgdisk -n... (12 Replies)
Discussion started by: RogerBaran
12 Replies
6. Red Hat
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
7. UNIX for Advanced & Expert Users
Hi
I'm running the following command to generate a random password in a KSH script on a RHEL Linux VM but for some reason the cmd is not being closed and it's causing problems on the host.
PASSWORD="$(cat /dev/urandom | tr -dc "a-zA-Z0-9" | fold -w 16 | head -1)Aa0!"
The code worked as... (2 Replies)
Discussion started by: user052009
2 Replies
8. HP-UX
Hi,
In our HP-UX B.11.11. I could not find dev/urandom and dev/random
Are all pseudo-devices implemented as device drivers, or in need to run /configure some package to install the package to have dev/urandom.
Please help (4 Replies)
Discussion started by: rashi
4 Replies
LEARN ABOUT OPENDARWIN
random
RANDOM(4) BSD Kernel Interfaces Manual RANDOM(4)
NAME
random , urandom -- random data source devices.
SYNOPSIS
pseudo-device random
DESCRIPTION
The random device produces uniformly distributed random byte values of potentially high quality.
To obtain random bytes, open /dev/random for reading and read from it.
To add entropy to the random generation system, open /dev/random for writing and write data that you believe to be somehow random.
/dev/urandom is a compatibility nod to Linux. On Linux, /dev/urandom will produce lower quality output if the entropy pool drains, while
/dev/random will prefer to block and wait for additional entropy to be collected. With Yarrow, this choice and distinction is not necessary,
and the two devices behave identically. You may use either.
OPERATION
The random device implements the Yarrow pseudo random number generator algorithm and maintains its entropy pool. Addditional entropy is fed
to the generator regularly by the SecurityServer daemon from random jitter measurements of the kernel. SecurityServer is also responsible
for periodically saving some entropy to disk and reloading it during startup to provide entropy in early system operation.
You may feed additional entropy to the generator by writing it to the random device, though this is not required in a normal operating envi-
ronment.
LIMITATIONS AND WARNINGS
Yarrow is a fairly resilient algorithm, and is believed to be resistant to non-root. The quality of its output is however dependent on regu-
lar addition of appropriate entropy. If the SecurityServer system daemon fails for any reason, output quality will suffer over time without
any explicit indication from the random device itself.
Paranoid programmers can counter-act this risk somewhat by collecting entropy of their choice (e.g. from keystroke or mouse timings) and
seeding it into random directly before obtaining important random numbers.
FILES
/dev/random
/dev/urandom
HISTORY
A random device appeared in Linux operating system.
Darwin September 6, 2001 Darwin