Slashdot Mirror
Why Munich Will Stick With Linux
Jason Hibbets writes: "There are many solved problems in open source. Groupware is not one of them," Georg Greve, co-founder and CEO of Kolab System starts off his post highlighting recent features of the latest release of the Kolab groupware project. He calls out a few newly elected politicians that don't like the current set-up, but says that thousands of users don't have the same experience. "Until today, the city of Munich is using the same stand-alone calendaring and email systems it had used when it was still fully operating on Windows. Updating these systems had a lower priority than the migration to LiMux then. But an upgrade is underway now. And, the solution they chose is agnostic to the desktop platform and will service LiMux and Windows alike. The primary difference made by another migration would likely be due to the perils that come with any migration, such as additional costs and delays. In other words: The very problem used to criticize the LiMux desktop is already being solved."
It all reads like an ad for Kolab.
This space for rent.
Yes but you usually don't run into this problem when using MSOffice because everyone in the office has the same Office....
Not all offices have the same version of MS Office installed throughout the office. I've been at companies that have had three different versions of MS Office installed, and they did have issues with exchanging documents. The easiest solution was just to tell everyone to "save as an old MS Office format" when a document needed to be shared.
.
Moving form office to office, I've found that LibreOffice does better than MS Office at properly importing office documents from various versions of MS Office. YMMV.
"Yes but you usually don't run into this problem when using MSOffice because everyone in the office has the same Office. "
No, no they dont.
My experience is that when new versions of Word have problems opening a file created by a previous version, the solution is to open them in OpenOffice and use OO to save to the newest MS Word format (or leave them as odt).
In that way, OpenOffice has BETTER compatibility with various types of MS Word documents than MS Word itself does.
That's fine as long as everything is done for the user. There's nothing easy about getting various H/W setup on Linux even with the best distro.
My Daughter's Talking Barbie Agrees with you.
Seriously, a person who cannot install and use linux today should not be allowed to use a computer.
The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
A person who assumes anything computer related is easy for a non-technical users should not be allowed to make suggestions on what is right for home users.
I consider changing disk brake rotors, pads and calipers easy. Can you give me the steps? Please don't skid any because I'm going to call you on it.
FIrst thing you do is raise the vehicle, and remove the wheel or wheels depending on the proficiency of your setup. Let's assume you do one side at a time., so I'll go singular.
Remove the bolts that hold the caliper onto the wheel.
Remove the caliper assembly from the wheel and rotor.
Remove the rotor
Troubleshooting steps if not just replacing the rotor:
Before removing the rotor, check for runout. Best way to do this is with a dial gauge. If out of spec, replace. Symptoms that there might be excessive runout or warpage would be if the brakes were pulsating when you were coming to a stop. Remove the rotor. Inspect the rotor for grooving from the pads.
If you will resurface the rotors due to grooving, measure the thickness of the rotor using calipers. There is a minimum thickness allowable depending on the vehicle.
Replace or reface as needed.
Replacement of pads
Remove bolts holding caliper together.
Remove old pads and discard or return to parts jobber. Some pads will have anti vibration shims. Do not discard unless your replacement pads include them.
Compress the caliper piston. I use a small chunk of wood and a C clamp to do this. Place the wood on top of the piston, and the c clamp on that. Open the brake bleeder valve, tighten the c clamp and place a can to catch expelled brake fluid.
After compressing the caliper piston, note the apparent condition of the piston by how it felt during compression. Inspect the brake fluid. If dirty or burnt smelling, or possible water contamination. replace the brake fluid.
Install new pads into caliper, and anti-vibration shims if used.
Install refaced or replacement rotor. Some shops I have known use a sort of hone on new rotors. Since most shade tree mechanics don't have these, it's optional. I haven't seen much of a difference.
Using a torque wrench, reinstall the caliper onto the wheel.
When finished, and using a helper, bleed the brakes. I've always pumped the brakes a few times, then opened the bleeder valve, allowed any air to escape, then shut the valve before releasing the brakes. Replace the fluid you removed during caliper compression. When only fluid comes out, tighten the bleeder valve, and move to the next wheel as needed. Brake bleeding is finished when the brakes have normal travel when pressed. Top off the master cylinder as needed with fresh brake fluid.
Give it a final inspection, then reinstall the tires.
Take a test drive to be certain the brakes work correctly.
Obviously during the process you look for worn or leaking hoses, brake lines, or vacuum lines for power brakes as needed, and during the bleeding process you note if there is any apparent pedal fade, which might indicate the need to replace the master cylinder.
I've done this a few dozen times. It is easy, and installing linux is a fucktub easier than changing out rotors and calipers.
The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
Yep, on the Dell laptop I did a couple weeks ago for my daughter, and the last two LTS releases have installed clean out-of-the-box on my Dad's desktop that I built for him from generic parts. Hmm, I should probably note that I often use the disk partitioning tools during installation rather than letting the install choose its own layout... but I didn't do that on the laptop.
I would agree with that last statement, but I always have to tweak every OS to get it to where I would consider it "smooth running". For my daughter and father, who only want to do web browsing and a few simple applications, I didn't do any tweaking. They are limited by their connection speed anyway. On my windows boxes, I tweak and tune for a week or more (mostly with Mark Russinovich's tools) before I get them where I want them.
Well, honestly I've spent six to eight hours a day at the command line for the last 30 years or so, using every kind of OS, so I'm not a representative sample of anything. I am vastly more productive with a cli, and I find the process of installing a windows driver to be insanely slow, tedious and repetitive. I can install a hundred drivers using a cli and only reboot once, but most of the times I've tried to install more than one driver at a time in Windows I've end up with a trashed system, so now I always reboot for each and every driver, which is super slow and boring.
It sounds like the big factor here is our relative experience. You are so accustomed to the stuff I find horrifying in a windows install that you didn't even think about it, and it never occurred to me that anyone would be bothered by having to use a command line because that's where I prefer to be (I use powershell in windows these days, and we are moving to no-GUI installs for our windows servers). We're both highly experienced in different realms, and consequently we find it aggravating to work where we are less efficient.
I mostly use linux to opt out of costly vendor upgrade cycles, not because I have any special devotion to the *nix paradigm. At work I use windows, OSX, HP-UX, Solaris... whatever they'll pay me for!
People do not want to install Linux. They want to buy a computing device and start doing things on it.
People do not care if it runs Windows, Mac, Android, Linux or Hurd. What they care about is if they are able to open the box and launch Facebook and Google.
The ONLY way to the Linux Desktop is by pre-installing it. All the rest is already there and much better than what WIndows has to offer.
All the major distributions already have an 'appstore' and have had it for years.
Android has shown that this is the case.
Even with a mulitybillion company, they can not get people to install a new version of Windows. What they ARE able to do is let people spend MORE money on a new computer.
Don't fight for your country, if your country does not fight for you.
You should get an account. The reason is that Word isn't designed for publishing. Word is just beginning to handle ligatures in English, it is far from handling them in complex languages like Arabic or Hindi. Office 2010 and 2013 have made huge strides in this regard. Word doesn't handle spacing between lines, letters and words entirely properly for readability. Certainly, kerning, tracking and spacing are screwed up. Here is a classic text only image of Word (left) vs. InDesign(right) http://www.thebookdesigner.com...
Take a look at the 3rd paragraph spacing. That's what's wrong with Word for text.