We use the command-line implementation http://sourceforge.net/projects/pwsafe integrated revision control. It has a 2-way merge feature, which makes it mostly usable with revision control, even though it's a little more tedious than necessary, since you have to manually accept or reject individual changes. For a while I've wanted to implement 3-way merge so that most merges can be automatic but I will probably never get around to doing so.
The downside of the CLI pwsafe is that it supports only v2 PasswordSafe databases which fortunately works with most other interfaces but lacks some features. The other downside (especially in comparison with a GPG-encrypted file) is the lack of an agent, which regrettably means that very often terminal access is done by 'pwsafe --exportdb | less'.
Absolutely. It's critical to keep in mind the fact that switching to CFLs is just a reduction of impact, not an elimination. Better, then, is to actually reduce one's needs or wants, rather than just reducing costs of fulfilling those desires. I get a queasy feeling everytime I see an ad for a hybrid which tells you that you are "doing your part for the environment"--better not to need to own one of those damn machines in the first place. Recycling plastic shopping bags is okay (and necessary if you're an urban dog-owner), but it's better to bring your own reusable cloth shopping bags. Sometimes I think I worry too much about these trade-offs, rather than actually doing something about them.
I've also found that the quality or color of light really makes a difference, at least in the middle of a perpetually gray Pacific Northwest winter. I bought some that seemed much brighter and less yellow than the others I had, despite equivalent wattage. I checked the package and realized I'd bought "bright white" lights and, getting a bit carried away, proceeded to rearrange the lighting in my entire house. I also found I could use a cheap bulb that suffers a brief delay when starting with another bulb that doesn't and the effect is hardly noticiable.
If you're doing that many installs, you should be using kickstart anyway, in which case you can skip X configuration with 'skipx' or if configuring X, do not include the '--startxonboot' option.
I was wondering about that too. I was just in the UK (I'm an American) and was surprised to find that body weights seem to be measured in "stone" pretty widely, at least in print and TV. I thought that was a term found in Maugham-era literature and earlier, although I suppose Maugham is the most modern British writers I have read...
Am I the only one who doesn't use the search engine feature? I much prefer to use the "Keywords" in bookmarks to make my own search-engine shortcuts, mainly because I don't want to devote more screen space to the search engine box. It's just as easy for me to type gg define:earsplittenloudenboomer in the Location box.
Funny, but curiously enough fake PGP/MIME attachments are used by spammers, because older versions of SpamAssassin foolishly increased the score of messages with a signature attachment. This, regrettably, led to the situation of some misguided spam-filtering companies blocking messages with signatures, further hindering adoption.
For that matter, how does it compare with Tivoli TotalStorage SAN Filesystem, which seems to be another shared-storage filesystem from IBM/Tivoli? Trying to read IBM's descriptions is an exercise in marketing-fluff cryptography.
You have reminded me of one of my favorite quotations from Neitzsche: "It is a curious thing that God learned Greek when he wished to turn author; even more curious that he did not learn it better."
Cyrus IMAP is designed for this size of installation. You can split the backends up with Murder on the front-ends to distribute load; divide mailboxes on each host between filesystems (which, you'd presumably spread over multiple disks); use a SAN and GFS or other shared-storage cluster filesystems and share the spool among servers; use the new pre-release 2.3 code with mailbox replication and use more discrete, commodity components. Lots of other features that are designed for large-scale implementations.
For authentication, of course you have choices among LDAP, Kerberos (both of which are usable even if you're stuck with a Windows domain for authentication), PAM and other things. Very flexible; too flexible for some and it can be a bit confusing.
You mention a million mailboxes, but that doesn't really mean much--that is just an estimate of storage requirements. What is more important to determine is how many concurrent users you will have and how much actual traffic--storage is cheap, memory not so much.
A computer really uses less than 300W, even if the power supply says 300W. I now have the luxury of metered PDUs at one place I work and my estimates are about 90-100W --but these are HP DL360s, with dual 3.8GHz Xeon processors and 2x 15k RPM SCSI disks. You can imagine that a regular desktop is drawing a fair amount less. No CRTs on the PDUs, of course, so I can't say what those draw.
The only thing mind-numbing at this party was the amount of beer I drank. And then the next party brought that numbness to an even greater level, and then...
We use the command-line implementation http://sourceforge.net/projects/pwsafe integrated revision control. It has a 2-way merge feature, which makes it mostly usable with revision control, even though it's a little more tedious than necessary, since you have to manually accept or reject individual changes. For a while I've wanted to implement 3-way merge so that most merges can be automatic but I will probably never get around to doing so.
The downside of the CLI pwsafe is that it supports only v2 PasswordSafe databases which fortunately works with most other interfaces but lacks some features. The other downside (especially in comparison with a GPG-encrypted file) is the lack of an agent, which regrettably means that very often terminal access is done by 'pwsafe --exportdb | less'.
There is also at least one Android app that can read the database file format: https://play.google.com/store/apps/details?id=com.jefftharris.passwdsafe
This is the best solution that I've found.
They've already got those. They call us "men".
Absolutely. It's critical to keep in mind the fact that switching to CFLs is just a reduction of impact, not an elimination. Better, then, is to actually reduce one's needs or wants, rather than just reducing costs of fulfilling those desires. I get a queasy feeling everytime I see an ad for a hybrid which tells you that you are "doing your part for the environment"--better not to need to own one of those damn machines in the first place. Recycling plastic shopping bags is okay (and necessary if you're an urban dog-owner), but it's better to bring your own reusable cloth shopping bags. Sometimes I think I worry too much about these trade-offs, rather than actually doing something about them.
I've also found that the quality or color of light really makes a difference, at least in the middle of a perpetually gray Pacific Northwest winter. I bought some that seemed much brighter and less yellow than the others I had, despite equivalent wattage. I checked the package and realized I'd bought "bright white" lights and, getting a bit carried away, proceeded to rearrange the lighting in my entire house. I also found I could use a cheap bulb that suffers a brief delay when starting with another bulb that doesn't and the effect is hardly noticiable.
If you're doing that many installs, you should be using kickstart anyway, in which case you can skip X configuration with 'skipx' or if configuring X, do not include the '--startxonboot' option.
I'd rather find desert planets... only there will we find the Spice.
Wil
What sort of clarification do you need? OSDL has had an NDA program for some time:
http://developer.osdl.org/dev/tab/nda/
Wil
We're finally moving past being a species that still thinks digitial watches are a pretty neat idea.
Now imagine a whole clone army of Natalie Portmans running Linux, serving up hot grits.
Wow, that was so 2000.
Chuck Norris's abilities to time-travel are severely limited, however--he can only go back 6,000 years.
Wil
Or perhaps Bat Boy.
I like Seed and Scienceblogs myself.
Anyone else reminded of "1999 was the year that the Indian nuclear satellite went out of control."?
Does that include telling Larry to STFU?
I was wondering about that too. I was just in the UK (I'm an American) and was surprised to find that body weights seem to be measured in "stone" pretty widely, at least in print and TV. I thought that was a term found in Maugham-era literature and earlier, although I suppose Maugham is the most modern British writers I have read...
Here are a few of mine:c tst =date
http://images.google.com/images?q=%25s
http://www.imdb.com/find?q=%25s
http://www.m-w.com/cgi-bin/dictionary?va=%25s
http://freshmeat.net/search/?q=%25s§ion=proje
http://search.cpan.org/search?mode=all&query=%25s
http://dir.gmane.org/search.php?match=%25s
http://search.gmane.org/search.php?query=%25s&sor
Am I the only one who doesn't use the search engine feature? I much prefer to use the "Keywords" in bookmarks to make my own search-engine shortcuts, mainly because I don't want to devote more screen space to the search engine box. It's just as easy for me to type gg define:earsplittenloudenboomer in the Location box.
Funny, but curiously enough fake PGP/MIME attachments are used by spammers, because older versions of SpamAssassin foolishly increased the score of messages with a signature attachment. This, regrettably, led to the situation of some misguided spam-filtering companies blocking messages with signatures, further hindering adoption.
I ran into this the other day trying to search for discussions of it... GPFs is overwhelmingly used as the plural for General Protection Fault...
For that matter, how does it compare with Tivoli TotalStorage SAN Filesystem, which seems to be another shared-storage filesystem from IBM/Tivoli? Trying to read IBM's descriptions is an exercise in marketing-fluff cryptography.
You have reminded me of one of my favorite quotations from Neitzsche:
"It is a curious thing that God learned Greek when he wished to turn author; even more curious that he did not learn it better."
Cyrus IMAP is designed for this size of installation. You can split the backends up with Murder on the front-ends to distribute load; divide mailboxes on each host between filesystems (which, you'd presumably spread over multiple disks); use a SAN and GFS or other shared-storage cluster filesystems and share the spool among servers; use the new pre-release 2.3 code with mailbox replication and use more discrete, commodity components. Lots of other features that are designed for large-scale implementations.
For authentication, of course you have choices among LDAP, Kerberos (both of which are usable even if you're stuck with a Windows domain for authentication), PAM and other things. Very flexible; too flexible for some and it can be a bit confusing.
I've been working on rewriting the HOWTO, although I haven't made a ton of progress, it may still be useful to you: http://nakedape.cc/info/Cyrus-IMAP-HOWTO and here's a presentation I put together for Linuxfest Northwest: http://nakedape.cc/info/Cyrus-IMAP-Intro.
You mention a million mailboxes, but that doesn't really mean much--that is just an estimate of storage requirements. What is more important to determine is how many concurrent users you will have and how much actual traffic--storage is cheap, memory not so much.
A computer really uses less than 300W, even if the power supply says 300W. I now have the luxury of metered PDUs at one place I work and my estimates are about 90-100W --but these are HP DL360s, with dual 3.8GHz Xeon processors and 2x 15k RPM SCSI disks. You can imagine that a regular desktop is drawing a fair amount less. No CRTs on the PDUs, of course, so I can't say what those draw.
The only thing mind-numbing at this party was the amount of beer I drank. And then the next party brought that numbness to an even greater level, and then...
Where is this Torrent you speak of?