From: Kracked_P_P---webmaster <firstname.lastname@example.org>
Sent: Saturday, 1 June 2013, 20:04
Subject: Re: [libreoffice-users] Re: no answers to my question
Thanks for the links Girvin.
The whole point is not the specifics of the genealogy of the OSs that
can be supported, but it does support them and can be "easily" ported to
some others, as long as there are not any hardware issues like tablets.
MSO would never support such a diverse market, like LO does and could be
I have a cross-platform package that has specific downloads for:
Linux - deb and rpg
and maybe AIX, if I remember correctly
plus a Java based version.
The key is not needing to learn a different package for each of the
different hardware and OS combinations. That is a big thing for people
who use more than one OS. I use Ubuntu/Linux for my main system, with
dual booting laptops that have Ubuntu and Windows on them.
I choose OpenOffice, originally for the Windows and Linux cross platform
options, and then switched to LO when it first came out. I really did
not want to have two different packages for each productivity option
[for the most part]. LO, GIMP, Inkscape, VLC, and some others, are
installed on all my Ubuntu and Windows single or dual booting systems.
That way I do not have to worry which OS I am using at that time on the
document or graphics that I am working on for someone. No need to
switch systems or change to another boot on the laptops. I just have to
make that the data is on a disk partition [for laptops] that can be
accessed by both Windows and Ubuntu, or on a USB drive [flash or big
external] or on my network [if in range of my laptop when I am not in my
place but 10 floors down in the common areas of the building].
On 06/01/2013 02:27 PM, Girvin R. Herr wrote:
Tom Davies wrote:
Not all our devs are volunteers. Some are paid by various companies,
notably SUSE but also Redhat and others to work on LibreOffice. Such
companies might normally attempt to create their own "in house"
product but instead choose to collaborate on creating something shared.
Macs are based on Bsd, which in turn is unix-based. Gnu&Linux are
also unix-based. So Bsd and Gnu&Linux share the same parent but do
Just to keep the record straight, on Linux day #1, Linus Torvalds
based his Linux on Minix https://en.wikipedia.org/wiki/MINIX , which
in turn was based on Unix. I do believe the Minix disk filesystem is
still included with today's Linux. Yes, I just checked and it is (man
mkfs.minix). Then GNU had a bunch of *nix utilities, such as ls, tar,
gcc, etc. which Linus merged into Linux. Linux grew from that
grafting ever since. That is why Linux is referred to as GNU/Linux.
To be accurate, the term Linux only refers to the kernel operating
system, not the GNU tools. GNU/Linux is not Unix, but it is very close
and the philosophy is very similar. BSD and GNU/Linux are two
branches of the same Unix tree. Although a bit dated (the Linux
kernel is now up to 3.x), here is a nice chart I just found:
Clearing the air...
Apparently a lot of Raspberry Pis are used to play around with
hardware experimentation such as control's for various types of
robots. One chap put quite a few together to create a super-server.
So significant numbers are not being used as desktop machines at all.
Regards from Tom :)
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy