OK--I'll answer the obligatory question before it's asked:-): Does Apache 2 work with PHP yet?
A: Yes, but only if you use the (default) Apache prefork module with PHP. Some libraries used by PHP are
not thread-safe, so you cannot use the multiple thread model.
For details on using Apache 2 and php see my FAQ at
http://dan.drydog.com/apache2php.html
I run Moneydance. Its written in Java and runs on multiple platforms. I run it from Linux, MS Windows XP, and Solaris with 1 license (accessing the same data files). It costs money, but I like the platform independence and Quicken/Quickbooks-free proprietary formats. No, I never worked for Moneydance--just a happy customer.
GnuCash is free, but does not run on MS Windows. It also uses the more-complex double entry system bookkeepers use. This may be ok for you though.
The problem with Quicken (and perhaps Quickbooks) is Quicken charges a "tax" on banks for each transaction (check) written in Quicken and uploaded to the bank. They also discontinued support for the open QIF exchange format most banks use.
System V UNIX had no virtual memory until the late 1980s. Sure, there were specialized versions, such as BSD with VM added on, but it wasn't in stock UNIX. It was around though, and was in IBM 360 and Multics (1960s).
I work a lot with putting copyright materials online. See/http://yosemite.ca.us/history/
I get a lot of resistience from librarians, but that's another story. Only original material can be copyrighted. For a reprinted book, for example, that would be new introductions or new art. It would not minor editing or line breaks.
A federal court found that high-quality
photographs of art do not have copyright protection. They were considered "slavish copies," without any additional creativity. Bridgeman Art Library v. Corel Corp., 36 F. Supp. 2d 191, 1999 (S.D.N.Y. 1999).
That said, it's always better to reproduce from an early printing, and not a new printing, to avoid any question of copyright.
Of course all operating systems have their security holes. However, it's stily to say that no matter how poor a OS design may be (Windoz), that it doesn't matter and they are "all the same."
Michal Gorman has posted a rebuttal to people who dislike his anti-digital stance. It's at
Library Journal
I don't agree with his anti-digital positions, including his unsupported belief Google is "inefficient" and somehow "random". Nor does he appreciate the value of posting books, previously inaccessible in library archives, online--thereby making them available to millions.
Yahoo was around longer than 10 years. Yahoo.com may have started in 1995, but it was going strong in 1994 as a non-dommercial directory at Stanford University. The URL, IIRC, was http://yahoo.stanford.com/
Google started similarly a few years later. It also was initially hosted at Stanford. It's address stared out as http://google.stanford.com/
(neither link is still live).
US tax returns are private and are available only to authorized IRS personnel and the filer. From IRS form 4506:
I declare that I am either the taxpayer whose name is shown on line 1a or 2a, or a person authorized to obtain the tax return requested. If the request applies to a joint return, either husband or wife must sign. If signed by a corporate officer, partner, guardian, tax matters partner, executor, receiver, administrator, trustee, or party other than the taxpayer, I certify that I have the authority to execute Form 4506 on behalf of the taxpayer.
Of course, you can obtain it by fraud. It would be easier to just break into the person's house. IRS personnal have also been caught with unauthorized access. But it's certaintly not "public records."
Many or most librarians are behind the times regarding Internet and online resources. Sure most have their catalog online and perhaps have cabinets of microfilm or microfiche.
I find many are unaware of Gutenburg or other online resources and are even hostile to my posting their books and materials online. Special Collections Librarians typically want a royalty fee of $50 or $100 a page to use public domain materials (they can do this as they have physical possession of the books). Sometimes I can find a book not in Special Collections in some another library, or can buy a cheap used copy, but it's frustrating that I have to work around these "temple keepers" to provide wider access of books to the public.
What you say is true, but the "Man in the Middle Attack" only works the first time. Once the certificate is accepted, the "man in the middle" can't send a fake certificate.
Usually SSL websites are used with people who have continuing relationships, such as businesses, confidential email, and so on. They are used less frequently with one-time visitors. That said, it still leaves a large hole for new visitors to fall into.
Open Source Message Queuing System (OSMQS?) is not an Application. An application is something like Firefox, Gimp, or OpenOffice. It can be started directly by the user to perform some tasks.
OSMQS can be used by applications, and appears useful (if it is reliable, not over-designed, efficient, and portable to multiple platforms), however it's something you or your grandmother will invoke directly.
Whether it belongs in the kernel or in userland is another question.
BTW, the problems PHP has with Apache 2 is the MTM model. If you won't use multithreading, you're OK. If you use MT, make sure the underlying libraries you compile in or use with PHP are MT-safe.
They can impose a royalty once you sign a licence agreement to do so. If you don't, you can copy public domain, but they won't give you access to do so. Sort of a Catch-22.
Here's a quote from a California Library Association webpage "Identifying Public Domain Sources to Borrow From" by Mary Minowis:
"Though controversial, licensing agreements have been upheld, even when they protect works that are not copyrightable [i.e, public domain]. See ProCD, Inc. v. Zeidenberg, 86 F.3d 1447 (7th Cir. Wis. 1996).
Here's some links to policies, which appear pretty uniform for all UC campuses--that is you pay a fee for reproduction of public domain works in their possession. I've tried all 3 libraries and they either say no, or don't even bother replying (for both personal visits and a snail mail letter):
A FOIA may help, if it applies to UC. I'm not familiar with it, but isn't that a federal law that applies to the U.S. government. I don't know if California has an equivalent. IANAL, but I'll look into it and see if there's a California state version of FOIA.
This will be sweet. I just hope that we don't get too many authors getting pissed.
Only public-domain books will be scanned. In all or most cases the author's are dead. However, this will revive a great body of work and widen access to many.
One class of author may be pissed will be authors who take older works and just slap a foreword or introduction to the front and collect royalties. I've seen this done for many histories. But author's of todays works can count on royalties for themselves, their children, and their grandchildren (if the book is still selling). The copyright term is too long in the U.S., but that's another story . . .
Typically, both page images and uncorrected OCR are made available. Correcting OCR is too labor-intensive for thousands of books.
The uncorrected OCR is very useful for indexing (by Google or others), as the 5% or fewer typos are not enough to interfere with indexing keywords. Uncorrected OCR can also be corrected later.
The page images are tied with the uncorrected OCR so you can see exactly what's there.
For an example, see books at University of Michigan's Making of America (MoA) Exhibit, which has thousands of 19th century books and periodicals available.
I'm not familiar with Google Print, but typically "slice and scan" is usually used for new books only. That's because there's multiple copies of the book available and the paper is usually flat and dust free.
For older books, most archivists use a cradle and photograph the pages. It's easier on the book, requires no slicing, and there's no scanner to clog with dust.
The disadvantage is the scanner operators need a little bit more training, but that's not a big problem.
This is great. Compare this pro-digitalization attitude of Harvard, Stanford, and others with the University of California's (UC's) anti-digital position.
For books in Special Collections, they won't allow copies to be digitalized unless they are (1) paid a fee to scan the book (fair enough) and (2) paid a royalty to post the book to the web.
The royalty amounts to hundreds or thousands of dollars per book (about $100/page or image). This allows the libraries to act as a "profit center" for the universities. This policy applies to all UC campuses (I've tried UCB, UCLA, UCI, UCSD).
This is true even though the book is in the public domain (because they have physical possession and nobdy can make copies until you sign a license agreement). This is true even if you're using the book for non-commercial purposes (such as free posting to the web).
Something is wrong here. People donate to UC libraries (either books or money) for the public good. They don't donate so the library can start a business licensing public-domain books.
Despite that, I have been able to scan many books (by using books in open stacks or purchasing them). These books concern Yosemite history and are at http://www.yosemite.ca.us/history/
Domains can be transferred at any time before a domain expires. Not just when it's up for renewal.
Acoustic couplers were only 110 baud
on
Firefox 1.0 Released
·
· Score: 2, Insightful
Accoustic couplers are only 110 baud. When 300 baud modems with direct connection to a phone line became legal in the early 1980s it was great. With 110 you watch every character slowly spit out. You appreciated the breviety of the UNIX command line and the short command names (ls, cp, mv, ln, rm).
I have a webpage against my Congressman, U.S. Rep. "Duke" Cunningham. It's not very flattering, but it's true. See
http://dukecunningham.org/
The domain used to belong to the Representative, but he (or his dormant campaign staff) forgot to renewal.
You may not agree with it, but I have my rights and having a easy-to-remember domain name certaintly helps people find it. I make no representation that it's "Duke's" website.
Apache 2.0.52 fixes 2.0.51 security regression
on
Apache 2.0.52 Released
·
· Score: 3, Informative
As I noted in the
Apache 2.0.51 notice in/., this Apache 2.0.52 fixes a security regression from 2.0.51. You can also apply a 4-line patch to 2.0.51. Apache 2.0.52 works fine for me in production (been using it since yesterday on 2 systems).
Slashdot Mirror
A: Yes, but only if you use the (default) Apache prefork module with PHP. Some libraries used by PHP are not thread-safe, so you cannot use the multiple thread model.
For details on using Apache 2 and php see my FAQ at http://dan.drydog.com/apache2php.html
GnuCash is free, but does not run on MS Windows. It also uses the more-complex double entry system bookkeepers use. This may be ok for you though.
The problem with Quicken (and perhaps Quickbooks) is Quicken charges a "tax" on banks for each transaction (check) written in Quicken and uploaded to the bank. They also discontinued support for the open QIF exchange format most banks use.
System V UNIX had no virtual memory until the late 1980s. Sure, there were specialized versions, such as BSD with VM added on, but it wasn't in stock UNIX. It was around though, and was in IBM 360 and Multics (1960s).
That said, it's always better to reproduce from an early printing, and not a new printing, to avoid any question of copyright.
Of course all operating systems have their security holes. However, it's stily to say that no matter how poor a OS design may be (Windoz), that it doesn't matter and they are "all the same."
For more information see the Solaris x86 FAQ (which I wrote with the help of hundreds)
I don't agree with his anti-digital positions, including his unsupported belief Google is "inefficient" and somehow "random". Nor does he appreciate the value of posting books, previously inaccessible in library archives, online--thereby making them available to millions.
Google started similarly a few years later. It also was initially hosted at Stanford. It's address stared out as http://google.stanford.com/ (neither link is still live).
Mosaic didn't support JPG initially either--just GIF and some obscure X bitmap file (xbm?). JPG support came later with Netscape and latter versions of Mosaic.
I declare that I am either the taxpayer whose name is shown on line 1a or 2a, or a person authorized to obtain the tax return requested. If the request applies to a joint return, either husband or wife must sign. If signed by a corporate officer, partner, guardian, tax matters partner, executor, receiver, administrator, trustee, or party other than the taxpayer, I certify that I have the authority to execute Form 4506 on behalf of the taxpayer.
Of course, you can obtain it by fraud. It would be easier to just break into the person's house. IRS personnal have also been caught with unauthorized access. But it's certaintly not "public records."
Many or most librarians are behind the times regarding Internet and online resources. Sure most have their catalog online and perhaps have cabinets of microfilm or microfiche.
I find many are unaware of Gutenburg or other online resources and are even hostile to my posting their books and materials online. Special Collections Librarians typically want a royalty fee of $50 or $100 a page to use public domain materials (they can do this as they have physical possession of the books). Sometimes I can find a book not in Special Collections in some another library, or can buy a cheap used copy, but it's frustrating that I have to work around these "temple keepers" to provide wider access of books to the public.
Usually SSL websites are used with people who have continuing relationships, such as businesses, confidential email, and so on. They are used less frequently with one-time visitors. That said, it still leaves a large hole for new visitors to fall into.
OSMQS can be used by applications, and appears useful (if it is reliable, not over-designed, efficient, and portable to multiple platforms), however it's something you or your grandmother will invoke directly.
Whether it belongs in the kernel or in userland is another question.
BTW, the problems PHP has with Apache 2 is the MTM model. If you won't use multithreading, you're OK. If you use MT, make sure the underlying libraries you compile in or use with PHP are MT-safe.
Here's a quote from a California Library Association webpage "Identifying Public Domain Sources to Borrow From" by Mary Minowis: "Though controversial, licensing agreements have been upheld, even when they protect works that are not copyrightable [i.e, public domain]. See ProCD, Inc. v. Zeidenberg, 86 F.3d 1447 (7th Cir. Wis. 1996).
-
Berkeley (Bancroft Library)
-
UCLA (Young Research Library Special Collections
-
http://orpheus.ucsd.edu/speccoll/duppol.html
A FOIA may help, if it applies to UC. I'm not familiar with it, but isn't that a federal law that applies to the U.S. government. I don't know if California has an equivalent. IANAL, but I'll look into it and see if there's a California state version of FOIA.Only public-domain books will be scanned. In all or most cases the author's are dead. However, this will revive a great body of work and widen access to many.
One class of author may be pissed will be authors who take older works and just slap a foreword or introduction to the front and collect royalties. I've seen this done for many histories. But author's of todays works can count on royalties for themselves, their children, and their grandchildren (if the book is still selling). The copyright term is too long in the U.S., but that's another story . . .
The uncorrected OCR is very useful for indexing (by Google or others), as the 5% or fewer typos are not enough to interfere with indexing keywords. Uncorrected OCR can also be corrected later.
The page images are tied with the uncorrected OCR so you can see exactly what's there.
For an example, see books at University of Michigan's Making of America (MoA) Exhibit, which has thousands of 19th century books and periodicals available.
For older books, most archivists use a cradle and photograph the pages. It's easier on the book, requires no slicing, and there's no scanner to clog with dust.
The disadvantage is the scanner operators need a little bit more training, but that's not a big problem.
For books in Special Collections, they won't allow copies to be digitalized unless they are (1) paid a fee to scan the book (fair enough) and (2) paid a royalty to post the book to the web.
The royalty amounts to hundreds or thousands of dollars per book (about $100/page or image). This allows the libraries to act as a "profit center" for the universities. This policy applies to all UC campuses (I've tried UCB, UCLA, UCI, UCSD).
This is true even though the book is in the public domain (because they have physical possession and nobdy can make copies until you sign a license agreement). This is true even if you're using the book for non-commercial purposes (such as free posting to the web).
Something is wrong here. People donate to UC libraries (either books or money) for the public good. They don't donate so the library can start a business licensing public-domain books.
Despite that, I have been able to scan many books (by using books in open stacks or purchasing them). These books concern Yosemite history and are at http://www.yosemite.ca.us/history/
Domains can be transferred at any time before a domain expires. Not just when it's up for renewal.
Accoustic couplers are only 110 baud. When 300 baud modems with direct connection to a phone line became legal in the early 1980s it was great. With 110 you watch every character slowly spit out. You appreciated the breviety of the UNIX command line and the short command names (ls, cp, mv, ln, rm).
The domain used to belong to the Representative, but he (or his dormant campaign staff) forgot to renewal.
You may not agree with it, but I have my rights and having a easy-to-remember domain name certaintly helps people find it. I make no representation that it's "Duke's" website.
As I noted in the Apache 2.0.51 notice in /., this Apache 2.0.52 fixes a security regression from 2.0.51. You can also apply a 4-line patch to 2.0.51. Apache 2.0.52 works fine for me in production (been using it since yesterday on 2 systems).
Apache 2.0.51 is not even available, as 2.0.52 fixes the 2.0.51 regression.
BTW, I have a document about using PHP and Apache2 at http://dan.drydog.com/apache2php.html