Optimizing: have you tried using hhbc/repo-auth-mode? This can gets you tens of percents, though isn't compatible with all code. Additionally, are you excluding JIT warm-up time?
Standard disclaimer: we are not faster at everyone's code. In particular, PHP tends to be faster if you have a load of code just in files, but not in functions/methods.
- we're open source (under the same licences as PHP itself). If we start showing ads, delete the code. If we stop being open source, fork it with the help of the other major companies using it
- same story for trying to move extensions to a "full" version
- HHVM gets us more from the benefits of open source (contributions, recruiting, new hires being familiar with our code, etc) than we could reasonably expect to get by selling it
* my job, and the job of the rest of the team, is to make HHVM better for people who aren't Facebook (Wikipedia, Baidu, Etsy, and everyone else who uses it). Facebook pays us full-time for this.
Additionally, Slamd64 isn't AMD-only at all. slamd64.com runs on an Athlon64 X2, but it developed on my desktop with a core 2 quad, and my laptop with a core 2 duo.
I'm in the ChangeLog/copyright notices where appropriate. All my published work on Slamd64 is free software; I don't care what's done as long as the licenses are followed.
This is probably a good time to say why I made slamd64 again:
I wanted a 64-bit Slackware. I didn't want to be a distro lead, or anything like that. I like Slackware, and I needed a 64-bit distro. I made it for my own use, and uploaded it in case anyone else wanted to use it. Now there's a 64-bit Slackware, that reason's gone.
Slamd64 will be continued in some form for the foreseeable future, but possibly as something slightly different.
A true Slackware64 is better for you too:
Security updates shouldn't lag behind "real" Slackware
you won't miss out on nearly two months of security updates (like you are right now) due to tendon issues on my part
Slamd64 is an unofficial amd64 port of Slackware. Slamd64 10.2 has also been released today, with 2.6.12.4 kernel (with reiser4 support), but otherwise very similar changes.
I applied no patches which weren't required to make packages compile/run on x86_64. I do not see how this can be considered ruining slack, rather than a neccessity.
We've been having problems with rsync timeouts and I've not been able to get hold of the admin of the primary mirror. ftp.heanet.ie/pub/slamd64/ contains the.xdelta files for final compared to RC4 - full isos should have finished in a few hours. Sorry for the delay.
- RE those "It's inconsiderate to post this on slashdot": "Now, I'm hoping that this will get seen by a lot of people and that if it hits Slashdot that some kind medical geek will help save my life."
- Clarifications: --he does not want a help fund - we've asked him. --the gpg signature is valid, key is on the slackware 10 disc, and he keeps the private keys on a computer which is not attached to the internet.
I'm an enthusiastic linux user and advocate (and a kde developer), however I don't think Linux, or Windows is the right OS for a PDA.
They were designed for intel processors, multitasking was a requirement, and various other design factors optimising them for "normal" computers.
PalmOS, however, is optimized for handhelds, doesn't do multitasking (I don't know about palm OS 5) simply because it's not neccesary on a PDA, and has one of the most intuitive interfaces i've seen. Also, PalmOS leaves me loads of space on my 2MB Zire for all of my data (several hundred contacts), and the entire new testament (seriously). I really doubt Windows could run with so little storage, and with Linux, there really wouldn't be that much room for data.
Slashdot Mirror
Have you seen https://docs.hhvm.com/hack/ove... ? :)
Optimizing: have you tried using hhbc/repo-auth-mode? This can gets you tens of percents, though isn't compatible with all code. Additionally, are you excluding JIT warm-up time?
Standard disclaimer: we are not faster at everyone's code. In particular, PHP tends to be faster if you have a load of code just in files, but not in functions/methods.
* my job, and the job of the rest of the team, is to make HHVM better for people who aren't Facebook (Wikipedia, Baidu, Etsy, and everyone else who uses it). Facebook pays us full-time for this.
Additionally, Slamd64 isn't AMD-only at all. slamd64.com runs on an Athlon64 X2, but it developed on my desktop with a core 2 quad, and my laptop with a core 2 duo.
I'm in the ChangeLog/copyright notices where appropriate. All my published work on Slamd64 is free software; I don't care what's done as long as the licenses are followed.
This is probably a good time to say why I made slamd64 again:
I wanted a 64-bit Slackware. I didn't want to be a distro lead, or anything like that. I like Slackware, and I needed a 64-bit distro. I made it for my own use, and uploaded it in case anyone else wanted to use it. Now there's a 64-bit Slackware, that reason's gone.
Slamd64 will be continued in some form for the foreseeable future, but possibly as something slightly different.
A true Slackware64 is better for you too:
You just beat me :) Here's a bit more info:
Slamd64 is an unofficial amd64 port of Slackware. Slamd64 10.2 has also been released today, with 2.6.12.4 kernel (with reiser4 support), but otherwise very similar changes.
I applied no patches which weren't required to make packages compile/run on x86_64. I do not see how this can be considered ruining slack, rather than a neccessity.
It is true that for a large proprotion of the packages (probably 2/5), all that needed changing was $ARCH. The problem was the other 3/5.
We've been having problems with rsync timeouts and I've not been able to get hold of the admin of the primary mirror. ftp.heanet.ie/pub/slamd64/ contains the .xdelta files for final compared to RC4 - full isos should have finished in a few hours. Sorry for the delay.
I did no K8-specific optimisations, just generic x86_64, so it should work fine on EM64T.
Chances are most of their paying customers from google. If they really don't want their images indexed, ROBOTS.txt beckons...
http://lists.insecure.org/lists/bugtraq/2004/Nov/0 223.html
Unofficial 3rd-party fix for slackware 10:
http://slacksec.info/update_12
- RE those "It's inconsiderate to post this on slashdot":
- NEEDS-YOUR-HELP.txt u rrent/PAT-NEEDS-YOUR-HELP.txt
"Now, I'm hoping that this will get seen by a lot of people and that if it hits Slashdot that some kind medical geek will help save my life."
- Mirrors:
http://uml.axpr.net/
http://slackware.osuosl.org/slackware-current/PAT
ftp://ftp.slackware.com/pub/slackware/slackware-c
- Clarifications:
--he does not want a help fund - we've asked him.
--the gpg signature is valid, key is on the slackware 10 disc, and he keeps the private keys on a computer which is not attached to the internet.
A PDA is a personal digitial assistant. It is not a palmtop. For a palmtop, Linux/Windows is more appropriate than PalmOS (don't know about 5).
PDA != palmtop.
I'm an enthusiastic linux user and advocate (and a kde developer), however I don't think Linux, or Windows is the right OS for a PDA.
They were designed for intel processors, multitasking was a requirement, and various other design factors optimising them for "normal" computers.
PalmOS, however, is optimized for handhelds, doesn't do multitasking (I don't know about palm OS 5) simply because it's not neccesary on a PDA, and has one of the most intuitive interfaces i've seen. Also, PalmOS leaves me loads of space on my 2MB Zire for all of my data (several hundred contacts), and the entire new testament (seriously). I really doubt Windows could run with so little storage, and with Linux, there really wouldn't be that much room for data.
http://kde.ground.cz/tiki-index.php?page=KIO+Fuse+ Gateway
Here's a link:
0
http://cgi.nessus.org/plugins/dump.php3?id=1158
nessus has been pointing this out as a security hole in it's scan results for at least 3 months now...
http://vigor.sf.net/
lol i got to say i do agree with the "redundant" moderation - but someone had to say it :)
"vogons? imagine a beowulf cluster of those!"
"I dream of emacs." "Folks, desktop GUIs are just Way Too Big. And not nearly powerful enough." Ah! You're an emacsOS user :)
http://www.suse.co.uk/en/company/customer_referenc es/mcd.html
I read that page a week ago...
i just checked - that is actually a quote :S