either that or GM gets bought out by Toyota of America 20 years from now, actualy Toyota probably too smart for that.
Why on earth would Toyota want to buy GM? The latest issue of Fortune (July 25,2005) has an article on how GM is trying to reduce costs by cutting health benefits for retirees. GM spends more each year on health insurance for people who *used to* work there than the people who are actively employed.
I don't think Toyota wants to get anywhere near that mess.
I think the Camry is already the most popular car (by volume of units sold). As soon as more people get over the "I ain't buyin no Jap car!" attitude and realize that "foreign" cars are actually built in the U.S., Toyota and Honda will crush GM, Ford and D-C.
My Solara was built here in the good ole US of A (Kentucky).
"Upstream slots: Unlike an ethernet card, a cable modem is not allowed to transmit on demand. A single upstream channel frequency has to be shared by hundreds of cable modems that cannot hear each other's transmissions. If more than one cable modem transmitted at once, the UBR would not be able to understand either of them. So all cable modems must remain silent until they are allocated a time slot (measured with a precision of microseconds) by the UBR. The time-slot allocations are broadcast by the UBR on the downstream as MAP packets, so called because they map time slots to individual cable modems. So a typical sequence might be:"
Re:Of course it isn't dead!
on
DECnet Isn't Dead
·
· Score: 2, Informative
And with "proxy" access defined on the remote node, you didn't even have to supply a username and password (to access a file on a remote system). The remote system would recognize the DECnet node you were coming from and your account, and then grant you access.
I don't know if you were being serious or not but we went through a rough period with an ES40 that was nearly full of RAM which would crash about once a week.
Finally, Field Service came in to replace add of the DIMMs from a certain date range and magically the system became rock solid.
Before we found out about the bad memory, we had Field Service swap the motherboard as well as swapping out the four CPUs in that system.
Like I said, once we changed-out the RAM, that system became rock-solid. I later filled the ES40 to its full capacity memory-wise (32 Gigs). Man, that box was sweet with about 20 Gigs of RAM reserved for the XFC.:^)
Because engineering (both h/w & s/w) and the tech support lines, and time and number of people it takes to write a Big {Blue|Red|Grey} Wall of 3-ring binder documentation, and the Field Circus all cost a lot of money that most people aren't willing to pay anymore..
True dat...
When you worked with a VAX 6000 or "DEC 7000" (the correct name for that line of Alpha-based systems), you got the feeling that you were working on something "solid". Those systems were made of steel and didn't feel like they would blow away in a strong wind. Just the CPU and memory cards for the DEC 7000 (anyone remember 'Laserbus'?) were big, heavy monsters.
Ahhh, yes, VMS on Alpha attached to Fibre Channel storage. You haven't seen an OS beat a disk array into submission until you've connected VMS 7.3-1 to some fibre channel storage and "tuned" things in SYSGEN.
We had an ES40 that could generate enough I/O that it would cause HSG80s to crash and/or lockup. Search through comp.os.vms and you'll find the write-up that I did on that topic.
As long as we are talking about VMS and storage, show me another OS that comes with built-in support for multi-path connections for storage. You put two HBAs (going to two different f.c. switches) in an Alpha and you've got four paths now to your disk unit. (This stuff was a left-over from the days of CI-based storage).
DECnet is often used these days for very mission critical applications.
Are you confusing DECnet and VMSclusters? They are two different animals.
You mention that your shop still DECnet extensively. Aren't you running into issues where your networking folks don't know what to do with DECnet, your routers don't recognize it as a routable protocol and you still need TCP/IP in order to be able to move files with ftp or send email?
Yeah, DECnet was nice, but it ain't "all that and a bag of chips".
The DECNET clustering software was also way ahead of its time. With clustering you could administer a hundred machines as if they were a single unit.
As someone who has spent years administering VMSclusters, your comment above made me stop and read twice.
VMSclusters and DECnet are two separate things. When you talk about managing many machines as if they were one, are you talking about using SYSMAN? Cluster communications was over SCS, not DECnet. You could have a VMScluster without using DECnet. Believe me, I spent enough hours in SDA looking at the various protocols bound to each network interface ("Let's see, SCS is here on the FDDI interface but LAT is over there on the 10mbit Ethernet interface.")
Pathworks went through a period where it was so buggy that I started calling it "Patchworks". A VAX runnig Pathworks was no match (performancewise) with the Novell file servers that were starting to become popular in the early 90s.
Yeah, it was cool to be able to copy your PC files to your home directory on your VMS system and vice versa, but Pathworks was more of a hindrance than a help.
Along the lines of your "old hardware is hard to find" story: I had heard through a reliable source that right after 9/11/2001, Compaq had to scramble to come up with enough memory boards and CPU boards to replace the VAX 7800s that were destroyed in NY city. Compaq went to the used equipment dealers to "buy back" boards to get customers running again.
That was probably the last big spike in demand for VAX CPU or memory cards.
TGV was acquired by Cisco (I still have the t-shirt with the Cisco logo and the Multinet jaguar that says "Assimilation Complete").
Later, Multinet ended-up in the capable hands of Process Software (makers of TCPware).
I've used UCX, TCPware and Multinet in a number of different production environments. Give me Multinet over sUCX any day. (TCPware is a close second to Multinet).
Sadly, most of the Slashdot crowd is too young to be able to tell whether I am telling the truth or if I just threw a bunch of random words together. No mods points for me.:^)
As for DECnet Phase V, or "DECnet Plus", it was a sucky piece of software that was wayyyy too complex for what we (the customers) needed. I played with DECnet Pus for a while and then de-installed it to go back to Phase IV.
If I had a dime for every CSC call or DSNlink case that was caused by DECnet Plus, I'd be one rich dude.:^)
Conduit? Dude, have you touched a PIX in the last five years?
If you don't understand how a graphical interface can make rule generation, NAT configuration and other firewall admin issues quicker, then feel free to not comment.
ASDM is more than just a pretty way to enter a "conduit" command.
So you have your five 2003 servers in the "Trust" zone and the ninety XP workstation in the "Untrust" zone?
The 5GT is a decent little firewall. And if you shell out a little more $$$, you can get the "Extended" license to enable the third security zone: "DMZ".
The embedded Trend antivirus is a pretty nice feature (especially for smaller shops).
Yeah, but now that you're at version 7.0 of the firmware for the Private Internet eXchange, you finally have a usable GUI to administer the PIX (ASDM).:^)
PDM sucked.:^)
But even on 7.0, there are certain operations that can't be done via ASDM and must be done through the CLI. There is too much "hand-holding" in ASDM. I need to write Cisco and tell them to turn off the "safetys" that keep your from creating rules that ASDM thinks are not valid.
Really????
What version of PIX code are you referring to? I've never seen a PIX that would shut down "port" for a while (on it's own) and then re-open things after so many minutes.
I call bull-puckey.
-s
Back in the day, patches for Pathworks came out as quickly as you could install them. I took great pleasure in pronouncing the software's name as "Patchworks", especially when talking to people who worked for Digital.
Slashdot Mirror
either that or GM gets bought out by Toyota of America 20 years from now, actualy Toyota probably too smart for that.
Why on earth would Toyota want to buy GM? The latest issue of Fortune (July 25,2005) has an article on how GM is trying to reduce costs by cutting health benefits for retirees. GM spends more each year on health insurance for people who *used to* work there than the people who are actively employed.
I don't think Toyota wants to get anywhere near that mess.
I think the Camry is already the most popular car (by volume of units sold). As soon as more people get over the "I ain't buyin no Jap car!" attitude and realize that "foreign" cars are actually built in the U.S., Toyota and Honda will crush GM, Ford and D-C.
My Solara was built here in the good ole US of A (Kentucky).
A /. discussion on astrology and none of the mods bothered to donate a "+1, Funny" to a joke about "Uranus"?
:^)
C'mon! C'mon!!
So, if I change a star's position or destroy it, this might change my future?
I take it you've never seen "Star Trek Generations"?
That's pretty much the main plot in that movie: Blow up stars and planets in order to alter a person's future (Dr. Soran's future).
http://www.imdb.com/title/tt0111280/
No, bubblegum is okay. The G.P. is safe unless he showed them how to play "foosball". Because, as we all know:
:^)
"Foosball is the devil!!!"
Cable modem setups *are* asymmetric:
i ps/latency.html
"Upstream slots: Unlike an ethernet card, a cable modem is not allowed to transmit on demand. A single upstream channel frequency has to be shared by hundreds of cable modems that cannot hear each other's transmissions. If more than one cable modem transmitted at once, the UBR would not be able to understand either of them. So all cable modems must remain silent until they are allocated a time slot (measured with a precision of microseconds) by the UBR. The time-slot allocations are broadcast by the UBR on the downstream as MAP packets, so called because they map time slots to individual cable modems. So a typical sequence might be:"
You can read more at:
http://homepage.ntlworld.com/robin.d.h.walker/cmt
And with "proxy" access defined on the remote node, you didn't even have to supply a username and password (to access a file on a remote system). The remote system would recognize the DECnet node you were coming from and your account, and then grant you access.
I don't know if you were being serious or not but we went through a rough period with an ES40 that was nearly full of RAM which would crash about once a week.
:^)
Finally, Field Service came in to replace add of the DIMMs from a certain date range and magically the system became rock solid.
Before we found out about the bad memory, we had Field Service swap the motherboard as well as swapping out the four CPUs in that system.
Like I said, once we changed-out the RAM, that system became rock-solid. I later filled the ES40 to its full capacity memory-wise (32 Gigs). Man, that box was sweet with about 20 Gigs of RAM reserved for the XFC.
Because engineering (both h/w & s/w) and the tech support lines, and time and number of people it takes to write a Big {Blue|Red|Grey} Wall of 3-ring binder documentation, and the Field Circus all cost a lot of money that most people aren't willing to pay anymore..
:^)
True dat...
When you worked with a VAX 6000 or "DEC 7000" (the correct name for that line of Alpha-based systems), you got the feeling that you were working on something "solid". Those systems were made of steel and didn't feel like they would blow away in a strong wind. Just the CPU and memory cards for the DEC 7000 (anyone remember 'Laserbus'?) were big, heavy monsters.
Ahh, the good ole days.
I have a "Multia" in my basement. That's even smaller than the DS15. Would you count that as an Alpha? :^)
Ahhh, yes, VMS on Alpha attached to Fibre Channel storage. You haven't seen an OS beat a disk array into submission until you've connected VMS 7.3-1 to some fibre channel storage and "tuned" things in SYSGEN.
We had an ES40 that could generate enough I/O that it would cause HSG80s to crash and/or lockup. Search through comp.os.vms and you'll find the write-up that I did on that topic.
As long as we are talking about VMS and storage, show me another OS that comes with built-in support for multi-path connections for storage. You put two HBAs (going to two different f.c. switches) in an Alpha and you've got four paths now to your disk unit. (This stuff was a left-over from the days of CI-based storage).
DECnet is often used these days for very mission critical applications.
Are you confusing DECnet and VMSclusters? They are two different animals.
You mention that your shop still DECnet extensively. Aren't you running into issues where your networking folks don't know what to do with DECnet, your routers don't recognize it as a routable protocol and you still need TCP/IP in order to be able to move files with ftp or send email?
Yeah, DECnet was nice, but it ain't "all that and a bag of chips".
After you try to get the Pathworks drivers to work with WFW, then you can sit at the big table with the adults. :^) :^)
I remember editing files like the PROTOCOL.INI wayyyyy too much.
The DECNET clustering software was also way ahead of its time. With clustering you could administer a hundred machines as if they were a single unit.
As someone who has spent years administering VMSclusters, your comment above made me stop and read twice.
VMSclusters and DECnet are two separate things. When you talk about managing many machines as if they were one, are you talking about using SYSMAN? Cluster communications was over SCS, not DECnet. You could have a VMScluster without using DECnet. Believe me, I spent enough hours in SDA looking at the various protocols bound to each network interface ("Let's see, SCS is here on the FDDI interface but LAT is over there on the 10mbit Ethernet interface.")
Pathworks went through a period where it was so buggy that I started calling it "Patchworks". A VAX runnig Pathworks was no match (performancewise) with the Novell file servers that were starting to become popular in the early 90s.
Yeah, it was cool to be able to copy your PC files to your home directory on your VMS system and vice versa, but Pathworks was more of a hindrance than a help.
Along the lines of your "old hardware is hard to find" story: I had heard through a reliable source that right after 9/11/2001, Compaq had to scramble to come up with enough memory boards and CPU boards to replace the VAX 7800s that were destroyed in NY city. Compaq went to the used equipment dealers to "buy back" boards to get customers running again.
That was probably the last big spike in demand for VAX CPU or memory cards.
I am under 45 (37) and I know exactly what you're talking about.
:^)
The SIG tapes were famous for useful little utilities. I remember using stuff from Hunter Goatley from that era.
TGV was acquired by Cisco (I still have the t-shirt with the Cisco logo and the Multinet jaguar that says "Assimilation Complete").
:^)
:^)
Later, Multinet ended-up in the capable hands of Process Software (makers of TCPware).
I've used UCX, TCPware and Multinet in a number of different production environments. Give me Multinet over sUCX any day. (TCPware is a close second to Multinet).
Sadly, most of the Slashdot crowd is too young to be able to tell whether I am telling the truth or if I just threw a bunch of random words together. No mods points for me.
As for DECnet Phase V, or "DECnet Plus", it was a sucky piece of software that was wayyyy too complex for what we (the customers) needed. I played with DECnet Pus for a while and then de-installed it to go back to Phase IV.
If I had a dime for every CSC call or DSNlink case that was caused by DECnet Plus, I'd be one rich dude.
Hey, that's a great idea. Why not submit your question to Slashdot to see what others think?
0 5/09/039204&tid=152
Oh, wait, it's already been done:
http://developers.slashdot.org/article.pl?sid=04/
You, my friend, would definitely get mod points if I had them today. :^)
:^)
Never has a one-line post been more "insightful".
>conduit permit tcp host blah blah blah...
Conduit? Dude, have you touched a PIX in the last five years?
If you don't understand how a graphical interface can make rule generation, NAT configuration and other firewall admin issues quicker, then feel free to not comment.
ASDM is more than just a pretty way to enter a "conduit" command.
So you have your five 2003 servers in the "Trust" zone and the ninety XP workstation in the "Untrust" zone?
The 5GT is a decent little firewall. And if you shell out a little more $$$, you can get the "Extended" license to enable the third security zone: "DMZ".
The embedded Trend antivirus is a pretty nice feature (especially for smaller shops).
Yeah, but now that you're at version 7.0 of the firmware for the Private Internet eXchange, you finally have a usable GUI to administer the PIX (ASDM). :^)
:^)
PDM sucked.
But even on 7.0, there are certain operations that can't be done via ASDM and must be done through the CLI. There is too much "hand-holding" in ASDM. I need to write Cisco and tell them to turn off the "safetys" that keep your from creating rules that ASDM thinks are not valid.
Really???? What version of PIX code are you referring to? I've never seen a PIX that would shut down "port" for a while (on it's own) and then re-open things after so many minutes. I call bull-puckey. -s
a script in a database that seeked certain kind of information.
Seeked? Geez, did you make it past the fourth grade?
Maybe when you change the name of the software to indicate that's the case?
Or maybe the old boat anchor Patchworks, err I mean, Pathworks on VMS:
http://h71000.www7.hp.com/pathworks/
Back in the day, patches for Pathworks came out as quickly as you could install them. I took great pleasure in pronouncing the software's name as "Patchworks", especially when talking to people who worked for Digital.