maybe with bs=1M fpr speed?

A somewhat saccharin homage. Never-the-less eliciting fond memories and affirming that computing, like nostalgia, just ain't what it used to be. I'm glad there's room on /. for such occasional nonsense... HGH

My first computer had 5K but only 3.5K available to the user, the guy in the shop said it was "all you'd ever need". I didn't solder it together but I do still have it. Later, I got the graphics super expander to get access to 160 x 160 pixels for "hi-res" graphics. I programmed in BASIC and saved my programs to cassette tape. I'd fire it up for old-times sake but my knees are too worn out to let me get up the ladders into the loft. *sigh*

Summary 1/ It's a good idea, really good actually & very useful - YAY 2/ It comes switched on by default which might not be ideal in all situations - BOO 3/ But don't worry, it doesn't leave your machines wide open in any way - YAY 4/ It's one line to switch it off: - DOUBLE YAY pkalalockdown --lockdown org.freedesktop.pakagekit.package-install Conclusion: 4:1 YAY:BOO ratio

This behaviour is common to all organizations, and commonly results in pathology within the team. What is uncommon is the open nature of Linux kernel development results in the internal dialogue being public & recorded. This level of transparency and raw material is interesting and potentially powerful. What seems to be missing is some mechanism to harness it through a reflective feedback process. Has it been considered? The self organizing nature of open source developement is powerful but not immune. I also note that given '80% of the kernel development' goes through Linus, despite his 2% actual contribution, the kernel development is, therefore, very brittle. Being vulnerable not only to the 'hit-by-bus' effect but simply to the emotional whims of the conduit of that 80% - as exampled by Conus & Cox.

I prefer & use 'markup-monkey' it has a nicer syllable cadence and allitertive appeal is more correct (html/css/javascript-cut-n-paste is not restricted to web) and maintains that belittling yet jolly imagery.

Yes IF you can deal with the 3 main issues of 'friendly worms' (autonomous patching agents): 1/ Control (this may have been dealt with) 2/ Testing 3/ Consent I suspect the big stumbling block would be consent, any thoughts?