Speaking of changing your password, I think I last logged in in 2007 and my password was still 1999 vintage until today. Oops. Disappointed the account was not cracked.

I understand not wanting to support Lenovo as a buisness entity, but to clarify, the Thinkpad line never had SuperFish installed.

The reason lots of us came to study engineering too.

You can't get a high score' from those tests. They are rigged so no matter what you answer, they always end up recomending you their audits and Dianetics courses. Those people are nuts. Don't go with them, even as a 'joke'. or to try to shame them.

Richard Geere?

Yes.. as a kid I kind of used to rationalize that gasoline should be the most powerfull explosive known to mankind, capable of blowing up by itself if you agitate a container full of it fast enough. When I first lerned that you needed other componets (like oxigen) mixed in a precise proportiont o make gasoline violently explosive, well... I was already ruined. Lets say I like my TV & Movie's falling cars explosive.

So they aren't? Why?, this site has journals you know. Slashdot is the only social network you need. What do you need pictures for?

Nice trolling attempt but I think mr. Cmdr To hit Armor Class 0 is quiting cold turkey for the moment.

About 10 years ago a couple of Alpha servers (Tru64 Unix) and EMA storage in a cluster arrangement was as fast and as stable you can get below the mainframe category (thanks to DEC VAX multiprocessor and shared memory technologies). The natural evolution of the alphas never came out of HP because of their infatuation with Intel Itanium processors, and see how that affair ended up.

All 10 years that I have.

There's no alt.* yet at all, in 1981, but this was just posted "today" to fa.info-cpm:

Keith Petersen (W8SDZ@MC) has uploaded the following files for those
of you with the APPLE II with the Microsoft Z80 cards and CP/M. We
suggest that you capture MC:CPM;APBOOT MAC (or MC:CPM;APMBOT ASM),
assemble it, and use it with :LMODEM on MC to get MC:CPM;CRCK COM and
the MC:CPM;APMODM 21ASM or MC:CPM;APMODM 2ASM. Assemble either APMODM
and you can throw away APBOOT. From there you can use APMODM to grab
whatever other files of interest from MC:CPM; or the various Remote
CP/M systems around the country (see MC:CPM;RCP/M NOS and MC:CPM;RCP/M
INFO for more details).

MC:CPM;
    1 APBOOT MAC 0 +235
    1 APBYE ASM 4 +764
    1 APHIGH MEMASM 0 +310
    14 APMBOT ASM 1 +500
    1 APMODM 21ASM 7 +550
    1 APMODM 2ASM 7 +832
    1 APMODM DOC 0 +908
    1 APXMOD ASM 4 +848

I'm ending it when my archive ends. If google or someone wants to donate more material I'll consider running it further.

I'd like to get to 1994 myself, so I can read my own 1st post.

One commit per tested bugfix. One commit per semi-tested feature. One commit per update to design spec. One commit per update to docs (if not included in a feature/bugfix commit). Also, one merge commit per non-fastforward, non-rebased merge from a feature or bugfix branch can easily bloat the numbers. Plus you can choose to make multiple commits while within those branches, which both bloats the numbers greatly, and helps with backing out if you get into that broken state you mention and can't find your way out.

Also, you can get seriously more productive by increasing your iteration rate. No matter what resources need to be thrown at the test infrastructure etc to allow an increase. This is why Debian, which used to iterate once a day, now pushes out updates to unstable 6 times a day (with CD builds etc) and testing 2, IIRC,