300,000 line numerical programs with no user interface are
portable, no matter what language they're written in.
FORTRAN got to the position it's in because all high-end
compiler work was focused on making FORTRAN run fast on
vector machines. These days, all compiler work is focused
Although my preference is BSD, then commercial Unix, then Linux,
I will admit that for the vast majority of uses, the choice
of Linux or BSD is a matter of taste. There are technical
differences, but they're subtle. The question is which style
of configuration & administration do you prefer...
You can change the sector size when you reformat. Some exotic
systems (Clariion RAID arrays are a famous example) use a
weird sector size.
The tearing-up-the-highway example is very good. Reformating
actually lays out where the tracks & sectors go, so it's just
like building a new road.
Yeah, early SunOS was BSD. They switched to SysV with SunOS 5,
and it was a complete switch, not just added SysVisms. Solaris 1
is SunOS 4 (BSD), all the later versions are SunOS 5 (SysV).
So - "Solaris 8" is technically "SunOS 5.8". The distinction
between SunOS and Solaris is really just...
I use an interface box from Prairie Digital. The only problem
is speed - it talks ASCII commands over a 9600 bps serial
line to the host - which makes it slow, but *incredibly*
easy to control. I bought mine to control some lights &
other gadgetry in an art installation at the Whitney...
Macintosh (original 128K ram, 400k floppy, no hard drive)
3B2/300 (mid-80s AT&T multi-user Unix system)
VAXstation-3100 (desktop version of the popular minicomputer)
RS/6000 Powerserver 930 (Monsterous 220-volt server - 1st generation
POWER processor, the ancestor of PowerPC.)...
Ok - I was just hunting around a bit, since I can never keep
this stuff straight - the Nova was DG's original 16 bit mini.
Then they came out with the Eclipse, which was also 16 bit.
Then there was a project, codenamed "Eagle" which was a
32 bit version of the Eclipse. That's the MV/8000...
Minicomputers are great fun. A friend of mine collections DG
gear. He has a few Novas and... I think an Eagle? They're
very hard to get. If you're interested in aquiring a fridge-
sized mini, I'd suggest a DEC PDP-11 as the easiest to aquire.
They also come in a very wide range of sizes - an...
It seems to me that your question is Escalade versus Highpoint,
not RAID1 versus RAID5.
The question of performance really depends on what you're
doing. What size files, how many users, what kind of LAN,
etc. How hard are you pushing the existing system?
1+0 is better, at least when you get into bigger arrays.
If you stripe first, then mirror (0+1), then any single
drive failure will take out one half of your mirror, and
a failure of any drive in the remaining stripe will lose
your data. If you mirror first, then stripe across the pairs...
Theoretically, all computers are capable of the exact same
calculations. There's no calculations this computer can do
that your PC can't do. However, in practice, the difference
between a job taking a day to run versus taking a year to
run makes the difference between what's considered...
There was a long period of shell experimentation back in the
80s, but it's really all boiled down to this:
You really just need to learn sh scripting.
Also - shell scripting is a *TERRIBLE* way to learn programming.
As a language it's really really ugly.
Rmove them both from wherever you're specifying that they
try dhcp - hostname.[interface], or wherever it is on your
distro. Then write a script, /etc/init-lan-connection that
either tries both with a short timeout, or checks the battery
status, or prompts you for a response, and stick a...
1: To make a file show up in a directory under a different name,
or just in a different directory, you make a "link" to it,
2: chmod is best used in octal, but that's confusing. Read
the man page a few more times.
3. "file" will attempt to identify what's in a file. Some...
I actually have a six disk RAID0 array running at the moment.
The chance of me losing the data there is very high, but I
only use it for work space. I write little source files, get
tens of thousands of large intermediate files, and then a
small final file. I copy the source & final file...
Parse it and call exec[...]() yourself, instead of using
system() to do all the work. Writing a shell is a fantastic
way to learn about unix's inner workings - I wrote one when
I was in college, then a better one when I got out, which
I actually used as my main shell for several years...
"../" is up one directory, but ". ./[something]", assuming
that space isn't a typo, means "execute [something], which you
will find in the current directory, and use the current shell,
don't spawn a subshell like you normally would". Generally
that's used if the script needs to set...
I don't know much Linux, but under every version of Unix
I've dealt with, /dev/tty is a special device that means
"my tty" to whatever process tries to open it. (Dates back
to when a unix box was the size of a vending machine, and
had a few dozen people logged in on serial lines from text...
daemontools drove me away from djbdns too.
I've been meaning to play with bind on openbsd, and just
haven't gotten around to it. I've been told using bind as
a cache is its default behaviour, and it's little more then