Heat in a large skillet or wok

• 3 tablespoons high temperature vegetable oil (Canola or Coconut)

Fry in the oil for a minute or two:

• 1 Stalk Lemongrass, peeled, sliced and ground in a spice grinder
• 1/2 Teaspoon Chile Flakes (Add up to 1 1/2 teaspoons for extra hot)

Add:

• 3-4 long asian eggplants sliced diagonally into 3/4″ sections (baby eggplant or even regular eggplant will do, but the long asian eggplants have fewer seeds and they stay together better as they cook)
• 1 carrot thinly sliced or julienne (yes I know carrots aren’t strictly Thai, but they taste so good)

Stir frequently but keep a lid on the mixture to retain heat.  As the eggplant cooks (5-6 minutes), monitor the level of oil, adding up to another tablespoon if the eggplant absorbs that much.

When the eggplant is not quite cooked through, add:

• 1 tablespoon of oil
• 1 onion cut into bite-sized pieces
• 3 cloves of thinly sliced garlic
• 1 large portobello mushroom sliced into 1/4″ strips

Stir for a few minutes then add:

• 1 tablespoon fish sauce
• 1 tablespoon maple syrup (Hey, not Thai either, but I live in Canada now!)

Stir until the eggplant is fully cooked and the onions are clear, turn off the heat and immediately stir in:

• 20 fresh basil leaves, ripped into small pieces

Serve with Coconut Rice

• 2 cups jasmine rice
• 2 cups water
• 1 can of coconut milk

First, I wash the rice, then add the coconut milk and water.  The trick is to fold the rice a couple of times as it cooks, in order to move the coconut milk down into the rice.  Without folding, the coconut milk will just collect on the surface.
Also, when the rice cooker turns off, give the rice one more quick flip, and then let it sit to absorb the coconut milk.

I don’t add any sugar.

Oden is my favorite Japanese winter food (ah, seasonal, those Japanese) and is best prepared in a Crock pot (slow cooker for the brand sensitive among you.)

The longer you cook oden, the better it tastes.  For best results, start the night before and set your cooker on low for up to 24 hours. On the low setting, I find that my oden starts to really taste like oden only after 12 or 14 hours, and really starts tasting good at the 20 hour mark.

Here’s what I use for a vegetarian version:

Start by preparing the Kombu broth in with a big stock pot with 6-8 cups of cold water. Throw in one piece of kombu seaweed (4×8 inches or 6×8).  Slowly bring to just to a boil and then turn the heat down very very low.  You can take out the kombu now. 

While the kombu broth is heating up, prepare:

• 1 daikon radish
• half a dozen red radishes
• 4 carrots
• (red radishes, potatoes, turnips, any root vegetables work great)
• 8 boiled eggs (my favorite)
• 2-4 blocks deep-fried tofu or 1-2 lbs firm tofu
• fish cakes (for non-vegetarian)
• 1/4 cup soy sauce
• 4 tbsps sake (Japanese rice wine)
• 1-2 teaspoons sugar

Veggies:
Cut the daikon and the carrots into 1.5″ thick rounds.  Cut any other root vegetables into similar large chunks (red radishes can be left whole).

Eggs:
Hard boil and peel the eggs.

Tofu:
If you can get deep-fried tofu at your supermarket, it often tastes the best.  If the blocks are large, you can cut them into pieces.

If you don’t live near an asian grocery that has deep-fried tofu blocks, you can fry them up yourself. I don’t use a deep fryer, rather I just put several tablespoons of a high-temp vegetable oil (canola or coconut seem to work fine) in a pan.

Cut the firm tofu into large triangular blocks.  I find that a 1-lb tofu block makes a good 6 pieces.  I then fry the tofu on each side in the hot oil, 4-5 minutes on a side until they tofu starts to get crispy.

Put everything together including the soy sauce into the crock pot and set it to low.

Go to bed.
Have oden tomorrow! ]]> http://www.metapaso.com/blog/damon/food/2009/01/28/24-hour-oden-recipe/feed/ 0 http://www.metapaso.com/blog/damon/technology/2008/02/09/os-x-needed-improvements-for-new-users/ http://www.metapaso.com/blog/damon/technology/2008/02/09/os-x-needed-improvements-for-new-users/#comments Sat, 09 Feb 2008 19:38:03 +0000 Damon http://www.metapaso.com/blog/damon/travel/2008/02/09/os-x-needed-improvements-for-new-users/ Ignoring Apple’s current and enormously successful “I’m-a-hipster-Mac-and-I’m-a-loser-pc” advertising strategy, I’ve come up with 6 items that I think should be included with with every Mac to make the system easier for brand new users and particularly for older new users. These issues come from my real-world attempts to teach my dad how to use his new Mac and the frustration he experienced with an operating system that—to his newbie eyes—behaved inconsistently.
Steve! Pay attention here, please! New users are feeling left behind with the MacOS!

1. Put the labels on the keyboard (OR enable the menu system to show natural language shortcuts)
Apple engineers have come up with an ingenious series of symbols to represent the various function keys on an Apple keyboard. Everyone knows Command (cmd), but there are half a dozen more, from (shift) and (option) to (esc) (delete) and (forward-delete). It’s nearly impossible for new users to take advantage of the quick-key combinations because in addition to having to learn what the combinations are, new users have to remember the language of these new symbols. Solution: put the labels right on the keyboard, OR, switch to natural language keyboard shortcut hints on the menu system.

http://www.danrodney.com/mac/index.html to see a few of them.
http://www.matias.ca/osxkeyboard/index.php

2. Fix Dragging and Dropping in Finder Column View
Don’t get me wrong, here. Column view works great in finder. New users need a small leap of understanding to understand column view (understanding that the next column shows what’s inside the folder). My dad took to it quite quickly. The problem for new users is that click+drag on items in column view behaves erratically. Because the column view jumps around, new users just can not get items moved into the correct folders. Apple, I don’t know the answer to this, but get your UI engineers on the task; it needs to be fixed.

3. Fix the shift+arrow key problem
I teach new users to hightlight things using shift+arrow keys. For older users who may be unfamiliar with trackpads and mice but who have used typewriter keyboards their whole lives, keyboard selection is an easy easy way to ensure precise selection in the Finder, in documents like Word, and even in apps like iPhoto. It’s like learning how to drive an automatic after driving standard for most of your life. Three buttons and you’ve got it. However, shift+arrow key selection is broken in OS X Finder.
Try this in Finder:
<ol><li>open any of your folders that have a long list of items.
<li>Click on one item somewhere in the middle.
<li>Now, hold the shift key down with your left hand, and use the up-arrow key to begin selecting items one at a time upwards.
<li>Pretend you’ve selected one to many, so you want to go back one–> Keep holding the shift key down and press the down arrow.
<li>What the $%$# happened? Instead of just retreating by one, the range of selected items is <italic>increased</italic> in the downward direction.
</ol>
Not only does this behavior not make any sense, but it’s contrary to the way these same shift+arrow keys behave inside documents. Try this above example inside TextEdit or iPhoto or iTunes, and the behavior is more intuitive and yet <italic>different</italic> from Finder.

4. Add a cut/paste feature in finder.
Every application has cut/paste. Why doesn’t Finder?
I’ve read a lot of blogs and forums on this issue. The basic objection from current Mac users is that this feature exists in windows, so Mac doesn’t need it. However, the lack of inclusion of a Cut/Paste feature in finder is a basic violation of Apple’s own user accessibility guidelines for providing mouse functionality

5. Allow copy/paste into the same directory in Finder.
Every other application in OS X allows you to copy and paste into the same region. Why finder disallows it is beyond me. Yes, Finder has the Duplicate command, but curiously, when you “Duplicate” something, the resulting file is labeled. “Copy”. This is a UI guideline violation of the first degree.

5. Get together with Canon and figure out how to fix the problems with the camera. Whappened to “it just works”

6. Create put forward–> and backward <– arrows in the Preview application so that you can easily see the next and previous pictures in a folder.
This one was suggested by my Dad. He has used computers a total of about 2 hours and already can see that this feature is missing. I daren’t explain the complicated method of selecting all the photos he wants to preview and then dragging them together onto the preview icon. This is difficult for him (the work-worn callouses on his fingertips make the capacitive-sensitive trackpad slow to respond) and invites mistakes such as accidentally dropping all the photos into a random folder.

7. Add Rename to the Edit Menu in finder.
I tried to explain to my dad that anything he wanted to do in any application, he can find if he searches through the menu system. Not true. Rename is not in any of the Finder Menus.

8. Image Capture straight to iPhoto.
This one seems so obvious, I can’t believe it hasn’t been done yet. Why is this necessary? I’m not sure why the mac mantra “it just works” doesn’t apply to a whole range of Canon digital cameras, but at least for my Dad’s Canon S3-IS, iPhoto will not import videos and often refuses to import all the pictures. My dad is therefore forced to use Image Capture, and then find all the files and drag them into iPhoto. This is ridiculous and should have been fixed many years ago.

How to start a flame war
Suggest an improvement for OS X
How to start a bigger flame war
Suggest an improvement for Apple hardware.
How to start an even bigger flame war
Suggest a new feature for OS X that no one has heard of.
How to start the biggest flame war
Suggest a new feature of OS X that Windows already has.
How to set loose hell on Earth.
Suggest a new feature for OS X that Windows has had since windows 95.

My Basic list of complaints with OS X:
1. Inconsistent keyboard support
2. Beautiful, sleek, hard-on-the-eyes interface that gives me brushed metal fatigue in under an hour.
3. Must pay to release full-screen functionality in Quicktime.
4. Like Quicktime, Finder functionality is limited. Yet there’s no option to buy Finder Pro.
5. Inconsistent menu item names across iLife apps.
6. Inconsistent Keyboard support (did I say that already?)

We visited Daniel Libeskind’s latest work at Toronto’s Royal Ontario Museum (ROM), the older classically-ornamented ROM structure now dominated by a architect’s crystalline facade which finally opened in 2007.  It was a delight to see the interior spaces after passing the construction along Bloor St. for the past two years.

At $20, I won’t be visiting the ROM as frequently as it deserves, but it was a real treat for the day, including my favorite of the many exhibitions: “Early Typewriters” from the collection of Torontonian Martin Howard.  The ROM staff has tucked “Early Typewriters” into one of the hardest-to-find of Libeskind’s many niches in the new structure, a windowless room where the dozen late 19th and early 20th century typewriters stare back from behind glass cases.  Depending on the direction of your tour, the display might be an antechamber or postchamber to the heavily advertised dinosaurs on display in the remaining rooms of the second floor.  The Dinosaurs you can see from the street.  The typewriters you cannot.

I’m sure that the the gaggle of schoolboys, exploding through the museum like a sonic clusterbomb, unable to heed the constant shushing of their teachers—they will be twice as excited to see the Montana-born T-Rex silently snarl back at them as to see the typewriting antiques.  Of course, unlike these 6th-graders, I don’t know the names of every known descendant to the allosaurs, tyrannosaurs, or diplodocii, so I focused keenly instead on the pre-QWERTY keyboards and daisy-wheel print-key technology of these early typewriters, some of their frames hulking like prisons for the mind, others exquisitely tiny, their miniature platens and keys supported by sturdy reduced-footprint frames.

I want one.

And just this same afternoon, after our visit to the ROM, Melanie and I were touring Renzo through the Distillery District (where Mel has her photography studio) when we ran into Ryan Barrett, “Canada’s foremost mousetrap artist.” Sadly, I couldn’t find a web presence for Ryan, but I did find a link to one of his mousetrap-plastered, resin-coated public art installations in Kelowna, BC.

Aside from moustrap-encrusting art pieces, Ryan has a fascination for the analog world of antique typewriters, and the 20-minute tour of his studio space included half a dozen working models that he uses for artist statements, art installations, and other typing needs.  At the ROM, glass cases protected the machines from my salivating interest, and then only hours later, there in his studio, I was able to put my fingers on the same machines and clack their keys.  Marvelous!

Powered by ScribeFire.

The video shows clips and photos from our recent trip through Mexico narrated by me in a monologue about beachcombing.

We had planned only on trying to hitch a ride from Alejo and Guadalupe’s ranch with whoever had space to take us out to the road. Julio’s wife Andrea confirmed that several buses passed each afternoon, and most of them stopped at “el tronque–the intersection” to pick up passengers, so as long as we got to the pavement before noon, we’d have a good chance of catching a bus southward.

View to the ocean at San Cosme from the top of the pass

But on the morning of our departure, luck and fate interceded. We ran into Juan El Vaquero and he said that he was planning to fire up his truck and drive all the way to Ciudad Insurgentes. We could catch a ride with him (obviously, for some cash exchange), up the mountain pass, out to the tronque, and 40 miles south into town, ensuring at least a place to stay or a bus ride from the real station at Insurgentes, and avoiding a possible marathon wait at el tronque.

Juan’s car exemplified the state of Baja automotive technology: an early-80s toyota pickup with a steel cage on the back, he was not immediately able to start it because he had lost the key, needing only “a few minutes” to hotwire it—a process that involved disconnecting and reconnecting several wires in the ignition column. Of course, whenever an additional wire was needed,

Juan simply sought out any unused wire from under the hood (and believe me, there were plenty), and tore it out to be used in his hotwire project. That the car would run with so many disconnected and broken wires flailing out under the hood was completely astonishing, but after a battery replacement and gas siphoned into his tank, the car did fire up…

Juan’s Jalopy

…not, however, before Mel and I found a more secure ride in a 4×4 pickup of some Arizona gringos headed out. We threw our bags in with them and made it easily up the thousand foot cliffs and 90 minutes of dirt to the tronque intersection with the highway. As we stopped at the tronque, we saw Juan pulling up behind us in his rattling truck.

Casting our lot with Juan el Vaquero and his jalopy Toyota

Our dice were cast. We threw our lot in with El Vaquero, tossing our bags into the bed of his pickup, and driving out onto the highway. Two quick stops–first at the tronque restaurant for snacks (including a beer for the trusty vaquero to go along with his plastic bottle of rot-gut tequila), and then at his birthplace, a ranch down the highway about half an hour. In the dusty yard, we watched a burro swat flies from its back and a half-dozen chickens stratch their way from fence to fence, and Juan smiled through a brief conversation with his kind-faced, mustachioed aunt—and back onto the highway with very little delay, cruising between 35 and 45 miles an hour, the traffic racing past us in both directions.

At km 16 from Insurgentes, the noise began…a kind of thumping or rattling that caused Juan and I to interrogate each other, mutually deciding that the rattling must be something loose, perhaps the air filter cover banging against the hood, or a sloppy bolt on one of the few remaining parts in the engine compartment.
After a few kilometers, as the rattling grew louder, Juan downshifted from 5 to 4, and as he let out on the gas, the engine quit. Series shifting down to 3 then 2, he couldn’t get the motor to re-ignite, and we slowed to a stop at a long straight stretch of the narrow highway.

Broken Down on Baja Highway 1

Juan connected and disconnected a couple of wires from the loose bundle under the steering column, trying to get the starter to engage, but the battery, which began the day in weak condition and had required a jump, had given up most of its charge to the first stage of our journey. It would only weakly turn the engine over one dissipating tug at a time. Juan el Vaquero pulled apart the last connection in his nest of ignition wiring and the fuel pump stopped. He popped the hood, and we searched to see if something was loose that could be quickly repaired. We found nothing. The emergency brake apparently didn’t work (perhaps the cable had been scavenged long ago for some other project; anything that wasn’t strictly necessary to the motion of the vehicle–and in my opinion a few items that were–had been stripped) so I blocked the tires with a couple of rocks. Mel took advantage of the break to use the desert restroom behind a cactus.

Thinking that the engine had just died because of a temporary short or break in the wad of ignition cables, I suggested that he connect the pump wire and that we could push, assisted by a slight downward slope on the road ahead.
Juan at the driver side, Melanie at the passenger door, and me on the rear bumper, pushing a beat-to-shit calico toyota of early 80’s pre-electronic ignition vintage, along the blacktop of the baja highway one, in blinding mid-afternoon sun, traffic whipping past us in both directions…with the additional suggestion of putting it in third, Juan jumped aboard and popped the clutch twice before she caught hold and ran, with me struggling to catch up and Mel sliding the middle of the passenger seat, we were off again…

…for about a mile. The rattling quickly grew into a pounding whose speed matched the engine rpm, and the poor little truck would die every time Juan let off on the gas to change gears. Smartly, Juan eased the foundering jalopy over the next hill and halfway down the straightaway, giving us both a downhill advantage in case we needed to push again, and a decent view in both directions to give passing cars a chance to slow down.
Remember, this is a two-lane road with absolutely no shoulder, where both lanes are narrower than the average in the U.S. Most two-lane highway construction in north america specifies a 40-foot roadway including the shoulders, the Baja road varies from 19 to 24 feet, this particular well-maintained section spread to probably about 22-feet across…so even this tiny truck of Juan’s was blocking nearly half the road.

We cracked the hood and peered at the smoking engine, scratching our heads, with Juan clearly concerned about his poor truck and about how we were depending on him. It was true that the sound matched the engine speed, but we we weren’t convinced that it was an engine problem. There was still the possibility that the fan was rattling or a belt was loose causing the knocking, or a loose engine mount.

We decided to give one last push, crack the hood while it was running, and see if we could spot the noise. So once again, two gringos and Juan, heaving the car, the clutch out two, three, four times before the engine sparked and rattled. I ran around to the hood and pulled it open, seeking the source of the rattle as the smoke cleared. With the hood up, the problem sounded more like grinding metal, coming straight from the heart of the quaking engine.

“Has to be valves or maybe even throwing a rod bearing,” I said to Juan who shook his head in glum agreement. We pushed the car off the asphalt onto a bit of gravel, and waited.

Juan assured us that a bus would be along shortly, probably at about 3:30, but he wasn’t sure if it would stop for us. Mexican buses even in the Baja hinterlands are running now on tighter schedules and drivers can face discipline for stopping to pick up random passengers along the road, not to mention the threat of banditos.

We sat on the ground behind the pickup, shaded by the tailgate, and listened to the cowboy talk.

“This is why I prefer my horse,” he said. “It may take a long time, maybe one, two, or three days. But I just give him food and water, and we get there. Never any problems.

“You may not believe it, but I have ridden my horse all the way to Insurgentes. It takes three days. The first day I ride from the sea up the mountain to the top of the pass. The second day I ride through the old rancho where my uncle lives and camp in the desert. On the third day, I arrive in town.

“I have even ridden as far as the Pacific. There is a three-day parade of horses there, in the summer. All the horsemen from around here, from Insurgentes, from Constitucion from the ranchitos from La Paz, some from Los Cabos, the all ride together for three days along the coast. Last year there were more than 500 horses–what a party!

“On one of the days, there’s a chance for everyone to show off what his horse can do. Each cowboy has a chance to tell everyone his name, where he’s from, and if his horse can do something special. Some horses can dance a little, or lie down or walk backwards or trot a certain way. Some horses have nothing special, but that’s just it, ‘My name is so-and-so and this is my horse ’such and such’. Not everyone has a special trick, but they still get to present themselves.”

We laughed a bit at the idea of horses having different skills, and conversation subsided for awhile. Mel and I staring at the Cacti and mesquite along the roadside, Juan peering into the face of each passing driver to see if he recognized anyone.

“I think,” he said at last, chewing on a bit of grass, “I don’t want you to misunderstand me, but I think this was caused by a woman who is trying to do me harm.”

I laughed, but seeing the earnestness in his eyes, I waited for him to continue.

“There is a woman, the mother of my son. We lived together for seven years. I tried very hard to love her. Seven years we lived together.

“In the end, I found that she had another man, and I left her. I said no more. She is very angry, and I heard that she is paying people to do bad things to me. I can’t tell you what those things are, but I have heard that she has a little money now and has asked people to do bad things. I think that this problem with my car comes from her.”

Of course, if I were a betting man, I would say that the odds-on favorite culprit was NOT the malfeasance of a hired agent but rather the raw age of the aggressively pillaged his—coupled with artificially prolonged decrepitude and entire absence of proper maintenance. Plus, the obvious tricks for disabling a vehicle such as flattening tires, draining the battery, emptying the fuel tank and ripping out all the wires from under the hood—all these had been done apparently by Juan himself the last time he used it—it would take a serious level of ingenuity to get a car to fail in a way that Juan el Vaquero couldn’t get it to run.

“The way I look at it,” I said, “is that even if someone tries to do something bad, they’re probably just helping you. Instead of hurting us, the guy who disabled your car saved us from a big accident that was waiting for us down the road. As long as we’re safe, everything is good.”

“Well,” he laughed, “That’s the way I look at it too. It’s good to be alive. We’ve been saved.

“Anyway, the next time you visit,” he continued, “I’m going to have my own car with windows and doors that lock, so no-one can mess with my car. It will be nice, and you’ll say, ‘Juan has a great car.’ Oh, here comes the bus.”

Full windshield reflected in our eyes, the bus eased over the hill, and Mel and I stood by the side of the raod trying to flag it down…no luck. The driver gave us a ‘no way’ shake of the hand, and hurtled past without even slowing down.

“Ah.” he said. “Aguila never stops. They’re not supposed to stop, but sometimes the drivers are nice and they pick you up. Maybe the next one.”

Of course, this made Mel even more nervous, as one hour of our afternoon had already slipped away, and less than two hours of daylight remaining. We agreed that we shouldn’t abandon Juan, although it was tempting to pull out the ‘gringo card’ and flag down the next passing RV.

But only moments later Juan spotted a friend of his and whistled him to stop. They negotiated for a few minutes and his friend Gaspar would be returning to pick us up after he dropped somethings off at the ranch. We had at least an outlet plan…
So another hour later, Gaspar did indeed return in his modern Ford Ranger, king cab seats for Mel and I in the back, and a top speed reaching somewhere between 80 and 85 miles an hour…a mere fifteen minutes into the bus station at Insurgentes, and a bus arriving half an hour later…we made it just fine, safe and happy, ready for the next step in our journey: La Paz.

La Paz

Powered by ScribeFire.

• Dell Latitude X1
• 768MB RAM
• 80GB internal Drive: 40GB ntfs / 30GB ext3 / 512MB swap
• Intel 915 built-in graphics chipset
• Dell 1280×768 widescreen monitor (Built-in on laptop)
• External Monitor is Samsung SyncMaster 151v 1024×768
• Ubuntu 7.10 (Gutsy)
• Xinerama enabled

I finally went for the Gutsy Upgrade to my original Feisty installation. Part of the reason I wanted to upgrade was for Gutsy’s built-in Screen Spanning support. However, after mucking around with it for a couple of hours, I couldn’t get a stable screen setup either spanned or just a single monitor, so I just switched back to my old xorg.conf files and I run a script to install the correct one depending on my needs.

I have three scripts for managing my xorg.conf. I keep them in a “scripts” folder on my desktop.

1. SetDual.sh copies the dual-monitor xorg.conf.dual file into place to get ready for dual-monitor operation.

   1 2 3 4 5 6

   #!/bin/sh # SetDual.sh by Damon Erickson www.metapaso.com # this script copies the dual-monitor xorg.conf file # to be used for a dual-monitor setup on a Dell Latitude X1 gksudo cp /etc/X11/xorg.conf.dual /etc/X11/xorg.conf # EOF.

2. SetSingle.sh is the partner to SetDual.sh. It moves the single-monitor configuration file into place.

   1 2 3 4 5 6 7 8 9

   #!/bin/sh # SetSingle.sh by Damon Erickson www.metapaso.com # this script copies the single-monitor xorg.conf file # to be used for a single monitor (laptop only) setup on a Dell Latitude X1 # requires sudo permission   gksudo cp /etc/X11/xorg.conf.single /etc/X11/xorg.conf   # EOF.

3. openbox.sh is no longer needed now that Metacity has better multiple-monitor support built in (Gutsy 7.10), but I did get used to OpenBox’s slimmer title bar an roll-up windows, so I still have the script.

   1 2 3

   #!/bin/sh openbox --replace # EOF.

Then I have two separate xorg.conf files that I use depending on a single monitor or dual montitor setup. I provide these as a reference only…I have no idea whether they will work on your system. They work for me on a Dell Latitude X1 with a built-in Intel 915 video system. They may be instructive to others with the same or similar Intel graphics hardware.

• xorg.single (I keep this in /etc/X11/xorg.conf.single)

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148

  # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf(5) manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg   Section "Files" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" # path to defoma fonts FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection   Section "Module" Load "i2c" Load "bitmap" Load "ddc" Load "dri" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "vbe" EndSection   Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection   Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "true" EndSection   Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" EndSection   Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device" "/dev/input/wacom" Option "Type" "stylus" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection   Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device" "/dev/input/wacom" Option "Type" "eraser" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection   Section "InputDevice" Driver "wacom" Identifier "cursor" Option "Device" "/dev/input/wacom" Option "Type" "cursor" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection   Section "Device" Identifier "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller" Driver "i810" BusID "PCI:0:2:0" EndSection   Section "Monitor" Identifier "Generic Monitor" Option "DPMS" EndSection   Section "Screen" Identifier "Default Screen" Device "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller" Monitor "Generic Monitor" DefaultDepth 24 SubSection "Display" Depth 1 Modes "1280x768" EndSubSection SubSection "Display" Depth 4 Modes "1280x768" EndSubSection SubSection "Display" Depth 8 Modes "1280x768" EndSubSection SubSection "Display" Depth 15 Modes "1280x768" EndSubSection SubSection "Display" Depth 16 Modes "1280x768" EndSubSection SubSection "Display" Depth 24 Modes "1280x768" EndSubSection EndSection   Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "stylus" "SendCoreEvents" InputDevice "cursor" "SendCoreEvents" InputDevice "eraser" "SendCoreEvents" InputDevice "Synaptics Touchpad" EndSection   Section "DRI" Mode 0666 EndSection

• xorg.dual (I keep this in /etc/X11/xorg.conf.dual)

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197

  # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf(5) manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg   Section "Files" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" # path to defoma fonts FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection   Section "Module" Load "i2c" Load "bitmap" Load "ddc" Load "dri" Load "extmod" Load "freetype" Load "glx" Load "int10" Load "vbe" EndSection   Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection   Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "true" EndSection   Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents" "true" Option "Device" "/dev/psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" EndSection   Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device" "/dev/input/wacom" Option "Type" "stylus" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection   Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device" "/dev/input/wacom" Option "Type" "eraser" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection   Section "InputDevice" Driver "wacom" Identifier "cursor" Option "Device" "/dev/input/wacom" Option "Type" "cursor" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection   Section "Device" Identifier "0 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller" Driver "i810" BusID "PCI:0:2:0" Screen 0 Option "DDC" "false" Option "DDCMode" "false" Option "IgnoreEDID" "true" Option "DRI" "true" Option "MonitorLayout" "CRT,LFP" #Option "AGPMode" "0" EndSection   Section "Device" Identifier "1 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller" Driver "i810" BusID "PCI:0:2:0" Screen 1 Option "DDCMode" "false" #Option "IgnoreEDID" "true" Option "DRI" "true" Option "MonitorLayout" "CRT,LFP" #Option "AGPMode" "0" EndSection     Section "Monitor" #DisplaySize 332 207 Identifier "0 Generic Monitor" #HorizSync 30 - 85 #VertRefresh 56 - 76 Option "DPMS"   DisplaySize 338 203   Mode "1280x768" # vfreq 59.870Hz, hfreq 47.776kHz DotClock 79.500000 HTimings 1280 1344 1472 1664 VTimings 768 771 778 798 Flags "-HSync" "-VSync" EndMode #Modeline "1280x768_59" 78.80 1280 1344 1480 1680 768 769 772 795 -HSync +Vsync   #Modeline "1280x768_60" 80.14 1280 1344 1480 1680 768 769 772 795 -HSync +Vsync   EndSection   Section "Monitor" Identifier "1 Generic Monitor" HorizSync 27 - 96 VertRefresh 50 - 160 VertRefresh 60 DisplaySize 347 260 Option "DPMS" Modeline "1024x768_60.00" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync   EndSection   Section "Screen" Identifier "Default Screen" Device "0 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller" Monitor "0 Generic Monitor" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x768" #Virtual 1280 768 EndSubSection EndSection   Section "Screen" Identifier "Second Screen" Device "1 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller" Monitor "1 Generic Monitor" DefaultDepth 24 SubSection "Display" #Viewport 0 0 Depth 24 Modes "1024x768" Virtual 1024 768   EndSubSection EndSection     Section "ServerLayout" Identifier "Default Layout" Screen 0 "Default Screen" Screen 1 "Second Screen" RightOf "Default Screen" Option "Xinerama" "on" Option "Xinerama" "true" Option "Clone" "off" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "stylus" "SendCoreEvents" InputDevice "cursor" "SendCoreEvents" InputDevice "eraser" "SendCoreEvents" InputDevice "Synaptics Touchpad"   EndSection   Section "DRI" Mode 0666 EndSection

I hope this helps!

Powered by ScribeFire.

Today, Saturday, broke with rain on my tent yet again, and we decided to pack it in, call it a day, call it a trip, and head for home. Lucky we did, too, because the top of the pass heading east from Bella Coola was starting to get snowed and nasty. My first taste of winter. And only September!

Powered by ScribeFire.