Dexter Gordon – Dexter Gordon: The Complete Blue Note Sixties Sessions

Disc: 1

  1. I Was Doing Allright
  2. I Want More
  3. You’ve Changed
  4. Society Red
  5. For Regulars Only (Alt. Take)
  6. It’s You Or No One
  7. For Regulars Only
  8. Landslide
  9. Modal Mood
  10. Clear The Dex
  11. Boy Saxophonist (Monologue By Dexter Gordon)

 

Disc: 2

  1. Soul Sister
  2. Smile
  3. Ernie’s Tune
  4. I Want More
  5. The End Of A Love Affair
  6. Serenade In Blue
  7. You Said It
  8. Love Locked Out
  9. Blue Gardenia
  10. Second Balcony Jump
  11. Six Bits Jones
  12. Lady Be Good
  13. On Be Bop (Monologue By Dexter Gordon)

 

Disc: 3

  1. Three O’Clock In The Morning
  2. Second Balcony Jump
  3. Where Are You?
  4. Cheese Cake
  5. I Guess I’ll Hang My Tears Out To Dry
  6. Love For Sale
  7. McSplivens
  8. The Backbone
  9. Soy Califa
  10. Until The Real Thing Comes Along
  11. You Stepped Out Of A Dream
  12. Don’t Explain

 

Disc: 4

  1. Our Love Is Here To Stay
  2. Broadway
  3. Stairway To The Stars
  4. A Night In Tunisia
  5. Willow Weep For Me
  6. Scrapple From The Apple
  7. Coppin’ The Haven
  8. Tanya
  9. It All Began… (Monologue By Dexter Gordon)

 

Disc: 5

  1. Kong Neptune
  2. Darn That Dream
  3. Hanky Panky
  4. Devilette
  5. Clubhouse
  6. Jodi
  7. I’m A Fool To Want You
  8. Lady Iris B

 

Disc: 6

  1. Le Coiffeur
  2. Manha De Carnaval
  3. Flick Of A Trick
  4. Everybody’s Somebody’s Fool
  5. Very Saxily Yours
  6. Shiny Stockings
  7. Who Can I Turn To
  8. Heartaches
  9. Dexter On Bird (Monologue By Dexter Gordon)

Source: Dexter Gordon – Dexter Gordon: The Complete Blue Note Sixties Sessions – Amazon.com Music

Dexter Gordon – Dexter Gordon: The Complete Blue Note Sixties Sessions was last modified: July 13th, 2017 by Jovan Stosic

How To Set Up MySQL Master-Master Replication

Intro

This second installment of “Scaling Web Applications” will list out the steps necessary for scaling a mysql deployment over two VPS.

The first article in this series laid out the steps needed to load-balance nginx over two VPS, and it is recommended that you read that article first.

MySQL replication is the process by which a single data set, stored in a MySQL database, will be live-copied to a second server. This configuration, called “master-slave” replication, is a typical setup. Our setup will be better than that, because master-master replication allows data to be copied from either server to the other one. This subtle but important difference allows us to perform mysql read or writes from either server. This configuration adds redundancy and increases efficiency when dealing with accessing the data.

The examples in this article will be based on two VPS, named Server C and Server D.

Server C: 3.3.3.3

Server D: 4.4.4.4

Step 1 – Install and Configure MySQL on Server C

The first thing we need to do is to install the mysql-server and mysql-client packages on our server. We can do that by typing the following:

sudo apt-get install mysql-server mysql-client

By default, the mysql process will only accept connections on localhost (127.0.0.1). To change this default behavior and change a few other settings necessary for replication to work properly, we need to edit /etc/mysql/my.cnf on Server C. There are four lines that we need to change, which are currently set to the following:

#server-id              = 1
#log_bin                = /var/log/mysql/mysql-bin.log
#binlog_do_db           = include_database_name
bind-address            = 127.0.0.1

The first of those lines is to uniquely identify our particular server, in our replication configuration. We need to uncomment that line, by removing the “#” before it. The second line indicates the file in which changes to any mysql database or table will be logged.

The third line indicates which databases we want to replicate between our servers. You can add as many databases to this line as you’d like. The article will use a single database named “example” for the purposes of simplicity. And the last line tells our server to accept connections from the internet (by not listening on 127.0.0.1).

server-id               = 1
log_bin                 = /var/log/mysql/mysql-bin.log
binlog_do_db            = example
# bind-address            = 127.0.0.1

Now we need to restart mysql:

sudo service mysql restart

We next need to change some command-line settings within our mysql instance. Back at our shell, we can get to our root mysql user by typing the following:

mysql -u root -p 

Please note that the password this command will prompt you for is that of the root mysql user, not the root user on our droplet. To confirm that you are logged in to the mysql shell, the prompt should look like the following.

mysql> 

Once we are logged in, we need to run a few commands.

We need to create a pseudo-user that will be used for replicating data between our two VPS. The examples in this article will assume that you name this user “replicator”. Replace “password” with the password you wish to use for replication.

create user 'replicator'@'%' identified by 'password'; 

Next, we need to give this user permissions to replicate our mysql data:

grant replication slave on *.* to 'replicator'@'%'; 

Permissions for replication cannot, unfortunately, be given on a per-database basis. Our user will only replicate the database(s) that we instruct it to in our config file.

For the final step of the initial Server C configuration, we need to get some information about the current MySQL instance which we will later provide to Server D.

The following command will output a few pieces of important information, which we will need to make note of:

show master status; 

The output will looking similiar to the following, and will have two pieces of critical information:

+------------------+----------+--------------+------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------------------+----------+--------------+------------------+
| mysql-bin.000001 |      107 | example      |                  |
+------------------+----------+--------------+------------------+
1 row in set (0.00 sec)

We need to make a note of the file and position which will be used in the next step.

Step 2 – Install and Configure MySQL on Server D

We need to repeat the same steps that we followed on Server C. First we need to install it, which we can do with the following command:

sudo apt-get install mysql-server mysql-client

Once the two packages are properly installed, we need to configure it in much the same way as we configured Server C. We will start by editing the /etc/mysql/my.cnf file.

sudo nano /etc/mysql/my.cnf 

We need to change the same four lines in the configuration file as we changed earlier.

The defaults are listed below, followed by the changes we need to make.

#server-id              = 1
#log_bin                = /var/log/mysql/mysql-bin.log
#binlog_do_db           = include_database_name
bind-address            = 127.0.0.1

We need to change these four lines to match the lines below. Please note, that unlike Server C, the server-id for Server D cannot be set to 1.

server-id              = 2
log_bin                = /var/log/mysql/mysql-bin.log
binlog_do_db           = example
# bind-address            = 127.0.0.1

After you save and quit that file, you need to restart mysql:

sudo service mysql restart

It is time to go into the mysql shell and set some more configuration options.

mysql -u root -p 

First, just as on Server C, we are going to create the pseudo-user which will be responsible for the replication. Replace “password” with the password you wish to use.

create user 'replicator'@'%' identified by 'password'; 

Next, we need to create the database that we are going to replicate across our VPS.

create database example; 

And we need to give our newly created ‘replication’ user permissions to replicate it.

grant replication slave on *.* to 'replicator'@'%'; 

The next step involves taking the information that we took a note of earlier and applying it to our mysql instance. This will allow replication to begin. The following should be typed at the mysql shell:

slave stop; 
CHANGE MASTER TO MASTER_HOST = '3.3.3.3', MASTER_USER = 'replicator', MASTER_PASSWORD = 'password', MASTER_LOG_FILE = 'mysql-bin.000001', MASTER_LOG_POS = 107; 
slave start; 

You need to replace ‘password’ with the password that you have chosen for replication. Your values for MASTER_LOG_FILE and MASTER_LOG_POS may differ than those above. You should copy the values that “SHOW MASTER STATUS” returns on Server C.

The last thing we have to do before we complete the mysql master-master replication is to make note of the master log file and position to use to replicate in the other direction (from Server D to Server C).

We can do that by typing the following:

SHOW MASTER STATUS; 

The output will look similiar to the following:

+------------------+----------+--------------+------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------------------+----------+--------------+------------------+
| mysql-bin.000004 |      107 | example      |                  |
+------------------+----------+--------------+------------------+
1 row in set (0.00 sec)

Take note of the file and position, as we will have to enter those on server C, to complete the two-way replication.

The next step will explain how to do that.

Step 3 – Completing Replication on Server C

Back on Server C, we need to finish configuring replication on the command line. Running this command will replicate all data from Server D.

 
slave stop; 
CHANGE MASTER TO MASTER_HOST = '4.4.4.4', MASTER_USER = 'replicator', MASTER_PASSWORD = 'password', MASTER_LOG_FILE = 'mysql-bin.000004', MASTER_LOG_POS = 107; 
slave start; 

Keep in mind that your values may differ from those above. Please also replace the value of MASTER_PASSWORD with the password you created when setting up the replication user.

The output will look similiar to the following:

Query OK, 0 rows affected (0.01 sec)

The last thing to do is to test that replication is working on both VPS. The last step will explain an easy way to test this configuration.

Step 4 – Testing Master-Master Replication

Now that have all the configuration set up, we are going to test it now. To do this, we are going to create a table in our example database on Server C and check on Server D to see if it shows up. Then, we are going to delete it from Server D and make sure it’s no longer showing up on Server C.

We now need to create the database that will be replicated between the servers. We can do that by typing the following at the mysql shell:

create database example; 

Once that’s done, let’s create a dummy table on Server C:

create table example.dummy (`id` varchar(10)); 

We now are going to check Server D to see if our table exists.

 
show tables in example; 

We should see output similiar to the following:

+-------------------+
| Tables_in_example |
+-------------------+
| dummy             |
+-------------------+
1 row in set (0.00 sec)

The last test to do is to delete our dummy table from Server D. It should also be deleted from Server C.

We can do this by entering the following on Server D:

DROP TABLE dummy; 

To confirm this, running the “show tables” command on Server C will show no tables:

Empty set (0.00 sec)

And there you have it! Working mysql master-master replication. As always, any feedback is more than welcome.

How To Set Up MySQL Master-Master Replication was last modified: July 13th, 2017 by Jovan Stosic

John Coltrane and Johnny Hartman – John Coltrane,Johnny Hartman

Track Listing

Sample Title/Composer Performer Time Stream
1 5:20 Spotify
2 5:32 Spotify
3 4:55 Spotify
4 5:29 Spotify
5 5:36 Spotify
6 4:19

Source: John Coltrane and Johnny Hartman – John Coltrane,Johnny Hartman | Songs, Reviews, Credits | AllMusic

John Coltrane and Johnny Hartman – John Coltrane,Johnny Hartman was last modified: July 13th, 2017 by Jovan Stosic

How To Set Up Master Slave Replication in MySQL

About MySQL replication

MySQL replication is a process that allows you to easily maintain multiple copies of a MySQL data by having them copied automatically from a master to a slave database. This can helpful for many reasons including facilating a backup for the data,a way to analyze it without using the main database, or simply as a means to scale out.

This tutorial will cover a very simple example of mysql replication—one master will send information to a single slave. For the process to work you will need two IP addresses: one of the master server and and one of the slave.

This tutorial will use the following IP addresses:

12.34.56.789- Master Database

12.23.34.456- Slave Database

Setup

This article assumes that you have user with sudo privileges and have MySQL installed. If you do not have mysql, you can install it with this command:

sudo apt-get install mysql-server mysql-client

Step One—Configure the Master Database

Open up the mysql configuration file on the master server.

sudo nano /etc/mysql/my.cnf

Once inside that file, we need to make a few changes.

The first step is to find the section that looks like this, binding the server to the local host:

bind-address            = 127.0.0.1

Replace the standard IP address with the IP address of server.

bind-address            = 12.34.56.789

The next configuration change refers to the server-id, located in the [mysqld] section. You can choose any number for this spot (it may just be easier to start with 1), but the number must be unique and cannot match any other server-id in your replication group. I’m going to go ahead and call this one 1.

Make sure this line is uncommented.

server-id               = 1

Move on to the log_bin line. This is where the real details of the replication are kept. The slave is going to copy all of the changes that are registered in the log. For this step we simply need to uncomment the line that refers to log_bin:

log_bin                 = /var/log/mysql/mysql-bin.log

Finally, we need to designate the database that will be replicated on the slave server. You can include more than one database by repeating this line for all of the databases you will need.

binlog_do_db            = newdatabase

After you make all of the changes, go ahead and save and exit out of the configuration file.

Refresh MySQL.

sudo service mysql restart

The next steps will take place in the MySQL shell, itself.

Open up the MySQL shell.

mysql -u root -p

We need to grant privileges to the slave. You can use this line to name your slave and set up their password. The command should be in this format:

GRANT REPLICATION SLAVE ON *.* TO 'slave_user'@'%' IDENTIFIED BY 'password';

Follow up with:

FLUSH PRIVILEGES;

The next part is a bit finicky. To accomplish the task you will need to open a new window or tab in addition to the one that you are already using a few steps down the line.

In your current tab switch to “newdatabase”.

USE newdatabase;

Following that, lock the database to prevent any new changes:

FLUSH TABLES WITH READ LOCK;

Then type in:

SHOW MASTER STATUS;

You will see a table that should look something like this:

mysql> SHOW MASTER STATUS;
+------------------+----------+--------------+------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------------------+----------+--------------+------------------+
| mysql-bin.000001 |      107 | newdatabase  |                  |
+------------------+----------+--------------+------------------+
1 row in set (0.00 sec)

This is the position from which the slave database will start replicating. Record these numbers, they will come in useful later.

If you make any new changes in the same window, the database will automatically unlock. For this reason, you should open the new tab or window and continue with the next steps there.

Proceeding the with the database still locked, export your database using mysqldump in the new window (make sure you are typing this command in the bash shell, not in MySQL).

mysqldump -u root -p --opt newdatabase > newdatabase.sql

Now, returning to your your original window, unlock the databases (making them writeable again). Finish up by exiting the shell.

UNLOCK TABLES;
QUIT;

Now you are all done with the configuration of the the master database.

Step Two—Configure the Slave Database

Once you have configured the master database. You can put it aside for a while, and we will now begin to configure the slave database.

Log into your slave server, open up the MySQL shell and create the new database that you will be replicating from the master (then exit):

CREATE DATABASE newdatabase;
EXIT;

Import the database that you previously exported from the master database.

mysql -u root -p newdatabase < /path/to/newdatabase.sql

Now we need to configure the slave configuration in the same way as we did the master:

sudo nano /etc/mysql/my.cnf

We have to make sure that we have a few things set up in this configuration. The first is the server-id. This number, as mentioned before needs to be unique. Since it is set on the default (still 1), be sure to change it’s something different.

server-id               = 2

Following that, make sure that your have the following three criteria appropriately filled out:

relay-log               = /var/log/mysql/mysql-relay-bin.log
log_bin                 = /var/log/mysql/mysql-bin.log
binlog_do_db            = newdatabase

You will need to add in the relay-log line: it is not there by default. Once you have made all of the necessary changes, save and exit out of the slave configuration file.

Restart MySQL once again:

sudo service mysql restart

The next step is to enable the replication from within the MySQL shell.

Open up the the MySQL shell once again and type in the following details, replacing the values to match your information:

CHANGE MASTER TO MASTER_HOST='12.34.56.789',MASTER_USER='slave_user', MASTER_PASSWORD='password', MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=  107;

This command accomplishes several things at the same time:

  1. It designates the current server as the slave of our master server.
  2. It provides the server the correct login credentials
  3. Last of all, it lets the slave server know where to start replicating from; the master log file and log position come from the numbers we wrote down previously.

With that—you have configured a master and slave server.

Activate the slave server:

START SLAVE;

You be able to see the details of the slave replication by typing in this command. The \G rearranges the text to make it more readable.

SHOW SLAVE STATUS\G

If there is an issue in connecting, you can try starting slave with a command to skip over it:

SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; SLAVE START;

All done.

Source: How To Set Up Master Slave Replication in MySQL | DigitalOcean

How To Set Up Master Slave Replication in MySQL was last modified: July 13th, 2017 by Jovan Stosic

Upgrading Your ownCloud Server — ownCloud 8.0 Server Administration Manual 8.0 documentation

Manual Upgrade Procedure

Always start by making a fresh backup.

If you are upgrading to a major release, for example from 8.1.3 to 8.2, you must review all third party applications (not core apps) for compatibility with your new ownCloud version. Then disable all of them before starting the upgrade.

Next put your server in maintenance mode. This prevents new logins, locks the sessions of logged-in users, and displays a status screen so users know what is happening. There are two ways to do this, and the preferred method is to use the occ command, which you must run as your HTTP user. This example is for Ubuntu Linux:

$ sudo -u www-data php occ maintenance:mode --on

The other way is by entering your config.php file and changing 'maintenance' => false, to 'maintenance' =>true,.

  1. Back up your existing ownCloud Server database, data directory, and config.php file. (See Backing up ownCloud.)
  2. Download and unpack the latest ownCloud Server release (Archive file) from owncloud.org/install/ into an empty directory outside of your current installation. For example, if your current ownCloud is installed in/var/www/owncloud/ you could create a new directory called /var/www/owncloud2/

To unpack your new tarball:: tar xjf owncloud-latest.tar.bz2

  1. Stop your Web server.
  2. Rename or move your current ownCloud directory (named owncloud/ if installed using defaults) to another location.
  3. This creates a new owncloud/ directory populated with your new server files. Copy this directory and its contents to the original location of your old server, for example /var/www/, so that once again you have/var/www/owncloud .
  4. Copy and paste the config.php file from your old version of ownCloud to your new ownCloud version.
  5. If you keep your data/ directory in your owncloud/ directory, copy it from your old version of ownCloud to theowncloud/ directory of your new ownCloud version. If you keep it outside of owncloud/ then you don’t have to do anything with it, because its location is configured in your original config.php, and none of the upgrade steps touch it.

We recommend storing your data/ directory in a location other than your owncloud/ directory.

  1. Restart your Web server.

  2. Now you should be able to open a Web browser to your ownCloud server and

    log in as usual. You have a couple more steps to go: You should see a Start Update screen, just like in theUpgrading With Your Linux Package Manager section, above. Review the prerequisites, and if you have followed all the steps click the Start Update button.

    If you are running a large installation with a lot of files and users, you should launch the upgrade from the command line using occ to avoid PHP timeouts, like this example on Ubuntu Linux:

    $ sudo -u www-data php occ upgrade
    

    The occ command does not download ownCloud updates. You must first download and install the updated code (steps 1-3), and then occ performs the final upgrade steps.

  3. The upgrade operation takes a few minutes to a few hours, depending on the size of your installation. When it is finished you will see a success message, or an error message that will tell where it went wrong.

Assuming your upgrade succeeded, take a look at the bottom of your Admin page to verify the version number. Check your other settings to make sure they’re correct. Go to the Apps page and review the core apps to make sure the right ones are enabled. Re-enable your third-party apps. Then apply strong permissions to your ownCloud directories (Setting Strong Directory Permissions).

Source: Upgrading Your ownCloud Server — ownCloud 8.0 Server Administration Manual 8.0 documentation

Upgrading Your ownCloud Server — ownCloud 8.0 Server Administration Manual 8.0 documentation was last modified: July 13th, 2017 by Jovan Stosic

Tenderly – Stacey Kent

Track Listing

Title/Composer Performer Time
1 3:41
2 2:13
3 4:34
4 3:42
5 4:03
6 3:47
7 2:57
8 3:28
9 4:24
10 3:28
11 4:01
12 2:53

Source: Tenderly – Stacey Kent | Songs, Reviews, Credits | AllMusic

Tenderly – Stacey Kent was last modified: July 13th, 2017 by Jovan Stosic

Miles Davis, Dave Brubeck, Chet Baker, Stan Getz, John Coltrane, Thelonious Monk, Oscar Peterson, Jimmy Smith, Erroll Garner, Lee Morgan – Worlds Greatest Jazz Collection: Modern Jazz – Cool Jazz, Westcoast, Hard Bop, Modern Mainstream – Amazon.com Music

Worlds Greatest Jazz Collection: Modern Jazz – Cool Jazz, Westcoast, Hard Bop, Modern Mainstream Box set, Import Miles Davis (Artist), Dave Brubeck (Artist), Chet Baker (Artist),

CD001 – Miles Davis (1953-54) Vol.1 [320] CD002 – Miles Davis (1953-54) Vol.2 [320] CD003 – Miles Davis (1954-55) Vol.3 [320] CD004 – Miles Davis (1955-56) Vol.4 [320] CD005 – Dave Brubeck (1953) Vol.1 [320] CD006 – Dave Brubeck (1953-54) Vol.2 [320] CD007 – Lee Konitz (1956) [320] CD008 – Gerry Mulligan, Shorty Rogers (1951-53) [320] CD009 – Tony Scott Quintet (1957) [320] CD010 – J.J. Johnson Quintet (1954-55) [320] CD011 – Lennie Tristano (1955) [320] CD012 – Modern Jazz Quartet (1952-55) [320] CD013 – Sonny Rollins & Modern Jazz Quartet (1953-55) [320] CD014 – Stan Getz Quintet (1952-54) Vol.1 [320] CD015 – Stan Getz Quintet (1951) Vol.2 [320] CD016 – Stan Getz & Lionel Hampton (1955) Vol.3 [320] CD017 – Stan Getz (1955) Vol.4 [320] CD018 – Chet Baker (1953) Vol.1 [320] CD019 – Chet Baker (1953-54) Vol.2 [320] CD020 – Chet Baker (1954-55) Vol.3 [320] CD021 – Chet Baker (1955) Vol.4 [320] CD022 – Gerry Mulligan Quartet (1952-53) Vol.1 [320] CD023 – Gerry Mulligan Quartet (1954) Vol.2 [320] CD024 – Gerry Mulligan Sextet (1955) Vol.3 [320] CD025 – Gerry Mulligan & Paul Desmond Quartet (1957) [320] CD026 – Clifford Brown, Tadd Dameron And His Orchestra (1953-54) [320] CD027 – Jimmy Giuffre (1954-56) Vol.1 [320] CD028 – Jimmy Giuffre (1955) Vol.2 [320] CD029 – Art Pepper Quartet (1957) [320] CD030 – Howard Rumsey’s Lighthouse All-Stars (1953) [320] CD031 – Shelly Mann And His Friends (1956) [320] CD032 – Herb Geller Quartet (1955) [320] CD033 – Herb Geller Sextette (1955) [320] CD034 – Serge Chaloff (1956) [320] CD035 – Barney Kessel (1954-57) Vol.1 [320] CD036 – Barney Kessel (1955) Vol.2 [320] CD037 – Shorty Rogers And His Giants (1953) [320] CD038 – Lou Donaldson, Clifford Brown (1953) [320] CD039 – Gigi Gryce, Clifford Brown (1953) [320] CD040 – Clifford Brown (1954) Vol.1 [320] CD041 – Clifford Brown (1954) Vol.2 [320] CD042 – Clifford Brown (1954) Vol.3 [320] CD043 – Art Blakey (1954) Vol.1 [320] CD044 – Art Blakey (1955) Vol.2 [320] CD045 – Art Blakey (1955) Vol.3 [320] CD046 – Art Blakey (1957) Vol.4 [320] CD047 – Art Blakey (1957) Vol.5 [320] CD048 – Sonny Rollins (1956) Vol.1 [320] CD049 – Sonny Rollins (1956) Vol.2 [320] CD050 – Sonny Rollins (1957) Vol.3 [320] CD051 – Sonny Rollins (1957) Vol.4 [320] CD052 – Sonny Rollins (1955-56) Vol.5 [320] CD053 – Horace Silver (1952) Vol.1 [320] CD054 – Horace Silver (1954-55) Vol.2 [320] CD055 – Charles Mingus (1956) [320] CD056 – Thad Jones (1956) [320] CD057 – Elmo Hope, Tadd Dameron (1956) [320] CD058 – Prestige All Stars (Tenor Conclave) (1956) [320] CD059 – John Coltrane (1957) Vol.1 [320] CD060 – John Coltrane (1957) Vol.2 [320] CD061 – John Coltrane (1957) Vol.3 [320] CD062 – Lee Morgan (1956-57) Vol.1 [320] CD063 – Lee Morgan (1956) Vol.2 [320] CD064 – Kenny Clarke, Cannonball Adderley (1955) [320] CD065 – Cannonball Adderley (1955) Vol.1 [320] CD066 – Cannonball Adderley (1957) Vol.2 [320] CD067 – Johnny Griffin (1957) [320] CD068 – Max Roach Quintet (1956-57) [320] CD069 – Kenny Dorham (1957) [320] CD070 – Prestige All-Stars (1957) [320] CD071 – Jimmy Smith (1956) Vol.1 [320] CD072 – Jimmy Smith (1957) Vol.2 [320] CD073 – Dexter Gordon (1955) [320] CD074 – Hank Mobley (1956) [320] CD075 – Sonny Clark (1957) [320] CD076 – Miles Davis Quintet (1954-56) [320] CD077 – Paul Chambers (1957) [320] CD078 – Thelonious Monk (1954-57) Vol.1 [320] CD079 – Thelonious Monk (1956) Vol.2 [320] CD080 – Thelonious Monk (1957) Vol.3 [320] CD081 – Jackie Mclean (1956-57) [320] CD082 – Nat Adderley Quintet (1955) [320] CD083 – Nat Adderley, Cannonball Adderley (1955-56) [320] CD084 – Oscar Peterson (1950) [320] CD085 – Buddy Defranco (1954) [320] CD086 – Birdland Stars (1956) [320] CD087 – Al Cohn & Zoot Sims (1957) [320] CD088 – Herb Ellis (1957) [320] CD089 – Jay And Kai Quintet (1954) [320] CD090 – The Four Brothers (1957) [320] CD091 – Erroll Garner (1955) [320] CD092 – Dizzy Gillespie-Sonny Rollins-Sonny Stitt (1957) [320] CD093 – Dizzy Gillespie & Stan Getz Sextet (1953) [320] CD094 – Dizzy Gillespie All-Stars (1956) [320] CD095 – Milt Jackson (1956) [320] CD096 – Mose Allison (1957) [320] CD097 – Frank Wess, Jazz Men Detroit (1956) [320] CD098 – Quincy Jones’-Clifford Brown -Art Farmer Swedish All-Stars (1953-56) [320] CD099 – Zoot Sims Quartet (1956) [320] CD100 – All-Star Live Jam Session (1954) [320]

 

Source: Miles Davis, Dave Brubeck, Chet Baker, Stan Getz, John Coltrane, Thelonious Monk, Oscar Peterson, Jimmy Smith, Erroll Garner, Lee Morgan – Worlds Greatest Jazz Collection: Modern Jazz – Cool Jazz, Westcoast, Hard Bop, Modern Mainstream – Amazon.com Music

Miles Davis, Dave Brubeck, Chet Baker, Stan Getz, John Coltrane, Thelonious Monk, Oscar Peterson, Jimmy Smith, Erroll Garner, Lee Morgan – Worlds Greatest Jazz Collection: Modern Jazz – Cool Jazz, Westcoast, Hard Bop, Modern Mainstream – Amazon.com Music was last modified: July 13th, 2017 by Jovan Stosic