<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I wondered already a few days, what happened to Paul?<br>
<br>
Not that I have to complain much about Ubuntu, but curious as I am,
I will give it a try. Thanks for the share.<br>
<br>
Best,<br>
Rinus<br>
<br>
Op 20-09-11 14:25, Paul Verizzo schreef:
<blockquote cite="mid:4E78861F.7090209@paulv.net" type="cite">
<font size="+1"><font face="Helvetica, Arial, sans-serif">As loyal
readers here might recall, I’ve been playing with - no,
working with -
various Linux distros in order to run digiKam in its native
OS. (Is
that loyalty, or what? Many dozens of hours!) I’ve come to
some
finalizations, which I will summarize here:<br>
<br>
Oh, native OS for me is Windows XP Pro, Service Pack 3,
running on an
AMD 3800+ with 3GB (soon to be 5GB) RAM. I have my hard drive
broken
into two partitions, C which is the Windows, Virtual Box, and
dual boot
Wubi OS’s and supporting files, and D which is all of my
data. Why, I
hear you ask? A long ago experience of having data wiped in
an aborted
Checkdisk run. I’ve gotten used to this and it’s very safe
from
machine or human error. <br>
<br>
The problem for me, using two partitions, with
Ubuntu/Wubi/Mint Linux:
As designed, the installer is prevented from having, or using,
or
becoming a root user. That means no access to the drive the
Linux OS
is installed on, “C” or hda1 to those who insist. That has
been my
default database location, although my photos are on easily
accessed
D. For Windows users on Wubi, it appears you just can’t get
access to
your C drive without going through the annoyance of Secret
Instructions
and Terminal. Maybe someday when I need another challenge in
my life,
I’ll correct that.<br>
<br>
For Virtual Box, The Winner Is: PC Linux OS. I tried a lot of
distros,
maybe a dozen. Some would not install, several I aborted
because I
wasn’t confident that it wasn’t going to partition my C drive,
several
insisted on pretending that the live CD was installed after VB
installation and hence, not the subsequent OS. BZZZZZT!<br>
<br>
Standard KDE PCLOS went in w/o a problem (although like many
other
distros, my screen resolution required constant sliding
downward to see
the Forward type buttons during the installation), reboots w/o
a
problem, and with the Guest Additions installed, sees my C and
D
partitions without a problem. I have found the overall look
and feel
welcoming to this Windows user. Not too simplistic, not too
complex,
just right. Nice large screens and icons. Visually robust.<br>
<br>
So, I’ve been hanging around the PCLOS community, and I guess
“ease of
use” on a desktop is the priority of development. No server
edition.
Also, a “When its ready" philosophy, which leads to great
stability. I
also like the rolling distribution, just update via Synaptic
now and
then. The independent on line magazine is stunning in its
usefulness
and teaching. <br>
<br>
I like it well enough that I might re-re-partition my primary
drive for
Linux again, or run PCLOS (What an awkward name! Of course
it’s an
OS!) on a different hard drive. <br>
<br>
If you’ve not tried this distro and don’t feel you must
continue down
the loyalty path of whatever you are using, give it a whirl. <br>
<br>
</font></font>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Digikam-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/digikam-users">https://mail.kde.org/mailman/listinfo/digikam-users</a>
</pre>
</blockquote>
<br>
</body>
</html>