i just tried to upgrade from 2.0.2 to 2.0.3 (linux version on freebsd amd64) and it segfaults when i try to start it. i've reverted back to 2.0.2 for now, but there are some critical security fixes in 2.0.3, so this isn't a permanent solution... any ideas? i tried looking on openoffice.org for some sort of bug reporting system, but wasn't able to find one...
ms office is superior.
>>2
link to linux/amd64 version of ms office plz
>>1 Perhaps downloading the source and compiling a native FreeBSD version would be better.
>>2 Ummm yeah... sure... that why Word can't read it's own files, but OO.o can... That's why Word runs a single CPU flat strap whereas OO.o spreads its load across two CPUs. That's why Office still doesn't have an integrated PDF writer, but OO.o has since v1.1... That's why OO.o supports the OpenDocument formats, where MS Office doesn't... That's why OpenOffice Base can use just about any JDBC DB as a backend whereas Access is stuck with its own internal DB engine. That's why OO.o runs (theoretically) on any OS I choose... whereas MS Office only runs on Windows NT (5.x and above) or Mac OS X.
Hrmm... I think someone needs to have a look at the dictionary again, and find out what "superior" actually means... 'cos ^^ that don't look like "superior".
> Perhaps downloading the source and compiling a native FreeBSD version would be better.
http://wiki.services.openoffice.org/wiki/Porting_to_x86-64_(AMD64,_EM64T)
>>4
It's still ugly as hell and super slow. And the powerpoint equivalent is just pathetic.
> It's still ugly as hell and super slow. And the powerpoint equivalent is just pathetic.
try koffice, then. it looks nicer than ms office and is a lot faster. and kpresenter looks a lot nicer than the last version of powerpoint i used, but i haven't used kpresenter much at all and the last time i used powerpoint was 3 years ago...
if koffice had better support for ms office file formats, i wouldn't need openoffice at all...
>>6 Indeed... but you're saying MS Office is any faster/prettier? For starters, you should never judge a book by its cover. ;-) This said... I don't think Office and OpenOffice 2.0 look that different.
It is true, OO.o seems slower, but I've found putting Windows on a machine seems to make /everything/ seem slower. On a Linux machine, my custom build of OO.o (yes, it took 17.5 hours on a dual PIII 1GHz) runs very well.
This said... the only times I use one of these "office suites" is:
For my word processing needs, I use LyX <http://www.lyx.org>, and for my presentation needs, there's Latex-Beamer <http://latex-beamer.sf.net>. I find these do a much nicer job than anything Sun or Microsoft have come up with to date.
Two examples of Latex-Beamer in action:
> I've found putting Windows on a machine seems to make /everything/ seem slower
Once upon a time, I would have agreed with that. Nowadays I'm not so sure. Take my box at work: SuSE 10 takes two minutes to boot, while XP takes 40 seconds. The graphics performance between the two cannot be compared (it's less than half), and the XP UI is more responsive. XP also seems to have a tendency to trash less, which I found surprising.
While the underlying *nix kernels probably have a major performance edge (particularly linux), the GUI stuff in particular has gone the opposite direction the past few years. I can't say I'm happy about that.
Of course, once Vista comes out, it'll probably be the other way around. What a sad comment on the state of the industry.
Actually... I get the feeling that Windows Vista will be good for the Linux community, in so far as, Microsoft will end up forcing all the low-end GPU makers, which traditionally have been very willing to release specs and opensource drivers, to make more high-end graphic chipsets.
I feel this will have the flow-on effect of improving the graphic driver situation on platforms such as *BSD and Linux.
The ideal of course, would be for nVidia and ATI to both pull their fingers out, and make their driver GPL. If they keep their intellectual property out of the driver, and instead put that in firmware (which is perfectly acceptable, just look at the Intel 2100 wireless driver), there shouldn't be an issue. Kernel developers will be happy, since the driver doesn't infringe their copyright, users will be happy, since the driver will likely JustWork, because we'll be able to distribute compiled drivers (which is illegal at the moment).
At the moment though, the legal situation is a nasty one, there was a discussion on gentoo-core a while ago about this very topic. Gentoo isn't alone here, many distributions have been forced to re-think the packaging strategy for binary drivers.
Right now, the buck-passing that nVidia and ATI go on with, isn't helping anybody.