[kde-linux] upgrading to KDE 4.2.4
lars.koraeus at gmail.com
Sat Dec 5 14:59:29 UTC 2009
On Saturday 05 December 2009 21:29:17 Kevin Krammer wrote:
> On Saturday, 2009-12-05, Gmail wrote:
> > On Saturday 05 December 2009 03:16:23 you wrote:
> > > On Friday 04 December 2009 13:38:19 Gmail wrote:
> > > > > Better still, back up the whole of your /home/you directory to a
> > > > > usb pen-drive if at all possible. If you have space to spare, back
> > > > > up /etc as well.
> > > > >
> > > > > Anne
> > > >
> > > > A thing to wish for would be that KDE apps had a better separation of
> > > > data/documents a user creates and other support files.
> > > > Then it had been easy to just have data in a separate partition that
> > > > could be mounted in different systems and used by different
> > > > applications. As standard not with manual work as now.
> > > > Now we have all data in a /local and own apps/script in /usr/local.
> > > > Always there whatever system we install or boot.
> > >
> > > I'm sorry - you have totally lost me. /home/you contains your personal
> > > settings and data. That's all. And none of your data is elsewhere
> > > unless you have very deliberately caused it to be so . How you come to
> > > have data scattered around your system is a puzzle that only you can
> > > answer.
> > >
> > > Anne
> > No Ann I did not lost you.
> > My computers are probably a little different from what is expected. I
> > have several distribution/version root file systems as I have our
> > embedded root file systems we are working on. But I want the same data
> > whichever system I boot. Also I might move to another computer but I
> > still want my "home data" with me but not every "homes" configuration.
> Anne didn't suggest to take the whole /home tree but only the one for your
> user account.
> Basically /home/$USER
> It indeed contains all your data and config unless you have explicitly put
> some things elsewhere.
Yes, sorry I was very unclear here.
What I am after is that configurations belongs to a packet and a person on a
specific architecture/distro. But Data belongs to me as a user and only me and
should , hopefully, not be dependent on a specific application, version,
Just using the normalisation rules for database design. Each property has it
very specific place. These normalisation rules do very well also apply on a
directory tree. An ordinary hierarchical database structure.
However the /home is probably a mount point in those cases. It will be too
complicated if every user has he's own partition.
When an application think it is the one and only "owner" to "user" data one
should be worried.The application/packet should only own its application data
This is not a big issue as everything can be solved with links but suddenly
every one needs there own special links and I will sooner or later get lost.
I do not think this is any problem for a "normal" user but it is for me.
More information about the kde-linux