My view on vi and vim (and nvi et al)
I have a confession: for all that I use it fairly often, I am a fairlybasic user of vi. As such, I have a pretty unsophisticated view ofwhat vi is; if I type ' vi ' and something starts up that behaves likevi and is not too freakishly super-intelligent ,I call it vi and don't think more about it, regardless of the nameof the actual implementation. Unless I actively think about it, I'monly vaguely aware that there are at least
Server problems caused by 'transparent' self-signed SSL certificates
One of the issues with allowing self-signed SSL certificates to beautomatically used for transparent encryption over https URLs is theproblems that they cause for server-side applications.
Right now, a server-side program that care can more or less assume thata SSL-encrypted connection means either that it is securely talkingto the real end user's machine or that the end user has been activelycompromised (which it can't do anything about). It may thus use thingslike 'you can only talk
Science
It is ironic that as we are getting a better picture of how epidemiology studies get closer to predicting illness (or recovery from an illness), we are learning at the same time to realize how irrelevant the scientific statistics
Good editors aren't better or worse, just different
It's common to compare text editors and say that one is better or worsethan another. But after a certain point this is wrong. Editors are oftennot better or worse but different than each other, each better atspecific things. Such differences mean that there is no absolute scaleof better and worse, and indeed that the question of which is a bettereditor in general is meaningless.
Let me illustrate this using the differences between the three editorsthat I use most frequently:
viis the best sysadmin editor
Why rootkits targeted at Red Hat Enterprise would make me especially nervous
A while back, I wrote in passing that I wouldbe especially nervous if I ran across a rootkit that specificallytargeted Red Hat Enterprise systems (for example, to the extent ofcorrupting the RPM database checksums ). TodayI feel like elaborating on that.
(Right off the bat I'll say that it's not because we use RHEL here.Our use of RHEL is small and so far none of it is in machines thatare particularly exposed to users or the world.)
What would make me