search for: active_flag

Hi, I''m just learning Ruby on Rails and ran into something where I know I''m either doing something very stupid or I''m missing something. My model as a boolean attribute called active_flag. In my Sql Server database this is stored as a bit value. I then setup a method in my controller called "deactivate". This is very simple, it does: def deactivate @department = Department.find(params[:id]) @department.active_flag = false @department.save! redirect_...

...ecord */ - record = malloc(synth_size); - if (!record) { + hand_area = malloc(synth_size); + if (!hand_area) { error("Could not build GPT hand-over record!\n"); goto bail; } /* Synthesize the record */ - memset(record, 0, synth_size); - record->active_flag = 0x80; - record->ostype = 0xED; + memset(hand_area, 0, synth_size); + hand_area->active_flag = 0x80; + hand_area->ostype = 0xED; /* All bits set by default */ - record->start_lba = ~(uint32_t) 0; - record->length = ~(uint32_t) 0; + hand_area->sta...

...class User < ActiveRecord::Base has_and_belongs_to_many :roles end class Role < ActiveRecord::Base has_and_belongs_to_many :users end console: >> user = User.find(1) => #<User:0xb771b494 @attributes={"id"=>"1", "location_id"=>nil, "active_flag"=>"1", "name"=>"joe"} >>> user.roles[0].default_flag.class => String >> user.roles[0].id.class => Fixnum shouldn''t default_flag be a Fixnum? _______________________________________________ Rails mailing list Rails-1W37MKcQCp...

...); goto endloop; } } /* Do the actual chainloading */ if ( partinfo ) { /* Actually read the boot sector */ /* Pick the first buffer that isn't already in use */ boot_sector = (char *)(((unsigned long)partinfo + 511) & ~511); sprintf(logs, "partinfo: active_flag %d, start_head %d, start_sect %d, start_cyl %d, ostype %d, end_head %d, end_sect %d, end_cyl %d, start_lba %d, length %d, boot_sector %s\n", partinfo->active_flag, partinfo->start_head, partinfo->start_sect, partinfo->start_cyl, partinfo->ostype, partinfo->end_head, partinfo-...

This patch introduces extra functionality to chain.c, mainly with reference to BPB adjustments, but not only that. It expects 3 small patches I sent earlier (they are included for easy reference, patches 1-3/4). The changes introduced are: 1) file and boot sector use separate options to control load address and jump address (if applicable). Options are as described below: *

1) code split and move Iterator related functionality is yanked from chain.c and moved to iterator.{c,h}. Both are moved to com32/chain and this way chain.c is ready for further splitting. Alternatively, partiter could be moved to com32/lib at any time in the future. It's potentially useful for other modules (e.g. if someone wanted to code partition dumper or editor). 2) Iterator updates

...ot; - " Head _______________ : 0x%.2x (%u)\n" - " Sector _____________ : 0x%.2x (%u)\n" - "Partition LBA start __ : 0x%.8x (%u)\n" - "Partition LBA count __ : 0x%.8x (%u)\n" - "-------------------------------\n", - part->active_flag, - chs_cylinder(part->start), - chs_cylinder(part->start), - chs_head(part->start), - chs_head(part->start), - chs_sector(part->start), - chs_sector(part->start), - part->ostype, - chs_cylinder(part->end), - chs_cylinder(part->end), -...

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address

This is a bit updated set of chain.c32 changes that simplifies a few things (and in partiter part), fixes few minor issues and adds a few new features. Details are in the following commits, below is the summary and pull details at the end. Shao - any chance to peek over them ? Most of those are relatively simple changes and well tested, though of course something might have slipped my attention.