search for: file_extension

I''m confused about how attributes work in models. For example: class Page < ActiveRecord::Base attr_accessor :body def foo id # works @id # won''t work IIRC body # won''t work @body #works end end Why doesn''t everything work the same? Joe -- Posted via http://www.ruby-forum.com/.

I want to upload a file. And what I am confused about is...should I upload it using a separate table or just as another file in the form. If as a separate table then I am not able to save it on the system/ Or/ If not that, then how can i check for the extensions? Do reply. Thanks. -- Posted via http://www.ruby-forum.com/.

...NFIG) { char *argv[] = { LDLINUX, NULL, NULL }; char *config; diff --git a/com32/elflink/ldlinux/ldlinux.c b/com32/elflink/ldlinux/ldlinux.c index 9b01dd3..0172117 100644 --- a/com32/elflink/ldlinux/ldlinux.c +++ b/com32/elflink/ldlinux/ldlinux.c @@ -31,6 +31,8 @@ static const struct file_ext file_extensions[] = { { NULL, 0 }, }; +jmp_buf __return_to_command_prompt; + /* * Return a pointer to one byte after the last character of the * command. @@ -302,6 +304,7 @@ __export int main(int argc __unused, char **argv) const void *adv; const char *cmdline; size_t count = 0; + int retval;...

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

...ude "cli.h" #include "console.h" #include "com32.h" @@ -11,40 +14,119 @@ #include <sys/module.h> -static enum kernel_type parse_kernel_type(char *kernel) -{ +struct file_ext { + const char *name; enum kernel_type type; +}; + +static const struct file_ext file_extensions[] = { + { ".com", KT_COMBOOT }, + { ".cbt", KT_COMBOOT }, + { ".c32", KT_COM32 }, + { ".img", KT_FDIMAGE }, + { ".bss", KT_BSS }, + { ".bin", KT_BOOT }, + { ".bs", KT_BOOT }, + { ".0", KT_PXE }, + { NULL, KT_NONE }, +}...

...+++ b/com32/elflink/ldlinux/ldlinux.c @@ -11,6 +11,7 @@ #include "menu.h" #include "config.h" #include "syslinux/adv.h" +#include "syslinux/boot.h" #include <sys/module.h> @@ -20,15 +21,15 @@ struct file_ext { }; static const struct file_ext file_extensions[] = { - { ".com", KT_COMBOOT }, - { ".cbt", KT_COMBOOT }, - { ".c32", KT_COM32 }, - { ".img", KT_FDIMAGE }, - { ".bss", KT_BSS }, - { ".bin", KT_BOOT }, - { ".bs", KT_BOOT }, - { ".0", KT_PXE }, - { NULL, KT_NONE }, +...

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