Linksys says I need a Windows machine to update my firmware

And iPod in CAPITALS would be IpOD? Not.

Was it in this group where someone told us about a work collegue who insisted that that not only should his name be written in all lower case letters, but that it should always be in a specific font?

Also, it seems to me that JR should have written:

Abbreviation (noun) - a shortened form of a word or phrase

Ian

Nobody is saying that there is any problem from any OS with upgrading the firmware on this boxes if the existing firmware allows for upgrading via a web browser.

However, on older (maybe much older) versions of these, linksys did not provide a mechanism for uploading firmware using a web browser. For those versions, linksys provided a Windows executable which basically unzipped the archive containing the firmware and did an upload via TFTP.

The problem, if I recall correctly, with doing this manually from Unix systems was that the tftp clients on Unix doesn't handle passwords in the expected way. So the work around was to use the web interface to remove the password from the linksys box and then use the Terminal tftp client.

For all of the linksys boxes that allow firmware upgrade via a web form, there is no problem. Those are, as you say, OS independent.

-j

On any recent version of Linksys firmware it is only necessary to download a single .bin, login to the router, choose administration, choose firmware upgrade. Browse for the file then click on 'update'.

Tftp,0.exe is also available from the Linksys site, though it's not necessary.

You are, of course, correct. : )

:^)

JD wrote in news:f706l0$6on$ snipped-for-privacy@aioe.org:

I said that in the part of my post that you conveniently snipped.

On 09 Jul 2007, "Bob F." posted some news:OKidnTjbE6nR-w_bnZ2dnUVZ snipped-for-privacy@comcast.com:

I have yet to see a eunuchs computing environment that is superior to VMS all things being equal.

I knew I was in for an uphill battle when I interviewed with the internal Ultrix group at DEC's Lytton labs in Palo Alto. I'd been a VMS systems programmer for over 8 years and the guy that interviewed me had a comic strip of Calvin (of Calvin and Hobbes) wacking a pizza with a huge mallet. The initials "VMS" were scribbled across the face of the pizza.

No, I didn't get the job. And it's funny (at least to us DECies and old VMS system types) to see SUN touting "clustering". OMG, it's 1985 all over again.

And my favorite was the VMS developer's canned response to all Software Performance Reports (SPRs):

From: 24766::XYZZY "DTN 521-xxxx 09-Oct-1990 0211" 9-OCT-1990

11:15:00.04 To: WINERY::VILAIN CC: Subj: See Figure 1

From: VAXWRK::XYZZY "It's all in the script..." 21-OCT-1986

14:13:30.14 To: PLUGH CC: Subj: all the answers you'll ever need

From: REGENT::PLUGH "MICHAEL PLUGH MLO3-6/B16 223-2230 08-Sep-1986

1606" 8-SEP-1986 16:06 To: DAVE Subj: see figure 1

VMS Version 3

Please stop submitting SPR's. This is our system. We designed it, we built it, and we use it more than you do. If there are some features you think might be missing, if the system isn't as effective as you think it could be, TOUGH! Give it back, we don't need you. See figure 1.

Forget about your silly problem, let's take a look at some of the features of the VMS operating system.

1) Options. We've got lots of them. So many in fact, that you need two strong people to carry the documentation around. So many that it will be a cold day in hell before half of them are used. So many that you are probably not going to do your work right anyway. However, the number of options isn't all that important, because we picked some interesting values for the options and called them ...

2) Defaults. We put a lot of thought into our defaults. We like them. If we didn't, we would have made something else be the default. So keep your cotton-picking hands off our defaults. Don't touch. Consider them mandatory. "Mandatory defaults" has a nice ring to it. Change them and your system crashes, tough. See figure 1.

3) Language Processors. They work just fine. They take in source, and often produce object files as a reward for your efforts. You don't like the code? Too bad! You can even try to call operating system services from them. For any that you can't, use the assembler like we do. We spoke to the language processor developers about this, they think a lot like we do, they said "See figure 1".

4) Debuggers. We've got debuggers, one we support and one we use. You shouldn't make mistakes anyway, it is a waste of time. We don't want to hear anything about debuggers, we're not interested, See figure 1.

5) Error Logging. Ignore it. Why give yourself an ulcer? You don't want to give us the machine to get the problem fixed and we probably can't do it anyway. Oh, and if something breaks between 17:00 and 18:00 or 9:30 and 10:30 or 11:30 and 13:30 or 14:30 and 15:30 don't waste your time calling us, we're out. See figure 1.

6) Command Language. We designed it ourselves, it's perfect. We like it so much we put our name on it, DCL- Digital's Command Language. In fact we're so happy with it, we designed it once for each of our operating systems. We even try to keep it the same from release to release, sometimes we blow it though, See figure 1.

7) Real Time Performance. We got it. Who else could have done such a good job? So the system seems sluggish with all those priority 18 processes, no problem, just make them priority 1. Anyway, realtime isn't important anymore like it used to be. We changed our groups name to get rid of the word realtime, we told all our realtime users to see figure 1 a long time ago.

In conclusion, stuff your SPR. Love VMS or leave it, but don't complain.

--adapted from TOPS-20

In comp.dcom.lans.ethernet Fujikawa Yamamoto wrote in part:

Surely you see this preference is dependant on your personal values. Just like some people prefer MS-Windows.

-- Robert