Posted on 10/03/2007 9:58:26 PM PDT by abt87
I would respectfully disagree. I think just because we don’t do it now doesn’t mean we can’t figure out a way to do it in the future.
I also agree with another poster who stated it has a philosophical and political (I didn’t say religious as well, although everyone knows that is sometimes a propensity as well) quality to the use of a free OS.
I understand that completely. Not my boat, but I can see how it is for some.
Bottom line...we are ALL monkeys with keyboards. If there is a way for people to break it, we are going to do so. Even OSX, an OS I use and like can be broken...I am the head of IT in my department so I understand technology pretty well, and I was trying to use Final Cut Pro last night on my Mac at home. It was completely screwed up, wouldn’t transfer data from the video camera, etc. It gave me very strange error messages, and I thought for sure SOMETHING on my computer was fouled up. I checked setting after setting, preference after preference, dicombobulated all external devices, etc.
I was pretty flummoxed. But after a day of dwelling on it, had the eureka moment...it wasn’t the computer, but the camera itself. My finger had accidentally pushed a switch and moved the camera from tape mode to flash disk mode somewhere in the last several days...it just wasn’t apparent from the symptoms what the problem was. It is a small, out of the way switch on the camera that I never even use.
Bottom line, if I hadn’t found that and called support, I’ll bet a buck someone would have had me reinstalling the OS or application. That is the kind of silly issue that people have to deal with all the time...a minor one, but if you don’t know the answer or how to find it...it becomes a major one.
So what? My boss is a Buddhist it has no effect on my Religious opinions one way or the other..
And beagles ;) Technically anything smaller than say a dlt tape can be toasted ... Oh the possibilities !
That used to be true, but isn't any more. Besides, think about how much feed and care you have to give a Windows PC to keep it running. Viruses and mallware prevention and repair takes more time than you probably think about.
People who open .exe from their inbox are not gonna wrap their head around the command line interface, ever.
You don't have to on Linux, if you don't want to.
It is pretty easy to get a running system (new install) working out of the box. A Knoppix LiveCD is a great example. Most new Windows installations work well out of the box as well. The problems show up after the systems have been running for a few months. Updates and patches arrive. Some are benign. Some cause significant failures. When the smoothly operating appliance stops working smoothly, it's time to fix it. That's what separates the appliance operator from the competent system administrator. What raises the stakes is that the system that has been running for months now has lots of valuable data and user customized configuration invested in it. Often that data represents significant hours of labor. It's not just a "throw away" and reload proposition. It has to be restored to working without destruction of all of the other investment in the system. That is not a task for an unwashed appliance operator. If you're going to adopt Linux as your OS, you also need to make the commitment to be a competent system administrator to properly maintain your new baby. It's going to take time and probably a fair number of new books on your shelf. "Free" only applies to the initial acquisition cost, not the ongoing maintenance.
If you think its tough getting your cell phone to work as a modem with a Windows OS, just spend some time trying to get it to work with Linux. I run Kyocera M200 1xRTT modules as my cell phone connection to VerizonWireless. My embedded systems are based on Linux. I recently had to tweak the PPP parameters to deal with the changes from Simple IP to Mobile IP being rolled out on Verizon. I'm still twiddling my new USB720 1xEV-DO dongle to work with Linux. The Verizon drivers for Windows XP worked just fine out of the box. Getting the USB streams pointed properly for Linux has been a chore. There a huge blogs with people discussing the difficulties over periods of months before stumbling on the right solutions.
My assessment came out kind of harsh...I was in a grouchy mood this morning. I always think I should not post on FR until after I get out of the shower.
I understand completely the point you make about freedom of choice and dumbing it down...I just cannot divide it so cleanly between no choice and no inhibibitions...:)
The points you make are perfectly valid though, and I appreciate your communicating them to me the way you did...:)
When I went from the 2.4 to 2.6 kernel on my desktop, rather than just do an upgrade in place, I opted to reload because the way the /dev/ filesystem was changed in such a major way. Since my /home partition was a separate physical drive, I simply told the installer to ignore the drive while wiping the rest of my stuff. Once it was complete, everything just worked. All my data was exactly where I left it, and all my preferences were maintained. That freaking rocks IMO.
Today, I have embedded Linux running from FLASH disks on my rail cars. Disk space is at a premium. The kernel is custom generated for minimum size...just the features required to do the job. Executables are examined with "ldd" to identify the minimum necessary set of shared libraries. Those libraries go on the disk in the correct spots to support the application. Boot time from power on is under 15 seconds to fully operational.
Once those FLASH images are deployed, the fun begins. Debian or Fedora patches are coming out on a regular basis. The compiler, headers, libraries and kernel on the development system are getting updated. The next time the applications tree gets recompiled....oops. The libraries underneath have changed. You can't just replace the applications because many of them require a later version of the shared libraries. In Windows parlance, welcome to DLL Hell. Further, when the kernel changes, there are special kernel modules required to support the interrupt driven I/O processes. They must be built against the exact kernel build tree that will be used for the execution environment.
Linux, QNX or Windows are equally painful when working with embedded systems. Trying to incrementally support a bunch of embedded Linux systems while the Linux world continues to morph underneath isn't particularly pleasant. A desktop Linux system with connections to the internet does a pretty good job of keeping pace with patches. Even so, I have a server on the east coast that was "upgraded" to Fedora Core 5 when the Debian 2 ran out of gas (and Debian support). Now Core 5 is itself out of date. I have to backup all the special web server applications and mySQL databases before upgrading to Core 7. The company network security people are constantly doing security scans. A Core 5 system is eventually going to fail to get a crucial update. The penalty is immediate loss of access to the network until the discrepancy is remedied.
I believe Fedora 8 is coming out in Dec. Fedora is on a 6-month release schedule now.
That's a pain. I have 3 Fedora Core 7 systems at the house and two Debian 4.0. The lab in Virgina is Debian 4.0. The server in Virginia is Core 5 awaiting update to Core 7. The embedded systems started as Slackware 9.0 because that was the example image provided by Diamond Systems to go with their boards. I needed extra items in my kernel to support OLSR mesh networking, so the canned example image wasn't enough. Diamond has only updated their DSCUD 5.92 kernel driver up to kernel 2.6.11.10. It has problems with the current 2.6.18 vintage. Keeping up with the constant change includes dealing with hardware/software vendors that are also behind the curve. Linux will soon ditch the x386 world. You'll need a more modern CPU to boot it. That will leave many of my PC104 CPU boards abandoned.
“LINUX runs the Google servers that manage billions of searches each day.”
That’s a disinginuous statement. Google has heavily modified their version of Linux to only include the pieces they needed and they even re-wrote much of it.
I had to drag my company (PacBell) in the TCP/IP direction. My room full of UNISYS 7000 systems were first linked with SLIP links at 19200 in a "star" configuration using the 36 port serial interface on one machine to create a big default destination and router. After demonstrating the economic benefit of the "cheap" implementation, the company authorized installation of Ethernet on all 80 machines (San Diego and Hayward). The savings continued to accrue and the pattern was set for continued deployment.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.