I'm assuming you'd let the engineers out of the office when the fire alarm was going off, otherwise you'd probably be looking at quite a jail term.
Every facility I have worked at with card readers on doors have crash bars and a door alarm, so that if you exit without swiping your card the alarm goes off. If there is a fire, nobody really cares about a door alarm.
The word processor and destop publisher in GEOS (they may have been the same program) were surprisingly functional and WYSIWIG. I did most of my HS papers with that system on my C64.
I.e. it might be fun to play with, but it's not very useful for the average Joe.
Well, Linux started out as something barely usable even to hardcore geeks (kermit was the most complex application for a good while), and look what it turned into.
Cormen, Leisserson, and Rivest's book was commonly known as the Big White Book of Pain at my university. Hopcraft and Ullman was known as the Little White Book of Pain.
What do you people do that get 100's of spam letters a day?
I have had my permanent email address since 1993 or so. Changing it would be a very big hassle, but it was snagged by the early bots and I now get a ton of spam.
Occasional fringe wacko? You must have not read alt.buddha.short.fat.guy:) Most of the comp and rec groups were pretty good, though.
I found my copy of the STANDARDIZED BONEHEAD REPLY FORM the other day in my archvies. I don't know where to be begin to modify it to apply to Usenet today...
Bit rate is the number of bits transmitted per second (duh). Baud rate is the number of symbols transmitted per second (also called the symbol rate).
When one bit is transmitted per symbol (ie, BPSK), then the bitrate is the same as the baudrate. When two or more bits are transmitted per symbol (ie, QPSK, QAM, etc), then the baudrate is slower than the bitrate.
All of the digicomm engineers I have worked with avoid the term baudrate, and use symbol rate instead, to avoice confusion.
The Bell 103 modems (110 and 300 baud modems) used FSK, where two tones are used (one for 0 and one for 1), so the baudrate was the same as the bitrate.
The primary limitation is the maximum weight we can get to the Earth/Moon Lagrange points. Once at the L-points, the cargo pretty much travels one gravity slingshot to the next with nearly no fuel expenditure.
If anyone is interested, I believe this is also known as a soft orbit transfer. IIRC, this technique was inveneted to rescue a mission that had suffered a pretty catastrophic failure.
I have never used it on a Unix system before, but I have done lots of work with it under VM/CMS on a 370 mainframe.
It is a somewhat whacky language, or at least using it to do tasks for VM/CMS is a bit whacky, probably because VM/CMS is a bit whacky. Mainly we used it to to add additional functionality to the built in commands, and to make them easier to use (VM/CMS commands make unix commands seem intuitive).
My fondest memory is having to write REXX using the XEDIT editor on a 3178 or 3179 terminal. Talk about fun. I can still hear the distinctive sound that those IBM keyboards made...
The reason to stick with an existing eight bit device is that it is a known entity. Depending on the application, a designed may chose a part with a proven track record over a new one.
For example, Motorola sold boatloads of their 68k based single board computers even when the PPC ones were available. Some of the sales were for existing products, but a lot were due to the fact that the 68k SBCs just plain old worked well.
FAQs have existed for a long time before the web (eg, the FAQs for the various newsgroups), and they worked well before becoming fancy.
The comp.lang.c FAQ is probably the best example. It is rather big, and has always been so as long as I can remember. It is also pretty usable, even when it is viewed as a single flat document. You just need something to search it, whether it is more, emacs, or a browser.
Having Linux or any other OS (or even CPU type functions) on the FPGA would be a waste of gates. The gates would be better spent for specialized vector operations, such as an FFT or crypto engine.
As others have mentioned, memory parts are alomst always described in terms of bits, and always have been. I believe there are a few reasons for this.
Not all computers use (or used) eight bit bytes. The PDP-10 (?) and a few IBM machines used nine bit bytes organized as 36 byte words. I also think there were a few machines with sub-eight bit bytes, but I can't think of any right now.
I seem to recall memory some memory parts being available with data bus widths other than eight. Caffine hasn't kicked in, though, or I would be more sure about this.
Also, because of error detecting and/or correcting memories (eg, parity, ECC, etc), the physical memory width may we wider that the logical width.
Take a look at some embedded electronics (such as cPCI boards) if you get a chance. A lot of these will literally use all available PWB real-estate, front and back) for components and also sometimes have to resort to daughterboards for more space (especially for memory).
PC motherboards typically have 4 - 6 layers. That's pretty complicated.
I guess I should have given a point of reference. I have worked on designs requiring 12-16 layers, even after conceding to use blind and buried vias and running the router for very long time (ie, days). That is pretty complicated.
PC motheboards aren't terribly complicated as far as PWBs go. The don't really have a lot of components, and they don't have a lot of layers.
What is interesting about them, but I don't think it really complicates the manufacturing proces, is the effort that goes into reducing the number of layers (number of layers is directly related to cost). This compilcates both routing and signal integrity.
I have had the original 4.4 version in my Amazon wish list for about four years now hoping that one of my relatives would buy it for me as a present. But alas, nobody did. An updated version may be enough inspiration for me to buy it myself.
Tannenbaum's book, as well as the Dinosaur Book are pretty standard in undergrad operating systems classes.
Personally, I never install X during the initial install. Typically, I install everything but X, then cvsup the src and ports trees, and then build world. I then install X from the ports tree.
Slashdot Mirror
I'm assuming you'd let the engineers out of the office when the fire alarm was going off, otherwise you'd probably be looking at quite a jail term.
Every facility I have worked at with card readers on doors have crash bars and a door alarm, so that if you exit without swiping your card the alarm goes off. If there is a fire, nobody really cares about a door alarm.
The word processor and destop publisher in GEOS (they may have been the same program) were surprisingly functional and WYSIWIG. I did most of my HS papers with that system on my C64.
I.e. it might be fun to play with, but it's not very useful for the average Joe.
Well, Linux started out as something barely usable even to hardcore geeks (kermit was the most complex application for a good while), and look what it turned into.
Cormen, Leisserson, and Rivest's book was commonly known as the Big White Book of Pain at my university. Hopcraft and Ullman was known as the Little White Book of Pain.
What do you people do that get 100's of spam letters a day?
I have had my permanent email address since 1993 or so. Changing it would be a very big hassle, but it was snagged by the early bots and I now get a ton of spam.
Occasional fringe wacko? You must have not read alt.buddha.short.fat.guy :) Most of the comp and rec groups were pretty good, though.
I found my copy of the STANDARDIZED BONEHEAD REPLY FORM the other day in my archvies. I don't know where to be begin to modify it to apply to Usenet today...
Bit rate is the number of bits transmitted per second (duh). Baud rate is the number of symbols transmitted per second (also called the symbol rate).
When one bit is transmitted per symbol (ie, BPSK), then the bitrate is the same as the baudrate. When two or more bits are transmitted per symbol (ie, QPSK, QAM, etc), then the baudrate is slower than the bitrate.
All of the digicomm engineers I have worked with avoid the term baudrate, and use symbol rate instead, to avoice confusion.
The Bell 103 modems (110 and 300 baud modems) used FSK, where two tones are used (one for 0 and one for 1), so the baudrate was the same as the bitrate.
The primary limitation is the maximum weight we can get to the Earth/Moon Lagrange points. Once at the L-points, the cargo pretty much travels one gravity slingshot to the next with nearly no fuel expenditure.
If anyone is interested, I believe this is also known as a soft orbit transfer. IIRC, this technique was inveneted to rescue a mission that had suffered a pretty catastrophic failure.
I read the same story here earlier today, and it also says that it was installed backwards.
I have never used it on a Unix system before, but I have done lots of work with it under VM/CMS on a 370 mainframe.
It is a somewhat whacky language, or at least using it to do tasks for VM/CMS is a bit whacky, probably because VM/CMS is a bit whacky. Mainly we used it to to add additional functionality to the built in commands, and to make them easier to use (VM/CMS commands make unix commands seem intuitive).
My fondest memory is having to write REXX using the XEDIT editor on a 3178 or 3179 terminal. Talk about fun. I can still hear the distinctive sound that those IBM keyboards made...
The reason to stick with an existing eight bit device is that it is a known entity. Depending on the application, a designed may chose a part with a proven track record over a new one.
For example, Motorola sold boatloads of their 68k based single board computers even when the PPC ones were available. Some of the sales were for existing products, but a lot were due to the fact that the 68k SBCs just plain old worked well.
FAQs have existed for a long time before the web (eg, the FAQs for the various newsgroups), and they worked well before becoming fancy.
The comp.lang.c FAQ is probably the best example. It is rather big, and has always been so as long as I can remember. It is also pretty usable, even when it is viewed as a single flat document. You just need something to search it, whether it is more, emacs, or a browser.
Having Linux or any other OS (or even CPU type functions) on the FPGA would be a waste of gates. The gates would be better spent for specialized vector operations, such as an FFT or crypto engine.
Has anyone else noticed that the three major BSD variants are all going to have major releases within about two weeks of each other?
FreeBSD 5.3 is scheduled for a Oct 17 release. NetBSD 2.0 is scheduled for a mid-October release. OpenBSD 3.6 is scheduled for a Nov 1 release.
Hmmm?
I believe that is Elvis Masterminds All Computer Science
As others have mentioned, memory parts are alomst always described in terms of bits, and always have been. I believe there are a few reasons for this.
Not all computers use (or used) eight bit bytes. The PDP-10 (?) and a few IBM machines used nine bit bytes organized as 36 byte words. I also think there were a few machines with sub-eight bit bytes, but I can't think of any right now.
I seem to recall memory some memory parts being available with data bus widths other than eight. Caffine hasn't kicked in, though, or I would be more sure about this.
Also, because of error detecting and/or correcting memories (eg, parity, ECC, etc), the physical memory width may we wider that the logical width.
It is also interesting how many digital problems turn out to be analog in nature: termination, noise, signal coupling, power, etc.
Will we still need telephone sanitizers in thirty years?
Take a look at some embedded electronics (such as cPCI boards) if you get a chance. A lot of these will literally use all available PWB real-estate, front and back) for components and also sometimes have to resort to daughterboards for more space (especially for memory).
PC motherboards typically have 4 - 6 layers. That's pretty complicated.
I guess I should have given a point of reference. I have worked on designs requiring 12-16 layers, even after conceding to use blind and buried vias and running the router for very long time (ie, days). That is pretty complicated.
PC motheboards aren't terribly complicated as far as PWBs go. The don't really have a lot of components, and they don't have a lot of layers.
What is interesting about them, but I don't think it really complicates the manufacturing proces, is the effort that goes into reducing the number of layers (number of layers is directly related to cost). This compilcates both routing and signal integrity.
I have had the original 4.4 version in my Amazon wish list for about four years now hoping that one of my relatives would buy it for me as a present. But alas, nobody did. An updated version may be enough inspiration for me to buy it myself.
Tannenbaum's book, as well as the Dinosaur Book are pretty standard in undergrad operating systems classes.
Personally, I never install X during the initial install. Typically, I install everything but X, then cvsup the src and ports trees, and then build world. I then install X from the ports tree.
No, the last thing we need are flying taxis.
Taxi drivers violate enough traffic laws already. Can you imagine what they will do given the ability to fly?
Kinda like one of these?