If he saw this article and the author mentioning several times that FreeBSD is "Free Software"?;-)
Parts of FreeBSD are free software in that they are covered by the GPL and LGPL, but great huge chunks of it are under the BSD license which RMS has a serious problem with and most people would call an OpenSource license, not "Free Software".
One you forgot that comes with most Linux distro's (and is definitely available for Debian) is GnomeMeeting. Probably the best known OSS H.323 client out there at the moment.
The client for Linux is available in RPM and Debs. There is also a Solaris/SPARC version available, but thats outside the scope of this app.
I have been using Yahoo a long time, I did not think the voice chat was available to the Linux version... My understanding was it was only available for the MacOSX and Windows versions (as is the webcam stuff).
RBC, who, along with Baystar, invested $50 million into SCO has begun looking at the contingency fees SCO will pay to their lawyers if SCO is bought out.
I agree, I find the whole RBC situation extremely amusing. Especially the fact that RBC now has veto powers over any action that could result in the legals getting 20% of any given resulting transaction.:-) That to me was probably one of the best things any investor of recent times could've done. Finally someone is making SCO stop and think before it does something. More than that, its also making SCO more responsible for any action they might take.
They get to look like a victim in the press, and they can do so without any proof what so ever.
This is one of the things that has bothered me about modern reporters. They no longer take the time to verify a press releases accuracy and instead build an entire article without confirming any of the facts. Its not just online press agents that do it. ZDNet/ZDTV (by extension, CNET) are also guilty of it as are organisations like TimeWarner and NYTimes (should I really go there?);-)
The problem that presents itself however, is that the public rarely question anything mentioned in the media any longer. They take for fact almost any article published by someone like the Associated Press. This is something many of us have complained about.... The problem however, is those of us writing to the editors are such a minority that the editors rarely take notice any longer and just put it straight into the trash. Accountability for factual representation of the news seems to no longer matter.
Still, what can we do? So few individuals take the time to point out the false. More people need to stand up and make the editors take notice. Then again, that would require action. Who wants to act when its so much easier to just accept whats presented to us?;-)
One day the truth will finally become important in the mainstream again. Sites like Groklaw (in the case of SCO) are starting to get so much momentum behind them that they can't be ignored or just brushed off as a radical wing of a minority group. When people actually take the time to point out the wrongs, it makes it easier for the journalists. <G>
This is getting just annoying. As has already been pointed out, the facts point to this being another hoax. However, as not everyone else in this community knows much about Security, let me add my few years of experience in to help those who don't understand.
I should point out, this has pretty much been covered by Groklaw already and my methods don't vary too much from those already posted by them.
SCO claims their email and web servers are unavailable because of a DDoS attack that has also infiltrated their Intranet and affected helpdesk services as well as other internal services. If this is the case, then it is more than just a DDoS they're suffering, or they are negligent in the highest order for failing to take simple steps to ensure a risk mitigated environment for conducting business within.
Lets start with their Mail Server. Everyone has a backup mail server, usually hosted by a 3rd party to ensure that if your primary mail server is offline for any reason, mail can still be delivered successfully. The fact that SCO claimed their mail servers were unavailable suggests they either failed to purchase this extremely basic service or their setup is absolutely wrong by anyones standards. The purpose of multiple MX records is for this exact situation. You start with a high priority MX record (say 10) and work your way down the order (usually in steps of +10, so the secondary is usually 20).
Their Web Server Their webserver is hosted on exactly the same subnet as their ftp server. However, during this attack, their FTP server has been available to anyone thats tried to connect to it. If they were suffering a DDoS attack of the proportions that SCO claims, this server would also have been affected and taken offline. Yet this is not the case. This blows open entirely the philosophy of a DDoS attack without any of the further evidence.
SCO has alluded to the fact that the attack is a basic SYN Flood. A very simple and old attack that has been blockable by nearly every appliance and OS for the past 3 years at least. Yet if they are suffering as they claim, then they are guilty of negligence for failing to apply patches or even configure their platforms correctly. Its very easy to turn the SYN Cookies on in Linux (sysctl isn't rocket science) and just as easy in something like a Cisco Router/PIX Firewall or a Checkpoint Firewall.
The claims that this has adversely affected their intranet suggests that the intranet is in some way exposed to the Internet. Even more alarming is the fact that it disabled their Helpdesk services for a period as well. This would suggest that their network has absolutely no perimeter protection of any kind. The smallest flaw in a product they use could apparently be used to access their core network infrastructure. Isn't that where their source code and IP documentation are kept? I'd start getting very worried about now if I were an investor.
Due diligence is a core principle of any company. That includes ensuring that the services relied upon are securely and properly setup and maintained. If SCO truly has been affected by an attack of any kind on the magnitued they're claiming, then they should be legally responsible for the results of their failure to perform due diligence. (However, IANAL so don't quote me on legalities, especially given I live in NZ, not the US).
In short, the supposed attack on SCO does not add up at all. In fact, if they are being attacked this time round, they are in serious legal trouble themselves if their reports are accurate.
I would also question why they have released this to the press as a Press Release instead of getting on with fixing the problem as quickly as possible. Also, how is it that their mail services are now restored, their FTP server never offline, yet their website remains offline? Surely, a DDoS would affect both.
Not to mention the fact that it would affect SCOs upstream provider who, when contacted last time, saw absolutely no evidence of an attack in progress at a
You miss the key aspect of the point that was being made. People are switching to Linux because it reduces the cost of support as well as the cost of implementation. However, the point was that there are still a lot of apps that run on Windows platforms for which there are no alternatives in the Linux world. Why give up all the extra benefits of Linux for just one or two applications for which no alternative exists?
The point of the WINE project is to provide that bridge. Get all the benefits of using something like Linux or BSD, get all the alternatives available to you (freely or otherwise) and if there are a few you need Windows for, use WINE to run them under Linux. Someone running Outlook under Linux would be a lot better off running Evolution and paying for the Connector license (cheaper licensing and native). However, someone running a core accounting app for which no Linux alternative exists is going to want to use WINE so they can still use that application AND get the benefits of the Linux alternatives for everything else.
WINE is a bridging tool for those migrating from Windows to Linux/Unix but who have applications for which no feasible Linux/Unix alternatives exist.
I would much prefer to save the costs involved in getting a Linux box up and running with WINE that spend the several hundred in licensing just for a few applications.
Hmmm...
($time to get up and running) vs ($time + $licensing costs for Windows)
Which is really the cheaper in the end? Support? Bah, its remote. Like you say, there is VNC if it comes down to it (bad solution really) but X across an SSH session is a lot better (regardless of how badly people think of the X protocol, it does its intended job very well still)
Just my $0.02. We differ in our opinions, but thats the beauty of diversity in life;-)
Actually, iTMS EU is due to go live next year. Its never been a secret that iTMS is currently only available in the US/CA.
Could be worse... I own 3 macs, all run OSX, all run iTunes and I live in New Zealand where there are currently no plans at all for an iTMS release. I've been taunted by the iTMS since it was released with no relief in sight;-)
Get in touch with Novell or Redhat and find out what platforms they can support using their products. Novell's (well, Ximians really) RedCarpet would probably be more likely to allow you to run it across multiple platforms.
There are heaps of products out there for this kind of updating. No matter what, there will always be an admin involvement in them however. You'll still need to keep an eye on things regardless of how you automate it. You'll still need to update the hosts and you'll still want to keep your eye on what the software you choose does to those hosts it monitors.
For more broad range of platforms, Tivoli and its like spring to mind. Tivoli can cover pretty much all "mainstream" platforms out there, but its probably overkill for what you're after.
Get rid of the whole regulation issue. Thats not necessary. It would be far better to make the software publisher liable for any faults or flaws in the software that led to an incident such as MSBlaster, Slammer or any other number of worms out there.
Virii like SoBig.F are not something that can be avoided because the vulnerability there is the user themself. The only way to sort out virii like that is to educate users to not open email they are not expecting or recognise. Even then its still a risk.
If Microsoft were liable for the damages caused by the worms such as MSBlaster and Slammer because their software was vulnerable, don't you think their culture would change very rapidly? Instead of having the worst security reputation, they'd suddenly have the very best. Win2k3 is a good start in the right direction by disabling everything by default. I applaud that. Now they need to sort out their coding practices so that these sorts of issues are a non-event.
Governments don't need to regulate anything. All they need to do is make it illegal for a company to not take responsibility for faulty products, regardless of the product. It worked in the automobile industry, its worked in the medical industry, its worked in the engineering industry.
If my car explodes because of a fault in the fuel line at manufacturing, I'm perfectly within my rights to sue that company. If my computer becomes completely unusable because a vulnerability allowed someone to damage it or similar, why shouldn't I sue the publisher of that software? I'd also reserve the right to sue the person that exploited that vulnerability and caused the damage.
Don't need regulation, just liability and a warranty of suitability for a purpose. 'This OS is guaranteed to perform to XXXXXXX level and is considered suitable for XXXXXXXXXX purpose.'
Umm... Both Kolab and OpenGroupWare.org are suitable for this purpose. They are freely available, work with quite a number of clients and offer a complete alternative to Exchange (including groupware calendaring features).
Now I admit that there is an investment required for them to be usable with Outlook and, by extension, Evolution, however this is minimal compared with the cost of licensing Exchange.
The biggest expense is time. They are not 'trivial' to set up just yet and do require a decent time investment in doing so. However, they are most definitely built on open standards and free/opensource software.
I'm sure there are plenty of others that'd do it to, but those are the ones most recently making waves and thus the ones that stand out in my head at the moment.
If the company hadn't paid the subscription, would the devs have been eligable to get the PDA's? If you buy a PS2 and I send in for the $20 rebate because you didn't realise you could, who gets the rebate?
Quite simply, the PDAs are the property of the company simply because it was their subscription that paid for them. Therefore they have the say over what does and does not happen with them. Just because you and your buddies saw the offer doesn't give you ownership. Thats like me claiming your rebate on a PS2.
Wake up and smell reality. Stop trying to be a troll. If you're that unhappy about the situation, take your toys and go home. I'm sure Cartman would be proud.
The more I read this, the more it reminded me of the marketing version of how Apple would like us to think of Resource Forks.
Truthfully, there isn't exactly a lot of difference in the concept or the idea. Implementation is vastly different but the idea remains very similar.
Why do I want to accept this sort of idea anymore than I want to accept resource forks? If I copy a file with resource forks from one of my macs to nearly any other OS on the market thats not specifically configured to support them, I lose that information. Why do I want to continue this?
I use HFS+ because I have to. To get all the functionality I want out of my macs, its the only real option I have. But for anything other than system level files that are never likely to be copied to another machine, this is just a waste of time to me.
Next question. Say I do run this file system on my machines. I build up a heap of data and I'm using "files as directories" to store metadata about those files. How do I back it up? Don't even try to tell me "rebuild tar". Haven't we put tar through enough to try and extend its capabilities? I wouldn't touch a file system with these capabilities without a guaranteed way of being able to backup ALL the data. Otherwise its just truly not worth the effort.
What do I use now? When more and more friends started wanting blogs and then more of their friends started wanting blogs, I wanted something that I could use for a whole lot more than just personal blogs. I also wanted to have the option to put subscription fees on it (when things started getting expensive to host) and that was a live and ongoing project.
So now I use the LiveJournal code. Its Perl (will run on nearly every platform from IIS to Apache to iPlanet to....) and SQL backed. Its scalable (like you wouldn't believe. Look at LiveJournal.com, over 1,000,000 active blogs) and its not slow.
It allows for full management of the user and also offers the abillity to move to a subscription model without having to change anything. There are various levels of subscription as well... Free, Paid, Permanant, Admin. You can also define more and levels within each.
I could ramble on further, but if its what you might find useful, check it out at http://www.livejournal.com/code/
They call it "Open Source/Free Software" with links to both opensource.org and fsf.org.
I have no probs recommending it
on
Using MovableType?
·
· Score: 4, Interesting
I used MovableType until recently for my own personal website. Both as a blog and as the engine to power the news of the website.
The advantage to MT is that it can store the info in one of 3 different databases (including a local file if you don't have SQL of some sort) and the only time the Perl application is accessed is when you're either adding a new entry to the blog or when someone is posting a comment. Everything is generated as HTML so when a user views the page, they're not calling any scripts. Keeps overheads down and allows for bigger sites on smaller servers.
Caching I found an issue. The HTML is static. So I quite often had to manually tell Squid to refresh the site if it was getting updated lots and I wanted to see those updates.
Multiple authors per blog is useful. Its pretty decent as far as permission system goes. I dislike the fact that a user can make certain changes (such as altering where on the file system their blog gets created) but this can be turned off simply enough with only minor loss of functionality to the end user themself. Then again, what they don't know they could've had, they won't miss.:-)
Security isn't so bad. You can use HTTP authentication to stop the users getting in to the directory with the Perl app and then their username/passwd to access the prog itself. This gets complicated if you want to permit comments. However, Security concerns are few and far between. 2.64 takes care of all known bugs and when bugs are announced, a patch is pretty quickly released.
Remember, the average Joe doesn't need to even get near the Perl application if you disable comments. All they get is straight HTML.
People complain about the CSS and so on. I haven't had a problem with this myself. I found it pretty simple to modify the entire look and feel. The template structure is pretty straight forward and expandable. Adding something like a WAP.wml file template was very simple.
Hunt around, there are a heap of plugins for it. Including plugins that allow you to use WikiWord formatting and more.
While it was of use to me, it suited my purposes very well. Its very quick and scalable. I had about 30 blogs plus a news page running from the single install on a P200. Because the Joe is getting HTML and not running the Perl scripts to generate it every view, it doesn't need a major box.
But you just admitted that the energy supply would deplete by "slowing down the spin of the Earth a little bit at a time".
Therefore, even that wouldn't be perpetual energy or perpetual motion and still follows the laws of thermodynamics.
Thing is, for over 150 years people have been trying to disprove the laws of thermodynamics. Quite simply put, it is impossible to create more energy than you use. Whether it be heat, kinetic, electricty or "other".
However, I could stand to lose a few pounds... slowing the Earth a bit sounds like a good way to do that... Purely in the interests of science that is.;-)
It is basic physics. It is impossible to get more energy out of a device than you put in to it. Simple example of this would be a turbine for a power plant.
To spin the turbine, you have to provide it energy. In many cases this comes in the form of Kinetic energy from moving water.
However, you can never generate so much electricity that the turbine can power itself. Heat, friction and a whole heap of others come in to play and eventually (it could take a long time if you engineer it really well) the turbine will have slowed right down and not be able to produce enough electricy to even spin itself, let alone power anything else.
I had a link to a site last year that went through a whole heap of "perpetual energy" machines and completely refuted them. However, I cannot find this link and so offer the following one instead.
http://www.phact.org/e/dennis4.html
Enjoy
Re:SSH is my preference
on
SSH or IPSec?
·
· Score: 1
You have no idea of the circumstances, preparation, precautions or anything else about the event, nor do you even know me.
Who are you to judge me?
More over, how does one picture of a single event have any bearing at all on my knowledge or anything else other than the event itself?
Is this honestly the best place to even have this discussion?
SSH is my preference
on
SSH or IPSec?
·
· Score: 5, Informative
Given the proliferation of NAT on many fronts now, I personally have used, installed and maintained SSH VPNs on many of my clients networks because I find it a lot more reliable than IPSec.
Here in NZ, ADSL is running via PPPoATM and all network terminators must be running NAT (this is a requiremet of the Telco, not of the technology). Because of the much lower costs of DSL vs Frame, this is becoming the default setup for most companies now. IPSec in this kind of environment where NAT is at both ends, or even just one, becomes a real PITA to get running and keep running. SSH just works.
Once the keys are set at both ends, the tunnels just do their thing. Establishing ports is not difficult. For my setup I create Virtual IPs at both ends of the network and then essentially do port forwarding across the tunnel to those ports. Essentially a combination of SSH and (in my case) IPTABLES. Works very well, very sweetly and NAT doesn't cause me any problems.
I can't believe this post got this far. A solution can even be found on Yahoo!
Dude, core rule of running ANY OS is to disable anything you don't use. If you don't know which services/daemons you do or don't need, then install a software based firewall on the OS until you can get help to start securing the OS properly.
For windows, software like Zone Alarm (http://www.zonelabs.com) is a good start. McAfee, Symantec and a whole heap of other companies offer similar products also.
For *BSD (Including OSX) IPF is available on nearly all variants. For GNU/Linux, NetFilter/IPTables in the modern kernels and IPCHAINS and IPFWADM in the older kernels.
For commercial versions of Unix, There are a quite a few options, but most home users aren't going to be running Solaris or HP-UX or AIX or other such OSs.
I got the 7650 the day it was released to my local market. Couldn't resist. Did the same with the 3650. The difference between the two? Other than the style... Not a lot. Audio Bluetooth on the 3650 allows for a bluetooth headset, and the MMC capabilities mean a lot more apps can be installed... Also a huge bonus.
I have to admit, the American cellular market makes me laugh. CDMA? What an expensive joke. GPRS is so much cheaper because you're only paying for what you use, not how long you spend connected (which includes idle time).
I personally will never go near a CDMA network as long as GSM/GPRS/UMTS are available. For a supposedly 3G service, its an extremely backward network.
BTW, OS X 10.2.5 supports the 7650 and the 3650 via bluetooth without a problem. Including transfering files between the two, syncing the calendars, addressbooks and so on... I have no problems with it on my Powerbook or my Powermac.
Oh well... What can I say? USA, congrats on gradually catching up to the rest of us.;-) Maybe if Verisign and T-Mobile sort their problems out, I'll be able to send MMS msg's to friends there.... Or maybe I'll just stick to sending them to my friends in every other country;-) (well, almost)
Actually, Gobbles Security are one of the most active, and largest, exploit groups hanging around the "Security" field at the moment. They have a knack for Pissing off Theo DeRaadt.
You can see the posting to bugtraq from them on the SecurityFocus website.
does anyone else find the fact that "Fritz" Hollings voted against this bill kind of ironic given is track record so far?
I would have figured that he would've loved to have more power to chase after pirates, especially in the name of "Homeland Defence":P
Oh well, I guess he just didn't get his asking price this time round.
I'm sorry, but I really find it concerning that someone so vocal in his support of other laws that are just as draconian, would then turn around and vote against this one. It just doesn't seem to add up.
Tutos for project management and basic CRM. It also kinda crosses over into an ERP application as well.
Tutos does product and project management, client management (with the ability to attach almost anything to a client and break it down into departments and more) and a whole heap of other things.
Best of all, its built using PHP on MySQL and Apache with *the only* (sic) free software license (GPL 2). I run it on Linux but I doubt you'll have trouble getting it to run on MacOS X.
You'll find it at http://www.tutos.org along with some pretty decent info including full documentation, a demo, screen shots and more. It is fully web based.
Slashdot Mirror
If he saw this article and the author mentioning several times that FreeBSD is "Free Software"? ;-)
;-)
Parts of FreeBSD are free software in that they are covered by the GPL and LGPL, but great huge chunks of it are under the BSD license which RMS has a serious problem with and most people would call an OpenSource license, not "Free Software".
Could be an interesting discussion
I didn't post suggesting Yahoo Messenger, I posted a reply to a request asking where it could be found. Get your facts correct first.
One you forgot that comes with most Linux distro's (and is definitely available for Debian) is GnomeMeeting. Probably the best known OSS H.323 client out there at the moment.
http://messenger.yahoo.com/
The client for Linux is available in RPM and Debs. There is also a Solaris/SPARC version available, but thats outside the scope of this app.
I have been using Yahoo a long time, I did not think the voice chat was available to the Linux version... My understanding was it was only available for the MacOSX and Windows versions (as is the webcam stuff).
RBC, who, along with Baystar, invested $50 million into SCO has begun looking at the contingency fees SCO will pay to their lawyers if SCO is bought out.
I agree, I find the whole RBC situation extremely amusing. Especially the fact that RBC now has veto powers over any action that could result in the legals getting 20% of any given resulting transaction. :-) That to me was probably one of the best things any investor of recent times could've done. Finally someone is making SCO stop and think before it does something. More than that, its also making SCO more responsible for any action they might take.
They get to look like a victim in the press, and they can do so without any proof what so ever.
This is one of the things that has bothered me about modern reporters. They no longer take the time to verify a press releases accuracy and instead build an entire article without confirming any of the facts. Its not just online press agents that do it. ZDNet/ZDTV (by extension, CNET) are also guilty of it as are organisations like TimeWarner and NYTimes (should I really go there?) ;-)
The problem that presents itself however, is that the public rarely question anything mentioned in the media any longer. They take for fact almost any article published by someone like the Associated Press. This is something many of us have complained about.... The problem however, is those of us writing to the editors are such a minority that the editors rarely take notice any longer and just put it straight into the trash. Accountability for factual representation of the news seems to no longer matter.
Still, what can we do? So few individuals take the time to point out the false. More people need to stand up and make the editors take notice. Then again, that would require action. Who wants to act when its so much easier to just accept whats presented to us? ;-)
One day the truth will finally become important in the mainstream again. Sites like Groklaw (in the case of SCO) are starting to get so much momentum behind them that they can't be ignored or just brushed off as a radical wing of a minority group. When people actually take the time to point out the wrongs, it makes it easier for the journalists. <G>
This is getting just annoying. As has already been pointed out, the facts point to this being another hoax. However, as not everyone else in this community knows much about Security, let me add my few years of experience in to help those who don't understand.
I should point out, this has pretty much been covered by Groklaw already and my methods don't vary too much from those already posted by them.
SCO claims their email and web servers are unavailable because of a DDoS attack that has also infiltrated their Intranet and affected helpdesk services as well as other internal services. If this is the case, then it is more than just a DDoS they're suffering, or they are negligent in the highest order for failing to take simple steps to ensure a risk mitigated environment for conducting business within.
Lets start with their Mail Server.
Everyone has a backup mail server, usually hosted by a 3rd party to ensure that if your primary mail server is offline for any reason, mail can still be delivered successfully. The fact that SCO claimed their mail servers were unavailable suggests they either failed to purchase this extremely basic service or their setup is absolutely wrong by anyones standards. The purpose of multiple MX records is for this exact situation. You start with a high priority MX record (say 10) and work your way down the order (usually in steps of +10, so the secondary is usually 20).
Their Web Server
Their webserver is hosted on exactly the same subnet as their ftp server. However, during this attack, their FTP server has been available to anyone thats tried to connect to it. If they were suffering a DDoS attack of the proportions that SCO claims, this server would also have been affected and taken offline. Yet this is not the case. This blows open entirely the philosophy of a DDoS attack without any of the further evidence.
SCO has alluded to the fact that the attack is a basic SYN Flood. A very simple and old attack that has been blockable by nearly every appliance and OS for the past 3 years at least. Yet if they are suffering as they claim, then they are guilty of negligence for failing to apply patches or even configure their platforms correctly. Its very easy to turn the SYN Cookies on in Linux (sysctl isn't rocket science) and just as easy in something like a Cisco Router/PIX Firewall or a Checkpoint Firewall.
The claims that this has adversely affected their intranet suggests that the intranet is in some way exposed to the Internet. Even more alarming is the fact that it disabled their Helpdesk services for a period as well. This would suggest that their network has absolutely no perimeter protection of any kind. The smallest flaw in a product they use could apparently be used to access their core network infrastructure. Isn't that where their source code and IP documentation are kept? I'd start getting very worried about now if I were an investor.
Due diligence is a core principle of any company. That includes ensuring that the services relied upon are securely and properly setup and maintained. If SCO truly has been affected by an attack of any kind on the magnitued they're claiming, then they should be legally responsible for the results of their failure to perform due diligence. (However, IANAL so don't quote me on legalities, especially given I live in NZ, not the US).
In short, the supposed attack on SCO does not add up at all. In fact, if they are being attacked this time round, they are in serious legal trouble themselves if their reports are accurate.
I would also question why they have released this to the press as a Press Release instead of getting on with fixing the problem as quickly as possible. Also, how is it that their mail services are now restored, their FTP server never offline, yet their website remains offline? Surely, a DDoS would affect both.
Not to mention the fact that it would affect SCOs upstream provider who, when contacted last time, saw absolutely no evidence of an attack in progress at a
You miss the key aspect of the point that was being made. People are switching to Linux because it reduces the cost of support as well as the cost of implementation. However, the point was that there are still a lot of apps that run on Windows platforms for which there are no alternatives in the Linux world. Why give up all the extra benefits of Linux for just one or two applications for which no alternative exists?
;-)
The point of the WINE project is to provide that bridge. Get all the benefits of using something like Linux or BSD, get all the alternatives available to you (freely or otherwise) and if there are a few you need Windows for, use WINE to run them under Linux. Someone running Outlook under Linux would be a lot better off running Evolution and paying for the Connector license (cheaper licensing and native). However, someone running a core accounting app for which no Linux alternative exists is going to want to use WINE so they can still use that application AND get the benefits of the Linux alternatives for everything else.
WINE is a bridging tool for those migrating from Windows to Linux/Unix but who have applications for which no feasible Linux/Unix alternatives exist.
I would much prefer to save the costs involved in getting a Linux box up and running with WINE that spend the several hundred in licensing just for a few applications.
Hmmm...
($time to get up and running) vs ($time + $licensing costs for Windows)
Which is really the cheaper in the end? Support? Bah, its remote. Like you say, there is VNC if it comes down to it (bad solution really) but X across an SSH session is a lot better (regardless of how badly people think of the X protocol, it does its intended job very well still)
Just my $0.02. We differ in our opinions, but thats the beauty of diversity in life
Actually, iTMS EU is due to go live next year. Its never been a secret that iTMS is currently only available in the US/CA.
;-)
Could be worse... I own 3 macs, all run OSX, all run iTunes and I live in New Zealand where there are currently no plans at all for an iTMS release. I've been taunted by the iTMS since it was released with no relief in sight
Get in touch with Novell or Redhat and find out what platforms they can support using their products. Novell's (well, Ximians really) RedCarpet would probably be more likely to allow you to run it across multiple platforms.
There are heaps of products out there for this kind of updating. No matter what, there will always be an admin involvement in them however. You'll still need to keep an eye on things regardless of how you automate it. You'll still need to update the hosts and you'll still want to keep your eye on what the software you choose does to those hosts it monitors.
For more broad range of platforms, Tivoli and its like spring to mind. Tivoli can cover pretty much all "mainstream" platforms out there, but its probably overkill for what you're after.
Ahhh... so you got MSOffice to run on WINE in a BSD environment then? ;-)
Get rid of the whole regulation issue. Thats not necessary. It would be far better to make the software publisher liable for any faults or flaws in the software that led to an incident such as MSBlaster, Slammer or any other number of worms out there.
Virii like SoBig.F are not something that can be avoided because the vulnerability there is the user themself. The only way to sort out virii like that is to educate users to not open email they are not expecting or recognise. Even then its still a risk.
If Microsoft were liable for the damages caused by the worms such as MSBlaster and Slammer because their software was vulnerable, don't you think their culture would change very rapidly? Instead of having the worst security reputation, they'd suddenly have the very best. Win2k3 is a good start in the right direction by disabling everything by default. I applaud that. Now they need to sort out their coding practices so that these sorts of issues are a non-event.
Governments don't need to regulate anything. All they need to do is make it illegal for a company to not take responsibility for faulty products, regardless of the product. It worked in the automobile industry, its worked in the medical industry, its worked in the engineering industry.
If my car explodes because of a fault in the fuel line at manufacturing, I'm perfectly within my rights to sue that company. If my computer becomes completely unusable because a vulnerability allowed someone to damage it or similar, why shouldn't I sue the publisher of that software? I'd also reserve the right to sue the person that exploited that vulnerability and caused the damage.
Don't need regulation, just liability and a warranty of suitability for a purpose. 'This OS is guaranteed to perform to XXXXXXX level and is considered suitable for XXXXXXXXXX purpose.'
Umm... Both Kolab and OpenGroupWare.org are suitable for this purpose. They are freely available, work with quite a number of clients and offer a complete alternative to Exchange (including groupware calendaring features).
Now I admit that there is an investment required for them to be usable with Outlook and, by extension, Evolution, however this is minimal compared with the cost of licensing Exchange.
The biggest expense is time. They are not 'trivial' to set up just yet and do require a decent time investment in doing so. However, they are most definitely built on open standards and free/opensource software.
I'm sure there are plenty of others that'd do it to, but those are the ones most recently making waves and thus the ones that stand out in my head at the moment.
If the company hadn't paid the subscription, would the devs have been eligable to get the PDA's? If you buy a PS2 and I send in for the $20 rebate because you didn't realise you could, who gets the rebate?
Quite simply, the PDAs are the property of the company simply because it was their subscription that paid for them. Therefore they have the say over what does and does not happen with them. Just because you and your buddies saw the offer doesn't give you ownership. Thats like me claiming your rebate on a PS2.
Wake up and smell reality. Stop trying to be a troll. If you're that unhappy about the situation, take your toys and go home. I'm sure Cartman would be proud.
The more I read this, the more it reminded me of the marketing version of how Apple would like us to think of Resource Forks.
Truthfully, there isn't exactly a lot of difference in the concept or the idea. Implementation is vastly different but the idea remains very similar.
Why do I want to accept this sort of idea anymore than I want to accept resource forks? If I copy a file with resource forks from one of my macs to nearly any other OS on the market thats not specifically configured to support them, I lose that information. Why do I want to continue this?
I use HFS+ because I have to. To get all the functionality I want out of my macs, its the only real option I have. But for anything other than system level files that are never likely to be copied to another machine, this is just a waste of time to me.
Next question. Say I do run this file system on my machines. I build up a heap of data and I'm using "files as directories" to store metadata about those files. How do I back it up? Don't even try to tell me "rebuild tar". Haven't we put tar through enough to try and extend its capabilities? I wouldn't touch a file system with these capabilities without a guaranteed way of being able to backup ALL the data. Otherwise its just truly not worth the effort.
What do I use now?
When more and more friends started wanting blogs and then more of their friends started wanting blogs, I wanted something that I could use for a whole lot more than just personal blogs. I also wanted to have the option to put subscription fees on it (when things started getting expensive to host) and that was a live and ongoing project.
So now I use the LiveJournal code. Its Perl (will run on nearly every platform from IIS to Apache to iPlanet to....) and SQL backed. Its scalable (like you wouldn't believe. Look at LiveJournal.com, over 1,000,000 active blogs) and its not slow.
It allows for full management of the user and also offers the abillity to move to a subscription model without having to change anything. There are various levels of subscription as well... Free, Paid, Permanant, Admin. You can also define more and levels within each.
I could ramble on further, but if its what you might find useful, check it out at http://www.livejournal.com/code/
They call it "Open Source/Free Software" with links to both opensource.org and fsf.org.
I used MovableType until recently for my own personal website. Both as a blog and as the engine to power the news of the website.
:-)
.wml file template was very simple.
The advantage to MT is that it can store the info in one of 3 different databases (including a local file if you don't have SQL of some sort) and the only time the Perl application is accessed is when you're either adding a new entry to the blog or when someone is posting a comment. Everything is generated as HTML so when a user views the page, they're not calling any scripts. Keeps overheads down and allows for bigger sites on smaller servers.
Caching I found an issue. The HTML is static. So I quite often had to manually tell Squid to refresh the site if it was getting updated lots and I wanted to see those updates.
Multiple authors per blog is useful. Its pretty decent as far as permission system goes. I dislike the fact that a user can make certain changes (such as altering where on the file system their blog gets created) but this can be turned off simply enough with only minor loss of functionality to the end user themself. Then again, what they don't know they could've had, they won't miss.
Security isn't so bad. You can use HTTP authentication to stop the users getting in to the directory with the Perl app and then their username/passwd to access the prog itself. This gets complicated if you want to permit comments. However, Security concerns are few and far between. 2.64 takes care of all known bugs and when bugs are announced, a patch is pretty quickly released.
Remember, the average Joe doesn't need to even get near the Perl application if you disable comments. All they get is straight HTML.
People complain about the CSS and so on. I haven't had a problem with this myself. I found it pretty simple to modify the entire look and feel. The template structure is pretty straight forward and expandable. Adding something like a WAP
Hunt around, there are a heap of plugins for it. Including plugins that allow you to use WikiWord formatting and more.
While it was of use to me, it suited my purposes very well. Its very quick and scalable. I had about 30 blogs plus a news page running from the single install on a P200. Because the Joe is getting HTML and not running the Perl scripts to generate it every view, it doesn't need a major box.
But you just admitted that the energy supply would deplete by "slowing down the spin of the Earth a little bit at a time".
;-)
Therefore, even that wouldn't be perpetual energy or perpetual motion and still follows the laws of thermodynamics.
Thing is, for over 150 years people have been trying to disprove the laws of thermodynamics. Quite simply put, it is impossible to create more energy than you use. Whether it be heat, kinetic, electricty or "other".
However, I could stand to lose a few pounds... slowing the Earth a bit sounds like a good way to do that... Purely in the interests of science that is.
It is basic physics. It is impossible to get more energy out of a device than you put in to it. Simple example of this would be a turbine for a power plant.
To spin the turbine, you have to provide it energy. In many cases this comes in the form of Kinetic energy from moving water.
However, you can never generate so much electricity that the turbine can power itself. Heat, friction and a whole heap of others come in to play and eventually (it could take a long time if you engineer it really well) the turbine will have slowed right down and not be able to produce enough electricy to even spin itself, let alone power anything else.
I had a link to a site last year that went through a whole heap of "perpetual energy" machines and completely refuted them. However, I cannot find this link and so offer the following one instead.
http://www.phact.org/e/dennis4.html
Enjoy
You have no idea of the circumstances, preparation, precautions or anything else about the event, nor do you even know me.
Who are you to judge me?
More over, how does one picture of a single event have any bearing at all on my knowledge or anything else other than the event itself?
Is this honestly the best place to even have this discussion?
Given the proliferation of NAT on many fronts now, I personally have used, installed and maintained SSH VPNs on many of my clients networks because I find it a lot more reliable than IPSec.
Here in NZ, ADSL is running via PPPoATM and all network terminators must be running NAT (this is a requiremet of the Telco, not of the technology). Because of the much lower costs of DSL vs Frame, this is becoming the default setup for most companies now. IPSec in this kind of environment where NAT is at both ends, or even just one, becomes a real PITA to get running and keep running. SSH just works.
Once the keys are set at both ends, the tunnels just do their thing. Establishing ports is not difficult. For my setup I create Virtual IPs at both ends of the network and then essentially do port forwarding across the tunnel to those ports. Essentially a combination of SSH and (in my case) IPTABLES. Works very well, very sweetly and NAT doesn't cause me any problems.
I can't believe this post got this far. A solution can even be found on Yahoo!
Dude, core rule of running ANY OS is to disable anything you don't use. If you don't know which services/daemons you do or don't need, then install a software based firewall on the OS until you can get help to start securing the OS properly.
For windows, software like Zone Alarm (http://www.zonelabs.com) is a good start. McAfee, Symantec and a whole heap of other companies offer similar products also.
For *BSD (Including OSX) IPF is available on nearly all variants. For GNU/Linux, NetFilter/IPTables in the modern kernels and IPCHAINS and IPFWADM in the older kernels.
For commercial versions of Unix, There are a quite a few options, but most home users aren't going to be running Solaris or HP-UX or AIX or other such OSs.
I got the 7650 the day it was released to my local market. Couldn't resist. Did the same with the 3650. The difference between the two? Other than the style... Not a lot. Audio Bluetooth on the 3650 allows for a bluetooth headset, and the MMC capabilities mean a lot more apps can be installed... Also a huge bonus.
;-) Maybe if Verisign and T-Mobile sort their problems out, I'll be able to send MMS msg's to friends there.... Or maybe I'll just stick to sending them to my friends in every other country ;-) (well, almost)
I have to admit, the American cellular market makes me laugh. CDMA? What an expensive joke. GPRS is so much cheaper because you're only paying for what you use, not how long you spend connected (which includes idle time).
I personally will never go near a CDMA network as long as GSM/GPRS/UMTS are available. For a supposedly 3G service, its an extremely backward network.
BTW, OS X 10.2.5 supports the 7650 and the 3650 via bluetooth without a problem. Including transfering files between the two, syncing the calendars, addressbooks and so on... I have no problems with it on my Powerbook or my Powermac.
Oh well... What can I say? USA, congrats on gradually catching up to the rest of us.
Actually, Gobbles Security are one of the most active, and largest, exploit groups hanging around the "Security" field at the moment. They have a knack for Pissing off Theo DeRaadt.
You can see the posting to bugtraq from them on the SecurityFocus website.
http://online.securityfocus.com/archive/1/306476does anyone else find the fact that "Fritz" Hollings voted against this bill kind of ironic given is track record so far?
:P
I would have figured that he would've loved to have more power to chase after pirates, especially in the name of "Homeland Defence"
Oh well, I guess he just didn't get his asking price this time round.
I'm sorry, but I really find it concerning that someone so vocal in his support of other laws that are just as draconian, would then turn around and vote against this one. It just doesn't seem to add up.
Tutos for project management and basic CRM. It also kinda crosses over into an ERP application as well.
Tutos does product and project management, client management (with the ability to attach almost anything to a client and break it down into departments and more) and a whole heap of other things.
Best of all, its built using PHP on MySQL and Apache with *the only* (sic) free software license (GPL 2). I run it on Linux but I doubt you'll have trouble getting it to run on MacOS X.
You'll find it at http://www.tutos.org along with some pretty decent info including full documentation, a demo, screen shots and more. It is fully web based.