Where does Kmail store its filter settings?
Hi list, - I'm in the proces of xferring all my files and stuff to my new SuSE9.3 from SuSE9.2. - Where does Kmail store its filter settings? - I managed to get all my mail moved across, but I've got a ton of filters, so It'd really be nice :-) -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Open Source Academy Denmark +45 56964223 +45 2014 5551 ------------------------------
On Saturday 07 May 2005 5:37 pm, Verner Kjærsgaard wrote:
- Where does Kmail store its filter settings?
On my vintage KDE 3.1.4, the file that Kmail uses to store the filters and other settings is: $HOME/.kde/share/config/kmailrc HTH, Jorge
Lørdag 07 maj 2005 23:44 skrev Jorge Fábregas:
On Saturday 07 May 2005 5:37 pm, Verner Kjærsgaard wrote:
- Where does Kmail store its filter settings?
On my vintage KDE 3.1.4, the file that Kmail uses to store the filters and other settings is:
$HOME/.kde/share/config/kmailrc
HTH, Jorge
SOLVED! - the true power of Linux/SuSE and the Open Source Community! - thanks a lot! -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Open Source Academy Denmark +45 56964223 +45 2014 5551 ------------------------------
Verner Kjærsgaard wrote:
Lørdag 07 maj 2005 23:44 skrev Jorge Fábregas:
On Saturday 07 May 2005 5:37 pm, Verner Kjærsgaard wrote:
- Where does Kmail store its filter settings? On my vintage KDE 3.1.4, the file that Kmail uses to store the filters and other settings is:
$HOME/.kde/share/config/kmailrc
HTH, Jorge
SOLVED!
- the true power of Linux/SuSE and the Open Source Community! - thanks a lot!
That sounds like you don't have /home as a separate partition and that you pretty much nuked your entire setup (after taking a backup) for the upgrade. My setup is probably overly complicated, /usr /opt /var /boot and /home are all partitions which I backup at random times and before upgrades. With /var this is probably overkill (it could have been left in the root partition) but this setup has saved me several times. When upgrading to a new level, I also rescue /etc and hide its backup in the /home tree for a couple of months. The upgrade is then always done as an upgrade rather than a new install. -- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
Søndag 08 maj 2005 10:08 skrev Andrew Williams:
Verner Kjærsgaard wrote:
Lørdag 07 maj 2005 23:44 skrev Jorge Fábregas:
On Saturday 07 May 2005 5:37 pm, Verner Kjærsgaard wrote:
- Where does Kmail store its filter settings?
On my vintage KDE 3.1.4, the file that Kmail uses to store the filters and other settings is:
$HOME/.kde/share/config/kmailrc
HTH, Jorge
SOLVED!
- the true power of Linux/SuSE and the Open Source Community! - thanks a lot!
That sounds like you don't have /home as a separate partition and that you pretty much nuked your entire setup (after taking a backup) for the upgrade. My setup is probably overly complicated, /usr /opt /var /boot and /home are all partitions which I backup at random times and before upgrades. With /var this is probably overkill (it could have been left in the root partition) but this setup has saved me several times.
When upgrading to a new level, I also rescue /etc and hide its backup in the /home tree for a couple of months. The upgrade is then always done as an upgrade rather than a new install.
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
Hi list, - a small misunderstanding here, on my behalf. I did not upgrade, I bought a brand new disk, installed SuSE9.3 on the disk and copied and re-installed what was needed. Part of that proces was copying mails, adresses and bookmarks and more over. - this all went without a hitch. - This way, I still have my original disk at hand, if things go wrong, I'm still productive monday morning :-) - thank you for your comments, anyhow! -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard Open Source Academy Denmark +45 56964223 +45 2014 5551 ------------------------------
On 5/8/05, Andrew Williams
Verner Kjærsgaard wrote:
Lørdag 07 maj 2005 23:44 skrev Jorge Fábregas:
On Saturday 07 May 2005 5:37 pm, Verner Kjærsgaard wrote:
- Where does Kmail store its filter settings? On my vintage KDE 3.1.4, the file that Kmail uses to store the filters and other settings is:
$HOME/.kde/share/config/kmailrc
HTH, Jorge
SOLVED!
- the true power of Linux/SuSE and the Open Source Community! - thanks a lot!
That sounds like you don't have /home as a separate partition and that you pretty much nuked your entire setup (after taking a backup) for the upgrade. My setup is probably overly complicated, /usr /opt /var /boot and /home are all partitions which I backup at random times and before upgrades. With /var this is probably overkill (it could have been left in the root partition) but this setup has saved me several times.
When upgrading to a new level, I also rescue /etc and hide its backup in the /home tree for a couple of months. The upgrade is then always done as an upgrade rather than a new install.
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
I've just recently installed Suse 9.1 and am still learning. What are the purposes of the different directories (/usr /opt /var)? Why should they be kept on seperate partitions, and why should they be backed up individually? I know what /root and /home are for. If there is a webpage that outlines this out, I would appreciate a link. Also, are these directories the same across all versions of linux? I have a little experience with Fedora, but not much. Thanks. Dotan Cohen http://LyricsList.com/
On Sunday 08 May 2005 15:22, Dotan Cohen wrote:
On 5/8/05, Andrew Williams
wrote: Verner Kjærsgaard wrote:
Lørdag 07 maj 2005 23:44 skrev Jorge Fábregas:
On Saturday 07 May 2005 5:37 pm, Verner Kjærsgaard wrote:
- Where does Kmail store its filter settings?
On my vintage KDE 3.1.4, the file that Kmail uses to store the filters and other settings is:
$HOME/.kde/share/config/kmailrc
HTH, Jorge
SOLVED!
- the true power of Linux/SuSE and the Open Source Community! - thanks a lot!
That sounds like you don't have /home as a separate partition and that you pretty much nuked your entire setup (after taking a backup) for the upgrade. My setup is probably overly complicated, /usr /opt /var /boot and /home are all partitions which I backup at random times and before upgrades. With /var this is probably overkill (it could have been left in the root partition) but this setup has saved me several times.
When upgrading to a new level, I also rescue /etc and hide its backup in the /home tree for a couple of months. The upgrade is then always done as an upgrade rather than a new install.
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
I've just recently installed Suse 9.1 and am still learning. What are the purposes of the different directories (/usr /opt /var)? Why should they be kept on seperate partitions, and why should they be backed up individually? I know what /root and /home are for. If there is a webpage that outlines this out, I would appreciate a link. Also, are these directories the same across all versions of linux? I have a little experience with Fedora, but not much.
Thanks.
Dotan Cohen http://LyricsList.com/
Try reading the Filesystem Hierarchy Standard - it may help give you some background http://www.pathname.com/fhs/ regards Ian
Dotan Cohen wrote:
On 5/8/05, Andrew Williams
wrote: That sounds like you don't have /home as a separate partition and that you pretty much nuked your entire setup (after taking a backup) for the upgrade. My setup is probably overly complicated, /usr /opt /var /boot and /home are all partitions which I backup at random times and before upgrades. With /var this is probably overkill (it could have been left in the root partition) but this setup has saved me several times.
When upgrading to a new level, I also rescue /etc and hide its backup in the /home tree for a couple of months. The upgrade is then always done as an upgrade rather than a new install.
--
I've just recently installed Suse 9.1 and am still learning. What are the purposes of the different directories (/usr /opt /var)? Why should they be kept on seperate partitions, and why should they be backed up individually? I know what /root and /home are for. If there is a webpage that outlines this out, I would appreciate a link. Also, are these directories the same across all versions of linux? I have a little experience with Fedora, but not much.
Thanks.
Dotan Cohen http://LyricsList.com/
/root is root's home directory, but you knew that :-) Software that is absolutely essential to the running of the system (and libraries that are essential) are kept in /sbin (root stuff), /bin (other stuff) and /lib. Configuration stuff is kept in /etc. I believe you will die a horrible death if you take them out of the '/' partition although I have never tried it. /usr contains another /bin, /sbin and /lib (amongst other stuff), for software which is not absolutely essential to get the system up and running. If you make this a separate partition, it may be read-only and that is considered a 'good thing' from a security point of view. Making that partition read-only causes yast horrible problems when you are installing software. I don't know why they don't check for it and scream. The 'rpm' program should do that as well. /opt is for 'optional software' and the distinction between /opt and /usr is pretty artificial. It may also be read-only. This also screws yast. SuSE moved OpenOffice from /opt to /usr with 9.3 (I think, maybe it was 9.2). Anything under /opt could just as easily be under /usr and some other distributions may well put it there. /var contains data which can be pretty volatile. The only advantage I have ever found in making it a separate partition is that I can easily drop into Runlevel 1 and then move the contents to another partition if I feel the need. I had a major problem with reiserfs under SuSE 9.2 so I ended up backing /var up and then recreating the partition as xfs and reloading it. If I'm doing surgery like that to the '/' partition then I need to boot using knoppix or the SuSE install discs. As to making /home it's own partition, I *always* do that. If some upgrade goes really horribly wrong, you can nuke the rest of the system and still have your user data there. The only files that interest me under /root are a few scripts in /root/bin and I've never bothered giving them their own partition. I have no idea why /root is not /home/root but the reason will either be historical or security. Backups: You only need to back /usr and /opt (and /boot) up if you have installed/updated some software there. Since rpm keeps it's database in the /var tree, you need to back /var up as well after installing software. /, /var and /home (also) need backing up under 'normal' circumstances. I often don't bother with /var because the only data I really care about there is the rpm database. I am sure other people see this totally differently! -- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
On 5/8/05, Andrew Williams
Dotan Cohen wrote:
On 5/8/05, Andrew Williams
wrote: That sounds like you don't have /home as a separate partition and that you pretty much nuked your entire setup (after taking a backup) for the upgrade. My setup is probably overly complicated, /usr /opt /var /boot and /home are all partitions which I backup at random times and before upgrades. With /var this is probably overkill (it could have been left in the root partition) but this setup has saved me several times.
When upgrading to a new level, I also rescue /etc and hide its backup in the /home tree for a couple of months. The upgrade is then always done as an upgrade rather than a new install.
--
I've just recently installed Suse 9.1 and am still learning. What are the purposes of the different directories (/usr /opt /var)? Why should they be kept on seperate partitions, and why should they be backed up individually? I know what /root and /home are for. If there is a webpage that outlines this out, I would appreciate a link. Also, are these directories the same across all versions of linux? I have a little experience with Fedora, but not much.
Thanks.
Dotan Cohen http://LyricsList.com/
/root is root's home directory, but you knew that :-)
Software that is absolutely essential to the running of the system (and libraries that are essential) are kept in /sbin (root stuff), /bin (other stuff) and /lib. Configuration stuff is kept in /etc. I believe you will die a horrible death if you take them out of the '/' partition although I have never tried it.
/usr contains another /bin, /sbin and /lib (amongst other stuff), for software which is not absolutely essential to get the system up and running. If you make this a separate partition, it may be read-only and that is considered a 'good thing' from a security point of view. Making that partition read-only causes yast horrible problems when you are installing software. I don't know why they don't check for it and scream. The 'rpm' program should do that as well.
/opt is for 'optional software' and the distinction between /opt and /usr is pretty artificial. It may also be read-only. This also screws yast.
SuSE moved OpenOffice from /opt to /usr with 9.3 (I think, maybe it was 9.2). Anything under /opt could just as easily be under /usr and some other distributions may well put it there.
/var contains data which can be pretty volatile. The only advantage I have ever found in making it a separate partition is that I can easily drop into Runlevel 1 and then move the contents to another partition if I feel the need. I had a major problem with reiserfs under SuSE 9.2 so I ended up backing /var up and then recreating the partition as xfs and reloading it. If I'm doing surgery like that to the '/' partition then I need to boot using knoppix or the SuSE install discs.
As to making /home it's own partition, I *always* do that. If some upgrade goes really horribly wrong, you can nuke the rest of the system and still have your user data there. The only files that interest me under /root are a few scripts in /root/bin and I've never bothered giving them their own partition. I have no idea why /root is not /home/root but the reason will either be historical or security.
Backups: You only need to back /usr and /opt (and /boot) up if you have installed/updated some software there. Since rpm keeps it's database in the /var tree, you need to back /var up as well after installing software.
/, /var and /home (also) need backing up under 'normal' circumstances. I often don't bother with /var because the only data I really care about there is the rpm database.
I am sure other people see this totally differently!
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
Thanks for that info. I still have much to read about in Ianseeks link, but Andrew Williams post summed it up very nice so that I can at least have a basic idea of what's going on. As I understand it, the reason for putting the directories in different partitions is for backup purposes only. If I am running a home system, then I can put it all in one partition and back them up one at a time as I go along? Thanks all. Dotan Cohen http://Music-Lyriks.com/ http://Song-Lirics.com/
On Sunday 08 May 2005 22:03, Andrew Williams wrote:
/opt is for 'optional software' and the distinction between /opt and /usr is pretty artificial. It may also be read-only. This also screws yast.
/opt and /usr/local are the places where third party applications go, things you compile and/or install yourself. The distribution should never touch /use/local, while they may put things in /opt. It makes sense to put things in opt when you have large packages of software that belong together. For example KDE or gnome or openoffice.
/var contains data which can be pretty volatile. The only advantage I have ever found in making it a separate partition is that I can easily drop into Runlevel 1 and then move the contents to another partition if I feel the need.
A huge advantage with putting /var on its own partition is that it contains things which may grow very rapidly, such as logs. A system that runs out of disk space can develop serious problems. So if you have a program running amok and filling up the logs with rubbish, you don't ruin it for the rest of the system. You also mentioned that other partitions can be mounted read-only, in which case you have to have /var on a separate partition.
Am Montag, 9. Mai 2005 01:04 schrieb Anders Johansson:
On Sunday 08 May 2005 22:03, Andrew Williams wrote:
A huge advantage with putting /var on its own partition is that it contains things which may grow very rapidly, such as logs. A system that runs out of disk space can develop serious problems. So if you have a program running amok and filling up the logs with rubbish, you don't ruin it for the rest of the system.
This applies also for the home directory. Some weeks ago a hanging app produced some GB of error messages in my ~.X.err file. [...] X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 15 (X_QueryTree) Resource id in failed request: 0x1026845 Serial number of failed request: 26694932 Current serial number in output stream: 26694932 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 15 (X_QueryTree) Resource id in failed request: 0x1026845 Serial number of failed request: 26694933 Current serial number in output stream: 26694933 [...] etc. Regards Uwe -- Uwe Krieg; 10437 Berlin;
On 5/9/05, Anders Johansson
On Sunday 08 May 2005 22:03, Andrew Williams wrote:
/opt is for 'optional software' and the distinction between /opt and /usr is pretty artificial. It may also be read-only. This also screws yast.
/opt and /usr/local are the places where third party applications go, things you compile and/or install yourself. The distribution should never touch /use/local, while they may put things in /opt.
It makes sense to put things in opt when you have large packages of software that belong together. For example KDE or gnome or openoffice.
/var contains data which can be pretty volatile. The only advantage I have ever found in making it a separate partition is that I can easily drop into Runlevel 1 and then move the contents to another partition if I feel the need.
A huge advantage with putting /var on its own partition is that it contains things which may grow very rapidly, such as logs. A system that runs out of disk space can develop serious problems. So if you have a program running amok and filling up the logs with rubbish, you don't ruin it for the rest of the system.
You also mentioned that other partitions can be mounted read-only, in which case you have to have /var on a separate partition.
Very interesting. I think that I'm going to play around with the different partitions just to get a feel for it. I have 8 gigs allocated for linux- how much should each partition get? I think that for now I will only put /home on it's own partition, but it would be nice to know for the future what all the other directories require. Thank you everybody. Dotan Cohen http://LyricsList.com/ http://Music-Liriks.com/
Op zaterdag 14 mei 2005 08:51, schreef Dotan Cohen:
Very interesting. I think that I'm going to play around with the different partitions just to get a feel for it. I have 8 gigs allocated for linux- how much should each partition get? I think that for now I will only put /home on it's own partition, but it would be nice to know for the future what all the other directories require.
You can check for size yourself with: du -sh /var du -sh /home du -sh /opt du -sh /tmp etc -- Richard Bos Without a home the journey is endless
Richard Bos wrote:
Op zaterdag 14 mei 2005 08:51, schreef Dotan Cohen:
Very interesting. I think that I'm going to play around with the different partitions just to get a feel for it. I have 8 gigs allocated for linux- how much should each partition get? I think that for now I will only put /home on it's own partition, but it would be nice to know for the future what all the other directories require.
You can check for size yourself with: du -sh /var du -sh /home du -sh /opt du -sh /tmp
etc
I'm lazy. cd / du -s * (or 'du -sh *' to get a feel for what the figures mean) Another one I like when trying to see where the space went is: du -s * | sort -n Which has absolutely *nothing* to do with KDE :-) -- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
Søndag 08 maj 2005 16:22 skrev Dotan Cohen:
On 5/8/05, Andrew Williams
wrote: Verner Kjærsgaard wrote:
Lørdag 07 maj 2005 23:44 skrev Jorge Fábregas:
On Saturday 07 May 2005 5:37 pm, Verner Kjærsgaard wrote:
- Where does Kmail store its filter settings?
On my vintage KDE 3.1.4, the file that Kmail uses to store the filters and other settings is:
$HOME/.kde/share/config/kmailrc
HTH, Jorge
SOLVED!
- the true power of Linux/SuSE and the Open Source Community! - thanks a lot!
That sounds like you don't have /home as a separate partition and that you pretty much nuked your entire setup (after taking a backup) for the upgrade. My setup is probably overly complicated, /usr /opt /var /boot and /home are all partitions which I backup at random times and before upgrades. With /var this is probably overkill (it could have been left in the root partition) but this setup has saved me several times.
When upgrading to a new level, I also rescue /etc and hide its backup in the /home tree for a couple of months. The upgrade is then always done as an upgrade rather than a new install.
-- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
I've just recently installed Suse 9.1 and am still learning. What are the purposes of the different directories (/usr /opt /var)? Why should they be kept on seperate partitions, and why should they be backed up individually? I know what /root and /home are for. If there is a webpage that outlines this out, I would appreciate a link. Also, are these directories the same across all versions of linux? I have a little experience with Fedora, but not much.
Well you can get some ideas here related to squeezing some performance out of your system by having a closer look at this howto: http://www.tldp.org/HOWTO/Multi-Disk-HOWTO.html Especially this "table" gives you a few ideas: http://www.tldp.org/HOWTO/Multi-Disk-HOWTO-9.html Have fun (please read carefully there's many valuable tips here). This is especially true the bigger your systems is and the more harddrives you have ;-) Johan
Thanks.
Dotan Cohen http://LyricsList.com/
participants (9)
-
Anders Johansson
-
Andrew Williams
-
Dotan Cohen
-
ianseeks
-
Johan Nielsen
-
Jorge Fábregas
-
Richard Bos
-
Uwe Krieg
-
Verner Kjærsgaard