A lot of HIV/AIDS research is going on, but I wonder, what about Hepatitis C virus? As I recall, it also leads to fatality (liver damage + death) in more than 70-80% of the cases, transmits much like HIV (blood transfusion, needles, sexual intercourse), and in some regions especially South East Asia it's far more prevalent than HIV. There's also no known vaccine against it at the moment.
I can transfer songs to my old iPod mini using gtkpod and amarok, which is fine. The only problem I have is when my brother connect the device using iTunes on Windows, the program erases all the existing songs. No problem, I can just smack my brother on the head and retransfer.
However, almost a year ago I bought a Creative Zen Vision (due to the new iPod haven't arrived on my country yet, plus this Zen Vision has audio recording and FM radio capability). To this day I haven't been able to use Linux to upload my songs. Sigh.
Re:My issue with Gnome is....
on
Why KDE Rules
·
· Score: 1
it's L for Location. Ctrl-L is pretty common I'd say, several browsers and file managers use it. but it's not documented, I found out about it here just like you did.
Blame those brain-dead PHP "architects" for designing the API for the sendmail() PHP function. The fourth argument accepts arbitrary headers. The 4th arg is used a lot because the damn function doesn't even provide another argument for the From header! It's easily exploitable because those idiotic PHP "programmers" never check values they send to functions, thus sendmail($to, $subject, $body, "From: $from") is easily exploitable by spammers through injecting nasty values to $from. I hate everything PHP-related.
What about AMR? It seems to be designed for speech and widely supported by mobile devices. Though I'm not sure about the licensing issues.
On a side note, does anyone know of an easy way to convert AMR to MP3/OGG/WAV, preferable on Linux? Yes, I've tried Google results like this, but couldn't make it to work.
I feel for the Firebird community, they probably do need more recognition and press. But then, maybe if they could release stuffs more often, they would get mentioned more often too.
It's hard to get more attention if your "competitors" are of PostgreSQL caliber. Postgres do major releases every 6-12 months and is getting better all the time at faster rate. It's getting picked up by companies and has the strongest open source support around it.
Meanwhile, when will FB 2.0-final be released? When will I be getting index longer than 240 (or was it in the order of 500) bytes? When will the documentation be half-decent?
I consider my decision to go with Postgres over Firebird several years ago was the best decision I've ever made.
Um, the license? Add to that: I'm tired of having my MyISAM tables corrupted, no views, no stored procedures, no CHECK constraints. Ok there's MySQL 5 but, sorry, I don't think I need it anymore. Well except when I need to install some PHP apps that insist on MySQL.
And the primary reason qmail is not used more _is_ the license.
There's also BDB, but we can consider it dead (it's been dead for long, actually). So yeah, MySQL is heavily dependent on InnoDB. The best alternative, should Oracle decide to refuse licensing or extort money from InnoDB licenses in the future, is to fork InnoDB and encourage community development.
Sigh, they have been "improving and optimizing" BDB for years, but still it's so slow compared to MyISAM and InnoDB. Try filling a BDB table with a million+ rows... I guess you really need a storage engine that's specifically designed for relational database. BerkeleyDB is basically just a hash/key-value pair transaction storage.
From what I understand there are several developers at MySQL who understand the innodb codebase extremely well. The first smell of trouble from Oracle and they fork the last GPL version and take it from there.
Are these the same developers that develop MyISAM? Then I wouldn't count on it. MyISAM has been developed for what, 10, 15 years? And yet it's still so crappy, no transactions, no row-level locking, no foreign key checking? The only good thing about it is full text indexing. So how in god's name would these MyISAM developers suddenly master InnoDB?
MaxDB is dead. Do many people really use MaxDB nowadays? Is it actively developed today? No and no. There's a reason SAP dumped SAPDB, it was unmaintainable and it was crap. It still is.
MySQL *does* depend a lot on InnoDB and InnoBase. It's the strongest, most featureful storage engine for general use. MyISAM doesn't support row locking, foreign key checking, MVCC, or even *transaction*, for Christ's sake. It's been developed for many years by MySQL AB yet still lacks so many features. So we can probably guess how competent MySQL AB is in writing storage engines...
PostgreSQL is indeed one of the later player in MVCC. Oracle had been doing MVCC for longer, and Interbase/Firebird for much much longer than that. In fact IB creator is said to be the inventor of MVCC, though the concept of logging/append-only has probably been around for even longer.
However, SQL Server is even a later player. Later than PostgreSQL and MySQL+InnoDB. SQL Server is only MVCC since Yukon, I believe.
... PostgreSQL is better than or equal to MySQL in every respect....
Here are three cases, among others, where I can't use Postgres or where Postgres is not the best solution: a) running database server natively on Win9x; b) embedded database manager; c) non-MVCC operation (e.g. due to high update+delete frequency). While these points can be argued (e.g. embedded is not the safest mode of operation, etc), there are people who want and/or need them.
There are other points/cases like availability of hosting providers, full text indexing (MySQL's is easier and works out of the box), etc. Everything has its place and there's no thing that can be better at other thing in every respect.
I'm not sure, but does ext3 actually have all the features you mention?
Sorry, should've stated more clearly that some of the points are optional. The most important features needed is quota, ACL, fast recovery, large dir and small files performance (think Maildir and squid), and being able to work nicely with Bestcrypt. Oh and yeah, it has to be stable. Reiser3 burns me once several years ago, have been reluctant to try it again. It's really not fun moving many terabytes of files only to find later that some of them rot or got corrupted because of filesystem bugs.
I'd looove to replace ext2/3 as my filesystem for years since it's not so fast and most distro don't include binary tree indexing for ext3 (so large dir is slow). Unfortunately I haven't been able to do so. Here are my requirements:
1. Distro support. I don't want to have to compile my own kernel. The FS needs to be supported by the distro (Debian in this case). I want to be able to create root partition and RAID with the FS.
2. ACL and extended attributes.
3. extended inode attributes would be nice ("chattr +i" is handy sometimes).
4. optionally I would like to be able to create large Bestcrypt partitions (e.g. 30GB) with that FS.
5. fast large dir and small files performance (I have millions of small files on my desktop).
6. no need to fsck or fast fsck (i.e. journalling or some other technique or whatever).
7. disk quota!
8. optionally, transparent compression and encryption will be a big plus point.
9. Snapshots would be nice too, for consistent backups.
10. Versioning is also very welcome.
XFS: very close but it still has problems with #4. It also doesn't have undelete like ext2/ext3 (not that it's a requirement though).
JFS: it just lacks many features.
Reiser3: How's the quota support, still have to patch kernel everytime? Plus it doesn't have ACL.
Reiser4: not ready yet.
I might have to look at FreeBSD after all. Background fsck, hmm....
Agreed. MyISAM seems to be the devil here. And to think that MyISAM is developed by MySQL AB themselves and still has corruption issues after years of being developed, and still haven't caught up with the other engines (transaction, foreign key checking, et al), makes me have less confidence in MySQL AB:-)
Sorry, I meant TX ID wrap around, not OID. I hope from now on (Postgres 8.1 onwards) I can forget about doing vacuuming (except when doing fine-tuning, perhaps).
tsearch2 is okay, but what I meant was something like a new index type that is directly supported by Postgres (like in MySQL and Oracle).
Large TEXT and BYTEA columns are not efficient to handle. As of now they do not allow stream or chunk processing (contrast this with the traditional blob data type).
8.1 has 2PC, but it is not XA compliant yet. I'm not sure if this is a big deal though.
Slashdot Mirror
A lot of HIV/AIDS research is going on, but I wonder, what about Hepatitis C virus? As I recall, it also leads to fatality (liver damage + death) in more than 70-80% of the cases, transmits much like HIV (blood transfusion, needles, sexual intercourse), and in some regions especially South East Asia it's far more prevalent than HIV. There's also no known vaccine against it at the moment.
I can transfer songs to my old iPod mini using gtkpod and amarok, which is fine. The only problem I have is when my brother connect the device using iTunes on Windows, the program erases all the existing songs. No problem, I can just smack my brother on the head and retransfer.
However, almost a year ago I bought a Creative Zen Vision (due to the new iPod haven't arrived on my country yet, plus this Zen Vision has audio recording and FM radio capability). To this day I haven't been able to use Linux to upload my songs. Sigh.
it's L for Location. Ctrl-L is pretty common I'd say, several browsers and file managers use it. but it's not documented, I found out about it here just like you did.
Sigh, every now and then someone will come and say something like this.
Perl, Ruby, Python, PHP are not statically typed.
Ruby and Python *are* strongly typed.
Perl, C, PHP are weakly typed.
Blame those brain-dead PHP "architects" for designing the API for the sendmail() PHP function. The fourth argument accepts arbitrary headers. The 4th arg is used a lot because the damn function doesn't even provide another argument for the From header! It's easily exploitable because those idiotic PHP "programmers" never check values they send to functions, thus sendmail($to, $subject, $body, "From: $from") is easily exploitable by spammers through injecting nasty values to $from. I hate everything PHP-related.
What about AMR? It seems to be designed for speech and widely supported by mobile devices. Though I'm not sure about the licensing issues.
On a side note, does anyone know of an easy way to convert AMR to MP3/OGG/WAV, preferable on Linux? Yes, I've tried Google results like this, but couldn't make it to work.
I feel for the Firebird community, they probably do need more recognition and press. But then, maybe if they could release stuffs more often, they would get mentioned more often too.
It's hard to get more attention if your "competitors" are of PostgreSQL caliber. Postgres do major releases every 6-12 months and is getting better all the time at faster rate. It's getting picked up by companies and has the strongest open source support around it.
Meanwhile, when will FB 2.0-final be released? When will I be getting index longer than 240 (or was it in the order of 500) bytes? When will the documentation be half-decent?
I consider my decision to go with Postgres over Firebird several years ago was the best decision I've ever made.
God, I'll take psql command line client than mysql's any day!
By the way, can you really use MySQL (or PostgreSQL) for SAP nowadays? Does SAP really "actively support" MySQL? In what ways?
Is Larry Wall among the ones who were laid off?
Um, the license? Add to that: I'm tired of having my MyISAM tables corrupted, no views, no stored procedures, no CHECK constraints. Ok there's MySQL 5 but, sorry, I don't think I need it anymore. Well except when I need to install some PHP apps that insist on MySQL.
And the primary reason qmail is not used more _is_ the license.
Hey, at least Postgres is a better hammer than MySQL. And it's fREE (as in beer and speech and more).
Too bad PostgreSQL is a PITA to install on Win32.
Wake up. This is 2005, not 1999. Postgresql-on-Cygwin era is over man. Read this. PostgreSQL is easiest to install, easier than MySQL or Oracle!
There's also BDB, but we can consider it dead (it's been dead for long, actually). So yeah, MySQL is heavily dependent on InnoDB. The best alternative, should Oracle decide to refuse licensing or extort money from InnoDB licenses in the future, is to fork InnoDB and encourage community development.
Sigh, they have been "improving and optimizing" BDB for years, but still it's so slow compared to MyISAM and InnoDB. Try filling a BDB table with a million+ rows... I guess you really need a storage engine that's specifically designed for relational database. BerkeleyDB is basically just a hash/key-value pair transaction storage.
From what I understand there are several developers at MySQL who understand the innodb codebase extremely well. The first smell of trouble from Oracle and they fork the last GPL version and take it from there.
Are these the same developers that develop MyISAM? Then I wouldn't count on it. MyISAM has been developed for what, 10, 15 years? And yet it's still so crappy, no transactions, no row-level locking, no foreign key checking? The only good thing about it is full text indexing. So how in god's name would these MyISAM developers suddenly master InnoDB?
MaxDB is dead. Do many people really use MaxDB nowadays? Is it actively developed today? No and no. There's a reason SAP dumped SAPDB, it was unmaintainable and it was crap. It still is.
MySQL *does* depend a lot on InnoDB and InnoBase. It's the strongest, most featureful storage engine for general use. MyISAM doesn't support row locking, foreign key checking, MVCC, or even *transaction*, for Christ's sake. It's been developed for many years by MySQL AB yet still lacks so many features. So we can probably guess how competent MySQL AB is in writing storage engines...
PostgreSQL is indeed one of the later player in MVCC. Oracle had been doing MVCC for longer, and Interbase/Firebird for much much longer than that. In fact IB creator is said to be the inventor of MVCC, though the concept of logging/append-only has probably been around for even longer.
However, SQL Server is even a later player. Later than PostgreSQL and MySQL+InnoDB. SQL Server is only MVCC since Yukon, I believe.
Here are three cases, among others, where I can't use Postgres or where Postgres is not the best solution: a) running database server natively on Win9x; b) embedded database manager; c) non-MVCC operation (e.g. due to high update+delete frequency). While these points can be argued (e.g. embedded is not the safest mode of operation, etc), there are people who want and/or need them.
There are other points/cases like availability of hosting providers, full text indexing (MySQL's is easier and works out of the box), etc. Everything has its place and there's no thing that can be better at other thing in every respect.
Yes, I might be secretly in love with NTFS. If only it had solid support on Linux/Unices.
But I read that NTFS is slow with large dir and lots of small files?
I'm not sure, but does ext3 actually have all the features you mention?
Sorry, should've stated more clearly that some of the points are optional. The most important features needed is quota, ACL, fast recovery, large dir and small files performance (think Maildir and squid), and being able to work nicely with Bestcrypt. Oh and yeah, it has to be stable. Reiser3 burns me once several years ago, have been reluctant to try it again. It's really not fun moving many terabytes of files only to find later that some of them rot or got corrupted because of filesystem bugs.
I'd looove to replace ext2/3 as my filesystem for years since it's not so fast and most distro don't include binary tree indexing for ext3 (so large dir is slow). Unfortunately I haven't been able to do so. Here are my requirements:
1. Distro support. I don't want to have to compile my own kernel. The FS needs to be supported by the distro (Debian in this case). I want to be able to create root partition and RAID with the FS.
2. ACL and extended attributes.
3. extended inode attributes would be nice ("chattr +i" is handy sometimes).
4. optionally I would like to be able to create large Bestcrypt partitions (e.g. 30GB) with that FS.
5. fast large dir and small files performance (I have millions of small files on my desktop).
6. no need to fsck or fast fsck (i.e. journalling or some other technique or whatever).
7. disk quota!
8. optionally, transparent compression and encryption will be a big plus point.
9. Snapshots would be nice too, for consistent backups.
10. Versioning is also very welcome.
XFS: very close but it still has problems with #4. It also doesn't have undelete like ext2/ext3 (not that it's a requirement though).
JFS: it just lacks many features.
Reiser3: How's the quota support, still have to patch kernel everytime? Plus it doesn't have ACL.
Reiser4: not ready yet.
I might have to look at FreeBSD after all. Background fsck, hmm....
Second that. "Traditional" Unix tools sometimes just don't cut it (or they do, but requires significantly longer typing and multi-piping work).
I use this all the time:
$ perlrename -e's/.\[www.descargasweb.net\]//' *
$ perlrename -e's/.\[www.\S+?\]//' *
$ perlrename -e'$_=lc' *
$ perlrename -de's/Sex And The City - S(\d+)E(\d+)/SATC - $1$2/ig' Sex*
etc etc
where perlrename is a 30-something perl script.
Agreed. MyISAM seems to be the devil here. And to think that MyISAM is developed by MySQL AB themselves and still has corruption issues after years of being developed, and still haven't caught up with the other engines (transaction, foreign key checking, et al), makes me have less confidence in MySQL AB :-)
Sorry, I meant TX ID wrap around, not OID. I hope from now on (Postgres 8.1 onwards) I can forget about doing vacuuming (except when doing fine-tuning, perhaps).
tsearch2 is okay, but what I meant was something like a new index type that is directly supported by Postgres (like in MySQL and Oracle).
Large TEXT and BYTEA columns are not efficient to handle. As of now they do not allow stream or chunk processing (contrast this with the traditional blob data type).
8.1 has 2PC, but it is not XA compliant yet. I'm not sure if this is a big deal though.
Yay for Postgres!