Xen3 is close enough to their scheduled release date that it had darned well be the little bugs they're working out by now.
I hope XeN on x86_64 works better than on the RC
on
SUSE 10.0 OSS Released
·
· Score: 2, Interesting
Per subject. I've done testing at my place at work using the release candidate (we're interested in Xen3 on x86_64... once SLES10 comes out and it's fully supported, of course), and it wasn't exactly successful. It did give me a chance to file some bugs, and Novell reported one of them fixed in their bugtracker -- but I still was unable to start up a DomU.
Hopefully the release will be more effective. As for me, I'm playing with the 10.1 alpha, which I hear is what will eventually become SLES10.
I'm going to hazard that what you're seeing is a problem with your distribution, not Firefox itself. Firefox on Linux is quite capable of being pretty.
If most autoresponders were written to be worth their salt, you might have a point. As for the mailing list proposal, most mailing lists do include headers indicating what they are, and they still get mail from autoresponders.
Yes, I could argue that people shouldn't use incompetently written autoresponders -- but frankly, since so many of the ones that are used in Real Life are crap, it's much easier to simply take the position that they shouldn't be used at all, at least until such time as good ones are reasonably commonplace.
Apache Tomcat is a simple double-click install and comes with a GUI service manager on Windows, while the Linux install is loads of manual fun.
Unless you have remotely halfway-competant staff.
I'm my employer's packaging dood (among a great many other things -- I also do everything from writing drivers to performance troubleshooting); I maintain customized packages for Oracle, Tomcat, various JVMs, and all the other components we use. Install the RPM, and the service is enabled -- done! And it just takes one of me for however many thousands of sites we end up supporting; no sysadmins need do anything custom whatsoever on the individual sites. Indeed, there's an autoconfiguration framework I wrote which pretty much makes setting up a new client installation a cookie-cutter operation -- something much easier to do on a Unix than elsewhere.
And I cost one helluvalot less than $100/hr. Heck, I'd be thrilled if I made half that.
The mailing list problem is really a minor annoyance.
When you have one autoresponder on a mailing list, maybe. I hold that being a "minor annoyance" to several hundred people is no longer being a minor annoyance... but let's leave that unresolved for the moment.
Let's say you have two autoresponders on a mailing list. Now, User A sends a message. A copy is sent to Autoresponder 1, which sends a message to the list, which is received by Autoresponder 2, which sends a message to the list, which is received by Autoresponder 1...
...and you've suddenly flooded hundreds or thousands of mailboxes, not to mention the list archives and such. There's nothing "minor" about that.
Perhaps because they're not 'useless' or 'evil' but actually 'useful' in some situations, like in business environments when people need to let other people know they're away and who to contact in the meantime?
Spoken like someone who's never had a mail server snafu'd by an autoresponder loop.
Autoresponders have a purpose, to be sure -- but their use has severe negative side effects due to their inability to determine whether they're letting an "other person" know something or they're sending mail to another automated system (which may in turn send an autoresponse to the former autoresponse...) or to a mailing list (in which case they annoy hundreds or thousands of 3rd parties).
Autoresponders are bad juju, and there are other business solutions (like delegation to a Real Human Being) to address the problem they attempt to solve.
I don't have any problems with code that only I read and modify, but what's going to happen when the next fella comes along with notepad and adds some CP/M style newlines and aligns his stuff with eight character tabs, or worse, changes one of my routines with that stuff?
Stackless is a completely different implementation from CPython, and has extremely different performance characteristics.
Consequently, your experiences with CPython simply don't apply here -- Stackless is largely focused around doing this kind of thing (microthreads and such) extremely well.
(If you're a non-native speaker, please accept my apologies -- it's the folks who grew up with English as a first language and still make these simple mistakes who earn my ire).
Three Mile Island was hardly a disaster, and Chernobyl was a plant with a horrifically poor design by modern standards.
Just because you say nuclear energy is a bad idea doesn't make it so -- and of the alternatives, they either do far worse environmental damage or cannot practically be scaled to meet demand.
depleted uranium, which has a half life of millions of years
Uhh.
Depleted uranium isn't dangerous because it's radioactive; it's dangerous because it's poisonous. The level of radioactivity given off by DU is completely insignificant -- hence "depleted" -- the problem is that breathing in DU dust causes cancer, for reasons completely and totally unrelated to radioactivity. Conclusion: the half life is completely irrelevant.
Being monstrous, horrible, merciless people is not necessarily such a bad idea in the long run.
Those who can cope with unfair disadvantages do so. Those who can't don't. Those who can sustain unfair advantages do so. Those who can't lose them to people who didn't previously have such advantages. Sooner or later, on average, the more deserving people do better and the less deserving people don't. It doesn't work down to such a fine scale -- there are plenty of deserving people whose unfair disadvantages put them below undeserving people with unfair advantages -- but by and large, things work out better than if one attempted to use brute force to interfere.
So -- if people live in drought-stricken areas, and are unable to earn sufficient income some other way to be able to import food, they should stop doing that. If they have enough resources to live at all, they presumably have enough resources to move. If someone is disabled and not adequately insured, they should find something productive they are capable of doing which earns sufficient income to pay for their expenses -- and if they can't do that, it obviously means that having them alive is more of a net loss to society than a benefit.
These are indeed monstrous, horrible positions -- but it would be better for you to refute them than merely apply names to them.
...and have been for a long time. Making synthetic diamonds which are on a size and quality scale appropriate for non-industrial uses -- that's what's shaking things up.
If you run a jabber server and want to S2S with them, email federation@google.com
I did. No (non-form) response.
Compared to having server-to-server support, though, it's just silly. Would you put up with needing to sign a contract with AOL before folks on your mail server could send messages to theirs?
But they must treat their server connection just like they did with gmail. They cant let just anybody in.
Eh? S2S on GMail is entirely open -- I can put up my own SMTP server and send mail from it to GMail users and visa-versa. I can't put up my own Jabber server and do the same with Google Talk.
See, what puts it ahead in my book is backending into XMPP (and, in the near future, SIP). Granted, that's not an advantage of the client but the service -- but in my book, it's a pretty big plus.
Oh, so you're talking criminal rather than civil law?
You do realize that DA's offices are generally overworked enough that they only prosecute a token number of spam-related cases, even though a very large number of these are already prosecutable already under preexisting law [such as fraud]? Given that that's true, how do you think adding more laws will make it any better?
Slashdot Mirror
Xen3 is close enough to their scheduled release date that it had darned well be the little bugs they're working out by now.
Per subject. I've done testing at my place at work using the release candidate (we're interested in Xen3 on x86_64... once SLES10 comes out and it's fully supported, of course), and it wasn't exactly successful. It did give me a chance to file some bugs, and Novell reported one of them fixed in their bugtracker -- but I still was unable to start up a DomU.
Hopefully the release will be more effective. As for me, I'm playing with the 10.1 alpha, which I hear is what will eventually become SLES10.
SuSE has always included lots of packages -- it's a feature, not a bug!
No, really. You aren't required to install all of them, after all.
I'm going to hazard that what you're seeing is a problem with your distribution, not Firefox itself. Firefox on Linux is quite capable of being pretty.
If most autoresponders were written to be worth their salt, you might have a point. As for the mailing list proposal, most mailing lists do include headers indicating what they are, and they still get mail from autoresponders.
Yes, I could argue that people shouldn't use incompetently written autoresponders -- but frankly, since so many of the ones that are used in Real Life are crap, it's much easier to simply take the position that they shouldn't be used at all, at least until such time as good ones are reasonably commonplace.
Apache Tomcat is a simple double-click install and comes with a GUI service manager on Windows, while the Linux install is loads of manual fun.
Unless you have remotely halfway-competant staff.
I'm my employer's packaging dood (among a great many other things -- I also do everything from writing drivers to performance troubleshooting); I maintain customized packages for Oracle, Tomcat, various JVMs, and all the other components we use. Install the RPM, and the service is enabled -- done! And it just takes one of me for however many thousands of sites we end up supporting; no sysadmins need do anything custom whatsoever on the individual sites. Indeed, there's an autoconfiguration framework I wrote which pretty much makes setting up a new client installation a cookie-cutter operation -- something much easier to do on a Unix than elsewhere.
And I cost one helluvalot less than $100/hr. Heck, I'd be thrilled if I made half that.
Let's say you have two autoresponders on a mailing list. Now, User A sends a message. A copy is sent to Autoresponder 1, which sends a message to the list, which is received by Autoresponder 2, which sends a message to the list, which is received by Autoresponder 1...
Perhaps because they're not 'useless' or 'evil' but actually 'useful' in some situations, like in business environments when people need to let other people know they're away and who to contact in the meantime?
Spoken like someone who's never had a mail server snafu'd by an autoresponder loop.
Autoresponders have a purpose, to be sure -- but their use has severe negative side effects due to their inability to determine whether they're letting an "other person" know something or they're sending mail to another automated system (which may in turn send an autoresponse to the former autoresponse...) or to a mailing list (in which case they annoy hundreds or thousands of 3rd parties).
Autoresponders are bad juju, and there are other business solutions (like delegation to a Real Human Being) to address the problem they attempt to solve.
Stackless is a completely different implementation from CPython, and has extremely different performance characteristics.
Consequently, your experiences with CPython simply don't apply here -- Stackless is largely focused around doing this kind of thing (microthreads and such) extremely well.
I'm sorry, but admitting the business degree isn't the sole way you're "loosing" credibility here.
See the differences between "lose" and "loose".
(If you're a non-native speaker, please accept my apologies -- it's the folks who grew up with English as a first language and still make these simple mistakes who earn my ire).
which makes them more radioactive ...but for a much shorter period of time.
Three Mile Island was hardly a disaster, and Chernobyl was a plant with a horrifically poor design by modern standards.
Just because you say nuclear energy is a bad idea doesn't make it so -- and of the alternatives, they either do far worse environmental damage or cannot practically be scaled to meet demand.
depleted uranium, which has a half life of millions of years
Uhh.
Depleted uranium isn't dangerous because it's radioactive; it's dangerous because it's poisonous. The level of radioactivity given off by DU is completely insignificant -- hence "depleted" -- the problem is that breathing in DU dust causes cancer, for reasons completely and totally unrelated to radioactivity. Conclusion: the half life is completely irrelevant.
Tried the samples at http://www.croczilla.com/svg/samples/? Using this 1.5 beta, they Work For Me.
But I'm a little dissapointed it looks like the built-in SVG support isn't in there.
Huh? It's there.
Being monstrous, horrible, merciless people is not necessarily such a bad idea in the long run.
Those who can cope with unfair disadvantages do so. Those who can't don't. Those who can sustain unfair advantages do so. Those who can't lose them to people who didn't previously have such advantages. Sooner or later, on average, the more deserving people do better and the less deserving people don't. It doesn't work down to such a fine scale -- there are plenty of deserving people whose unfair disadvantages put them below undeserving people with unfair advantages -- but by and large, things work out better than if one attempted to use brute force to interfere.
So -- if people live in drought-stricken areas, and are unable to earn sufficient income some other way to be able to import food, they should stop doing that. If they have enough resources to live at all, they presumably have enough resources to move. If someone is disabled and not adequately insured, they should find something productive they are capable of doing which earns sufficient income to pay for their expenses -- and if they can't do that, it obviously means that having them alive is more of a net loss to society than a benefit.
These are indeed monstrous, horrible positions -- but it would be better for you to refute them than merely apply names to them.
...and have been for a long time. Making synthetic diamonds which are on a size and quality scale appropriate for non-industrial uses -- that's what's shaking things up.
Compared to having server-to-server support, though, it's just silly. Would you put up with needing to sign a contract with AOL before folks on your mail server could send messages to theirs?
But they must treat their server connection just like they did with gmail. They cant let just anybody in.
Eh? S2S on GMail is entirely open -- I can put up my own SMTP server and send mail from it to GMail users and visa-versa. I can't put up my own Jabber server and do the same with Google Talk.
...and they haven't given me any response, either in public or from my private email (w/ the same content) to their federation link.
It didn't say it was out of beta, it said it was "open to everyone". RTFP.
See, what puts it ahead in my book is backending into XMPP (and, in the near future, SIP). Granted, that's not an advantage of the client but the service -- but in my book, it's a pretty big plus.
Oh, so you're talking criminal rather than civil law?
You do realize that DA's offices are generally overworked enough that they only prosecute a token number of spam-related cases, even though a very large number of these are already prosecutable already under preexisting law [such as fraud]? Given that that's true, how do you think adding more laws will make it any better?
It's already illegal -- but how're you going to prove it, particularly if they go through an offshores 3rd party?