Question: I try to mount the mqueue on /dev/mqueue to get an overview about the created message queues (created by mq\_open()). I already tried it in the terminal with this:

```
mount -t mqueue none /dev/mqueue

```

It works fine. Now I want to do this inside my c++ code with this:

```
mount("mqueue", "/dev/mqueue", "vfat", MS_NOATIME, NULL)

```

But I get always the error: "No such file or directory".

Does somebody has an idea what could be my failure?

Answer: 
This is a two part question:

**Part 1:**

First part will be your data store and pull. Where you will use in your cfquery, cfqueryparam that will look like this:

```
INSERT into EMPLOYEES (FirstName,LastName,Photo)
VALUES ('Aiden','Quinn',<cfqueryparam value="#ImageGetBlob(myImage)#" cfsqltype='cf_sql_blob'>)

```

To select then reconstruct you will use this:

```
<cfset myImage = ImageNew(#GetBLOBs.PHOTO#)>

```

Where you can then do this:

```
<img src='#myImage#>

```

[Above examples pulled from the docs.](http://help.adobe.com/livedocs/coldfusion/8/htmldocs/help.html?content=functions_h-im_23.html)

Get familiar with `<cfimage>` and cfscript version `image()` for editing (rotating, scaling, etc.)

**Part 2:**

The other part to your question has to do with upload limits.

Coldfuion has limits that can be changed in CFIDE or RAILO equivalent. There is also limiters set in your web service like apache and IIS, you will have to look into this to change it.

BUT if you are only concerned about 10 mb size images you will be fine. It is when you get into hundreds of MB size files that will cause you headaches.

Remember on your form to set your form enctype to this because you will have to upload your file to your server before you can work with it: 

```
<form action="workPage.cfm" method="post" enctype="multipart/form-data">

```

Also you will have to access that file using `<cffile>`

I think all this is enough to get you started.
If you are concerned about the storage size of an image, and this is of course a reasonable concern, then you could use to scale the image down to the maximum dimensions and quality or compression level (if stored as a jpeg) that you need within your application. 

Storing your images within a database allows them to be more easily portable, across a cluster for instance. If that is not a concern, then what I tend to do is generate a unique name for each image uploaded, rename them, and store the unique name in the database rather than the image itself.