similar to: Ruby / Rails / MySQL/ AJAX project, developer needed (Oasis Digital)

Displaying 20 results from an estimated 4000 matches similar to: "Ruby / Rails / MySQL/ AJAX project, developer needed (Oasis Digital)"

2009 Feb 25
2
Segmentation fault in shadow.so
Trying to fire up Puppet 0.24.7 on an Ubuntu 6.06 x64 machine (yes, I know it''s obsolete, but we have a pile of machines), I get this failure: ---------------------------- # /etc/init.d/puppet start * Starting puppet configuration management tool /usr/lib/ruby/1.8/x86_64-linux/shadow.so: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [x86_64-linux] /etc/init.d/puppet: line 35:
2006 Mar 15
3
slider control for touch screens?
I was wooed here by this demo page for the script.aculo.us slider control: http://wiki.script.aculo.us/scriptaculous/show/SliderDemo ... but I''m looking for a slider control well adapted for use in a touch-screen kiosk application (an unusual place to put a web application, perhaps, but bear with me...) I''ve posted an example (screencast and downloadable program) here:
2006 Mar 24
3
1.1RC and Lighttpd
I started what I thought was going to be a 30 minute project on the train this morning to write a little timetracker for myself. Amongst other things (don''t have a model called Task as it conflicts with Rake at the moment, don''t have a model called Action as it disappears in the hash when you submit a form :-), I had to use Webrick as Lighty complained about an unknown
2014 Sep 16
1
4.1.12: ldapcmp differences on attribute 'whenChanged'
Hi all, I have just updated our dc's from sernet 4.1.11 to sernet 4.1.12. And suddenly since that update, we're getting many ldapcmp failures on the attribute 'whenChanged'. In 4.1.11 life was good, and ldapcmp reported no differences at all. Here is a sample: (dc2 <-> dc3) Comparing: 'CN=podcast,CN=Users,DC=samba,DC=company,DC=com' [ldap://dc2]
2013 Feb 13
0
make dist: errors, and www.oasis-open.org almost stale
Hi, I am trying to create a tarball from a 4.0.3 git checkout using "make dist", but it throws errors (small sample below, detailed Copy&Paste on request), and apart from this, www.oasis-open.org seems stale on connects from xsltproc, as can be seen in the lsof sample, below as well. Briefly and cheekily asked, is that normal? Are we all omitting docs in packaging at the moment?
2015 Jan 15
2
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, Jan 15, 2015 at 06:51:01PM +0200, Michael S. Tsirkin wrote: > Host no longer knows the alignment, so why is it needed? > In fact, I notice that 4.3.2.3 Virtqueue Layout seems completely wrong: > it corresponds to legacy devices, and it does not > say what "align" is. I created https://issues.oasis-open.org/browse/VIRTIO-129 to track this. Can you write up a patch
2015 Jan 15
2
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, Jan 15, 2015 at 06:51:01PM +0200, Michael S. Tsirkin wrote: > Host no longer knows the alignment, so why is it needed? > In fact, I notice that 4.3.2.3 Virtqueue Layout seems completely wrong: > it corresponds to legacy devices, and it does not > say what "align" is. I created https://issues.oasis-open.org/browse/VIRTIO-129 to track this. Can you write up a patch
2015 Jan 15
1
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, Jan 15, 2015 at 05:15:30PM +0000, Pawel Moll wrote: > On Thu, 2015-01-15 at 17:12 +0000, Michael S. Tsirkin wrote: > > On Thu, Jan 15, 2015 at 06:51:01PM +0200, Michael S. Tsirkin wrote: > > > Host no longer knows the alignment, so why is it needed? > > > In fact, I notice that 4.3.2.3 Virtqueue Layout seems completely wrong: > > > it corresponds to
2015 Jan 15
1
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, Jan 15, 2015 at 05:15:30PM +0000, Pawel Moll wrote: > On Thu, 2015-01-15 at 17:12 +0000, Michael S. Tsirkin wrote: > > On Thu, Jan 15, 2015 at 06:51:01PM +0200, Michael S. Tsirkin wrote: > > > Host no longer knows the alignment, so why is it needed? > > > In fact, I notice that 4.3.2.3 Virtqueue Layout seems completely wrong: > > > it corresponds to
2012 Jul 13
0
How to simulate the relationship of vegetation and groundwater in Minqin Oasis, Gansu Province, China
*Dear **Madam**/**Sir,* *What would happen if we irrigate the degraded land using the desalinated saline water in Minqin Oasis, Gansu Province, China? Can we prevent the disappearing of Minqin Qasis?* * * *Background:* *1. **The Minqin Oasis is surrounded by two deserts, Badain Jaran Desert and Tengger Desert. * *2. **Water is the root of ecological
2006 Jul 05
2
activerecord - finding parent info..
i am SURE this is really simple.. and i am SURE i have read this a million times.. but i am not wiring this up in my brain correctly.. if i have a parent class that has fields: Podcasts id title description and a child class like: Episodes id podcast_id title description filename i can get the episode information all day.. but using the "Episode" class, can i access the
2015 Jan 15
0
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, 2015-01-15 at 17:12 +0000, Michael S. Tsirkin wrote: > On Thu, Jan 15, 2015 at 06:51:01PM +0200, Michael S. Tsirkin wrote: > > Host no longer knows the alignment, so why is it needed? > > In fact, I notice that 4.3.2.3 Virtqueue Layout seems completely wrong: > > it corresponds to legacy devices, and it does not > > say what "align" is. > > I
2015 Jan 15
0
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, 2015-01-15 at 17:12 +0000, Michael S. Tsirkin wrote: > On Thu, Jan 15, 2015 at 06:51:01PM +0200, Michael S. Tsirkin wrote: > > Host no longer knows the alignment, so why is it needed? > > In fact, I notice that 4.3.2.3 Virtqueue Layout seems completely wrong: > > it corresponds to legacy devices, and it does not > > say what "align" is. > > I
2014 Mar 30
0
[chet.ensign@oasis-open.org: [members] 15-day Public Review for Virtual I/O Device (VIRTIO) V1.0 - ends 14 April]
----- Forwarded message from Chet Ensign <chet.ensign at oasis-open.org> ----- Date: Fri, 28 Mar 2014 17:54:16 -0400 From: Chet Ensign <chet.ensign at oasis-open.org> To: tc-announce at lists.oasis-open.org, members at lists.oasis-open.org, virtio at lists.oasis-open.org, virtio-comment at lists.oasis-open.org Subject: [members] 15-day Public Review for Virtual I/O Device (VIRTIO)
2014 Mar 30
0
[chet.ensign@oasis-open.org: [members] 15-day Public Review for Virtual I/O Device (VIRTIO) V1.0 - ends 14 April]
----- Forwarded message from Chet Ensign <chet.ensign at oasis-open.org> ----- Date: Fri, 28 Mar 2014 17:54:16 -0400 From: Chet Ensign <chet.ensign at oasis-open.org> To: tc-announce at lists.oasis-open.org, members at lists.oasis-open.org, virtio at lists.oasis-open.org, virtio-comment at lists.oasis-open.org Subject: [members] 15-day Public Review for Virtual I/O Device (VIRTIO)
2015 Jan 15
0
[RFC] virtio-mmio: Update the device to OASIS spec version
On Fri, Dec 19, 2014 at 06:38:04PM +0000, Pawel Moll wrote: > Tested with our custom models (*not* qemu). Could you look into updating qemu as well please? I'd like to make sure patches are widely testable before pushing them, to reduce the chances of finding issues after kernel is released. You can find draft patches for pci and s390 here:
2015 Jan 15
1
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, 2015-01-15 at 18:39 +0000, Michael S. Tsirkin wrote: > On Fri, Dec 19, 2014 at 06:38:04PM +0000, Pawel Moll wrote: > > Tested with our custom models (*not* qemu). > > Could you look into updating qemu as well please? No, sorry. I'm officially not allowed to touch qemu, due to some legal issues. I'll talk to Peter Maydell. Pawe?
2015 Jan 20
0
[RFC] virtio-mmio: Update the device to OASIS spec version
On Tue, Jan 20, 2015 at 05:18:23PM +0000, Pawel Moll wrote: > On Mon, 2015-01-19 at 18:36 +0000, Michael S. Tsirkin wrote: > > > > > Well, not quite: as of now I've got legacy block device driver happily > > > > > working on top of compliant (so v2 in MMIO speech) MMIO device - the > > > > > transport if completely transparent here. > >
2015 Jan 20
1
[RFC] virtio-mmio: Update the device to OASIS spec version
On Tue, 2015-01-20 at 17:44 +0000, Michael S. Tsirkin wrote: > Good. But your current code will also try to support a mix: device that > uses the new transport underneath, but old layout and semantics on top. It will not try to support the mix, but rather will not stop it from working. > This has no value: the spec does *not* define such devices > and it also does not match any
2015 Jan 15
0
[RFC] virtio-mmio: Update the device to OASIS spec version
On Fri, Dec 19, 2014 at 06:38:04PM +0000, Pawel Moll wrote: > Tested with our custom models (*not* qemu). Could you look into updating qemu as well please? I'd like to make sure patches are widely testable before pushing them, to reduce the chances of finding issues after kernel is released. You can find draft patches for pci and s390 here: