Clint Adams: No stray snails in this picture
“You have to begin to lose your memory, if only in bits and pieces, to realize that memory is what makes our lives. Life without memory is no life at all, just as an intelligence without the possibility of expression is not really an intelligence. Our memory is our coherence, our reason, our feeling, even our action. Without it, we are nothing.” Luis Bu uelBut what was a little odd (but nonetheless very endearing) about most of the account is that it was not organized by stories, or date, but by car models. Yes, by technology. My dad organized the stories about Enid by virtue of the cars they had, which struck me a little strange because it is not like he was a car buff or anything (growing up we always had the most unsexy cars, like Ford Tauruses). The cars he covers are the following: The Model A Ford Convertible
This was the first General Motors car with automatic drive. It was called Hydromatic and even though this car had a powerful 8-cylinder engine, this first automatic drive was very sluggish. Forget about 0 to 60 miles an hour in 7 seconds. This was in minutes. It was the car that Abe used to teach both Enid and I to drive. We both had to have additional lessons with a stick shift car, because the driving test was only given on stick shift cars. I learned to drive in 1944, when I was 16. Enid took lessons from Abe and learned to drive in 1945 when she was fifteen. This was against the law, but the law in the name of Tom, the policeman that covered our neighborhood, liked Enid and looked the other way.For those who care to read more (it may only be amusing to me and those few people that are into American car history), I have included all the cars and here are the main cast of characters. Ruth = My Grandmother
The above diagram shows how the SE Linux identity limits the roles that may be selected, and how the role limits the domains that may be entered. Therefore the identity controls what the user may do and in this example the identity "root" means that the user has little access to the machine (a Play Machine configuration). I think that the above is reasonably effective and have been using it for a few years. I have considered a more complex diagram with the "staff_r" role included as well and possibly including the way that "newrole" can be used to change between roles. So I could have the above as slide #1 about identities and roles with a more detailed diagram following to replace a page of text about role transition.
The above diagram shows the domain transitions used in a typical system boot and login process. It includes the names of the types and a summary of the relevant policy rules used to implement the transitions. I also have another diagram that I have used which is the same but without the file types and policy. In the past I have never used both in the one talk - just used one of the two and had text to describe the information content of the other. To make greater use of diagrams I could start with the simple diagram and then have the following slide have all the detail.
The above diagram simply displays the MCS security model with ellipses representing processes and rectangles representing files.
The above diagram shows a simplified version of the MMCS policy. With MMCS each process has a range with the low level representing the minimum category set of files to which it is permitted to write and the high level representing the files that it may read and write. So to write to a file with the "HR" category the process must have a low level that's no higher than "HR" and a high level that is equal or greater than "HR". The full set of combinations of two categories with low and high levels means 10 different levels of access for processes which makes for a complex diagram. I need something other than plain text for this but the above diagram is overly complex and a full set is even more so. Maybe a table with process contexts on one axis, file contexts on another and access granted being one of "R", "RW" or nothing?
This last one is what I consider my most effective diagram. It shows the benefits of SE Linux in confining daemons in a clear and effective manner. Any suggestions for improvement (apart from fixing the varying text size which is due to a bug in Dia) would be appreciated.

Etch is out! Thanks
to everyone involved in the best release ever, and special congratulations
for making this happen in 13 months less than for Sarge despite all the, er,
obstacles. I d personally love to see the trend continue for Lenny.
If you live in Paris, you have two opportunities
to meet, have a beer and rejoice: tomorrow (Wednesday the 11th) and in three
days (Friday the 13th). Everyone is welcome and you do not have to book, the
place has plenty of room during the holidays. And if you live somewhere else,
there s probably a party
near your place.
| 2005/06 | 2006/07 | |
|---|---|---|
| number of (partial) days | 25 | 16 |
| Damüls | 10 | 10 |
| Diedamskopf | 15 | 3 |
| Warth/Schröcken | 0 | 3 |
| total meters of altitude | 124634 | 74096 |
| highscore | 10247m | 8321m |
| # of runs | 309 | 189 |
There are very useful services around, such as http://www.buildd.net/, http://bts.turmzimmer.net/ or http://bjorn.haxx.se/debian/. I cannot understand why they are not Debian services.
Amita noticed as soon as she got up ("EGGS!!"), and ran around the house picking up eggs, breaking them in half, and eating the grapes inside. She also got an improvised Easter "basket" -- they didn't have baskets at the store, so I got a little Easter gift-bag instead -- with apples, a chocolate bunny, and a stuffed duck. Pretty good haul.
This afternoon we're going out to a cabane sucre -- a traditional "sugar shack", where maple syrup is made. We'll have a big dinner, go on a horse ride, and listen to some traditional Qu bec music. It's my first time going, and I'm pretty excited.
tags: easter cabane sucre easter egg hunt maj amitajune chocolate bunny maple syrup
Next.