I use LTSP for Internet Kiosks at UNC - Chapel Hill. We have a mix of Dell machines and an HP5500 think client, soon to migrate all of them to the pure thin clients. It's been an excellent set-up. I just updated everything to LTSP4.1 and the latest Firefox. All the machines PXE boot from the server in seconds.Students hammer them pretty hard and they've stood up well. LTSP is a great solution and the support mailing list is active, timely and useful.
I bought one of these recently and use it every day. Padded inner sleeve, but I wouldn't drop it. Very comfortable to carry on either side. Bright color inside makes it easier to find small things and a nice water resistant outer pocket for the MP3 player. Not too pricey compared to some of the other things mentioned and it doesn't look at all like a computer bag.
I disagree that Exchange 2000 is "old". It's the most widely used MS "mail" application, very few people have moved to Exchange 2003 and it's still supported by MS.
Your point about the Linux distro is also incorrect. This is not an OS vulnerabilty, it's an appication issue. Perhaps you meant to say, "install any sendmail version that is years old, then don't patch it..".
Also, there are very few Apache exploits which would cause me to be worried about my sendmail server. Separation of processes is a good thing (TM).
Well, they're very likely already looking into it. If you download the public_affairs.pdf file you'll see that they had a "Successful meeting with Office of Homeland Security Director Tom Ridge".
Sounds like they're doing the behind the scenes work to get the legislation in place. Pretty soon they'll probably start saying it's a way to stop terrorists and there will be no stopping it.
I can see it now - "Homeland Security Director Rom Ridge announced today that all Arab visitors to the U.S. will be implanted with RFID tags to ensure their identity and ease their identification while boarding transportation systems. All airplanes have now been equipped with RFID scanners at the door which wil notify the crew if one of these people tries to board".
Or once you;ve got it up and running there's even a Jabber module included in a default Webmin install:
http://www.webmin.com/standard.html
Doesn't get a whole lot easier than Webmin.
You used the wrong product. Crossover plugin is for flash, etc. plugins for your web browser. Crossover Office allows you to install actual apps like Office. I've used both and they are quite impressive. It's real fun when after your Office install, the windows installer wants to reboot the machine and the window just closes for a second. It took something like 5-10 mintues to install Office 2000 and it was up an running. Very nice work on their part.
Apparently quite a few of us did. According to the article at one point she was getting an e-mail every 90 seconds. Not bad, but let's not forget the DMCA still exists.
Now if HP were to come out against the DMCA, citing this type of incident as exactly the kind of thing that _could_ happen under the law I would gain back some of my respect for them (and maybe my desire to purchase their products).
She understnads economics. If you purchase HP or Compaq for your company, let her know you will be reassessing that decision. That's what I did. Boycotts of companies that exhibit this kind of behavior are the best way to get them to change. We don't buy their products and they feel the effects.
If you're meeting with Compaq or HP sales people anytime soon, cancel the meeting. If you've got a contract from them, don't sign it. Let them know why you're doing this. Sales people need the sales and if they can't get them that will work it's way back up the chain of command.
Corporate Time from Steltor www.steltor.com. Runs on Linux, Windows 2000, Solaris. They have clients for Linux, Mac and Pcs and it blows Exchange calnedaring out of the water.
Use up2date and the RedHat network. You run it, it identifies and downlaods the patches and installs them. Also excellent is Ximian's Red Carpet (although you need X for that and I don't run X on my servers).
Or, simply subscribe to the update e-mails from RedHat and apply the ones that matter. For instance, my servers don't run (or even have installed) about 80% of the stuff upgates get issued for so I can pick and choose what I want to install.
That's not an option on XP. You get it whether you want it or not and backing it out is virtually impossible since you really don't know what happened.
That's the difference between being a sysadmin on a server and a desktop user. You gotta know what you're doing, but I'd much rather have the control that a Linux distro gives me.
Re:Missing PIM Functionality
on
StarOffice 6.0
·
· Score: 1
So ? Keep Outlook and ditch Office for Star / Open Office. What's to stop you from doing that. Even better (of course) ditch that Windows box for something that works.
There's also Corporate Time from Steltor. They have a native Linux client and as a calendaring server it's far superior to Exchange. I've always thought that craking open the Evolution code and isnerting the CT Linux client for the Evolution Calendar would be a great way to remove Exchange from a lot of places...
Um, what rock have you been looking under. Certainly you haven't been looking at real products.
In addition to OpenMail and Notes, try Corporate Time ( www.steltor.com). A much more robust calendaring app then Exchange will ever be. It runs on Linux and supports Outlook as a client.
It's been deployed in lots of big companies and universities (BMW apparently has 40,000 seats).
You can quite happily use group policies with Samba. And mapped drives and anti-virus updates are a snap via logon batch file. We've got over 1,500 Windows 98 machines going all that right now. I'm typing this from one with 5 mapped drives and the latest NAV signature files which were automatically installed.
Sure, it's not point and click, buy a third party tool, MS way of doing things, but it's not too darned difficult to do either. It's all clearly dosumented in the Samba docs, I suggest you take a look.
In addition, our file servers have been up for almost a year (no reboots except for power outages since deployment). While our Exchange 2000 servers (with AD, soon to be replaced with a real LDAP directory) have to be rebooted at least once a week due to memory leaks in the Exchange services.
Licensing costs for Linux deployemt for file and print (the stuff that works) $0. Costs for Exchange 2000 server, licenses, etc. that doesn't work : over $70,000. Which one was the better business decision ?
Corporate Time (www.steltor.com). Not open source, but a very nice calendaring app. They have clients for Mac, PC and Unix/Linux, a nice web interface and a plug-in for Outlook. This is the calendaring server that HP used for Open Mail and was the guts behind the Netscape calendaring server as well. Good stuff.
WebDAV rules. We've been using mod_DAV for Apache for some time now to provide the "web folders" experience for IE clients. It lets us run Linux file and print servers with remote access via IE and Web Folders. mod_DAV will be included standard with Apache 2.0. Definitely a great protocol.
The problem with MS and standard protocols is they always tend do to something to them to reduce or hamper interoperability with non-MS clients. I've been trying to get a variety of LDAP clients to talk to Active Directory for some time now and nothing but the MS ones seem to work.
Plus, Outlook 2000 and Exchange 2000 aren't talking WebDAV AFAIK, to get the full functionality (calendaring, etc.) you need the MAPI APIs and then we're into the proprietary stuff. OWA (the web component of Exchange) may use WebDAV to get to your calendar, but Outlook still relies on MAPI.
Take at look at Corporate Time from Steltor (www.steltor.com). We're currently evaluating it to replace Exchange 2000. It runs on Linux (and Soalris and HPUX and 2000) and provides better calendaring than Exchange does. They have native clients for Windows, Mac and Unix.
They also have an Outlook client which uses an IMAP server to handle mail. To the user is looks like Outlook plugged in to Exchange, but you can run it all on Linux and way fewer machines than Exchange. It's not cheap, but it does seem to be a really good product.
So, if I read this right it's also a pretty effective way for MS to shut down Linux. Either we get some copy protection schemes - sure, they'll be open source and we'll all get to work on the code - in the kernel or no running Linux for you in the U.S.
That's the really ugly side of this, it stretches far beyond simply having a chip in the PC. It would require software to prevent copying as well.
What you don't see is that they won't be able to do that. I would likely be seen as "enabling" the distribution of protected material. More likely, they'll seal the boxes so you can't even get it open to try (or add RAM, or replace a bad hard drive). Otherwise, they'd be at risk under the broad language of this act.
Despite their complaints they will find a way to make money out of this.
You can get the RTF to stay if you enable it for the IMAP and POP3 protocol on the Exchange server. Of course, as soon as you set up a rule that stops working. That was a lovely find.
The real issue is the POP3 and IMAP services on Exchange 2000 are not stable, they leak memory like a seive and bring the services down. Our servers crash and/or refuse users on an almost daily basis. No surprise, but SP2 didn'f fix it and MS just sort of says "gee, it shouldn't do that".
We're looking at either converting to full MAPI mode and upping the bandwidth to remote sites or dumping Exhchange in favor of an IMAP/POP3 server and something like Corporate Time for scheduling.
You must not be doing anything with them. Just in my office I've got 2 Linux boxes with uptimes in the months and they're running all kinds of services. Meanwhile, the corporate Exchange 2000 / Windows 2000 servers are now on a 2-3 day reboot cycle to keep them from eating up a gigabyte of RAM.
We're currently in the process of rolling out 50+ samba (2.0.7) servers across the U.S. The installation consists of installing RedHat then running a shell script which sets up: Apache, Samba, Webmin, user permissions, start-up scripts, DHCP server, etc. The whole process takes about half an hour and is unattended once you type./setup.sh.
Sure, it's not completely unattended, but because it's based on GPL software we were able to save big bucks on licensing and provide a customized admin tool set for non-technical local administrators.
At the same time as this we did an Exchange 2000 / Windows 2000 / Active Directory deployment for e-mail and I can tell you fom experience the Linux / Samba stuff was inifinitely easier to understand. We had to bring in consultants to help us get through the Windows 2000 stuff, whereas I pretty much single handedly configured the Linux servers and the installation routines myself (and I'm not what I would consider a guru, just someone who is willing to put in the up-front work for the long-term gains).
Got a problem with Samba ? Check the extensive, included docs, edit the text based config file, restart the SERVICE, not the SERVER and you're done, clients don't even notice the service was off for 5 seconds. Got a problem on 2000 ? Good luck, no useful docs are included, you have to click 50 things and turn on "advanced view" everytime you want to do something useful and you often have to restart the whole machine - clients definitely notice the server is down for 15 minutes.
If you're talking costs you have to figure long-term and we've already seen the huge difference in support costs (time and money) in dealing with these 2 plaforms. Give me Linux and Samba any day and tremendous kudos to the Samba team for a fantastic product!
Slashdot Mirror
he'd be 1/8 of the man he should be.
I use LTSP for Internet Kiosks at UNC - Chapel Hill. We have a mix of Dell machines and an HP5500 think client, soon to migrate all of them to the pure thin clients. It's been an excellent set-up. I just updated everything to LTSP4.1 and the latest Firefox. All the machines PXE boot from the server in seconds.Students hammer them pretty hard and they've stood up well. LTSP is a great solution and the support mailing list is active, timely and useful.
Um. How many of us are running IE on Linux? Besides, that's the same exploit that's already under discussion.
I bought one of these recently and use it every day. Padded inner sleeve, but I wouldn't drop it. Very comfortable to carry on either side. Bright color inside makes it easier to find small things and a nice water resistant outer pocket for the MP3 player. Not too pricey compared to some of the other things mentioned and it doesn't look at all like a computer bag.
Your point about the Linux distro is also incorrect. This is not an OS vulnerabilty, it's an appication issue. Perhaps you meant to say, "install any sendmail version that is years old, then don't patch it..".
Also, there are very few Apache exploits which would cause me to be worried about my sendmail server. Separation of processes is a good thing (TM).
Sounds like they're doing the behind the scenes work to get the legislation in place. Pretty soon they'll probably start saying it's a way to stop terrorists and there will be no stopping it.
I can see it now - "Homeland Security Director Rom Ridge announced today that all Arab visitors to the U.S. will be implanted with RFID tags to ensure their identity and ease their identification while boarding transportation systems. All airplanes have now been equipped with RFID scanners at the door which wil notify the crew if one of these people tries to board".
Yeah, I got it. I was feeling smart-assed this morning. That has passed now and I'm back to dumb-assed again and feel much better.
Not to be picky, but Alan Cox lives in Wales these days, I believe and I don't think the Europeans are very fond of guns anyway...
Or once you;ve got it up and running there's even a Jabber module included in a default Webmin install: http://www.webmin.com/standard.html Doesn't get a whole lot easier than Webmin.
You used the wrong product. Crossover plugin is for flash, etc. plugins for your web browser. Crossover Office allows you to install actual apps like Office. I've used both and they are quite impressive. It's real fun when after your Office install, the windows installer wants to reboot the machine and the window just closes for a second. It took something like 5-10 mintues to install Office 2000 and it was up an running. Very nice work on their part.
Now if HP were to come out against the DMCA, citing this type of incident as exactly the kind of thing that _could_ happen under the law I would gain back some of my respect for them (and maybe my desire to purchase their products).
Boycotts of companies that exhibit this kind of behavior are the best way to get them to change. We don't buy their products and they feel the effects.
If you're meeting with Compaq or HP sales people anytime soon, cancel the meeting. If you've got a contract from them, don't sign it. Let them know why you're doing this. Sales people need the sales and if they can't get them that will work it's way back up the chain of command.
Corporate Time from Steltor www.steltor.com. Runs on Linux, Windows 2000, Solaris. They have clients for Linux, Mac and Pcs and it blows Exchange calnedaring out of the water.
Or, simply subscribe to the update e-mails from RedHat and apply the ones that matter. For instance, my servers don't run (or even have installed) about 80% of the stuff upgates get issued for so I can pick and choose what I want to install.
That's not an option on XP. You get it whether you want it or not and backing it out is virtually impossible since you really don't know what happened.
That's the difference between being a sysadmin on a server and a desktop user. You gotta know what you're doing, but I'd much rather have the control that a Linux distro gives me.
So ? Keep Outlook and ditch Office for Star / Open Office. What's to stop you from doing that. Even better (of course) ditch that Windows box for something that works.
There's also Corporate Time from Steltor. They have a native Linux client and as a calendaring server it's far superior to Exchange. I've always thought that craking open the Evolution code and isnerting the CT Linux client for the Evolution Calendar would be a great way to remove Exchange from a lot of places...
- In addition to OpenMail and Notes, try Corporate Time ( www.steltor.com). A much more robust calendaring app then Exchange will ever be. It runs on Linux and supports Outlook as a client.
It's been deployed in lots of big companies and universities (BMW apparently has 40,000 seats).
- You can quite happily use group policies with Samba. And mapped drives and anti-virus updates are a snap via logon batch file. We've got over 1,500 Windows 98 machines going all that right now. I'm typing this from one with 5 mapped drives and the latest NAV signature files which were automatically installed.
Sure, it's not point and click, buy a third party tool, MS way of doing things, but it's not too darned difficult to do either. It's all clearly dosumented in the Samba docs, I suggest you take a look.In addition, our file servers have been up for almost a year (no reboots except for power outages since deployment). While our Exchange 2000 servers (with AD, soon to be replaced with a real LDAP directory) have to be rebooted at least once a week due to memory leaks in the Exchange services. Licensing costs for Linux deployemt for file and print (the stuff that works) $0. Costs for Exchange 2000 server, licenses, etc. that doesn't work : over $70,000. Which one was the better business decision ?
Corporate Time (www.steltor.com). Not open source, but a very nice calendaring app. They have clients for Mac, PC and Unix/Linux, a nice web interface and a plug-in for Outlook. This is the calendaring server that HP used for Open Mail and was the guts behind the Netscape calendaring server as well. Good stuff.
The problem with MS and standard protocols is they always tend do to something to them to reduce or hamper interoperability with non-MS clients. I've been trying to get a variety of LDAP clients to talk to Active Directory for some time now and nothing but the MS ones seem to work.
Plus, Outlook 2000 and Exchange 2000 aren't talking WebDAV AFAIK, to get the full functionality (calendaring, etc.) you need the MAPI APIs and then we're into the proprietary stuff. OWA (the web component of Exchange) may use WebDAV to get to your calendar, but Outlook still relies on MAPI.
They also have an Outlook client which uses an IMAP server to handle mail. To the user is looks like Outlook plugged in to Exchange, but you can run it all on Linux and way fewer machines than Exchange. It's not cheap, but it does seem to be a really good product.
That's the really ugly side of this, it stretches far beyond simply having a chip in the PC. It would require software to prevent copying as well.
Despite their complaints they will find a way to make money out of this.
The real issue is the POP3 and IMAP services on Exchange 2000 are not stable, they leak memory like a seive and bring the services down. Our servers crash and/or refuse users on an almost daily basis. No surprise, but SP2 didn'f fix it and MS just sort of says "gee, it shouldn't do that".
We're looking at either converting to full MAPI mode and upping the bandwidth to remote sites or dumping Exhchange in favor of an IMAP/POP3 server and something like Corporate Time for scheduling.
You must not be doing anything with them. Just in my office I've got 2 Linux boxes with uptimes in the months and they're running all kinds of services. Meanwhile, the corporate Exchange 2000 / Windows 2000 servers are now on a 2-3 day reboot cycle to keep them from eating up a gigabyte of RAM.
Sure, it's not completely unattended, but because it's based on GPL software we were able to save big bucks on licensing and provide a customized admin tool set for non-technical local administrators.
At the same time as this we did an Exchange 2000 / Windows 2000 / Active Directory deployment for e-mail and I can tell you fom experience the Linux / Samba stuff was inifinitely easier to understand. We had to bring in consultants to help us get through the Windows 2000 stuff, whereas I pretty much single handedly configured the Linux servers and the installation routines myself (and I'm not what I would consider a guru, just someone who is willing to put in the up-front work for the long-term gains).
Got a problem with Samba ? Check the extensive, included docs, edit the text based config file, restart the SERVICE, not the SERVER and you're done, clients don't even notice the service was off for 5 seconds. Got a problem on 2000 ? Good luck, no useful docs are included, you have to click 50 things and turn on "advanced view" everytime you want to do something useful and you often have to restart the whole machine - clients definitely notice the server is down for 15 minutes.
If you're talking costs you have to figure long-term and we've already seen the huge difference in support costs (time and money) in dealing with these 2 plaforms. Give me Linux and Samba any day and tremendous kudos to the Samba team for a fantastic product!