search for: image_types

This is what I have class Photo < ActiveRecord::Base belongs_to :image, :polymorphic => true acts_as_list :scope => image end class Place < ActiveRecord::Base has_many :photos, :as => :image end class Child < ActiveRecord::Base has_many :photos, :as => :image end I want to be able to reorder the images. What I need is for the position of the photos to be set

This piece of code takes an uploaded image and resizes it. It''s a bit nasty at the moment as I am still messing around with it. What I can''t understand is why it works for one iteration but then fails with: zero-length blob not permitted `'' On the line: img = Magick::Image.from_blob(self.image).first I am basically doing this in the controller and it fails on the

I can confirm that I'm also seeing this issue with DRBD backed block devices. A test dom0 pair that I've just dist upgraded from Wheezy to Jessie is no longer able to boot any domUs via pygrub. As a test I've just pulled pygrub out of xen-tools-4.5 from experimental but I'm still getting the same error in the bootloader.log: ---- Traceback (most recent call last): File

The following changes since commit 81ad566f155fac31089fde69c87059b217e7e9b6: NEWS: Update for 6.03 release (2014-10-06 09:27:44 -0700) are available in the git repository at: https://github.com/wferi/syslinux/ pub for you to fetch changes up to 68cb978ab7e692d772e4d62d3585b8f7bac43b4b: lua: simplify the function/value handling in the automenu test (2014-10-13 12:44:15 +0200)

Hi everybody, my background: I'm doing Xen since 10++ years, many years with DRBD for high availability, since some time I'm using preferable GlusterFS with FUSE as replicated storage, where I place the image-files for the vms. In my current project we started (successfully) with Xen/GlusterFS too, but because the provider, where we placed the servers, uses widely CEPH, we decided to

# HG changeset patch # User Zhigang Wang <zhigang.x.wang@oracle.com> # Date 1342720736 14400 # Node ID ec9655b30a5fa5b5abb3e05505f681f9be559613 # Parent 43e21ce7f22151524b800a6cf0ac4ba1233b34a7 pygrub: add syslog support to pygrub Currently, when pygrub failed, we don''t know the reason because xend/xl will not capture the stderr message. This patch will log the error message to

....com> > --- > diff -uprN a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c > --- a/com32/elflink/ldlinux/execute.c 2014-10-06 10:27:44.000000000 -0600 > +++ b/com32/elflink/ldlinux/execute.c 2015-02-18 18:46:02.193886584 -0700 > @@ -41,6 +41,7 @@ const struct image_types image_boot_type > { "fdimage", IMAGE_TYPE_FDIMAGE }, > { "com32", IMAGE_TYPE_COM32 }, > { "config", IMAGE_TYPE_CONFIG }, > + { "efi", IMAGE_TYPE_EFI }, > { NULL, 0 }, > }; > > @@ -89,6 +90,13 @@ __export void ex...

Hi, we are still experiencing this error on stable jessie with xen 4.4.1 and it does not appear to be fixed in that version at all. The actual error is: -- snip -- Traceback (most recent call last): File "/usr/lib/xen-4.4/bin/pygrub", line 809, in <module> part_offs = get_partition_offsets(file) File "/usr/lib/xen-4.4/bin/pygrub", line 106, in

...28 ++++++++++++++++++++-------- 2 files changed, 23 insertions(+), 9 deletions(-) diff --git a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c index 653c880..3955571 100644 --- a/com32/elflink/ldlinux/execute.c +++ b/com32/elflink/ldlinux/execute.c @@ -44,6 +44,7 @@ const struct image_types image_boot_types[] = { { NULL, 0 }, }; +extern jmp_buf __return_to_command_prompt; extern int create_args_and_load(char *); __export void execute(const char *cmdline, uint32_t type, bool sysappend) @@ -136,7 +137,8 @@ __export void execute(const char *cmdline, uint32_t type, bool sysapp...

I have a database field called file_type. I want to compare it against an array of types to either display it as an image or just create a link to it. I am sure there is an easy way to do this but I can''t think of it. I don''t want to do this: <% if resource.file_type == ".png" OR resource.file_type == ".jpg" ... %> I would like to do: <% if

How to find out image width and height which is saved in database, with out using any applications or addons Please help --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe

On Mon, Oct 13, 2014 at 12:53:43PM +0200, Ferenc Wagner wrote: > The following changes since commit 81ad566f155fac31089fde69c87059b217e7e9b6: > > NEWS: Update for 6.03 release (2014-10-06 09:27:44 -0700) > > are available in the git repository at: > > https://github.com/wferi/syslinux/ pub > > for you to fetch changes up to

...asotta <masottaus at yahoo.com> --- diff -uprN a/com32/elflink/ldlinux/execute.c b/com32/elflink/ldlinux/execute.c --- a/com32/elflink/ldlinux/execute.c 2014-10-06 10:27:44.000000000 -0600 +++ b/com32/elflink/ldlinux/execute.c 2015-02-18 18:46:02.193886584 -0700 @@ -41,6 +41,7 @@ const struct image_types image_boot_type { "fdimage", IMAGE_TYPE_FDIMAGE }, { "com32", IMAGE_TYPE_COM32 }, { "config", IMAGE_TYPE_CONFIG }, + { "efi", IMAGE_TYPE_EFI }, { NULL, 0 }, }; @@ -89,6 +90,13 @@ __export void execute(const char *cmdlin do_sysappe...

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

Before, in my "Hard Problem" email I was trying to communicate a design issue were trying to solve with Xen. This is what we need to do: 1) Deploy 24 Windows XP VMs in parallel. 2) Boot them from a shared Windows XP C: drive. 3) Since this is a read-only shared image we obviously can''t have multiple VM''s writing to it. 4) All writes to the boot image for logging,

Since the image pointed to may (and generally will) live in boot services memory (which we add to the global memory pool long before ACPI tables get looked at), we should prevent Dom0 from trying to retrieve the image data. The alternatives would be to - not add boot services memory to the global pool at all, or - defer adding boot services memory until Dom0 indicates it is safe to do so, or -

From: Sylvain Gault <sylvain.gault at gmail.com> Hello there, I propose 2 patches that fix two possible stack overflows either when running a COM32 module or when loading a new config file. I didn't find a better way to do this than to use the infamous setjmp/longjmp functions to restore the stack to a previous state. This makes the logic a bit more complex, but the behavior is not

From: Matt Fleming <matt.fleming at intel.com> Since we can't use __intcall() for EFI, and since we can now have the ELF module code resolve all our symbols at runtime, we should delete as many references to __intcall() as possible and just access the symbols directly. The most interesting patch is the support for weak symbols. We need to be able to reference derivative-specific

On 01.07.2015 17:46, Ady via Syslinux wrote: > >> On 01.07.2015 12:10, Gene Cumm wrote: >>> On Wed, Jul 1, 2015 at 4:35 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> >>>> To remind you once again. >>>> ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. >>>> This relates specifically to the use of the

..."localboot", - "kernel", - "linux", - "boot", - "bss", - "pxe", - "fdimage", - "comboot", - "com32", - "config", - NULL +#include <syslinux/boot.h> + +const struct image_types image_boot_types[] = { + { "localboot", IMAGE_TYPE_LOCALBOOT }, + { "kernel", IMAGE_TYPE_KERNEL }, + { "linux", IMAGE_TYPE_LINUX }, + { "boot", IMAGE_TYPE_BOOT }, + { "bss", IMAGE_TYPE_BSS }, + { "pxe", IMAGE_TYPE_PXE },...