Nope, but keep in mind that the m64 chip on those puppies is kinda broken. It doesn't work properly at anything other than 8 or 24-bit -- and it doesn't have enough ram to be useful at 24-bit.
IIRC trying to run at 16 bits produces a black screen with dark blue writing, at least in Solaris.
If you can fiddle the debian loader like you can with knoppix (closest thing to Debian I use), try 1152x900 with 8-bit colour. Oh, and select a reasonable refresh rate...
The hardware runs a program. That program loads the kernel and executes it. Any more specific, and you're now talking platform-specifics which don't have to with UNIX.
For example, Linux on a DEC Alpha might boot like this:
- Windows NT ARC loader configured to spawn program MILO.EXE on FAT-formatted disk in Drive A:
- MILO.EXE understands Linux ext2fs, and launches the kernel wherever the Windows NT ARC loader's environment variables tell it to find it. (Hint - it's faster if you point it at a harddisk). The kernel is generally called/vmlinuz is a gzip-compressed Alpha ELF binary. (Or is it COFF?)
Another example, Solaris on a SPARC box might boot like this:
- The EEPROM stores the identity of the boot partition
- The PROM loader goes looking for the boot blocks (installboot (1M)) on that partition, and executes the code it finds there
- The software just executed understands the Unix Filesystem (UFS), goes looking for the kernel where it belongs (set by the installer, I forget where it's written down). Traditionally, it was/vmunix, now it's somewhere else.
- The kernel looks in/etc/path_to_inst to figure out what device drivers to load, and loads them.
Solaris on an x86 box boots pretty much like windows.
- The BIOS goes looking for the first "active" partition, as marked by the disk partitioning utility. Generally on the first IDE controller's master disk.
- The BIOS executes the code in the master boot record (MBR), which somehow winds up loading the boot blocks. - The software just executed understands the Unix Filesystem (UFS), goes looking for the kernel where it belongs (set by the installer, I forget where it's written down). Traditionally, it was/vmunix, now it's somewhere else.
- The kernel looks in/etc/path_to_inst to figure out what device drivers to load, and loads them.
> How does it interact with hardware?
Same as any other operating system; through the PCI/ISA/etc bus and the API implemented by the hardware.
> Is there a general hint to what all the directories are > about or any memory aids for knowing what's in them?
Keep in mind, UNIX is not Windows. Generally speaking, you can put anything anywhere you want, as long as you change everything which cares about it. Which is usually possible!
Keep in mind also, that nothing is absolute./etc - misc OS crap that doesn't have a defined place. Generally config files/etc/inet - Like etc, but for networking stuff in SYSV. Generally linked to same-named files in/etc to be compatible with BSD./var - Theoretically, for VARs. Nothing much officially lives here, except log files (/var/log,/var/adm on Solaris). Oh, and also spools (/var/spool/mail,/var/spool/lp, etc. Lp stands for "line printer")/opt - OEM or Third party packages on SYSV boxes, esp Solaris./usr - Apps and stuff that came with the OS/usr/bin - Binaries for anybody to run (executable prorgrams) that should be available all the time./bin - Like/usr/bin, but more OS-centric/important/sbin - Like/usr/sbin, " " "/"/usr/sbin - Binaries for super users/usr/local - Addons which are local to that box/usr/local/bin, sbin, etc -- Local to that box, but have/bin,/sbin,/etc functionality
> Permissions - any chance of an overview of what the bits mean,
Permissions are most useful to examine as four-digit octal numbers. Assign each octal digit as such: SOGW
S - Special stuff, like sticky bits. Almost always 0 O - Permissions for the file owne
You also need to factor in the cost of replacing the disks in the U5s. Commodity PC disks will do.
Those piece of crap Conners (rebadged as Seagates) that they shipped with have a high failure rate when used heavily. Not to mention that they are dog slow.
I use U5s in my lab, they're cheap and binary-compatible with my production platforms. Their slowness is useful in finding bottlenecks early, however I still need to test on other platforms to identify multi-CPU issues.
Your point w.r.t. wire gauge is absolutely correct. Can you imaging the PITA factor of trying to wire a socket for, say, 4 awg solid copper wire? That's 1/4" of solid copper -- basically, brazing wire! It'd be damned near impossible to fish, as well, as it wouldn't go around corners without SIGNIFICANT force.
I haven't actually RTFA, but most telco DCs I'm aware of work on 48VDC IIRC.
Please, tell us about these "helper apps" and "commit charge".
I am a dyed-in-the-wool Sun guy who just got his first XP tablet/laptop last night (I use '98 on my desktop... hey, at least it's the devil I know). It has a half a gig of RAM, and swaps constantly, even after turning off all the eye candy. It's worse than Solaris 9!!!
Oh, yes, the only application I'm running is "Windows Explorer". Whoo!
This XP "experience" has been wonderful. When I first got it, "fresh" from the factory, it even had a virus! And the XP installer had yet to run! (No, I don't have a WiFi AP, No, I didn't even plug it into the 'net yet).
Needless to say, I Knoppix-nuked the disc and did the factory restore instead of trying to clean it..
All you have to do is use Win'95 to diskcopy a: a: from a good windows install disk to a blank. It's now 1.7mb formatted. Then erase all the files (deltree/y *.*), and copy the recovered files from your bad disk to the new good one. Hopefully the files that were affected are not critical to the install.
> Which, if you did your job right, would be the bottom > of the loop, so it would break out the instant the > termination condition becomes true.
Ever noticed that most people writing absolute statements on Slashdot tend to be those with little relevant experience?
Endless loops are a legitimate construct, and can be very beneficial when used correctly!
They are especially useful for job schedulers, event managers, etc., although I suspect at least one popular scheduler has been written in the form of do..while(screen_not_blue);
for(;;) {
do_work();
if (poll_event_one())
break;
do_more_work();
if (poll_event_two())
break;
do_even_more_work();
if (poll_event_three())
break;
cleanup(); }
Please rewrite this code to put all three terminal conditions at the bottom of the loop, without changing the semantics of the program. Then evaluate which version of the program is easier to read.
I won first place in the district science with an experient that FAILED. Yes, it didn't work!
But I did good science, explained WHY it failed, and postulated appropriate requirements for success.
It was also possible in my chemistry and physics classes to achieve a near-perfect score for an experiment that didn't work. You would only lose marks on the do-it-right part of the evaluation, so long as your write up was good and you explained your errors.
Widescreen format may seem like it's aimed at windows users, but it's really a boon for us nerds, too!
I spend a lot of my day wishing I had a wider display, about another 4", for those stupidly-wide Oracle SQL*Plus queries, other-people's code which uses insane tab widths for indenting (I use two spaces), and so forth.
Really, I rarely want a widescreen when in GUI land, but wish for one daily as I live in Terminal Land.
At first, I thought that system was insane. Now I see that it is the ideal!
In my home town, there are *two* Main Streets. Neither is very long, and certainly not very main (all residential).
They are about 8 miles apart, with a river in between. When somebody says they live on Main St., the only way to know *which* Main St., is if the house number is above or below 200.
If it makes you feel any better, I recall paying $1600 for Samsung 16MB fast page mode DRAM SIMMs at one point in time. I think I bought them for a Pentium-90 system.
So, is it likely that I would go deaf from a sonar ping nearby? Or even blue whale moans?
Or does "nearby" change dramatically in water due to transmission effects?
The chart you provided makes it look like scuba diving is incredibly dangerous to your hearing, even if you don't get a pressure tear in your timpanii.
Of course, it's not, so I must be missing something. The chart you provided pretty much affirms that!
Slashdot Mirror
Nope, but keep in mind that the m64 chip on those puppies is kinda broken. It doesn't work properly at anything other than 8 or 24-bit -- and it doesn't have enough ram to be useful at 24-bit.
IIRC trying to run at 16 bits produces a black screen with dark blue writing, at least in Solaris.
If you can fiddle the debian loader like you can with knoppix (closest thing to Debian I use), try 1152x900 with 8-bit colour. Oh, and select a reasonable refresh rate...
> How does **nix boot?
/vmlinuz is a gzip-compressed Alpha ELF binary. (Or is it COFF?)
/vmunix, now it's somewhere else. /etc/path_to_inst to figure out what device drivers to load, and loads them.
/vmunix, now it's somewhere else. /etc/path_to_inst to figure out what device drivers to load, and loads them.
/etc - misc OS crap that doesn't have a defined place. Generally config files /etc/inet - Like etc, but for networking stuff in SYSV. Generally linked to same-named files in /etc to be compatible with BSD. /var - Theoretically, for VARs. Nothing much officially lives here, except log files (/var/log, /var/adm on Solaris). Oh, and also spools (/var/spool/mail, /var/spool/lp, etc. Lp stands for "line printer") /opt - OEM or Third party packages on SYSV boxes, esp Solaris. /usr - Apps and stuff that came with the OS /usr/bin - Binaries for anybody to run (executable prorgrams) that should be available all the time. /bin - Like /usr/bin, but more OS-centric/important /sbin - Like /usr/sbin, " " "/" /usr/sbin - Binaries for super users /usr/local - Addons which are local to that box /usr/local/bin, sbin, etc -- Local to that box, but have /bin, /sbin, /etc functionality
The hardware runs a program. That program loads the kernel and executes it. Any more specific, and you're now talking platform-specifics which don't have to with UNIX.
For example, Linux on a DEC Alpha might boot like this:
- Windows NT ARC loader configured to spawn program MILO.EXE on FAT-formatted disk in Drive A:
- MILO.EXE understands Linux ext2fs, and launches the kernel wherever the Windows NT ARC loader's environment variables tell it to find it. (Hint - it's faster if you point it at a harddisk). The kernel is generally called
Another example, Solaris on a SPARC box might boot like this:
- The EEPROM stores the identity of the boot partition
- The PROM loader goes looking for the boot blocks (installboot (1M)) on that partition, and executes the code it finds there
- The software just executed understands the Unix Filesystem (UFS), goes looking for the kernel where it belongs (set by the installer, I forget where it's written down). Traditionally, it was
- The kernel looks in
Solaris on an x86 box boots pretty much like windows.
- The BIOS goes looking for the first "active" partition, as marked by the disk partitioning utility. Generally on the first IDE controller's master disk.
- The BIOS executes the code in the master boot record (MBR), which somehow winds up loading the boot blocks.
- The software just executed understands the Unix Filesystem (UFS), goes looking for the kernel where it belongs (set by the installer, I forget where it's written down). Traditionally, it was
- The kernel looks in
> How does it interact with hardware?
Same as any other operating system; through the PCI/ISA/etc bus and the API implemented by the hardware.
> Is there a general hint to what all the directories are
> about or any memory aids for knowing what's in them?
Keep in mind, UNIX is not Windows. Generally speaking, you can put anything anywhere you want, as long as you change everything which cares about it. Which is usually possible!
Keep in mind also, that nothing is absolute.
> Permissions - any chance of an overview of what the bits mean,
Permissions are most useful to examine as four-digit octal numbers. Assign each octal digit as such: SOGW
S - Special stuff, like sticky bits. Almost always 0
O - Permissions for the file owne
Interesting. Tell us more about this "Mac" processor.
Crap, looks like we'll have to rename the GNU Assembler (gas).
The epidemic (pandemic, actually) you're postulating may very well have been the Bubonic Plague (Black Death).
v iew.htmlt m
http://www.pbs.org/wnet/secrets/case_plague/inter
http://www.science-frontiers.com/sf119/sf119p05.h
You also need to factor in the cost of replacing the disks in the U5s. Commodity PC disks will do.
Those piece of crap Conners (rebadged as Seagates) that they shipped with have a high failure rate when used heavily. Not to mention that they are dog slow.
I use U5s in my lab, they're cheap and binary-compatible with my production platforms. Their slowness is useful in finding bottlenecks early, however I still need to test on other platforms to identify multi-CPU issues.
Hmm, RIM should buy Texas Instruments, then George's "PDA" woudl be a Blackberry too!
(Hey, if it's good enough for ET, it's good enough for GB!)
Your point w.r.t. wire gauge is absolutely correct. Can you imaging the PITA factor of trying to wire a socket for, say, 4 awg solid copper wire? That's 1/4" of solid copper -- basically, brazing wire! It'd be damned near impossible to fish, as well, as it wouldn't go around corners without SIGNIFICANT force.
I haven't actually RTFA, but most telco DCs I'm aware of work on 48VDC IIRC.
Please, tell us about these "helper apps" and "commit charge".
I am a dyed-in-the-wool Sun guy who just got his first XP tablet/laptop last night (I use '98 on my desktop... hey, at least it's the devil I know). It has a half a gig of RAM, and swaps constantly, even after turning off all the eye candy. It's worse than Solaris 9!!!
Oh, yes, the only application I'm running is "Windows Explorer". Whoo!
This XP "experience" has been wonderful. When I first got it, "fresh" from the factory, it even had a virus! And the XP installer had yet to run! (No, I don't have a WiFi AP, No, I didn't even plug it into the 'net yet).
Needless to say, I Knoppix-nuked the disc and did the factory restore instead of trying to clean it..
> WONDERFULL, where were you TEN FREAKING YEARS AGO!!!!!!!
:)
Working in a shitty little computer store and wishing more people would buy CD-ROM drives.
Um, not to put too fine a point on it dude, but the colours on the Apple II -- and vi suck way more than either the C64 or EMACS.
All you have to do is use Win'95 to diskcopy a: a: from a good windows install disk to a blank. It's now 1.7mb formatted. Then erase all the files (deltree /y *.*), and copy the recovered files from your bad disk to the new good one. Hopefully the files that were affected are not critical to the install.
I've been thinking about quitting, but I think now I'll just wait for these safe cigarettes.
As long as they're full of nicotine and taste like shit, I'm sure they'll work out fine!
> I figured that if I CAPTIALIZED some of my WORDS, people might get a CLUE.
Actually, it makes you look like Zippy the Pinhead.
Other than that, I agree with the content of your post.
> of the loop, so it would break out the instant the
> termination condition becomes true.
Ever noticed that most people writing absolute statements on Slashdot tend to be those with little relevant experience?
Endless loops are a legitimate construct, and can be very beneficial when used correctly!
They are especially useful for job schedulers, event managers, etc., although I suspect at least one popular scheduler has been written in the form of do..while(screen_not_blue);Please rewrite this code to put all three terminal conditions at the bottom of the loop, without changing the semantics of the program. Then evaluate which version of the program is easier to read.
Your school system must be different from mine!
I won first place in the district science with an experient that FAILED. Yes, it didn't work!
But I did good science, explained WHY it failed, and postulated appropriate requirements for success.
It was also possible in my chemistry and physics classes to achieve a near-perfect score for an experiment that didn't work. You would only lose marks on the do-it-right part of the evaluation, so long as your write up was good and you explained your errors.
Try looking under Nancy Reagan's shirt.
Have I fallen into some kind of alternate universe?
If so, is it the one where Spock has a goatee, or do I get treated to Nana Visitor in tight leather pants?
If this happened to them, I'd be PISSED, and I'd be shouting from the tallest soapbox I could find.
Your idea is excellent, and suitably inflammatory to those in the wrong -- but clearly falls within the directives provided by the church.
As for Blog names, I think I'd prefer "Station One", or better yet:
Widescreen format may seem like it's aimed at windows users, but it's really a boon for us nerds, too!
I spend a lot of my day wishing I had a wider display, about another 4", for those stupidly-wide Oracle SQL*Plus queries, other-people's code which uses insane tab widths for indenting (I use two spaces), and so forth.
Really, I rarely want a widescreen when in GUI land, but wish for one daily as I live in Terminal Land.
Thanks for the clarification.
At first, I thought that system was insane. Now I see that it is the ideal!
In my home town, there are *two* Main Streets. Neither is very long, and certainly not very main (all residential).
They are about 8 miles apart, with a river in between. When somebody says they live on Main St., the only way to know *which* Main St., is if the house number is above or below 200.
Now THAT's insane.
What the hell?
Does the City of Lindon, UT have some kind of freaky Euclidean or Cartesian layout plan?
That at least would make it easy to calculate absolute distances between addresses. Especially if you memorized all the easy Pythagorean triangles.
Wes
You're thinking of Multics, which predates Unix.
If it makes you feel any better, I recall paying $1600 for Samsung 16MB fast page mode DRAM SIMMs at one point in time. I think I bought them for a Pentium-90 system.
Interesting.
So, is it likely that I would go deaf from a sonar ping nearby? Or even blue whale moans?
Or does "nearby" change dramatically in water due to transmission effects?
The chart you provided makes it look like scuba diving is incredibly dangerous to your hearing, even if you don't get a pressure tear in your timpanii.
Of course, it's not, so I must be missing something. The chart you provided pretty much affirms that!
Thanks.