Sunday, September 25, 2011

Blog Move Announcement

I have a new blog posting tips and information about computers, that will include some things similar to what this blog was. You can also get a notification emailed to you every week when I post something new--check out the sidebar on the new blog. If you got here via Google or random blog search, take a look at it:

I don't anticipate posting anything more on this blog, as the new one will fill that role just fine.
--
Soren "scorchgeek" Bjornstad
http://www.thetechnicalgeekery.com
Microsoft is not the answer.Microsoft is the question.The answer is "No."

Monday, August 30, 2010

Annotated Command Prompt History

Bash (the Linux command line) has a very useful and interesting feature that saves your last 500 entered commands. So this is an annotated version of my history output from three sets of history (my main computer, the administrator account on that computer ('root'), and my server). It's actually pretty funny in places. I think most people who don't understand the commands should be able to follow along. (ls gets a listing of files in current folder, cd changes folders, grep searches things, vim and emacs are text editors, sudo runs a command as administrator, and you should pick up the rest.)

UPDATE: This formatting is kind of a pain to read--the editor stripped out my tabs, which made it much easier to spot which were commands and which were annotations. You can see it on Google Docs with much better formatting at http://tinyurl.com/33fh3qj.


1 cd Desktop/anki-1.0/
2 ls
3 cat * -r
4 cat *
5 cat * |grep 'statistics'
6 cd libanki
7 ls
8 cd anki
9 ls
10 cat * |grep 'statistics' |less
Still can't find that elusive 'statistics'...
11 exit
12 sudo apt-get install SQLite3
13 cd Downloads
14 ruby
15 sudo apt-get install ruby
16 ruby anki1.0.rb
17 sqlite
18 cd Downloads
19 vi anki1.0.rb
Now I have to edit the script I just downloaded two programs to run?
20 telnet nethack.alt.org
21 telnet termcast.org
22 telnet nethack.alt.org
23 telnet slashem.crash-override.net
24 telnet nethack.alt.org
25 sudo /usr/games/nethack -D
26 telnet nethack.alt.org
27 telnet slashem.crash-override.net
28 sudo /usr/games/nethack -D
29 telnet nethack.alt.org
Playing enough nethack here?
30 ping 192.168.1.44
31 serverlogin
32 ping 192.168.1.34
33 ping 192.168.1.44
34 ??
35 serverlogin
Guess someone's confused about his IP address, based on the ??...
36 vi
37 vim
38 emacs
39 exit
Really can't decide which text editor to use. Guess I'll just have to leave.
40 cd Desktop/interhack
41 ls
42 perl interhack.pl
43 ssh soren@192.168.1.44
44 exit
45 kompozer
46 sudo apt-get install kompozer
47 kompozer
Whoops! Missing that program...wait, it's Ubuntu, I'll just install it instantly.
48 telnet termcast.org
49 qqqqclear
50 clear
Typing in the wrong window...
51 telnet nethack.alt.org
52 ls
Not sure what the ls was about.
53 exit
54 ssh soren@192.168.1.44
55 nethack
56 telnet nethack.alt.org
57 exit
58 lynx
59 exit
60 telnet nethack.alt.org
61 telnet termcast.org
62 telnet nethack.alt.org
63 telnet nethack.alt.org
64 telnet termcast.org
65 telnet nethack.alt.org
66 sudo /usr/games/nethack -D
67 telnet nethack.alt.org
68 nethack -X
69 irssi
70 exit
71 sudo /usr/games/nethack -D
72 telnet nethack.alt.org
73 telnet nethack.alt.org
74 telnet nethack.alt.org
75 sudo /usr/games/nethack -D
76 telnet nethack.alt.org
77 ssh soren@192.168.1.44
78 telnet nethack.alt.org
79 sudo /usr/games/nethack -D
80 telnet nethack.alt.org
81 crawl
82 exit
More nethack. And crawl.
83 sudo emacs23 /etc/init.d/rc
84 sudo vim /boot/grub/menu.lst
Still can't decide on a text editor.
85 sudo cp /boot/grub/menu.lst /boot/grub/menu.baklst
86 sudo vim /boot/grub/menu.lst
87 sudo update-grub
88 vim /boot/grub/menu.lst
89 bash
Go ahead--start bash from within bash. Not sure where that came from.
90 chrome
91 chrome-browser
What's that program called again?
92 sudo killall gdm
93 sudo telinit 1
94 ls /var/cache/apt/archives |less
95 sudo apt-get autoclean
96 sudo apt-get autoremove
97 ssh soren@192.168.1.44
98 crawl
99 telnet nethack.alt.org
100 startx
101 telnet nethack.alt.org
102 sudo /usr/games/nethack -D
103 SET SPLEVTYPE minetn-7
104 set SPLEVTYPE minetn-7
105 echo $SPLEVTYPE
106 echo SPLEVTYPE
107 env
108 cd /
109 find '*breaking*'
110 find *breaking*
111 find
112 find |grep 'breaking'
How do you breaking find again?
113 env $XDG_CACHE_HOME
114 cd
115 ls
116 cd .chrome
117 ls
118 ls -a
119 cd http://www.youtube.com/user/zmusicguy#p/f/0/rJXbwioyK8E
120 cd /home/soren/.mozilla/firefox/rs4s7t4h.default/Cache
121 ls
122 sudo /usr/games/nethack -D
123 telnet nethack.alt.org
124 ls
125 cat soren@192.168.1.44
126 ls
127 ./soren@192.168.1.44
128 telnet nethack.alt.org
129 emacs23; exit
130 emacs23&;exit
131 emacs23& ;exit
132 emacs23 &;exit
133 emacs23 & exit
Wait--how do you type & without hitting the ; key again?
134 cd Desktop/interhack
135 ls
136 perl interhack.pl
137 cpan -i $VT102.pm
138 ./interhack
139 perl interhack.pl
140 perl Makefile.PL; sudo make installdeps
141 ./interhack
142 ./interhack.pl
143 chmod +x interhack.pl
144 ./interhack.pl
145 telnet nethack.alt.org
146 ./interhack.pl
147 cd ./Desktop/interhack
148 ./interhack.pl
149 cpan -i $VT102.pm
150 cpan -i $Role.pm
151 cpan -i /.pm/
152 cpan
153 cpan -i
154 exit
155 perl interhack.pl
156 cd Desktop
157 cd interhack
158 ls
159 perl interhack.pl
160 cpan -i Calf
161 i
162 cpan -i /Calf/
163 perl interhack.pl
That ./interhack.pl doesn't like me...
164 %1
165 I had a question the other day: If everyone forgot everything they knew about computers, how many people would still be using Windows?
166 Imagine that you decided you were going to completely remodel your bathroom. Not being an expert on bathrooms, you don't know much about the various toilets, sinks, and bathtubs available, so you talk to a salesman, and he helps you pick out something that you think will work well. Then he says that you have a choice between the electric blue and lime green varieties of toilet paper. Let's assume that they look equally absurd, and you don't prefer one for its color. The salesman tells you that 90% of people buy the electric blue type. Naturally, you choose the blue, because you assume that if all those people use it, it must be the best.
167 But what you don't know is going to hurt you. Had you taken the time to do your research, you would have found out that electric blue toilet paper dyes your toilet a funny color, clogs the drain on a regular basis, and occasionally even spontaneously explodes. On the other hand, the green kind almost never clogs the toilet, contains much more toilet paper on the same roll, and doesn't lose its dye.
168 Making the situation even more complicated is the existence of the burnt orange variety of toilet paper. It is completely free, allows you to control the exact amount of toilet paper you want to put on a roll (allowing for dispensers of different sizes), lets you refill your toilet paper roll any time you want, and clogs your toilet only in very exceptional circumstances. Unfortunately, you can't buy it along with your bathroom--you have to install it yourself later. You also need to read the short manual in order to learn how to use it correctly. And the existence of this toilet paper is never even mentioned when you buy your toilet. A small number of people find out about and properly set up their orange toilet paper and are very happy with it, but when they try to tell others about the great toilet paper they found, those people only laugh and say, "Wait--you had to read a manual to use your toilet paper?"
169 Now I'm going to add some additional factors to the toilet paper debate.
170 1. The lime green toilet paper is significantly more expensive than the blue kind. The orange kind is still free.
171 2. People can break your toilet's security and damage or make your toilet paper unusable.
172 3. Occasionally, all types of toilet paper will stop working. However, green and orange toilet paper do this less often, and can usually be recovered within a couple of minutes. Orange toilet paper has the potential to be wrecked beyond repair if used improperly, but will almost never break of its own accord.
173 4. Once you have selected a type of toilet paper, you cannot use another one with the toilet without going through an hour-long process that converts it to a different type.
174 5. Blue toilet paper is much easier to find than green and orange toilet paper, and it's very likely that your neighbor will have some blue toilet paper you can borrow if you run out, but (due to their lesser popularity), this is often not true with other types.
175 6. People who normally use a different type of toilet paper may have difficulty using yours. People who prefer orange toilet paper are usually used to all the different types, and will often have no problem. However, users of orange toilet paper are quite rare.
176 So, summarizing:
177 * Electric blue toilet paper is very unreliable--it damages your toilet, clogs it frequently, and sometimes even explodes. It often breaks and can be difficult to repair, and malicious people can easily damage your toilet paper. However, it is very common and you will nearly always be able to find some, and nearly everybody can use it without any trouble.
178 * Lime green toilet paper uses different concepts than blue toilet paper, so people may experience a slight learning curve changing from one to the other. However, it's just as easy to learn to use as blue toilet paper, and is significantly more reliable. Unfortunately, only a small number of people use it, so your use of green toilet paper may annoy people, and you may have difficulty finding more when you run out. It's also the most expensive
179 I think we can all agree on the fact that if popularity concerns were removed, the blue toilet paper is an absolutely terrible deal and nobody would use it. Lime green and burnt orange toilet paper would then be the serious contenders. In this case, I would expect that roughly the same number of people would choose to use green toilet paper as orange. People who are willing to spend some money and don't like learning things would choose lime green toilet paper, while those who want to save their money and are willing to work a little bit to have better control of their toilet would choose orange toilet paper. In this situation, the issue of people having difficulty using other types of toilet paper would also be diminished--with only two types of toilet paper in use, and without one having a near-total monopoly, people would learn the basics of how to use the other type properly, even if they didn't like it much.
180 ---
181 If you didn't get it yet, my electric blue toilet paper represents Windows, lime green toilet paper represents the Mac OS X, and burnt orange toilet paper represents Linux. I may have exaggerated a bit on the instability of Windows, but I honestly have never used another operating system that occasionally chooses to melt down at an inopportune time and sit there with a guilty blue screen facing me. Although occasional slow performance and bugs are a fact of life with computers, Windows also seems to have more of them than any other operating system. And it's not like Windows has a terribly innovative interface or anything else to particularly recommend it, either. It does, as with blue toilet paper, have a wide user base (although more and more new college students, for one, are beginning to purchase Macs), and is compatible with nearly everything. Even that advantage is beginning to change, as more devices provide Linux drivers, more cross-platform software is developed, and the amount of extremely useful free software (free as i
Here I accidentally pasted a text file into my terminal. Most annoying when trying to run a search through my history.
182 telnet nethack.alt.org
183 ./interhack.pl
184 ~/Desktop/interhack/interhack.pl
185 cd Desktop/interhack
186 perl interhack.pl
187 cd ./Desktop/interhack
188 perl interhack.pl
More nethack.
189 top
190 ls
191 top
192 cd /tmp
193 ls
194 ls -a
195 cd .
196 cd ..
197 cd tmp
198 ls
199 ls -a
200 crontab -e
201 crontab -select-editor
202 select-editor
203 ed
204 man ed
205 select-editor
206 crontab -e
Guess we're still not sure on which editor to use.
207 at 1:40 today
208 at 13:40 today
209 atq
210 time
211 clear
212 atq
213 cd ./Desktop/interhack
214 perl interhack.pl
215 telnet nethack.alt.org
216 crawl
217 cd ./Desktop/interhack
218 perl interhack.pl
219 sudo apt-get install sbackup
220 ssh soren@192.168.1.44
221 hmm
222 exit
223 ??
224 exit
225 screen
226 exit
227 screen
228 byobu
229 exit
Exiting seems to cause a lot of confusion. Oddly enough, I'd always thought it was a fairly simple concept.
230 sudo halt
231 telnet nethack.alt.org
232 irssi
233 man irssi
234 sudo killall gdm
235 sudo killall Xorg
236 telnet nethack.alt.org
237 irssi
238 sudo halt
239 sudo /usr/games/nethack -D
240 cd ./Desktop/interhack
241 ./interhack.pl
242 cd ./Desktop/interhack
243 ./interhack.pl
244 cd ./Desktop/interhack
245 ./interhack.pl
246 crawl
247 telnet nethack.alt.org
248 cd ./Desktop/interhack
249 ./interhack.pl
Yet more Nethack.
250 ls
251 df
252 df -h
253 cd regextests
254 ls
255 cd t1
256 ls
257 rm A\ broken\ file
258 ls
259 cd /home
260 ls
Having a bit of trouble deleting a folder.
261 tar -?
262 history | grep 'tar'
263 ls
264 tar -cjf /media/Files/backup.tar.bz2 soren
265 tar -cjf /media/Backup/backup.tar.bz2 soren
266 telnet nethack.alt.org
267 telnet termcast.org
268 clear
269 cd /home/wizard
270 cd ./Desktop/interhack
271 cd ~
272 cd ./Desktop/interhack
273 ./interhack.pl
274 telnet termcast.org
275 ./interhack.pl
276 exit
277 sudo /usr/games/nethack -D
278 ssh soren@192.168.1.44
279 exit
280 telnet termcast.org
281 cd /usr/share/nethack
282 ls
283 cd /usr/games/nethack
284 ls
285 cd /usr/share
286 ls
287 cd ..
288 locate nethack
289 cd /var/games/nethack
290 ls
291 cd save
292 ls
293 clear
294 ps
295 ps -e
296 ls -1
297 ls -l
298 telnet termcast.org
299 telnet nethack.eu
300 exit
301 emacs23
302 firefox &
303 fg %1
304 telnet nethack.alt.org
305 telnet nethack.de
306 telnet nethack.eu
307 clear
308 sudo /usr/games/nethack -D
309 telnet nethack.eu
310 telnet nethack.alt.org
311 cd Desktop/interhack
312 ./interhack.pl
313 telnet nethack.alt.org
314 exit
315 crawl
316 exit
317 cd Desktop
318 ./nethackize
319 vi nethackize
320 gedit nethackize
321 ./nethackize
322 python nethackize
323 serverlogin
324 ./serverlogin
Even more Nethack. Getting tired of this in my history.
325 ssh soren@192.168.1.44
326 --
327 Soren Bjornstad
328 http://www.thetechnicalgeekery.com
329 "Using Linux is like driving a tank.
330 Not everyone knows how to drive a tank,
331 but once you learn how, you're driving a tank!
Another mis-paste.
332 exit
333 cd Desktop
334 mv Organize-Screenshot-* Organize-Screenshots
335 mv Organize-Screenshot-* Organize-Screenshot
That little s can be a pain.
336 ls
337 cd Organiz
338 cd Organize-Screenshot/
339 ls
340 echo Test\Test
341 echo \$Test
We like tests, don't we? Let's put some on the screen!
342 clear
343 crawl
344 telnet nethack.alt.org
345 crawl
346 cd Desktop/interhack
347 ./interhack.pl
348 ssh soren@192.168.1.44
349 exit
350 cd /home/wizard
351 ls
352 rogue
353 exit
354 cd /media
355 ls
356 cd cdrom
357 ls
358 cd ..
359 rogue
360 killall keepass
361 p
362 ps
363 ps -e
364 ps -e |grep 'kee'
365 killall keepassx
Oh, so that's what the program is called. (Strange, I had always thought the 'killall' command killed anything with part of the name in it.
366 ftp www.valpo.k12.in.us
367 ssh www.valpo.k12.in.us
368 ping www.valpo.k12.in.us
Wait, how do you access this server? (I'm not really sure what I was trying to do, actually--I knew perfectly well it didn't accept any connections.)
369 rogue
370 telnet nethack.alt.org
371 sudo /usr/games/nethack -D
372 telnet nethack.alt.org
373 exit
374 gksu nautilus /media
375 gksu nautilus
376 ssh soren@192.168.1.44
377 exit
378 rogue
379 crawl
380 exit
381 anki
382 lynx
383 exit
384 ping
385 ping 188.165.157.209
386 exit
387 cd ..
388 ls
389 tar -cjf /media/Backup/backup100823.tar.bz2 soren
390 sudo tar -cjf /media/Backup/backup100823.tar.bz2 soren
391 telnet nethack.alt.org
392 nethack
393 sudo /usr/games/nethack -D
394 telnet nethack.alt.org
395 sudo /usr/games/nethack -D
396 exit
397 ping www.ancestry.com
Not sure what's up with 397.
398 exit
399 ssh soren@192.168.1.44
400 ssh soren@192.168.1.44
401 sftp soren@192.168.1.44
402 rsync
403 rsync -e ssh
404 rsync ssh
405 cd /media/Digital\ Video
406 ls
407 scp * soren@192.168.1.44:/media/music
408 rsync
409 rsync * soren@192.168.1.44:/media/music
410 rsync -r * soren@192.168.1.44:/media/music
Just copying some of those files can be a bit troublesome...
411 sudo halt
412 sudo reboot
413 ls /dev
414 mt
415 mt --help
416 man mt
417 mt -f /dev/st0 rewind
418 sudo mt -f /dev/st0 rewind
419 ls
420 sudo tar -czf /dev/st0 Incognita.xptv
421 tar -tzf /dev/st0
422 sudo tar -tzf /dev/st0
423 sudo tar -czf /dev/st0 CablesDitching
424 sudo tar -tzf /dev/st0
425 sudo mt -f /dev/sd0 rewind
426 sudo mt /dev/sd0 rewind
427 sudo mt -f /dev/sd0 rewind
428 sudo mt rewind /dev/sd0
429 sudo mt /dev/sd0
430 sudo mt /dev/sd0 rewind
431 mt --help
Trying to learn to use a new tape drive. Took me a while to realize it wasn't working because I typed /sd0 instead of /st0.
432 mf -f /dev/st0
433 mt -f /dev/st0
434 mt -f /dev/st0 rewind
435 sudo mt -f /dev/st0 rewind
436 mt -f /dev/st0 offline
437 sudo mt -f /dev/st0 offline
438 sudo mt -f /dev/st0 rewind
439 sudo tar -tzf /dev/st0
440 sudo tar -czf /dev/st0 Incognita.xptv
441 sudo tar -tzf /dev/st0
442 sudo mt -f /dev/st0 rewind
443 sudo mt -f /dev/st0 status
444 sudo mt -f /dev/st0 erase
445 ls Downloads/
446 ssh soren@192.168.1.44
447 exit
448 ls
449 ssh soren@192.168.1.44
450 ls
451 cd /media/Files
452 ls
453 cd ..
454 cd /etc
455 ls
456 cd ..
457 exit
458 ls
459 tar --help | grep '-d'
460 tar --help | grep "'-d'"
461 tar --help | grep "-d"
462 tar --help
Grep didn't like me. I'll just have to read it myself.
463 ls -a
464 ls -a >listing.txt
465 gedit listing.txt &
466 history | grep 'tar'
467 tar -czf /dev/st0 /home/soren /media/Files /etc --exclude /home/soren/.cache
468 sudo tar -czf /dev/st0 /home/soren /media/Files /etc --exclude /home/soren/.cache
469 mt -f /dev/st0 rewind
470 sudo mt -f /dev/st0 rewind
471 sudo tar -czfv /dev/st0 /home/soren /media/Files /etc --exclude /home/soren/.cache
472 ls
473 tar --help
474 sudo tar -czf /dev/st0 /home/soren /media/Files /etc --exclude /home/soren/.cache --verbose
475 mt /dev/sd0 status
476 mt -f /dev/sd0 status
477 sudo mt -f /dev/sd0 status
478 sudo status /dev/sd0
479 sudo mt -f /dev/st0 status
480 sudo mt -f /dev/sd0 rewind
481 sudo mt -f /dev/st0 rewind
482 sudo tar -czf /dev/st0 /home/soren /etc --exclude /home/soren/.cache --exclude /home/soren/.local/share/Trash --verbose
483 sudo tar -df /dev/st0 /home/soren /etc --exclude /home/soren/.cache --exclude /home/soren/.local/share/Trash --verbose
484 sudo tar -czf /dev/st0 /home/soren /etc --exclude /home/soren/.cache --exclude /home/soren/.local/share/Trash
485 sudo tar -df /dev/st0 /home/soren /etc
486 sudo tar -tzf /dev/st0
Takes a while to get that right...
487 sudo mt -f /dev/st0 rewind
488 sudo mt -f /dev/st0 offline
489 chmod +x backscript
490 ls -l
491 sudo ./backscript
Now maybe I can just run the script instead of typing commands over and over and over and over and over again.
492 cat /media/Files/baklog.txt
493 cat /media/Files/difflog.txt
494 history
495 history | ~/history.txt
496 history > ~/history.txt
Takes a few tries to get the history properly.

--------ROOT---------

1 clear
2 cd ~
3 ls
4 pwd
5 clear
6 reboot
7 halt
8 halt
9 reboot
Rebooting a few times should so *something*!
10 apt-get
11 apt-get remove kompozer
12 reboot
13 ls
14 clear
15 quit
16 exit
17 cd /etc
18 cp fstab fstab_backup
19 ls
20 nano fstab
Nano? This history must go back a long way, I haven't used nano in months.
21 clear
22 logout
23 cd /home
24 ls
25 rm -rf soren
This one scares me a bit, not sure why I was trying to delete my own user account.
26 ls
27 clear
28 reboot
29 nano /etc/fstab
30 rebooyt
31 reboot
32 ls
33 umount /home
34 ls
35 cd /home
36 ls
37 mkdir soren
38 ls
39 nano /etc/fstab
40 reboot
41 ls
42 umount /home/sore
43 umount /home/soren
Oh, I remember this time now. I tried to move my (Linux) home directory onto a Windows-formatted drive. Did not go well at all.
44 cd /home/soren
45 ls
46 mount /dev/sdb1 /media/files
47 mount /dev/sdb1 /media/Files
48 cd /media/Files
49 ls
50 cp "05 - Track 05.mp3" /home/soren
51 cp -r * /home/soren
52 cd /home/soren
53 ls
54 rm -r OldDocs
55 ls
56 du
57 df
58 ls
59 cd /media/Files
60 ls
61 cp [p-z,P-Z]* /home/soren
62 cp -r [p-z,P-Z]* /home/soren
Something wrong with the a-o folders? Not sure what's up there.
63 ls
64 cd /home/soren
65 sl
66 ls -a
67 rm -r "Tape Copy Project"
68 ls
69 rm -r "System Volume Information"
70 rm -r "Technical Geekery Website"
71 ls
72 df
73 du
74 ls
75 cd Music
76 ls
77 cd ..
78 cd soren
79 ls
80 du
81 cd ..
82 ls
83 du "SORDRIVE dump 4-19-09"
84 du "SORDRIVE dump 4-19-09"\
85 du "SORDRIVE dump 4-19-09"/
86 clear
87 df
88 ls
89 cd Videos
90 ls
91 clear
92 ls
93 cd ..
94 ls
95 cd hom
96 cd home
97 ls
98 cd ..
99 cd home
100 ls -a
101 cd ..
102 rm home
103 rm -rt home
104 rm -r home
105 ls
106 rm -r "SORDRIVE dump 4-19-09"
107 df
108 cd /dev/sdb1
109 cd /media/Files
An insane number of cd's, ls's, and a couple of rm's, especially ones of important system directories, can never fail to go well, apparently.
110 ls
111 ls -a
112 ls -a |grep .*
113 ls
114 grep
115 grep .*
116 ls
117 ls |grep .
118 ls -a |grep .*
Guess I didn't understand the grep command yet. That winds up searching for everything.
119 clear
120 ls
121 clear
122 ls
123 clear
I don't like the directory listing--get it out of here!
124 ls -a
125 cp .* /home/soren
126 cp -r .* /home/soren
127 cd /home/soren
128 ls
129 ls -a
130 cd ./.audacity-data
131 ls
132 du
133 cd ..
134 df
135 ls
136 ls -a
137 cd ..
138 ls
139 cd /media/Files
140 ls
141 ls -a
142 cp .??* /home/soren
143 cp -r .??* /home/soren
144 ls
145 cp --help
146 cp --help |less
147 clear
148 ls
149 ls -a
150 cp .*/ /home/soren
151 cp -rv .*/ /home/soren
152 ls
153 cp -rv /media/Files/.*/ /home/soren
154 ls
155 cp -rv /media/Files/.*/ /home/soren/
156 cd /home/soren
Copying didn't like me that day. Or I didn't like it. Or both.
157 ls
158 ls -a
159 mkdir .
160 cd .
161 cd /media/Files
162 ls
163 ls -a
164 cp .bashrc /home/soren
165 ls /home/soren
166 ls -a /home/soren
167 ls
168 ls -a
169 ls -a /home/soren
170 cp -rv .* /home/soren/
171 ls
172 cd /home/soren
173 ls
174 rm -r OldDocs
175 rm -r $RECYCLE.BIN
176 rm -r "$RECYCLE.BIN"
177 rm -r "$RECYCLE.BIN"
178 rm -r ""$RECYCLE.BIN""
How did you spell $RECYCLE.BIN again?
179 ls
180 du $RECYCLE.BIN
181 cd $RECYCLE.BIN
182 df
183 cd /media/Files
184 clear
185 ls
186 ls -a
187 cp ".*" /home/soren
188 cp ./"."* /home/soren
189 cp -rv ./"."* /home/soren
190 ls
191 ls -a
192 ls -al
193 ls -a |more
194 ls
195 ls -a
196 ls -a | dirs
197 ls -a > dirs
None of those listings any good. Especially the second time I ask for the same one.
198 nano dirs
199 clear
200 ls
201 dirs |grep .* >dirs2
Better filter everything out of the file and put it in another!
(For the record, the correct way to do this [search for a . at the beginning of filenames) is \.*)
202 nano dirs2
203 clear
204 ls
205 .*
206 ls -a
207 cp .bashrc /home/soren
208 cp .bzf /home/soren
209 cp -r .bzf /home/soren
210 ls -a
211 cp -r .cache /home/soren
212 cp -r .compiz /home/soren
213 cp -r .config /home/soren
214 cp -r .dbus /home/soren
215 cp -r .dillo /home/soren
216 cp -r .dmrc /home/soren
217 cp -r .esd_auth /home/soren
218 cp -r .evolution /home/soren
219 cp -r .filezilla /home/soren
Resistance is futile, computer! I'll do it anyway! (Making it even funnier, I didn't even know you could hit 'tab' to complete a filename, so I typed every one of those commands out.)
220 ls
221 ls -a
222 ls -a |more
223 ls -a >nano
224 nano nano
Not sure why I called that file nano.
225 ls
226 ls -a
227 nano dirs
228 clear
229 ls -a
230 cp -r .fontconfig /home/soren
231 cp -r .gconf /home/soren
232 ls -a /home/soren
233 ls -a
234 cp -r .gconfd /home/soren
235 cp -r .gegl-0.0 /home/soren
236 cp -r .gimp-2.6 /home/soren
237 cp -r .gksu.lock /home/soren
238 cp -r .gksu.loc /home/soren
239 cp -r .gnome2 /home/soren
240 cp -r .gnome2-private /home/soren
241 cp -r .gnome2_private /home/soren
242 cp -r .gnupg /home/soren
243 cp -r .gstreamer-0.10 /home/soren
244 cp -r .gtk-bookmarks /home/soren
245 ls -a
246 cp -r .ICEauthority /home/soren
247 ls -a
248 cp -r .icons /home/soren
249 cp -r .kompozer /home/soren
250 cp -r .kompozer.net /home/soren
251 cp -r .local /home/soren
252 cp -r .macromedia /home/soren
253 cp -r .mozilla /home/soren
254 cp -r .nautilus /home/soren
255 cp -r .nvidia-settings-rc /home/soren
256 cp -r .openoffice.org /home/soren
257 cp -r .openoffice.org2 /home/soren
258 cp -r .profile /home/soren
259 cp -r .pulse /home/soren
260 cp -r .pulse-cookie /home/soren
261 cp -r .recently-used /home/soren
262 cp -r .recently-used.xbel /home/soren
263 ls
264 ls -a
265 nano dirs
266 ls -a
267 cp -r .ripoff /home/soren
268 cp -r .Skype /home/soren
269 cp -r .sudo_as_admin_successful /home/soren
270 cp -r .sudoku /home/soren
271 cp -r .supertux /home/soren
272 cp -r .supertux2 /home/soren
273 cp -r .themes /home/soren
274 ls -a
275 cp -r .thumbnails /home/soren
276 cp -r .tomboy /home/soren
277 cp -r .tomboy.log /home/soren
278 cp -r .update-manager-core /home/soren
279 cp -r .update-notifier /home/soren
280 cp -r .w3m /home/soren
281 cp -r .wapi /home/soren
282 cp -r .Xauthority /home/soren
283 cp -r .xscreensaver-getimage.cache /home/soren
284 cp -r .xsession-errors /home/soren
285 cd /home/soren
Beat that! 175 commands to do something that should have been accomplished in one!
286 ls -a
287 ls -l
288 cd ..
289 ls
290 chown soren soren
Wait, soren should own soren?
291 ls
292 chown -r soren soren
293 chown -R soren soren
294 cd soren
295 ls
296 ls -l
297 chmod * 665
298 cd ..
299 chmod -r soren 665
The wonders of permissions.
300 reboot
301 halt
302 top
303 sudo reboot
304 halt
305 top
306 reboot
Guess we finally solved that one.
307 nethack -D
308 /usr/games/nethack -D
309 /usr/games/nethack -D
310 nethack -D
311 /usr/gamesnethack -D
312 /usr/games/nethack -D
313 /usr/games/nethack -D
314 nethack -D
315 /usr/games/nethack -D
316 nethack -D
317 /usr/games/nethack -D
318 /usr/games/nethack -D
319 /usr/games/nethack -D
320 /usr/games/nethack -D
321 /usr/games/nethack -D
322 /usr/games/nethack -D
323 clear
324 /usr/games/nethack -D
325 clear
326 /usr/games/nethack -D
327 /usr/games/nethack -D
328 /usr/games/nethack -D
329 /usr/games/nethack -D
330 exit
331 /usr/games/nethack -D
332 /usr/games/nethack -D
333 /usr/games/nethack -D
334 /usr/games/nethack -D
335 clear
336 quit
337 /usr/games/nethack -D
338 clear
339 quit
340 exit
341 /usr/games/nethack -D
342 /usr/games/nethack -D
343 /usr/games/nethack -D
344 /usr/games/nethack -D
345 /usr/games/nethack -D
346 /usr/games/nethack -D
347 /usr/games/nethack -D
348 /usr/games/nethack -D
349 /usr/games/nethack -D
350 /usr/games/nethack -D
351 /usr/games/nethack -D
352 /usr/games/nethack -D
353 /usr/games/nethack -D
354 /usr/games/nethack -D
355 /usr/games/nethack -D
356 exdit
357 exit
358 exit
359 /usr/games/nethack -D
360 /usr/games/nethack -D
361 /usr/games/nethack -D
362 exit
363 /usr/games/nethack -D
364 clear
365 exit
366 /usr/games/nethack -D
367 exit
368 /usr/games/nethack -D
369 /usr/games/nethack -D
370 /usr/games/nethack -D
371 exit
372 /usr/games/nethack -D
373 exit
374 /usr/games/nethack -D
375 nethack
376 /usr/games/nethack -D
377 /usr/games/nethack -D
378 /usr/games/nethack -D
379 /usr/games/nethack -D
380 /usr/games/nethack -D
381 exit
382 exit
383 exit
384 /usr/games/nethack -D
385 /usr/games/nethack -D
386 /usr/games/nethack -D
387 /usr/games/nethack -D
388 /usr/games/nethack -D
389 /usr/games/nethack -D
390 /usr/games/nethack -D
391 /usr/games/nethack -D
392 /usr/games/nethack -D
393 /usr/games/nethack -D
394 /usr/games/nethack -D
395 exit
396 /usr/games/nethack -D
397 /usr/games/nethack -D
398 /usr/games/nethack -D
399 /usr/games/nethack -D
400 /usr/games/nethack -D
401 /usr/games/nethack -D
402 /usr/games/nethack -D
403 /usr/games/nethack -D
404 nethack
405 /usr/games/nethack -D
406 /usr/games/nethack -D
407 /usr/games/nethack -D
408 /usr/games/nethack -D
409 /usr/games/nethack -D
410 /usr/games/nethack -D
411 exit
412 exit
413 /usr/games/nethack -D
414 /usr/games/nethack -D
415 /usr/games/nethack -D
416 /usr/games/nethack -D
417 /usr/games/nethack -D
418 /usr/games/nethack -D
419 /usr/games/nethack -X
420 /usr/games/nethack -X
421 exit
422 /usr/games/nethack -X
423 /usr/games/nethack -D
424 /usr/games/nethack -D
425 /usr/games/nethack -D
426 /usr/games/nethack -D
427 /usr/games/nethack -D
428 /usr/games/nethack -D
429 exit
430 /usr/games/nethack -D
431 /usr/games/nethack -D
432 exit
433 /usr/games/nethack -D
434 /usr/games/nethack -D
435 /usr/games/nethack -D
436 /usr/games/nethack -D
437 exit
438 /usr/games/nethack -D
439 /usr/games/nethack -D
440 /usr/games/nethack -D
441 /usr/games/nethack -D
442 /usr/games/nethack -D
443 /usr/games/nethack -D
444 /usr/games/nethack -D
445 exit
446 /usr/games/nethack -D
It took me quite a while, 139 runs in fact, to realize that running 'sudo /usr/games/nethack -D' was the same as logging in as root and running it.
447 top
448 killall xorg
449 killall Xorg
450 logout
451 /usr/games/nethack -D
452 portablelinux
453 ls
454 ls |grep 'portablelinux'
455 portablelinux
456 chown portablelinux root
457 chown root portablelinux
458 portablelinux
459 nautilus
460 portablelinux
461 chmod portablelinux
462 chmod --help
463 ls -l portablelinux
464 chmod 744 portablelinux
465 ls
466 portablelinux
Had more than a bit of trouble setting up a Linux flash drive.
467 ls
468 pwd
469 cd /tmp
470 ls
471 rm -rf /tmp/*
472 ls
473 tar -czf Incognita.xptv
474 tar -czf /dev/st0 Incognita.xptv
475 tar -tzf /dev/st0
476 mt -f /dev/st0 eod
477 man mt
478 mt -f /dev/st0 eom
479 tar -czf /dev/st0 GMAIL\ PASSWORD\ RESET
480 mt -f /dev/st0 rewind
481 tar -tzf /dev/st0
Not sure why I was logged in as root to do this.
482 tar -czf /dev/st0 Downloads/
483 tar -tzf /dev/st0
484 mt -f /dev/st0 rewind
485 mt -f /dev/st0 offline
486 ls
487 exit
488 history
489 history | /home/soren/historyroot.txt
490 history > /home/soren/historyroot.txt
I make the same exact mistake I did extracting the last one.

---------SERVER---------
4 logout
5 exit
6 sudo /etc/init.d/ssh start
7 sudo /etc/init.d/sshd start
8 ls /etc/init.d
9 sudo apt-get install ssh
This was the point that I realized, after about five hours of troubleshooting total, that I couldn't connect to the server with ssh because the ssh server wasn't installed.
10 ssh soren@localhost
11 exit
12 sudo /etc/init.d/shorewall start
13 clera
14 exit
15 sudo reboot
16 ls
17 uptime
18 ls
19 exit
20 ls
21 cat blogonpuzzlesquare.txt
22 less blogonpuzzlesquare.txt
23 ls
24 rm *.ttyrec
25 ls
26 rm ttyrec-1.0.8
27 rm -r ttyrec-1.0.8
28 ls
29 rm ttyrec-1.0.8.tar.gz
30 ls
31 scp blogonpuzzlesquare.txt soren@192.168.1.66:/home/soren
Some things that don't really belong on your server end up there when your computer breaks and you use the server for a couple of days.
32 ls
33 exit
34 firefox
35 lynx
36 call
37 open
38 gksu lynx
39 clear
40 ssh soren@192.168.1.64
41 ssh soren@192.168.1.66
Silly me, I let my IP address change, so I had to go look it up constantly to make a connection to my other computer.
42 exit
43 ls
44 uptime
45 cat info
46 cat ipbt
47 scp -r ipbt /home/soren
48 scp -r ipbt soren@192.168.1.66:/home/soren
49 ls
50 rm -r ipbt
51 ls
52 exit
53 ls
54 exit
Log in, get a listing, and exit!
55 ifconfig
56 ls
57 cd /var
58 ls
59 cd www
60 ls
61 ls !
Yay for ls!
62 ls ~
63 ls /home/soren
64 mv /home/soren/Techgeek\ Tips\ November-December.ppt .
65 ls
66 cd Windows
67 ls
68 cd archives
69 ls
70 cd ..
71 ls
72 cd pdfs
73 ls
74 cd ..
75 ls
76 mv current.pdf ./pdfs/2009_10.pdf
77 cd pdfs
78 ls
79 mv 2009_10.pdf tips_2009.10.pdf
80 ls
81 cd ..
82 ls
83 vi tips.html
84 cd ..
85 ls
86 mv Techgeek\ Tips\ November-December.ppt ./Windows/current.pdf
87 cd Windows & ls
88 cd Windows
89 ls
90 current.pdf
91 scp current.pdf soren@192.168.1.34:/home/soren
92 ls
93 cd ..
94 ls
95 mv Techgeek\ Tips\ November-December.pdf ./Windows/current.pdf
96 cd Windows
Can take a while to get your files in order.
97 ls
98 history |less
99 vim /etc/network/interfacews
100 vim /etc/network/interfaces
101 sudo vim /etc/network/interfaces
102 sudo reboot
103 exit
104 sudo vim /etc/network/interfaces
105 sudo reboot
106 exit
107 ls
108 exit
109 sudo apt-get upgrade
110 sudo apt-get
111 sudo aptitude
112 sudo apt-get dist-upgrade
113 version
114 v
115 ver
116 vr
117 clear
118 kernel
Not sure what that was about.
119 exit
120 cd /var/www
121 cd Images
122 cd images
123 ls
124 mv Google\ 2. png Google\ 1.png
125 ls
126 mv "Google 2.png" "Google 1.png"
127 ls
128 mv Google\ 1.png Google1.png
129 mv Google\ 2.png Google2.png
130 mv Google\ 3.png Google3.png
131 ls
132 mv Google?.png google?.png
133 mv "Google?.png" "google?.png"
134 mv Google?.png "google?.png"
135 mv Google?.png google?.png
136 mv Google1.png google1.png
137 mv Google2.png google2.png
138 mv Google3.png google3.png
Changing a capital letter to a lowercase one can take a while if you're too tired.
139 ls
140 cd /var/ww
141 cd /var/www/images
142 ls
143 mv google1.png Google1.png
144 mv google2.png Google2.png
145 mv google3.png Google3.png
And now we put it back. Don't even ask.
146 ls
147 exit
148 ifconfig
149 exit
150 cd /var/www
151 ls
152 vi index.html
153 exit
154 uptime
155 exit
156 uptime
157 exit
158 uptime
159 exit
160 uptime
For a while, I seemed to enjoy logging into the server just to check its uptime.
161 top
162 ls
163 cd /var/www
164 ls
165 cd ..
166 exit
167 cd /var/www
168 ls
169 cd Windows
170 ls
171 cd archives/
172 ls
173 cd ..
174 ls
175 cd pdfs/
176 ls
177 exit
178 sudo apt-get update
179 sudo apt-get upgrade
180 sudo apt-get
181 sudo aptitude
182 exit
183 uptime
184 last
185 sudo apt-get
186 sudo apt-get upgrade
187 sudo apt-get upgrade *
188 ls
189 exit
190 sudo halt
191 uptime
Upgrade. Upgrade? Upgrade!
192 sudo lshw -C disk
193 sudo fdisk /dev/sdb
194 sudo mkfs -t ext4 /dev/sdb1
195 tune2fs --help
196 sudo tune2fs -m 1 /dev/sdb1
197 cd /medis
198 ls
199 cd /media & ls
200 cd /media
201 ls
202 cd exthd
203 ls
204 cd ..
205 mkdir music
206 sudo mkdir music
207 ls
208 cd music
209 ls
210 cd ..
211 sudo vi /etc/fstab
212 sudo mount /dev/sdb1 /media/music
213 sudo mount ext4/dev/sdb1 /media/music
214 sudo mount ext4 /dev/sdb1 /media/music
215 sudo mount -t ext4 /dev/sdb1 /media/music
216 lol
'lol' is my inability to type the correct command in four attempts. The system's (lack of) cooperation was not the least bit amusing.
217 sudo reboot
218 uptime
219 clear
220 ls
221 cd /media/music
222 ls
223 cd ..
224 mount
225 mount /dev/sdb1 /media/music
226 sudo mount /dev/sdb1 /media/music
227 aaaaargh
Like that.
228 sudo mkfs -t ext3 /dev/sdb1
229 tune2fs -m 2 /dev/sdb1
230 sudo tune2fs -m 2 /dev/sdb1
Guess I'll just give up and reformat the drive so it works.
231 ls
232 gksu gedit /etc/fstab
233 sudo vi /etc/fstab
234 sudo mount -a
235 ls
236 mount
237 cd music
238 ls
239 cd ..
240 chown music soren
241 chown soren /media/music
242 sudo chown soren /media/music
243 ls -l
244 lsls
245 lsl
246 ll
247 lls
What's that one command with the 'l' and the 's' again?
248 ls
249 ls -l
250 cd music
251 ls
252 cd ..
253 ls -l /var
254 exit
255 cd /media/music
256 ls
257 cd Family\ Videos/
258 ls
259 cd ..
260 cd DOWNSTAIRS-BACKUP/
261 ls
262 cd new
263 ls
264 cd Red\ Alien\ Hacker/
265 ls
266 cd ..
267 cd newer
268 ls
269 cd ..
270 cd new
271 cd ../newer
272 ls
273 cd ../newest
274 ls
275 cd ..
276 ls
277 cd newerer/
278 ls
279 cd ..
280 cd new
281 cd ../newer
282 ls
283 cd ..
New? Newer? Newest? Newerer?!
284 ls
285 cd music
286 ls
287 cd Incognita/
288 ls
289 cd ..
290 cd Music
291 ls
292 cd ..
293 cd music
294 ls
295 cd /media/music
296 ls
297 cd Family\ Videos/
298 ls
299 cd ..
300 exit
301 cd /media/music
302 ls
303 cd Family\ Videos/
304 ls
305 cd ..
306 exit
307 sudo mount -a
308 ls
309 cd /media
310 ls
311 cd exthd
312 ls
313 cd ..
314 mount
315 cd music
316 ls
317 cd Incognita/
318 ls
319 cd ..
320 ls
321 ls /dev
322 sudo mount -a
323 ls
324 cd exthd
325 ls
326 cd ..
327 sudo vi /etc/fstab
328 sudo mount -a
329 ls /dev
330 sudo vi /etc/fstab
331 sudo mount -a
332 cd exthdd
333 cd exthd
334 ls
335 cd ..
336 ls
337 cd music
338 ls
339 cd ..
340 cd exthd
341 ls
Finally figured that one out.
342 sudo cp -r * /media/music/*
343 vi /etc/samba/smb.conf
344 sudo vi /etc/samba/smb.conf
345 sudo cp /etc/samba/smb.conf /etc/samba/smb.confbak
346 sudo vi /etc/samba/smb.conf
347 history | grep 'samba'
348 sudo /etc/init.d/samba restart
349 sudo vi /etc/samba/smb.conf
350 history | grep 'shorewall'
351 sudo /etc/init.d/shorewall stop
352 sudo vi /etc/default/shorewall
353 sudo vi /etc/shorewall/rules
354 sudo /etc/init.d/shorewall start
355 less /var/log/shorewall-init.log
356 sudo /etc/init.d/shorewall stop
357 sudo vi /etc/shorewall/rules
358 sudo /etc/init.d/shorewall start
359 sudo vi /etc/shorewall/rules
360 sudo /etc/init.d/shorewall start
361 info shorewall
362 sudo vi /etc/shorewall/rules
363 sudo /etc/init.d/shorewall start
364 sudo vi /etc/shorewall/rules
365 sudo /etc/init.d/shorewall stop
366 sudo vi /etc/shorewall/rules
367 sudo /etc/init.d/shorewall start
368 sudo vi /etc/shorewall/rules
369 sudo /etc/init.d/shorewall start
370 sudo apt-get install shorewall
371 sudo /etc/init.d/shorewall stop
372 history 10
373 sudo vi /etc/shorewall/rules
374 ls /usr/share/shorewall/macro.*
375 sudo vi /etc/shorewall/rules
376 sudo /etc/init.d/shorewall start
377 tail /var/log/shorewall-init.log
378 sudo vi /etc/shorewall/rules
379 sudo /etc/init.d/shorewall start
380 tail /var/log/shorewall-init.log
381 sudo vi /etc/shorewall/rules
382 sudo /etc/init.d/shorewall start
383 tail /var/log/shorewall-init.log
384 sudo vi /etc/shorewall/rules
385 sudo /etc/init.d/shorewall start
386 sudo vi /etc/shorewall/rules
387 tail /var/log/shorewall-init.log
388 sudo vi /etc/shorewall/rules
389 sudo /etc/init.d/shorewall start
390 tail /var/log/shorewall-init.log
391 sudo vi /etc/shorewall/zones
392 sudo vi /etc/shorewall/rules
393 sudo /etc/init.d/shorewall start
394 tail /var/log/shorewall-init.log
395 sudo vi /etc/shorewall/rules
396 sudo /etc/init.d/shorewall start
397 tail /var/log/shorewall-init.log
398 sudo vi /etc/shorewall/rules
399 sudo /etc/init.d/shorewall start
400 tail /var/log/shorewall-init.log
401 sudo vi /etc/shorewall/rules
402 sudo /etc/init.d/shorewall start
403 tail /var/log/shorewall-init.log
404 sudo vi /etc/shorewall/rules
405 sudo /etc/init.d/shorewall start
406 sudo vi /etc/shorewall/rules
64 commands to figure out the right way to state the firewall rules.
407 ifconfig
408 cd /media/music
409 ls
410 ls -l
411 cd ..
412 chmod +rwx music
413 ls -l
414 chmod +w music
415 ls
416 lls
417 ls
418 ls -l
419 chmod music 777
420 chmod 777 music
421 ls
422 ls -l
423 cd music
424 ls
425 ls -l
426 cd ..
427 chmod 755 music
428 ls -l
429 cd music
430 chmod 777 *
431 ls -l
432 cd The\ Ammonite
433 ls
434 cd ..
435 cd The\ Ammonite\ New/
436 ls
437 cd 6-20-2008/
438 ls
439 cd ..
440 cd Trinity\ Videos/
441 ls
442 cd ..
443 cd The\ Ammonite\ New/
444 sudo ls
Apparently sometimes having administrator privileges influences your directory list. Anything seems believable when your files just disappear.
445 cd 6
446 cd 6-20-2008/
447 sudo ls -al
448 cd ..
449 sl
450 ls
451 ls -r
452 ls
453 ls -l
454 chmod 777 * -r
455 chmod * 777 -r
456 cd ..
457 chmod 777 music -r
458 chmod music 777 -r
459 cd music
460 ls
461 cd ..
462 ls
463 ls -l
464 chmod music 777
465 chmod 777 music
466 ls
467 ls
468 ls -l
469 chmod 777 -r music
470 chmod -r 777 music
471 chmod -r music 777
472 chmod music 777
473 chmod 777 music
474 ls -l
475 man chmod
476 chmod music 777 -R
477 chmod 777 music -R
478 sudo chmod 777 music -R
That's a few commands to figure out the right combination of r, R, chmod, and 777.
479 ls -l
480 cd music
481 ls -l
482 history | grep cp
483 cp --help
484 ls -R
485 cd Music\ New/
486 ls
487 ls -r > contents.txt
488 cat contents.txt
489 ls -R > contents.txt
490 cat contents.txt
491 ls -R /media/exthd/Music\ New/ > /media/music/Music\ New/ > contents2.txt
492 ls -R /media/exthd/Music\ New/ > /media/music/Music\ New > contents2.txt
493 ls -R /media/exthd/Music\ New/ > /media/music/Music\ New/contents2.txt
Typing a bit slower may help.
494 ls -l
495 diff contents.txt contents2.txt
496 rm contents.txt
497 rm contents2.txt
498 ls -l
499 top
500 mount
501 history
502 ls
503 history > historyserver.txt
Glad to see I didn't make the same mistake yet again.

--
Soren "scorchgeek" Bjornstad
http://www.thetechnicalgeekery.com
Microsoft is not the answer.Microsoft is the question.
The answer is "No."

Wednesday, August 11, 2010

OS Popularity

I had a question the other day: If everyone forgot everything they knew about computers, how many people would still be using Windows?

Imagine that you decided you were going to completely remodel your bathroom. Not being an expert on bathrooms, you don't know much about the various toilets, sinks, and bathtubs available, so you talk to a salesman, and he helps you pick out something that you think will work well. Then he says that you have a choice between the electric blue and lime green varieties of toilet paper. Let's assume that they look equally absurd, and you don't prefer one for its color. The salesman tells you that 90% of people buy the electric blue type. Naturally, you choose the blue, because you assume that if all those people use it, it must be the best.

But what you don't know is going to hurt you. Had you taken the time to do your research, you would have found out that electric blue toilet paper dyes your toilet a funny color, clogs the drain on a regular basis, and occasionally even spontaneously explodes. On the other hand, the green kind almost never clogs the toilet, contains much more toilet paper on the same roll, and doesn't lose its dye.

Making the situation even more complicated is the existence of the burnt orange variety of toilet paper. It is completely free, allows you to control the exact amount of toilet paper you want to put on a roll (allowing for dispensers of different sizes), lets you refill your toilet paper roll any time you want, and clogs your toilet only in very exceptional circumstances. Unfortunately, you can't buy it along with your bathroom--you have to install it yourself later. You also need to read the short manual in order to learn how to use it correctly. And the existence of this toilet paper is never even mentioned when you buy your toilet. A small number of people find out about and properly set up their orange toilet paper and are very happy with it, but when they try to tell others about the great toilet paper they found, those people only laugh and say, "Wait--you had to read a manual to use your toilet paper?"

Now I'm going to add some additional factors to the toilet paper debate.
1. The lime green toilet paper is significantly more expensive than the blue kind. The orange kind is still free.
2. People can break your toilet's security and damage or make your toilet paper unusable.
3. Occasionally, all types of toilet paper will stop working. However, green and orange toilet paper do this less often, and can usually be recovered within a couple of minutes. Orange toilet paper has the potential to be wrecked beyond repair if used improperly, but will almost never break of its own accord.
4. Once you have selected a type of toilet paper, you cannot use another one with the toilet without going through an hour-long process that converts it to a different type.
5. Blue toilet paper is much easier to find than green and orange toilet paper, and it's very likely that your neighbor will have some blue toilet paper you can borrow if you run out, but (due to their lesser popularity), this is often not true with other types.
6. People who normally use a different type of toilet paper may have difficulty using yours. People who prefer orange toilet paper are usually used to all the different types, and will often have no problem. However, users of orange toilet paper are quite rare.

So, summarizing:
* Electric blue toilet paper is very unreliable--it damages your toilet, clogs it frequently, and sometimes even explodes. It often breaks and can be difficult to repair, and malicious people can easily damage your toilet paper. However, it is very common and you will nearly always be able to find some, and nearly everybody can use it without any trouble.
* Lime green toilet paper uses different concepts than blue toilet paper, so people may experience a slight learning curve changing from one to the other. However, it's just as easy to learn to use as blue toilet paper, and is significantly more reliable. Unfortunately, only a small number of people use it, so your use of green toilet paper may annoy people, and you may have difficulty finding more when you run out. It's also the most expensive type of toilet paper.
* Burnt orange toilet paper is uncommon, but it allows you to do basically anything you want with it. It requires reading a short manual to familiarize yourself with its workings, and also needs a small amount of time to install and master. However, once you have done these things, you'll think it's great. It's also completely free.

I think we can all agree on the fact that if popularity concerns were removed, the blue toilet paper is an absolutely terrible deal and nobody would use it. Lime green and burnt orange toilet paper would then be the serious contenders. In this case, I would expect that roughly the same number of people would choose to use green toilet paper as orange. People who are willing to spend some money and don't like learning things would choose lime green toilet paper, while those who want to save their money and are willing to work a little bit to have better control of their toilet would choose orange toilet paper. In this situation, the issue of people having difficulty using other types of toilet paper would also be diminished--with only two types of toilet paper in use, and without one having a near-total monopoly, people would learn the basics of how to use the other type properly, even if they didn't like it much.

---
If you didn't get it yet, electric blue toilet paper represents Windows, lime green toilet paper represents the Mac OS X, and burnt orange toilet paper represents Linux. I may have exaggerated a bit on the instability of Windows, but I honestly have never used another operating system that occasionally chooses to melt down at an inopportune time and sit there with a guilty blue screen facing me. Although occasional slow performance and bugs are a fact of life with computers, Windows also seems to have more of them than any other operating system. And it's not like Windows has a terribly innovative interface or anything else to particularly recommend it, either. It does, as with blue toilet paper, have a wide user base (although more and more new college students, for one, are beginning to purchase Macs), and is compatible with nearly everything. Even that advantage is beginning to change, as more devices provide Linux drivers, more cross-platform software is developed, and the amount of extremely useful free software (free as in freedom, not as in free beer), much of which works on any system, increases daily.

What do you think? If you had to relearn everything you knew about computers and you knew nothing about the popularity (or compatibility, although as I mentioned, that's beginning to be less and less important) of operating systems, but only their features, which would you choose? Let me know in the comments.

--
Soren "scorchgeek" Bjornstad
http://www.thetechnicalgeekery.com
Microsoft is not the answer. Microsoft is the question.
The answer is "No."

Copyright 2010 Soren Bjornstad.
Verbatim copying and redistribution of part or all of this work
is permitted, provided this notice is preserved.

Monday, July 26, 2010

Who can you trust on the Internet?

Introduction
Who can you trust on the Internet? It's a question we have to face all the time. Everyone knows that they shouldn't email their credit card numbers to that guy in Nigeria who really needs their help to keep his rightful inheritance of $1,988,356.76 away from the evil government (and will pay you an absurd amount of money to do it). But it gets harder than that.

Part One: Malware
There are lots of less-than-reputable websites that would love you to download viruses from them. There are also some sites that offer “ad-supported” software that puts so many ads on your PC that you can't do anything but look at ads (and it often can't be removed through normal methods either). Most of the time, you can easily tell when you've visited one of those sites. (Of course, there are clearly still enough gullible people that they continue making money, but I doubt you're one of them if you're reading this blog.) Unfortunately for us, there are plenty of borderline websites, where you can't tell if the site is reputable or not. I've personally never been burned by one of these sites (knock on wood), but you should always scan even semi-questionable downloaded files with a good antivirus program, and don't run any ActiveX controls or allow other security warnings unless you're sure about the site. Your antivirus software is not invincible, though, and ultimately the best defense against malware is to exercise common sense.

My No-Nonsense Download Checklist
1. Do you really need this program? If you need a word processor or a video editor to finish a project, then that's a good download. If you were just browsing the Internet and said, “Huh, that sounds cool,” think for a minute before you decide to try it. If you install it and don't need it, not only do you raise your chances of getting hit by malware, you also clog your PC with unnecessary garbage and waste time downloading and installing it.

2. Does the program make any mention of being supported by ads or requiring other (questionable-sounding) programs? If so, pass it by and find something else. Although it may seem like a fair tradeoff at the time, chances are very good you'll regret it later—and such downloads are far more likely to contain actively destructive or dangerous software.

3. Does the URL contain a load of unidentifiable characters? I don't mean at the end—that's normal. I mean, instead of, say, http://earth.google.com/download at the beginning, http://6ths7.free67.info/73nds. Junk programs, especially ones that will steal your personal information or reformat your hard drive, frequently have URLs that are cheap to obtain. Another common trick (for phishing sites too) is to use something like http://microsoft.d6shc.com. Although many people say “Oh, it's Microsoft.com, must be good then”, anyone can change the first part (microsoft, in this case), known as the subdomain, to whatever they fancy. The part right before the .com is the only part you actually have to register.

4. If the program didn't pass one of those requirements, or you just aren't sure about it, try googling the function of the program. Chances are very good you'll find another free program with a less questionable background, and quite possibly better features as well.

5. If you really want the program, and aren't sure of its legitimacy, download it, scan it with your antivirus program, and back up your files first or install it on a junk PC just in case. (Of course, you really should have a valid backup at all times; I've got an upcoming feature on making a backup script for yourself.) If your antivirus program comes up with a warning, ditch it and find something better. It's definitely not worth the trouble.


Despite my lobbying for the antivirus industry, I'm not saying the program always knows better than you. If your antivirus program comes up with a warning for a perfectly reputable program, like Microsoft Office or Spybot Search and Destroy, check the warning a bit more carefully, and do some research if you're not sure. Although viruses can infect and damage legitimate programs, it happens less and less nowadays, and it's far more likely that the scanner just made a mistake (or the program was performing a “suspicious” activity, like Spybot accessing a spyware-filled folder to remove spyware).

Part Two: Collected Information
You don't just have to deal with malware, though. Most websites collect information about you, and you have to decide who you can trust with that information. When you visit a website, a certain amount of information can be collected about you automatically, and you can't do a thing about it. This information includes the browser and operating system you're using and your IP (Internet Protocol) address, which uniquely identifies your computer on the Internet. Normally, the website also collects any cookies the website has stored on your computer. You can turn this off, but it has a number of adverse affects on your web browsing, and only total privacy freaks (or the same Internet purists who refuse to use any Web content besides plain text) choose to do so. (One note: Cookies are not programs that can look through your files and steal information. They're not even necessarily bad. That said, cookies can be used to track your browsing and shopping habits; see http://www.tomsarazac.com/tom/opinions/cookies.html for more information about cookies.)

Most of this information isn't really earth-shaking; if you really care about hiding any of it, check out http://the-cloak.com/. It's what you give websites that really matters. For instance, Google, with some settings, collects information about what websites you visit in order to personalize your searches. Most of the time, you have to decide how much privacy you're willing to give up in order to get useful functions.

Try this: Head over to http://www.google.com/dashboard and log in with your Google account. (If you don't have one, just follow along.) Scroll down and check out all the stuff Google has stored about you. Bet you didn't know they stored all the websites you visited after searching while logged in, and all the searches themselves. And even though you knew they stored your contacts, emails, voicemails, and so on (if you use Gmail or other Google products extensively), it somehow seems a lot more impressive and scary when it's all in one place.

Check out these three screenshots:
http://www.thetechnicalgeekery.com/images/Google1.png
http://www.thetechnicalgeekery.com/images/Google2.png
http://www.thetechnicalgeekery.com/images/Google3.png

In the first one, you can see most of the Google searches I made in the last two days, and that I've made 4,913 searches since Google enabled Web history. This catches nearly all of the searches I've made on my home computers, since I'm nearly always logged into Gmail, but I'd say that it probably still only represents about half my searches. (Interestingly, I found that there were searches on my history page I hadn't made today, meaning that I had accidentally left myself logged in on the family computer—oops. If you ever accidentally leave yourself logged in on another computer, you can log in to Gmail, click the Details link at the bottom of the page where it says “This account is open in x other locations...”, and choose Sign Out All Other Sessions.) Still, Google has stored, and still has accessible, about half of my searches all the way back to January 2008. That's kind of cool, and a neat way to look through what you've done on the Internet in the past, but it's also naturally a concern if someone else gains access to your Google account (besides being able to log in and represent you on any Google service, and some others). The other two shots show other parts of my history, including all my stored emails, documents, and many phone calls and texts I've made through Google Voice. Not displayed is also contact information for over 100 people.

The good news is that if you're scared by the web history, you can easily stop it from collecting items or clear some or all items from the history. Just open up your Web History from the dashboard and select Pause or Remove Items, on the left. (It should be noted that Incognito Mode in Chrome does not prevent Web History from collecting items, although you are not logged into your account in a new Incognito window and therefore cannot have your searches collected. If you want to browse totally privately, stay logged out of your account or pause the web history.) Other services like Gmail are harder—you can't really use email without leaving tracks with *someone*, be it Google, Microsoft, or your ISP. However, I generally trust Google with my information; they've had a fairly good record of not throwing your information out the window, especially compared to some other websites. (I've heard some people worried about what might happen if Google was bought out and had a change of ownership; I say that's not currently a valid question, as Google is not within reach of any purchases.)

Facebook is much more questionable. It seems that they change their privacy policy about every six months, and every time they seem to have some absurd clause designed to make them more money that quickly gets picked up by the media and causes public outrage. (Then they provide a public apology and reverse that change, but some others may remain.) Although (at the time of this writing), the privacy policy is fairly reasonable, it's still clear that they track everything you do and keep all your information and posts, and who knows what could happen with them, especially since the privacy policy can change at any time. (For a while there was even a note that stated that Facebook gained ownership of anything you posted on the site.)

The most important thing you need to worry about with your Google, Facebook, and other accounts is that nobody steals your password. If anyone ever gained access to my Google or maybe even Facebook accounts, they could easily impersonate me—they immediately have many of the websites I've visited and therefore know what I'm interested in, all my email, contact information for all my friends, family, and more people, and can change my Google Voice settings so they get my calls. Besides being much easier to do than, say, a cracker stealing half their database or the company deciding to release your information to the public, having your password stolen is one thing you can easily guard against. Choose a strong password, don't write it down, and make sure nobody gets it. Sign out of the computer when you leave it, and immediately change it if there's a chance someone else has stolen it. See http://thetechnicalgeekery.blogspot.com/2009/10/ten-ways-to-keep-your-passwords-safe-we.html for more information on the ways passwords get stolen and how to protect yourself.

I'm seriously considering keeping any information I'm even the least bit concerned about off Facebook and maybe even off other websites, and put it on my own website instead. I run the server, so nobody is going to mess with my information except by breaking into it.

EDIT: The blog was capitalizing the image links, causing them to break. I renamed the files and the links.

--
Soren "scorchgeek" Bjornstad
http://www.thetechnicalgeekery.com

Yesterday it worked
Today it is not working
Windows is like that

Copyright 2010 Soren Bjornstad.
Verbatim copying and redistribution of part or all of this work
is permitted, provided this notice is preserved.

Wednesday, March 24, 2010

Random Failures, SimCity, and the Core i7

These don't seem to go together, do they? In fact, if you think the title makes sense, you're lying, crazy, or you've been following what I've been doing the past couple of days.

Everything started when I woke up on Monday, my first day of spring break. I slept until about 8:30, woke up, and figured I'd check my email and maybe read the news before breakfast. I walked over to my computer, which was in standby, hit the power button, and...nothing came up. The fans started, but the monitor stayed in power-save. Thinking nothing of it, I rebooted.

Guess what? The monitor still stayed in power-save mode. Okay, suppose the monitor's bad. Or maybe the cable; the last time the screen was all green, I unrationally suspected the graphics card and bought a new one before I realized the cable had died. But my second monitor wasn't picking the signal up either. So I walked down the stairs, grabbed our 21-inch TV, which has a standard computer input, lugged it up, and plugged it in. Power back on. Nothing.

I started thinking, "Hmm, what have I changed that might have caused this?" Thing is, I hadn't installed or changed anything. I had recently installed a sound card, but that was about a week before, and it had worked flawlessly up until then. No, it seemed to point toward some sort of random hardware failure.

I guess the graphics card has to be bad, right? Pull out the graphics card and plug into the graphics built into the motherboard. No luck there either. Maybe the settings are still set to use the nonexistant graphics card? Reset the BIOS settings. No luck.

The computer didn't seem to be POSTing (passing the power-on self test), since it wasn't making the usual sounds it did right before it went to the boot menu. Only problem was that I couldn't see where it failed, since the monitor wasn't working. And the oh-so-unhelpful motherboard (which came in the HP system I bought a couple of years back) didn't make any error beeps or have any helpful lights to tell me what the problem might be.

I did some googling, and found someone who suggested I unplug the computer, hold the power button for 30 seconds, and plug it back in. Worth a shot, I suppose. Surprise, surprise, it didn't work. I removed the battery that holds the settings and tested it, and the battery tester said it was low. I suppose it's worth a try, right? So I bought a new battery. Guess what? The battery tester said it was low. Guess the battery tester's broken too (or at least can't measure that type of battery properly). Naturally, the new battery didn't fix anything.

I started taking out RAM, unplugging the sound card and hard drives, and more, trying to isolate the source of the problem. The same thing kept happening. I was absolutely stumped.

Defeated, I called the Best Buy Geek Squad, and they told me they would look at the system for free. So I dragged it over (getting envious looks and exclamations of how large my case was from employees), and had them look at it. They swapped out the graphics card and had no more luck than I had. The final report was that my motherboard was probably bad.

That was what my assumption had been, too, but I hadn't really wanted to admit it. With nothing else left to do, I went home and ordered a new one. Having a fair amount of money sitting around, I decided that I might as well make the best of it and buy an upgrade that would last me a while, so I bought 6 gigabytes of RAM, a Core i7 processor, and a motherboard. The total bill was a somewhat painful $720.

When it came today, I spent three hours or so cracking the case open and installing the stuff. I had never installed a processor before, and I'm not sure I did such a great job at applying the thermal grease (which goes between the processor and the heatsink), as it seems to be idling at a fairly high 44 degrees Celsius. (I set an alarm to notify me if the temperature breaks 60 degrees, so I know it's starting to heat up and I might need to fix this.)

Nevertheless, my new setup just flies. I installed a clean copy of Windows (and experienced inexplicable freezes during the start of the installation), and there are hardly any delays. I actually feel like I should be typing and mousing faster to compensate! I installed SimCity 4. On my largest city (which I had nearly stopped playing because of the annoying frame rate and delays), the scrolling is totally smooth, I don't have to wait on dialogs, and it loads in a fraction of the time it used to.

I should reiterate how annoying this whole thing was. To have done nothing at all wrong and to suddenly have the system not work at all is unbelievably frustrating. In all our expectations of reliability, remember that someday your computer could just quit working--yet another reason to have backups and have some sort of plan for how to keep working if your computer suddenly fails.

I uploaded four screenshots of SimCity 4 (in the city I was talking about) so you can see how the graphics take some oomph to be displayed properly. Note that this is only medium detail, too.
http://snipurl.com/v1nmy

--
Soren "scorchgeek" Bjornstad
http://www.thetechnicalgeekery.com

Microsoft is not the answer.
Microsoft is the question.
The answer is "No."

Copyright 2010 Soren Bjornstad.
Verbatim copying and redistribution of part or all of this work
is permitted, provided this notice is preserved.

Thursday, March 11, 2010

Concept Idea: The Phone Control System

Concept Idea: The Phone Control System

Note: the Concept Idea is a new series I'm hoping to start describing technology I envision. They are not anything that has happened, nor is necessarily going to happen.

We've all experienced someone's cell phone ringing at an inconvenient time. Even more annoyingly, people have developed a nasty tendency to ignore everyone around them at times when they should be paying attention and use their phones instead. Even more importantly, there are problems with people communicating information that is supposed to be kept secret. This can be done by text message, or by taking a picture (for instance, a student sending a picture of a test to his friend who is going to take the test the next period). Some people suggest jamming signals to prevent people from using their phones in certain places, but this hardly seems like an ideal solution. Something better would look like this.

Point 1: Control zones
Any institution that desired to put restrictions on cell phone use could purchase a control box that allows them to do so. With the control box, three other nodes would be provided, which would end the controlled zone and form a restricted-area triangle. These nodes would prevent any restrictions beyond the location of the triangle. When setting up the zone, the people responsible would have to make sure that the zone did not extend beyond their own property. (If a conflict were to occur, there could be an inspector to make people adjust the controlled area.) I don't know exactly how such a thing could be set up, but this is, after all, a concept.

Point 2: Control Levels
Level 0: Unrestricted—cell phones would work normally as if they were outside any control zone.
Level 1: Silenced—If sound level was above vibrate, the level would automatically be lowered to vibrate on any phones that were on. (Leaving the area would restore the previous setting.) Incoming calls could be received, but answering the call and placing calls would be prohibited. Attempting to place or answer a call would give a message instructing the user where to go in order to talk. Text messaging and internet use would be allowed, although the backlight level would be lowered to minimize distraction to surrounding people in the dark. This would be a good mode to use in many public places, like concerts and movie theaters, because it would allow people to be notified of important calls and events (because, let's face it, there are some times when being in contact can actually be important), but not distract others.
Level 2: Communications Blocked—Calling, text messaging, internet use, and any other activities that used a cell phone signal would be blocked, as if there was no signal available. Once again, attempting to do one of these things would trigger a message pointing the user to an unrestricted area. The camera, calendar, calculator, some iPhone apps, etc., would be unaffected.
Level 3: Communications+Camera Blocked—To prevent removal of important information (like pictures of tests) from the area, the camera would also not work. Attempting to use the camera would trigger a message stating that no photography was permitted in the area. (Although one could bring in a dedicated camera to bypass this restriction, someone using an actual camera would be easily spotted.) This would probably be a good level for schools, so that students could use tools that would be appropriate for academic use, but not be able to use phones to cheat or talk to friends.
Level 4: Cell Phone Blocked—Any cell phones that were on upon entering the area would turn off. Attempting to turn on the phone would result in a message directing the user to move to an unrestricted area to use his phone. This would be a good mode to use, for instance, in testing environments. For instance, when I recently went to take the SAT, people were discouraged from bringing phones in, and anyone whose phone went off during the test would be dismissed and have their scores canceled. For me, I needed my phone to call for a ride home when the test was done, so I resorted to removing the battery and placing both the battery and the phone in my bag. Having this mode would remove the problem completely.

Point 3: Emergency Use
I can just see the people who are opposed to this sort of control going, “But what if there's an emergency?”

o An emergency switch would be located inside the battery compartment of each phone (to prevent accidentally triggering it). Turning the switch would allow the phone to pass through the communications and phone blocked modes (after answering a question on the screen as extra confirmation). To prevent abuse, the phone would immediately and automatically connect you to 911.
o The control box, which would be located in a public place, would have an emergency lever that would call 911 and activate emergency mode.
o Emergency mode would be triggered by turning the switch on one's phone or by pulling the lever that would be situated on the control box. Emergency mode would have the following effects:
--The mode would immediately be set to unrestricted, allowing anyone to make any calls.
If the mode was triggered from a phone, the control box would also submit an emergency call.
--Whatever device triggered the mode would be connected to 911.
--An event would be logged on the control box stating what device triggered it, to track down people setting off false alarms.
--An alarm would sound on anyone's phone who had been blocked from switching it on within the past few minutes, allowing them to make any important calls they had been trying to make. A message stating that an emergency mode had been triggered would also appear on the control box.
--The mode would remain in unrestricted until an administrator reviewed it and reset the mode.

Point 4: Control Box
The control box would be located in a public, easily accessible place. On a display at the front of the control box, anyone would be able to see the area the zone extended to and the mode the area was currently in. An administrator could also log in from the control box to change settings, the mode, and review logs and emergency events. Logging in would require a key and a passcode, to avoid anybody messing with it. The control box would also log any failed logins.

Point 5: Technical Aspects
Setting up a system that could control phone use effectively would be fairly complicated, but could be accomplished by having phones listen for signals from control boxes. The signal would state the current zone the system was in, and would immediately cause their respective effects on the phone when received. Also, all communications would be intercepted by the control box, and provided that they weren't from a banned phone, sent on to the tower. To lower the chance of phones' restrictions being cracked and broken, it could be made simply illegal to own such a phone. Therefore, anyone caught using a phone breaking restrictions would be automatically pointed out as guilty. In addition, control boxes could be set up to block all communications from a phone (ban the phone) that had been caught breaking the restrictions. As extra defense against this, control boxes could log events that occurred on the phone, such as a ringtone sounding. (Perhaps that's a little bit overboard, as it could be seen as an invasion of privacy; it could also possibly be spoofed by having one's cracked phone firmware send incorrect messages to the log. If the system really worked, anyone whose phone went off in violation of restrictions might be so unaccepted by society that someone would report them anyway.)

Point 6: Setup
Of course, phones can't be made to respond to these signals out of the blue, nor can my suggested emergency switch be reasonably added to phones that already exist. The simplest way, therefore, to get any such system to work would be to simply include the necessary software and logic on all new phones, and after some period of time (say, 7 years), all phones that were purchased before that time would simply cease to work (after sufficient warning from the provider, of course), and the rest of the system could be implemented.

Point 7: Conclusion

Naturally, I have no leverage whatsoever to get something like this working. It's a very ambitious concept, and I have severe doubts that our society will welcome anything like this. Maybe you don't agree with me on all the points; maybe you don't even agree that something like this is necessary. The thing to remember is that having phones ringing during performances and at other inappropriate times is extremely annoying, and that people have a tendency to try to use phones when it is not reasonable to do so. If we can't trust people to take care of this themselves (and it seems that we can't, from the past few years), I see no other real solution than to implement some kind of control. I don't even trust myself to always turn off my phone at the right times (and I'm writing this)—more than once, I've discovered I've left my phone on during school, or an equally bad time.
--
Soren "scorchgeek" Bjornstad
http://www.thetechnicalgeekery.com

Microsoft is not the answer.
Microsoft is the question.
The answer is "No."

Copyright 2010 Soren Bjornstad.
Verbatim copying and redistribution of part or all of this work
is permitted, provided this notice is preserved.

Wednesday, February 24, 2010

Complex technology...better?

At my old school, the administration once had a brilliant idea. All the clocks were frequently unsynchronized, and so people didn't know what time the bell was actually going to ring. So they decided to buy atomic clocks for every room, naturally assuming that such clocks would always be right. Great idea, you say? Not quite. They bought all the clocks, put them up, and followed the directions to synchronize them. Unfortunately, the time that they synchronized to was simply incorrect. They ultimately had to put all the old clocks back up and were left with a huge stack of non-working atomic clocks that they apparently couldn't return.

Why is it that complex technology invariably just doesn't work as well? Of course, the easy answer is that there's simply much more to go wrong. But, even if you assume that everything works perfectly, simpler stuff tends to work better anyway. I've tried numerous methods of keeping calendars, lists, and reminding myself to do various things. Ultimately, I always find something new, think it's a great idea, and then I end up missing things anyway. The only method I've found that actually works nearly every time is putting a sticky note on my monitor.

Why does this work? First of all, I look at the monitor whenever I turn on my computer and while I'm working on it, which is fairly often. Also, the computer is in the middle of my room and on a desk where I keep other assorted objects, so I end up looking at it anyway. In contrast to a computerized calendar like the one included in Microsoft Outlook, it simply works better. With Outlook, my computer may make a noise at the right time or send me an email, but sticky notes can't accidentally be turned off, nor can a bug prevent them from working. They may fall off, but that's a small chance compared to the possibility of me accidentally deleting the event or having the program closed. Besides, it's much harder to miss a sticky note that is in your line of sight than a window buried under your 60 tabs of internet work or an email in your 150 unread messages. I have even tried my cell phone. For some people, this works okay, but besides the hassle of inputting an event using your phone keypad, I don't always have mine with me. When I go out, I usually do, but it's frequently turned off because I'm in school or something similar. In the rare instances when I actually get the notice, I do, in fact, remember, but this happens so rarely that it doesn't actually help. All this just goes to show that, despite the fact that there are plenty of complex organization systems that work, if you do something extremely simple and get in the habit of looking at it, you'll be very well off. (I once read a story about a professional attending a conference about cutting-edge mobile technology who was using a paper planner.)

This same thing came into my head when we recently learned about the accelerator issue in certain Toyota cars. If you're reading this far in the future or never picked up on it, accelerator pedals were simply getting stuck, which had been an occuring issue on those cars (nobody apparently saw fit to fix the problem earlier). The bigger problem, however, was that the brake pedal was not designed to override the accelerator, since it was computer-controlled. (Of course, here, a possibly more relevant question is "What idiot decided that going faster was more important than stopping?") In fact, if you held down the brake and then stepped on the accelerator pedal, your car would still move. In certain cars which recover power when braking, having the brake electronically is a necessity. But in most of them, a mechanical brake would have worked just as well, and the problem would have been simply annoying, rather than life-threatening, when one could actually stop. What's the point of adding another unnecessary layer of complexity?

I've come to the conclusion that simpler things are nearly always better. Don't let the crazy marketing fool you.
--
Soren "scorchgeek" Bjornstad
http://www.thetechnicalgeekery.com

Microsoft is not the answer.
Microsoft is the question.
The answer is "No."