-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anyone have any tips or clues as to how i can fix this ? Note i am not
If all else fails, delete the ~/kde* stuff. This should set your panel
(and everything else..) back to default.
HTH
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why would I use tar, Whats wrong with 'cp'?
Its your choice in the end. Just conservative reasons.
For some time, cp was not able to handle ie sparse
files correctly.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
will i have to do something with lilo aswell?
nothing more than last time you installed lilo
PS: /boot sometimes needs to be bootable...
- --
0x87D205F6 hkp://pgp.mit.edu #198379 http://counter.li.org
You can't prove it won't happen...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
should I copy my /tmp directory over aswell?
You don't have to, no.
- --
0x87D205F6 hkp://pgp.mit.edu #198379 http://counter.li.org
You can't prove it won't happen...
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
