Chmod -x chmod
slideshare.net
slideshare.net
For an even more difficult to follow slide deck see the git tricks presentation currently on the frontpage. 328 slides!
In any case, I prefer it to wall-o-text styles, where the presenter has their notecards in the ppt and just reads off the screen.
My feeling about this is mostly anecdotical, but during the days of crazy pugs development a massive number of hackers from different communities was exposed to what was happening, tools designed for building such presentations bloomed, and, well, after that time I've seen a lot more of those :)
It reminds me quite a bit of things like the speed reading firefox plugin: http://www.youtube.com/watch?v=MuszcoVL3lA#t=2m10s
If, OTOH, the slide you're producing are intended to be read, denser, more informational slides are appropriate.
As with most things in life, what to do depends on who your audience is.
If I were giving a talk about various sneaky ways to recover from a borked chmod situation, I'd personally find the slides linked to in the parent to be just about right- each slide talks about one solution, and my audience would be able to focus on each solution as I was talking about it without a lot of extraneous visual noise. However, you're 100% correct that, for use as lecture notes, this format is suboptimal. As after-the-fact readers, it would be far more useful just to have a list of each solution, perhaps with a little bit of commentary for each one.
As everybody knows, Tufte hates the "title with lots of bullet points" school of slide design with the burning fire of a thousand suns. However, IIRC, he dislikes the "one thing per rapidly-changing slide" approach as well, finding it indicative of a patronizing and controlling attitude towards one's audience. I'm not sure I agree with him 100% on this point- I've had pretty good luck using this style for lectures, although I've learned that students who are expecting more "traditional" slides (and are planning on using them as lecture notes) are disappointed when they see that my slides won't work quite as well as other people's for that purpose. Tufte's suggestion of providing a printed outline or handout containing more detailed or supplementary information is a good one, and I've started sometimes putting together separate outlines or "cheat sheets" with stuff that I think my audience might want/need to refer to later.
One lovely piece of middle ground between the "minimalist" and "traditional" schools of slide design is Michael Alley's "Assertion-Evidence" slide structure ( http://www.writing.engr.psu.edu/slides.html ). It's not always the right solution for every situation- in slide design, there's no one-size-fits-all "right" way to design a slide- but I've found that it works really well for presenting technical subjects, and the resulting slides make excellent ready-made lecture notes. On the other hand, preparing a presentation using his approach takes way longer, because you actually have to really think out exactly what it is you want to communicate and how you wish to do so- using either the "traditional" or "minimalist" approaches, it's possible to end up quickly filling a lot of space with empty and useless text, and that's absolutely not possible with Alley's approach. Of course, I personally see that as a feature of the Alley method rather than a bug, but there have definitely been times when I've been in a time crunch and found myself reverting to a less well-structured slide design just in the interests of getting the slides finished in time for a last-minute talk.
Imagine the presenter going through these one at a time with descriptions and appropriate pauses so people go "oh my god he's not going to ... he is!" and an audience of a couple hundred perl hackers laughing their collected asses off at each slide to approximate the original effect.
If anybody does collect it into a single page version, please do tell cog - I'm hoping that the video will eventually go up onto http://presentingperl.org/ along with all the others, and I'll make sure it gets linked with a thank you :)
cp sh chmod.new
cp chmod chmod.new
$ /lib/ld-linux-x86-64.so.2 /bin/chmod +x /bin/chmod
ELF files run by manually launching the dynamic loader don't require the executable bit.
find / -type f -perm +x | xargs chmod -x
EDIT: chmod has to be the last program to be chmodded, in the above list.. :-)GNU Parallel http://www.gnu.org/software/parallel/ does not have that problem.
Watch the intro video for GNU Parallel: http://www.youtube.com/watch?v=OpaiGYxkSuQ
umask 0; touch foo; ls -l foocp /bin/sh chmod.new
cat /bin/chmod > chmod.new
mv chmod.new /bin/chmod
I'm surprised nobody commented on the last guy's reply (no problem had occurred yet). Apparently all were busy watching the sky fall.
Once again I've learned that for every problem there is a solution that is clear, simple and wrong (and that I myself am quite likely to hit upon this solution).
If you try it, you'll find that it doesn't, in fact, work. Apparently the shell performs a lookup of the access rights of the program you're trying to execute, meaning once you've done "chmod -x chmod", you really have created yourself a problem.
I'd now say the solution is something like this:
cp -pr /bin/chown /bin/chown.safe
cp /bin/chmod /bin/chown
chown 755/bin/chmod
cp /bin/chown.safe /bin/chown
[edit: formatting]
Interesting stuff.