« January 2006 | Main | March 2006 »
February 27, 2006
Redefining key binding of Screen to avoid conflicts with Emacs
http://lists.gnu.org/archive/html/help-gnu-emacs/2005-04/msg00373.html
http://lists.debian.org/debian-user/2000/08/msg00467.html
Also see the Customize Section of the Screen manual.
Posted by Roy at 01:46 AM | Comments (0)
February 25, 2006
Kernel auditing
inotify
Then there're some people at Redhat that developed the kernel auditing subsystem.
http://www.uniforum.chi.il.us/slides/HardeningLinux/LAuS-Design.pdf
http://lxr.linux.no/search?string=audit
http://syn.cs.pdx.edu/wiki/index.php/Light_weight_auditing_framework
https://www.redhat.com/archives/linux-audit/2004-August/msg00002.html
And some user space utilities released with SELinux, RHEL & Fedora Core:
http://people.redhat.com/sgrubb/audit/
http://rpmfind.net//linux/RPM/fedora/devel/i386/audit-1.1.4-5.1.i386.html
A third party patch that looks to have nice UI:
http://www.intersectalliance.com/projects/Snare/
Posted by Roy at 02:03 PM | Comments (0)
February 22, 2006
Some access control stuffs
Zhenkai Liang, Isolation work.
ugidfw.
systrace.
mac.
acl.
selinux
chroot
BSD jail
union file system (mount_unionfs)
Posted by Roy at 05:40 PM | Comments (0)
February 17, 2006
How to beat a speeding ticket?
http://lifetips.us/2006/how-to-beat-a-speeding-ticket#more-3
Posted by Roy at 09:53 PM | Comments (0)
Changing Headlight Bulbs
http://www.wisebuyers.co.uk/motoring/car-maintenance/Changing-Tyres-+-Lighbulbs/25/
1 Disconnect the wiring plug from the bulb ...
2 ... and peel off the rubber cover.
3 Squeeze the legs of the spring clip together to release it. Move the clip out of the way and pull out the bulb.
4 The bulb will have tangs like this round the edge so it can only be fitted one way.
5 Fit the new bulb, making sure it's the right way up, and secure it with the spring clip. Remember, don't touch the glass.
6 After fitting the new bulb, check that the lights are working normally before you use the car.
Posted by Roy at 03:33 PM | Comments (0)
Paper accepted to VEE '06
VEE is co-located with PLDI. This year it takes place in Ottawa, Canada.
This is my first English paper, and attending PLDI will get me chances to talk to a lot of cool PL people, isn't that sweet?
According to Michał Cierniak, VEE is the result of merging the USENIX VM Symposium and the ACM SIGPLAN IVME Workshop. VEE '06 is just the second gathering.
Posted by Roy at 02:36 PM | Comments (0)
February 06, 2006
GPS软件比较
Configuration:
DELL Axim X50v（CF SanDisk Ultra2 512M）+Holux GPSlim236，
英文系统2003SE(和一部带蓝牙功能的手机Nokia 6620)
Pocket Streets 2005 功能很少。
DestinAtor3版本太低不兼容其机器。
iGuidance 2功能挺强，运行较慢。
Mapopolis 4 beta版可免费下载，地图收费。功能还不错。
Tomtom navigator 5完全版达8CD之多。功能非常强劲，语音提示包含中文。
Navigon MobileNavigator 5将近8G的庞然大物，但界面并不友好，占资源过多。
Posted by Roy at 01:19 PM | Comments (0)
February 01, 2006
Comments on English writing
English is hard, life is harder..
CS655 is a super cool class taught by an awesome young prof.
It is perfectly legal to use primes (') in ocaml variable names.
Below is his attitude on homework:
Homework itself isn't a big deal in grad classes. I don't care about the homework for its own sake. I do care about you all learning how to recognize PL research techniques and apply them to your own work. The project matters much more, especially since it's closer to the actual process of doing research and submitting papers.
Some of you may have been surprised at my obnoxious pickiness for English prose details in the formal written part of the homework. I graded those parts as I would review a conference submission. I realize that English is not everyone's first language and that formal writing in a foreign tongue is difficult (if you want a laugh and you know one of these languages, ask me to say something non-trivial in French, Latin or Japanese -- I'm abysmal). Actually, my first-draft English isn't so hot either -- bonus points if I make a mistake while claiming to correct one of yours.
However, we publish in English venues, TA in English, present our work in English at conferences, and network in conferences in English (well, most of the time). I believe that anything I can do to give you a bit more practice with formal English will be a boost to your later research career.
Sad but true: people will often conflate the clarity of your prose with the brilliance of your ideas.
And my sad story goes:
Book Hoare Set Div LetOp LetHR Interp Ex
Hu, Wei 1 1/3 2 2 2 2- 5 1
HW1 Grade: 16/18
> Most of the design principles are still valid today after software >
> engineering is better understood, and software乫s security has received
> more and more attention.
You should start by mentioning Hoare's name or his article's name. Swap the order of your first and second sentences. Then change this one to something
like:
"Most of his design principles are still valid today, despite many advances in software engineering and security."
> Simplicity is emphasized as the first principle.
Avoid the passive voice. "Hoare's first programming language design principle is simplicity."
> As mentioned in the class, a complex language feature has the risk
> that implementations can not get it right.
"As mentioned in the class, a complex language feature carries the risk that implementations may not get it right."
> Even if a programmer could manage to work when he only understands
> parts of the language, he would get into trouble when an unknown
> feature is accidentally triggered.
Putting "programmers" in the plural avoids he/she problems.
"Programmers that only understand parts of a complex language will run into difficulties when their programs make use of misunderstood language features."
> That is exactly why my favorite language is Scheme, whose syntax is
> elegantly simple.
Scheme isn't a person, so "whose" will sound strange to some readers.
"Such arguments about complexity explain why Scheme, with its elegantly simple syntax, is my favorite language."
> It is also glorious that Hoare noticed the importance of security at
> that time, although his description is not close to today乫s security
> concerns.
"Glorious" is a bit too "showy" or "flashy" for this kind of writing.
"It is also remarkable that Hoare noticed the importance of security so long ago, even though his description is not perfectly aligned with today's primary security concerns."
> I would say Hoare乫s argument on fast translation is wrong.
"I disagree with Hoare's argument about fast translation."
> He thought independent
We don't actually know this. When you refer to the position of another researcher you should always use phrases like "He claimed" or "He suggested". You never want to claim that Hoare (or anyone else) is "wrong"
or "stupid" -- you want to claim that his ideas, conjectures or positions are wrong.
> He thought independent compilation was a poor technique that would
> encourage a programmer to split a large program into very small modules.
"He argued that independent compilation was a poor technique because it would encourage programmers to split large programs into very small modules."
> Also separate compilation is a technique that is used in all large
> programs nowadays.
Avoid starting a sentence with "also". Avoid "nowadays" in formal writing.
Finally, avoid sweeping generalizations.
"Separate compilation is used successfully in almost all modern software development."
Your writeup does not feature a conclusion or summary -- even a single sentence would go a long way towards wrapping it up.
Your ideas are fine, but your English presentation could use some polish.
Consider asking someone else to proofread your prose. One of the goals in this class is to help you write research papers. Much of writing a research paper is having a good idea and backing it up with proofs or experiments.
However, the clarity of your English writing is also a large determining factor. In particular, a submitted paper written in the same manner as your answer to Problem 2 would probably be rejected regardless of its intellectual merit. I realize that often you end up writing papers in a group and that someone else can be delegated to do a final pass over the text and fix up the grammar. However, a some point in your research career (e.g., when you are a new professor or new research staff member) you will have to write papers on your own. I am interested in helping you obtain a more natural grasp of English (that's one of the reasons why I included concrete examples for how you would fix things up) -- feel free to stop by my office with questions about phrasing or grammar or whatnot, even if they aren't related to 655.
Posted by Roy at 05:44 PM | Comments (0)