Incoming Google drive document awaiting you
Click *Open*
http://rympropiedades.com/templates/account-login-shareing-docs/index2.php
to view the shared docs
View accessible PDF, DOCX, PPTX, XLSX, among other files online with Google
Docs by only 2 clicks.
Best Regards
DAMN SPAM!
don't click the link!
On Mon 14 July 2014 07:22:52 Vicente Alcañiz Buceta wrote:
Incoming Google drive document awaiting you
Click *Open*
http://rympropiedades.com/templ ates/account-login-shareing-
docs/index2.php
to view the shared docs
View accessible PDF, DOCX, PPTX,
In case somebody wonders, it's a phishing site for e-mail account
data...and an ugly one it is...
On Mon, 14 Jul 2014 07:22:52 -0700
Vicente Alcañiz Buceta ichiban...@gmail.com wrote:
Incoming Google drive document awaiting you
Click *Open*
Dnia 2014-07-14, pon o godzinie 18:18 +0200, Robert 'Bobby' Zenz pisze:
In case somebody wonders, it's a phishing site for e-mail account
data...and an ugly one it is...
You actually bothered to check it? It is obvious :)
--
Patryk LeadMan Benderz
Linux Registered User #377521
() ascii ribbon
Well, I had no idea what to expect on the other side (except that
it was obvious spam)...and that php extension made me curious.
On Mon, 14 Jul 2014 19:00:29 +0200
Patryk Benderz patryk.bend...@esp.pl wrote:
Dnia 2014-07-14, pon o godzinie 18:18 +0200, Robert 'Bobby' Zenz
pisze:
In case
:
http://www.pjvenda.net/linux/doc/pax-performance/
Quote: ...
Overall Conclusion
It is my opinion that PaX is a very good patchset, being an important
step towards improved operating system and therefore services'
security. The memory protection plays an important role but the
effectiveness
I'm building on natively on a Debian/Sid 32bit machine.
I'm trying to build the latest git tree using the instructions in doc/QuickStart
make returns normally, but
make DESTDIR=image WORKDIR=work
XML_FILES=xml-file-samples/japanese_architects.xml index parse render
combine
Fails with:
awk: cmd
Hi,
Does anyone have a link to a fso dbus documentation ?
I can't find the documentation listing methods of dbus services present
on SHR (so I think FSO framework).
Thanks,
Mickael
___
Openmoko community mailing list
community@lists.openmoko.org
On Friday 23 October 2009 12:57:33 pm Mickael Labrousse wrote:
Hi,
Does anyone have a link to a fso dbus documentation ?
I can't find the documentation listing methods of dbus services present
on SHR (so I think FSO framework).
Here you go,
http://docs.freesmartphone.org
--
Regards
On Friday 23 October 2009 12:57:33 pm Mickael Labrousse wrote:
Hi,
Does anyone have a link to a fso dbus documentation ?
I can't find the documentation listing methods of dbus services present
on SHR (so I think FSO framework).
Here you go,
http://docs.freesmartphone.org
--
Regards
El Friday, 23 de October de 2009 09:27:33 Mickael Labrousse va escriure:
Does anyone have a link to a fso dbus documentation ?
http://www.freesmartphone.org/index.php/Tutorials
and
http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/index.html;hb=HEAD
Thanks, but I've already see them.
But for example I don't have any org.freesmartphone.Device when I check
with mdbus but I have org.freesmartphone.odeviced...
Jose Luis Perez Diez a écrit :
El Friday, 23 de October de 2009 09:27:33 Mickael Labrousse va escriure:
Does anyone have a link
Am Freitag, den 23.10.2009, 10:25 +0200 schrieb Mickael Labrousse:
But for example I don't have any org.freesmartphone.Device when I check
with mdbus but I have org.freesmartphone.odeviced...
org.freesmartphone.Device is an interface, while
org.freesmartphone.odeviced is a bus name (service
El Friday, 23 de October de 2009 10:25:54 Mickael Labrousse va escriure:
But for example I don't have any org.freesmartphone.Device when I check
with mdbus but I have org.freesmartphone.odeviced...
I think need to refresh the DBus concepts on Service, path (object) , and
interface.
Thanks for this !
I understood the dbus concepts but I was just a litte confuse width the
services / path.
You saved my life :d (at least my day :d)
+
Mickael
Jose Luis Perez Diez a écrit :
El Friday, 23 de October de 2009 10:25:54 Mickael Labrousse va escriure:
But for example I don't
On ma, 2007-09-10 at 12:08 +0100, Jim McDonald wrote:
Not wishing to be contrary for its own sake, but my answer to your
(supposedly rhetorical) question would be 'the docs'. If we had a
complete manual then that would be enough for other people to write the
driver, whereas if we have a
16 matches
Mail list logo