[opensuse] Exporting KMail folders etc, Revisited
I had begun a thread recently in which I tried to find a good way to carry over my KMail structure from v10.3-KDE3 to v11.1-KDE4, as-is (as closely as possible). This did not seem to be as easy and straightforward a process as I might have hoped. But in the meantime I have come to believe that KDE4 (at least in its present state) is not for me (at least in my own present state) and that I would be better off sticking with KDE3. It seems to me therefore that the most straightforward way to proceed is simply to carry over my home directory from the v10.3 installation to a new v11.1 installation. Because the intent is to retain the existing v10.3 installation on one HD, and put the new v11.1 on another one, my conception of how to do this safely is as follows. I would be exceedingly grateful for any comments that might show up potential pitfalls or misunderstandings. 1) I would set up clean root and home partitions for the new v11.1 using DFSee. 2) Working from the existing v10.3, I would install ext3 on the home partition and mount that partition v10.3. 3) As though I were backing up the v10.3 home partition, I simply copy it in toto to the partition newly made to be the v11.1 home partition. 4) Finally I install v11.1 on the root partition prepared for it, defining the newly populated partition as it /home, and instruct that this /home partition not be formatted. To me, this looks like the perfect way to proceed, and it should leave me with a new system very much like the old one, although there would no doubt be a few apps that need to be replaced. Is there any problem with this? Have I overlooked something? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-04-24 at 13:04 +0300, Stan Goodman wrote: ...
To me, this looks like the perfect way to proceed, and it should leave me with a new system very much like the old one, although there would no doubt be a few apps that need to be replaced. Is there any problem with this? Have I overlooked something?
It looks a good plan to me. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknxqEwACgkQtTMYHG2NR9VpqgCgi6p4eNMex3J+wZMLWigm5ibW LkgAn3zGHCxEnWRdx84o5onfFpCG1/b/ =xQzO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 24 April 2009 05:04:15 am Stan Goodman wrote: ...
2) Working from the existing v10.3, I would install ext3 on the home partition and mount that partition v10.3.
New created ext3 mounted on /home will mask existing files, so you want to mount it to /mnt or any other directory created for that purpose.
3) As though I were backing up the v10.3 home partition, I simply copy it in toto to the partition newly made to be the v11.1 home partition.
4) Finally I install v11.1 on the root partition prepared for it, defining the newly populated partition as it /home, and instruct that this /home partition not be formatted.
To me, this looks like the perfect way to proceed, and it should leave me with a new system very much like the old one, although there would no doubt be a few apps that need to be replaced. Is there any problem with this? Have I overlooked something?
From safety point of view it is OK. From usage point it is a hassle. All your communication and bookmarks will be obsolete very soon, so if you need to go back you will miss all new stuff. Although, I don't think that you will go back without major breakage in anew system. In that case some obsolete communication stuff is of no concern anyway. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 19:13:26 on Friday Friday 24 April 2009, "Rajko M." <rmatov101@charter.net> wrote:
On Friday 24 April 2009 05:04:15 am Stan Goodman wrote: ...
2) Working from the existing v10.3, I would install ext3 on the home partition and mount that partition v10.3.
It is possible that I didn't write sufficiently clearly, and that there has been a misunderstanding. Maybe the misunderstanding is mine, in which case I hope you will help me resolve it.
New created ext3 mounted on /home will mask existing files, so you want to mount it to /mnt or any other directory created for that purpose.
I don't think there is anything to mask. To be clear, the existing v10.3 is on Disk 1, and the v11.1 installation will be on Disk 2, which initially has no Linux on it at all. I prepare partitions on Disk 2 using DFSee, and put ext3 on the one destined to be for /home; at this point, there are no files anywhere on Disk 2. Then I copy the entirety of partition 10.3/home to the still empty partition 11.1/home. If I later wish to return to using v10.3, its home directory is intact, and I have lost nothing.
3) As though I were backing up the v10.3 home partition, I simply copy it in toto to the partition newly made to be the v11.1 home partition.
4) Finally I install v11.1 on the root partition prepared for it, defining the newly populated partition as it /home, and instruct that this /home partition not be formatted.
To me, this looks like the perfect way to proceed, and it should leave me with a new system very much like the old one, although there would no doubt be a few apps that need to be replaced. Is there any problem with this? Have I overlooked something?
From safety point of view it is OK.
From usage point it is a hassle.
In what way is it a hassle? What could I do that would be simpler, and would still leave me the return path if I wish to use it later?
All your communication and bookmarks will be obsolete very soon, so if you need to go back you will miss all new stuff.
What new stuff? I am moving from KDE3 to KDE3. If I later want to move back, it can only be because I was less than happy with "new stuff". I keep browser bookmarks synchronized among all machines and OSes anyway; I keep emails backed up in per month files on CDs.
Although, I don't think that you will go back without major breakage in anew system. In that case some obsolete communication stuff is of no concern anyway.
Again, I think you missed the fact that the two installations are separate and independent on distinct partitions. An alternative would have been NOT to copy the /home partition, but to use the same partition in common by the two OSes. I am trying to prevent the kind of breakage/corruption/confusion that you are warning me about. If I have mistaken your intent, please tell me. I have no desire to make a mess of this. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 24 April 2009 12:17:17 pm Stan Goodman wrote:
At 19:13:26 on Friday Friday 24 April 2009, "Rajko M."
<rmatov101@charter.net> wrote:
On Friday 24 April 2009 05:04:15 am Stan Goodman wrote: ...
2) Working from the existing v10.3, I would install ext3 on the home partition and mount that partition v10.3.
It is possible that I didn't write sufficiently clearly, and that there has been a misunderstanding. Maybe the misunderstanding is mine, in which case I hope you will help me resolve it.
New created ext3 mounted on /home will mask existing files, so you want to mount it to /mnt or any other directory created for that purpose.
I don't think there is anything to mask. To be clear, the existing v10.3 is on Disk 1, and the v11.1 installation will be on Disk 2, which initially has no Linux on it at all. I prepare partitions on Disk 2 using DFSee, and put ext3 on the one destined to be for /home; at this point, there are no files anywhere on Disk 2. Then I copy the entirety of partition 10.3/home to the still empty partition 11.1/home. If I later wish to return to using v10.3, its home directory is intact, and I have lost nothing.
It will work if you use dd program and you are logged in as root, and nothing else, so 'init 1' would be good idea before you start. The dd doesn't need mounted partition and you don't want anything to change 10.3 /home while you are copying it, so working from runlevel 1 (single user) will suffice. Example 1: 10.3/home = /dev/sda3 11.1/home = /dev/sdb3 Size of /dev/sda3 = /dev/sdb3 init 1 (Give root password) dd if=/dev/sda3 of=dev/sdb3 will safely copy sda3 to sdb3 . Potential problem is that dd doesn't check much ahead of transfer, if sdb3 is just a sector shorter then sda3, the result can be error message, or overwritten begin of the next partition. I can't tell which will be the case, although I would expect error message, and partition most probably in tact, ie. usable. The same is problem in case of any typo, it will diligently overwrite target without questions. In case that you want to copy files, which is safer, it is good to be in runlevel 1, again, but you have to mount 11.1/home somewhere in 10.3 file system. Example 2: (partitions as in exmple 1) init 1 (Give root password) mount /dev/sdb3 /mnt cp /home /mnt will do the same without complains if sdb3 is just a bit shorter then sda3, with additional benefit of doing some kind of defragmentation, as it will not copy sector by sector, like dd, but file by file. Preserving some of original file attributes can be of interest. You can check 'man cp' for command line options. Ownership of files in this case is not important, as Installation program will adjust that when you create user with the same name as the old one. If you give the new user name then copied /home/<old_user_name> directory will belong to user known only as 1000, by numeric ID. I can't recall how that translates in the practice, is new user numeric ID 1001, or it will be 1000 as the old one creating potential for problems, so better is to be exact when creating new user. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 21:21:51 on Friday Friday 24 April 2009, "Rajko M." <rmatov101@charter.net> wrote:
On Friday 24 April 2009 12:17:17 pm Stan Goodman wrote:
At 19:13:26 on Friday Friday 24 April 2009, "Rajko M."
<rmatov101@charter.net> wrote:
On Friday 24 April 2009 05:04:15 am Stan Goodman wrote: ...
2) Working from the existing v10.3, I would install ext3 on the home partition and mount that partition v10.3.
It is possible that I didn't write sufficiently clearly, and that there has been a misunderstanding. Maybe the misunderstanding is mine, in which case I hope you will help me resolve it.
New created ext3 mounted on /home will mask existing files, so you want to mount it to /mnt or any other directory created for that purpose.
I don't think there is anything to mask. To be clear, the existing v10.3 is on Disk 1, and the v11.1 installation will be on Disk 2, which initially has no Linux on it at all. I prepare partitions on Disk 2 using DFSee, and put ext3 on the one destined to be for /home; at this point, there are no files anywhere on Disk 2. Then I copy the entirety of partition 10.3/home to the still empty partition 11.1/home. If I later wish to return to using v10.3, its home directory is intact, and I have lost nothing.
It will work if you use dd program and you are logged in as root, and nothing else, so 'init 1' would be good idea before you start. The dd doesn't need mounted partition and you don't want anything to change 10.3 /home while you are copying it, so working from runlevel 1 (single user) will suffice.
I had thought of copying files, as in your Example 2 below. But your Example 1 looks even simpler.
Example 1: 10.3/home = /dev/sda3 11.1/home = /dev/sdb3 Size of /dev/sda3 = /dev/sdb3
init 1 (Give root password) dd if=/dev/sda3 of=dev/sdb3
will safely copy sda3 to sdb3 .
Potential problem is that dd doesn't check much ahead of transfer, if sdb3 is just a sector shorter then sda3, the result can be error message, or overwritten begin of the next partition. I can't tell which will be the case, although I would expect error message, and partition most probably in tact, ie. usable. The same is problem in case of any typo, it will diligently overwrite target without questions.
The v11.1/home partition is set to be larger than the v10.3/home.
In case that you want to copy files, which is safer, it is good to be in runlevel 1, again, but you have to mount 11.1/home somewhere in 10.3 file system.
Thank you for the warning about runlevel 1; I would not have thought of it.
Example 2: (partitions as in exmple 1)
init 1 (Give root password) mount /dev/sdb3 /mnt cp /home /mnt
will do the same without complains if sdb3 is just a bit shorter then sda3, with additional benefit of doing some kind of defragmentation, as it will not copy sector by sector, like dd, but file by file.
Preserving some of original file attributes can be of interest. You can check 'man cp' for command line options.
I had already done that. I'm relieved to see that I have been thinking in the right direction, at least in this instance.
Ownership of files in this case is not important, as Installation program will adjust that when you create user with the same name as the old one. If you give the new user name then copied /home/<old_user_name> directory will belong to user known only as 1000, by numeric ID. I can't recall how that translates in the practice, is new user numeric ID 1001, or it will be 1000 as the old one creating potential for problems, so better is to be exact when creating new user.
The new user name will be my name, just as the old user name. I was sure I would miss some of the finer points, and am grateful that you have clarified them. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-04-24 at 22:04 +0300, Stan Goodman wrote: ...
Potential problem is that dd doesn't check much ahead of transfer, if sdb3 is just a sector shorter then sda3, the result can be error message, or overwritten begin of the next partition. I can't tell which will be the case, although I would expect error message, and partition most probably in tact, ie. usable. The same is problem in case of any typo, it will diligently overwrite target without questions.
The v11.1/home partition is set to be larger than the v10.3/home.
Notice that if you dd a partition to another, and say, source is 1 GiB, and destination is, say, 2 GiB, the end result is a filesystem that "thinks" it has only 1 GiB and wastes the other 1 GiB. If the situation is the reverse, dd will stop at 1 GiB (1), but the resulting filesystem will be broken, because it thinks it has 2 GiB. As you are copying files, you should be better using a file copy tool, like rsync. Or even midnight commander. Or you could use clonezilla. (1) "dd if=/dev/sda3 of=dev/sdb3" knows about the size of destination and does not overwrite a partition. Or rather, the kernel will not allow writing past the end of the destination partition. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknzAqMACgkQtTMYHG2NR9XfngCdHI2PSVvYkq7RlB6TXjwraGdz rRsAnR+bL2VBa6nxwdkI5Z9RXYGOEajV =BigT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 15:31:29 on Saturday Saturday 25 April 2009, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Friday, 2009-04-24 at 22:04 +0300, Stan Goodman wrote:
...
Potential problem is that dd doesn't check much ahead of transfer, if sdb3 is just a sector shorter then sda3, the result can be error message, or overwritten begin of the next partition. I can't tell which will be the case, although I would expect error message, and partition most probably in tact, ie. usable. The same is problem in case of any typo, it will diligently overwrite target without questions.
The v11.1/home partition is set to be larger than the v10.3/home.
Notice that if you dd a partition to another, and say, source is 1 GiB, and destination is, say, 2 GiB, the end result is a filesystem that "thinks" it has only 1 GiB and wastes the other 1 GiB.
In other words, it ignores the file system that was there before the copying began, and formats according to whatever is on the source partition? And stops when the copying is complete, leaving the rest unformatted? Very bad, as I am thinking of enlarging the /home partition.
If the situation is the reverse, dd will stop at 1 GiB (1), but the resulting filesystem will be broken, because it thinks it has 2 GiB.
=;-/8
As you are copying files, you should be better using a file copy tool, like rsync. Or even midnight commander. Or you could use clonezilla.
Why is any one of these better than the simple cp, which knows very well how to copy files? Thanks... -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 25 April 2009 19:32:14, Stan Goodman wrote:
As you are copying files, you should be better using a file copy tool, like rsync. Or even midnight commander. Or you could use clonezilla.
Why is any one of these better than the simple cp, which knows very well how to copy files?
rsync will also keep all file attributes (owner etc.) and links correct, while cp will copy a file when there is only a link (as much as I know). regards, Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 21:13:35 on Saturday Saturday 25 April 2009, Daniel Bauer <linux@daniel-bauer.com> wrote:
On Saturday 25 April 2009 19:32:14, Stan Goodman wrote:
As you are copying files, you should be better using a file copy tool, like rsync. Or even midnight commander. Or you could use clonezilla.
Why is any one of these better than the simple cp, which knows very well how to copy files?
rsync will also keep all file attributes (owner etc.) and links correct, while cp will copy a file when there is only a link (as much as I know).
regards, Daniel
Thanks. Actually, as I read the "help" file for rsync, you have to tell it what to do with links, out of a large repertoire of possibilities. I wouldn't want to copy links anyway, in the present case: a file that's far enough away that one would want to link to it is apt not to be in the /home directory at all. But rsync knows how to deal with that too. I have to study this help file thoroughly, as well as the man page. The cp command, BTW, also has a way to preserve file attributes. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-04-25 at 22:13 +0300, Stan Goodman wrote:
At 21:13:35 on Saturday Saturday 25 April 2009, Daniel Bauer <> wrote:
On Saturday 25 April 2009 19:32:14, Stan Goodman wrote:
Why is any one of these better than the simple cp, which knows very well how to copy files?
rsync will also keep all file attributes (owner etc.) and links correct, while cp will copy a file when there is only a link (as much as I know).
Yes, that's correct. But you can give the "-a" parameter to "cp" and it will keep the attributes as much as possible. Also rsync is optimized for a massive (backup) copy, and even better if you use it for repeated copies, ie, for a backup, each day for example. It is not the current case, but, if for example, you have to halt the process, on restart it will skip the already copied files, and copy only those new or modified. It can also be told to delete files on the destination that do not exist any longer on the source.
Thanks. Actually, as I read the "help" file for rsync, you have to tell it what to do with links, out of a large repertoire of possibilities. I wouldn't want to copy links anyway, in the present case: a file that's far enough away that one would want to link to it is apt not to be in the /home directory at all. But rsync knows how to deal with that too.
Ii use this set of options: - --archive --acls --xattrs --hard-links --del --stats --human-readable
I have to study this help file thoroughly, as well as the man page.
Notice that there is a difference with having a "/" or not at the end of the source or dest path given to rsync. Try. I never remember the difference O:-)
The cp command, BTW, also has a way to preserve file attributes.
Right. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknzY4cACgkQtTMYHG2NR9VT6wCdGnhhXiYLr5+04FGVsZ5W+jsh UTQAn0ayFStWS1jXedYA8og0Fncn0SLW =HmjW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 25 April 2009 12:32:14 pm Stan Goodman wrote:
At 15:31:29 on Saturday Saturday 25 April 2009, "Carlos E. R." ...
Notice that if you dd a partition to another, and say, source is 1 GiB, and destination is, say, 2 GiB, the end result is a filesystem that "thinks" it has only 1 GiB and wastes the other 1 GiB.
In other words, it ignores the file system that was there before the copying began, and formats according to whatever is on the source partition? And stops when the copying is complete, leaving the rest unformatted? Very bad, as I am thinking of enlarging the /home partition.
If the situation is the reverse, dd will stop at 1 GiB (1), but the resulting filesystem will be broken, because it thinks it has 2 GiB.
=;-/8
In both cases dd simply copies input sector by sector, byte by byte, to output, whatever that is file, or another device. It will create exact copy of source partition. It has no idea about formatting, as that is above level dd works. The file system idea of own size is possible to change and avoid space waste if partition is larger, or file system driver attempts to write beyond partition boundary. As file system driver is part of the kernel, it can happen that it can write over next partition on the disk and spoil the joy.
As you are copying files, you should be better using a file copy tool, like rsync. Or even midnight commander. Or you could use clonezilla.
Why is any one of these better than the simple cp, which knows very well how to copy files?
I used cp to copy whole systems from one place to another, and only problem happened when it went from reiserfs to ext3. Usually I would use Midnight Commander from another installation, or Live CD. If you have 1 GB it should be more then enough, as live system will take 2-3 hundred MB, and the rest can be used to copy files. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-04-25 at 14:11 -0500, Rajko M. wrote:
The file system idea of own size is possible to change and avoid space waste if partition is larger, or file system driver attempts to write beyond partition boundary. As file system driver is part of the kernel, it can happen that it can write over next partition on the disk and spoil the joy.
When a partition is specified as source or destination, it will not overwrite past the end. It may try, but the kernel will not allow it. I don't remember the exact message it gives at that point. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknzZGIACgkQtTMYHG2NR9XybgCeI1zWygogoy2ACuVDbX5z9JTm GCkAnR+zZcS4msFauNqnwAv83dq3pyBN =Vm24 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-04-25 at 20:32 +0300, Stan Goodman wrote:
Notice that if you dd a partition to another, and say, source is 1 GiB, and destination is, say, 2 GiB, the end result is a filesystem that "thinks" it has only 1 GiB and wastes the other 1 GiB.
In other words, it ignores the file system that was there before the copying began, and formats according to whatever is on the source partition? And stops when the copying is complete, leaving the rest unformatted? Very bad, as I am thinking of enlarging the /home partition.
That's correct. Notice that, even then, it is possible to resize the filesystem, using whatever tools that filesystem has (it is different for xfs, reiserfs or ext3). But why go to that hassle, when it is easier to simply copy files? You can also take the chance to change the filesystem type if you like to.
Or you could use clonezilla.
Why is any one of these better than the simple cp, which knows very well how to copy files?
I answered that already, but while we are thinking, clonezilla is specifically designed for this task. I haven't tried it personally, but I think they have a live CD too. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknzZbgACgkQtTMYHG2NR9WQmACgiXNEzaub6UqqTyLoPx3wVksq +SMAn0IZy7xz0r2jLo5FUocQ45PL4jFN =aIIl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 22:34:14 on Saturday Saturday 25 April 2009, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Saturday, 2009-04-25 at 20:32 +0300, Stan Goodman wrote:
-----snip all----- I elected to use Midnight Commander, which has a UI that I recognize (but apparently imperfectly) from elsewhere. In principle, the operation preceded like duck soup, except for my imperfect recollection. As follows: I did everything from a maintenance partition that I keep on the machine for purposes like this when it seems wise not to operate from a partition that I am trying to change. This is an openSuSE v10 on sda8. 1) I formatted the target partition (destined to be v11.1 /home), which is sdb7, to ext3. (sda7 is the source partition to be copied to sdb7). 2) I made two subdirectories in the maintenance machine, called /mnt/homeSource and /mnt/homeTarget, mounted sda7 and sdb7 to them respectively. 3) I loaded Midnight Commander, and but the sda7 in the left panel, sdb7 in the right. I can see that what is iin each is exactly what should be there. I make the left panel (the source) ACTIVE. Right here my memory betrays me. I remembered that pressing F5 would copy the left (active) panel to the right panel, but 'tain't so. What happened is that the copy took place to the /home directory of the the maintenance machine, that was supposed to be outside the game altogether. File managers of the commander type are, unfortunately, so ubiquitous that everyone is assumed to now instinctively how to use them, and developers do not trouble to write documentation for them. I do not find anything helpful through Google. Please remind me how to perform the required copy from one panel to the other. I am embarrassed to have to ask this question. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Stan Goodman <stan.goodman@hashkedim.com> [04-27-09 12:27]:
3) I loaded Midnight Commander, and but the sda7 in the left panel, sdb7 in the right. I can see that what is iin each is exactly what should be there. I make the left panel (the source) ACTIVE.
Right here my memory betrays me. I remembered that pressing F5 would copy the left (active) panel to the right panel, but 'tain't so.
Yes, not quite. F5 copies what is highlighted or selected to the opposite panel.
What happened is that the copy took place to the /home directory of the the maintenance machine, that was supposed to be outside the game altogether. File managers of the commander type are, unfortunately, so ubiquitous that everyone is assumed to now instinctively how to use them, and developers do not trouble to write documentation for them. I do not find anything helpful through Google.
Please remind me how to perform the required copy from one panel to the other. I am embarrassed to have to ask this question.
Select/highlight the highest directory and F5 will copy that to the opposite panel or where you designate in the popup. btw, there is help in mc, normally assigned to F1. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 27 April 2009 11:26:21 am Stan Goodman wrote:
At 22:34:14 on Saturday Saturday 25 April 2009, "Carlos E. R."
<robin.listas@telefonica.net> wrote:
On Saturday, 2009-04-25 at 20:32 +0300, Stan Goodman wrote:
-----snip all-----
I elected to use Midnight Commander, which has a UI that I recognize (but apparently imperfectly) from elsewhere. In principle, the operation preceded like duck soup, except for my imperfect recollection. As follows:
I did everything from a maintenance partition that I keep on the machine for purposes like this when it seems wise not to operate from a partition that I am trying to change. This is an openSuSE v10 on sda8.
1) I formatted the target partition (destined to be v11.1 /home), which is sdb7, to ext3. (sda7 is the source partition to be copied to sdb7).
2) I made two subdirectories in the maintenance machine, called /mnt/homeSource and /mnt/homeTarget, mounted sda7 and sdb7 to them respectively.
3) I loaded Midnight Commander, and but the sda7 in the left panel, sdb7 in the right. I can see that what is iin each is exactly what should be there. I make the left panel (the source) ACTIVE.
Right here my memory betrays me. I remembered that pressing F5 would copy the left (active) panel to the right panel, but 'tain't so. What happened is that the copy took place to the /home directory of the the maintenance machine, that was supposed to be outside the game altogether. File managers of the commander type are, unfortunately, so ubiquitous that everyone is assumed to now instinctively how to use them, and developers do not trouble to write documentation for them.
F1 is not up to today's standards, but it is still good help.
I do not find anything helpful through Google.
Not even http://en.opensuse.org/Midnight_Commander http://en.opensuse.org/Midnight_Commander/Tips :-) I recommend to use Lynx Like Motion. It is not enabled by default, and IMHO it is one of things that make mc my file manager of choice for all operations except those that benefit from image preview. Basically only multimedia files browsing is what I'm doing using Dolphin. The only assumption, after years of Midnight Commander use, is that your destination panel was /home on sda8. F5 never did unexpected copy. It was always copy from active half to inactive. Though, I did mess source and target directories not once. The most recent was backup of old home, where I moved around picking files, checked something in new home and forget to go back to old, so continued "backup" was from the new one.
Please remind me how to perform the required copy from one panel to the other. I am embarrassed to have to ask this question.
I can only advice to check twice where you are. It is showed at the top of each of the panels, which is not always useful for long paths, as you can see only the last part, but the command line at the bottom is longer and most of the time it has whole path. Switching with TAB key between panels you can check both. HTH -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 20:29:16 on Monday Monday 27 April 2009, "Rajko M." <rmatov101@charter.net> wrote:
On Monday 27 April 2009 11:26:21 am Stan Goodman wrote:
At 22:34:14 on Saturday Saturday 25 April 2009, "Carlos E. R."
<robin.listas@telefonica.net> wrote:
On Saturday, 2009-04-25 at 20:32 +0300, Stan Goodman wrote:
-----snip all-----
I elected to use Midnight Commander, which has a UI that I recognize (but apparently imperfectly) from elsewhere. In principle, the operation preceded like duck soup, except for my imperfect recollection. As follows:
I did everything from a maintenance partition that I keep on the machine for purposes like this when it seems wise not to operate from a partition that I am trying to change. This is an openSuSE v10 on sda8.
1) I formatted the target partition (destined to be v11.1 /home), which is sdb7, to ext3. (sda7 is the source partition to be copied to sdb7).
2) I made two subdirectories in the maintenance machine, called /mnt/homeSource and /mnt/homeTarget, mounted sda7 and sdb7 to them respectively.
3) I loaded Midnight Commander, and but the sda7 in the left panel, sdb7 in the right. I can see that what is iin each is exactly what should be there. I make the left panel (the source) ACTIVE.
Right here my memory betrays me. I remembered that pressing F5 would copy the left (active) panel to the right panel, but 'tain't so. What happened is that the copy took place to the /home directory of the the maintenance machine, that was supposed to be outside the game altogether. File managers of the commander type are, unfortunately, so ubiquitous that everyone is assumed to now instinctively how to use them, and developers do not trouble to write documentation for them.
F1 is not up to today's standards, but it is still good help.
I did read the F1 Help in its entirety. It too tells me that F5 should copy from left-panel selected item to the right panel. But that is not what happened. In the left panel, I navigated to /mnt/homeSource, and I saw there only one item, "home". I selected this item. In the right panel, I navigated to /mnt/homeTarget, which was empty (since I had just formatted that partition with mkfs.ext3), so there was nothing to select. From there, there was nothing to do but press F5. Then I sat and watched the previously almost empty desktop of the maintenance OS fill up with what I knew to be on the Source desktop. I am not arguing that I did everything right; I am sure that I didn't. But I am trying to identify what it was that I did wrong, and I don't see it. I'll run through the whole operation again tomorrow.
I do not find anything helpful through Google.
Not even http://en.opensuse.org/Midnight_Commander http://en.opensuse.org/Midnight_Commander/Tips
:-)
I recommend to use Lynx Like Motion.
It is not enabled by default, and IMHO it is one of things that make mc my file manager of choice for all operations except those that benefit from image preview. Basically only multimedia files browsing is what I'm doing using Dolphin.
The only assumption, after years of Midnight Commander use, is that your destination panel was /home on sda8.
F5 never did unexpected copy. It was always copy from active half to inactive.
Though, I did mess source and target directories not once. The most recent was backup of old home, where I moved around picking files, checked something in new home and forget to go back to old, so continued "backup" was from the new one.
Please remind me how to perform the required copy from one panel to the other. I am embarrassed to have to ask this question.
I can only advice to check twice where you are. It is showed at the top of each of the panels, which is not always useful for long paths, as you can see only the last part, but the command line at the bottom is longer and most of the time it has whole path. Switching with TAB key between panels you can check both.
I haven't used the command line at the bottom; I don't think it would be useful for the simple operation I am trying to do. Until now, all I have seen down there is "Hint: ...."
HTH -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 27 April 2009 01:34:12 pm Stan Goodman wrote:
I am not arguing that I did everything right; I am sure that I didn't. But I am trying to identify what it was that I did wrong, and I don't see it.
You previous post was clear, I just wanted to assure you that F5 has no bugs, to help you focus on other possible reasons. I mentioned my No.1 problem is and was setting target panel to wrong directory. I did that 2-3 days ago, and noticed that last night when I needed backup. Luckily, I didn't remove original. It could be that something went wrong prior to using mc, but you are the only person that can, going trough bash history, find out what happened.
I'll run through the whole operation again tomorrow.
-- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 22:09:20 on Monday Monday 27 April 2009, "Rajko M." <rmatov101@charter.net> wrote:
On Monday 27 April 2009 01:34:12 pm Stan Goodman wrote:
I am not arguing that I did everything right; I am sure that I didn't. But I am trying to identify what it was that I did wrong, and I don't see it.
You previous post was clear, I just wanted to assure you that F5 has no bugs, to help you focus on other possible reasons.
I mentioned my No.1 problem is and was setting target panel to wrong directory. I did that 2-3 days ago, and noticed that last night when I needed backup. Luckily, I didn't remove original.
It could be that something went wrong prior to using mc, but you are the only person that can, going trough bash history, find out what happened.
I'll run through the whole operation again tomorrow.
Actually, I have repeated the copy operation already, and have located my earlier error, which (like most errors) was the result of not paying close attention. I have also observed the results of my first copy operation (which was a good one, except that it ended in the wrong place). I see that on the Desktop, icons are present for the files that were there, some of them JPEGs for example, but clicking on them shows that the system doesn't know how to open them; the associations didn't make it across the copying. Where does that need to be fixed? So far, I see only trivial things otherwise that failed to copy. For example, even my second Panel made it, even fully populated. But the first panel (the usual one with the chameleon) lost my six-desktop set, and what is there is only the default two-desktop set. Trivial, as I say, but it surprised me. Tomorrow I will try to see what apps succeeded and which did not. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 22:09:20 on Monday Monday 27 April 2009, "Rajko M." <rmatov101@charter.net> wrote: I have finished installing openSuSE v11.1, after using dd to clone the /home partition from the v10.3 installation. All went well, and the result looks and feels like the original. I had only to configure the network, and have received and sent email messages and used the browser. What doesn't work is the automatic update facility. When I click on the orange triangle that tells me I have upgrades, I get an error message as follows: ***** PackageKit Error no-network. Cannot refresh cache whilst offline. ***** "Whilst"? But I am not ofline. What prevents this facility from working? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 29 April 2009 05:28:29 am Stan Goodman wrote:
At 22:09:20 on Monday Monday 27 April 2009, "Rajko M." <rmatov101@charter.net> wrote:
I have finished installing openSuSE v11.1, after using dd to clone the /home partition from the v10.3 installation. All went well, and the result looks and feels like the original. I had only to configure the network, and have received and sent email messages and used the browser.
What doesn't work is the automatic update facility. When I click on the orange triangle that tells me I have upgrades, I get an error message as follows:
***** PackageKit Error no-network. Cannot refresh cache whilst offline. *****
"Whilst"?
But I am not ofline. What prevents this facility from working?
Network settings? Run YOU (YaST Online Update) manually from YaST control center. I would go and check can I browse: http://download.opensuse.org/ specially http://download.opensuse.org/update If still nothing can be deducted disable all online repositories, drop DVD in the drive, install Wireshark, run it and then try to update. Output is verbose, but there is no chance not to find out what is going wrong. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 05:46:59 on Thursday Thursday 30 April 2009, "Rajko M." <rmatov101@charter.net> wrote:
On Wednesday 29 April 2009 05:28:29 am Stan Goodman wrote:
At 22:09:20 on Monday Monday 27 April 2009, "Rajko M." <rmatov101@charter.net> wrote:
I have finished installing openSuSE v11.1, after using dd to clone the /home partition from the v10.3 installation. All went well, and the result looks and feels like the original. I had only to configure the network, and have received and sent email messages and used the browser.
What doesn't work is the automatic update facility. When I click on the orange triangle that tells me I have upgrades, I get an error message as follows:
***** PackageKit Error no-network. Cannot refresh cache whilst offline. *****
"Whilst"?
But I am not ofline. What prevents this facility from working?
Network settings?
Run YOU (YaST Online Update) manually from YaST control center.
I did as follows: In YaST > Software > Online Update, I selected "yast2-network", and that ran. I didn't see that it provided any results of interest.
I would go and check can I browse: http://download.opensuse.org/ specially http://download.opensuse.org/update
I can load both these URLs and navigate the sites. I assume that is what you are asking.
If still nothing can be deducted disable all online repositories, drop DVD in the drive, install Wireshark, run it and then try to update. Output is verbose, but there is no chance not to find out what is going wrong.
I have disabled all the repositories and installed Wireshark. I then called it to bring up its UI, but did nothing within it, because I am not clear what I should do. With the program running, I clicked on the updates icon (which has changed since yesterday from being an orange triangle to being a dark square with a white downward-pointing arrow in its center). This brings up a dialog box telling me that I have two optional updates waiting (only two?); it has the expected "Install" button for confirmation, but it is greyed out, so there is nothing to click. Meantime, nothing has happened either in the Wireshark window or in the terminal from which I called it. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 30 April 2009 08:03:31 am Stan Goodman wrote:
If still nothing can be deducted disable all online repositories, drop
DVD in the drive, install Wireshark, run it and then try to update. Output is verbose, but there is no chance not to find out what is going wrong.
I have disabled all the repositories and installed Wireshark. I then called it to bring up its UI, but did nothing within it, because I am not clear what I should do.
Hovering over first few icons from left to right will give you tooltips popups that should be clear enough what that icons do. I use one that offer available interfaces, and choose eth0 from selection, and then Start. Following capture is running on that interface only.
With the program running, I clicked on the updates icon (which has changed since yesterday from being an orange triangle to being a dark square with a white downward-pointing arrow in its center). This brings up a dialog box telling me that I have two optional updates waiting (only two?); it has the expected "Install" button for confirmation, but it is greyed out, so there is nothing to click. Meantime, nothing has happened either in the Wireshark window or in the terminal from which I called it.
What I did forget to tell that disabling online repositories is just temporary measure to enable Wireshark installation without wading trough error messages. After Wireshark is installed you should turn them again on. Sorry for confusion. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 03:36:34 on Friday Friday 01 May 2009, "Rajko M." <rmatov101@charter.net> wrote:
On Thursday 30 April 2009 08:03:31 am Stan Goodman wrote:
If still nothing can be deducted disable all online repositories, drop
DVD in the drive, install Wireshark, run it and then try to update. Output is verbose, but there is no chance not to find out what is going wrong.
I have disabled all the repositories and installed Wireshark. I then called it to bring up its UI, but did nothing within it, because I am not clear what I should do.
Hovering over first few icons from left to right will give you tooltips popups that should be clear enough what that icons do. I use one that offer available interfaces, and choose eth0 from selection, and then Start. Following capture is running on that interface only.
Done. I will attach two captures, explained below.
With the program running, I clicked on the updates icon (which has changed since yesterday from being an orange triangle to being a dark square with a white downward-pointing arrow in its center). This brings up a dialog box telling me that I have two optional updates waiting (only two?); it has the expected "Install" button for confirmation, but it is greyed out, so there is nothing to click. Meantime, nothing has happened either in the Wireshark window or in the terminal from which I called it.
What I did forget to tell that disabling online repositories is just temporary measure to enable Wireshark installation without wading trough error messages. After Wireshark is installed you should turn them again on. Sorry for confusion.
No confusion. I restored them at once, and also added Packman. Attached ("NewSW.log") is the first log I made. After starting the capture, I clicked the new "black rectangle w/white down-arrow", which caused a dialog box telling me that new optional software is available, and asking to "Install"; but the Install button is greyed, and therefore ineffective. I note that this notice was for one single optional file, whereas past notices were for two, showing me that failed upgrades are being lost to me, not merely deferred. The second attachment ("YaSTSW.log") is for an attempt to reinstall XMMS with YaST (which is why I added the Packman repository). YaST went through its usual stages, telling me what it was going to install, etc, and crashed only at the end. YaST now tells me that XMMS is installed, but I think that is incorrect, as calling XMMS from a CLI does nothing. But the apparent failure has restored the XMMS icon that I kept on a second panel on my screen. I hope I have done properly what you asked, and have supplied some hints for going further. No-flame disclaimer: I've seen some complaints on the forum deploring the use of attachments here. The two files I have attached are not text files; I see no way to convey them other than as attachments. -- Stan Goodman Qiryat Tiv'on Israel
On Friday 01 May 2009 04:04:38 am Stan Goodman wrote: ...
No confusion. I restored them at once, and also added Packman.
Attached ("NewSW.log") is the first log I made. After starting the capture, I clicked the new "black rectangle w/white down-arrow", which caused a dialog box telling me that new optional software is available, and asking to "Install"; but the Install button is greyed, and therefore ineffective.
Nothing much to see. Except that you probably need temporary fix for /etc/resolv.conf. Put in nameserver 127.0.0.1 Also disable IPv6 using YaST. It is useless for you, it just doubles name resolution queries, ie. slows down browsing. I remove it as soon as computer is on, system wide in YaST and then specially for Firefox (see some other tips http://en.opensuse.org/Firefox ). I'm wondering how long it will take for IPv6 to pick up and finally make a day to those that push it. It is good idea that many years after introduction is just another layer of frustration for Internet users.
I note that this notice was for one single optional file, whereas past notices were for two, showing me that failed upgrades are being lost to me, not merely deferred.
It is probably software management related, and masks other. Again, use YOU, install that update first. While updater applet is nice to have, I can't recall that it survives long in my tray. Recently I let it live, and more or less it works, but first few months it was most of the time off. YOU is the law. Stick with it and live happy. Second, update repo has priority 20, while any other is 99 (default) which is not good for people that want to use extra repositories, including Packman. High priority is masking other repos, which is good if you don't have any extra repos, but in particular case it often leads to strange effects. Change update priority to be the same as other. If you don't play with priorities, then it would mean to 99 (default).
The second attachment ("YaSTSW.log") is for an attempt to reinstall XMMS with YaST (which is why I added the Packman repository). YaST went through its usual stages, telling me what it was going to install, etc, and crashed only at the end.
YaST in 11.1 has new behavior. It disappears as soon as it is done. There is feature request to change that, so that user doesn't need to start it for each package, and to give few words what happened.
YaST now tells me that XMMS is installed, but I think that is incorrect, as calling XMMS from a CLI does nothing. But the apparent failure has restored the XMMS icon that I kept on a second panel on my screen.
I guess when you fix repository priority, restart YaST Software Management, and force XMMS update it should work.
I hope I have done properly what you asked, and have supplied some hints for going further.
Not much to see. There is a lot of activity around interface binding. I don't have it here, nor I know much about, so I can't say is it normal to see every 2 seconds something about binding.
No-flame disclaimer: I've seen some complaints on the forum deploring the use of attachments here. The two files I have attached are not text files; I see no way to convey them other than as attachments.
Both are < 56kB, so I can't see a problem. For bigger files, you can make tar.gz and upload on your server in some obscure directory and then post the link. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 03:17:46 on Saturday Saturday 02 May 2009, "Rajko M." <rmatov101@charter.net> wrote:
On Friday 01 May 2009 04:04:38 am Stan Goodman wrote: ...
No confusion. I restored them at once, and also added Packman.
Attached ("NewSW.log") is the first log I made. After starting the capture, I clicked the new "black rectangle w/white down-arrow", which caused a dialog box telling me that new optional software is available, and asking to "Install"; but the Install button is greyed, and therefore ineffective.
Nothing much to see. Except that you probably need temporary fix for /etc/resolv.conf. Put in nameserver 127.0.0.1
Done.
Also disable IPv6 using YaST.
Done. I also deleted the lines relating to IPv6 in /etc/hosts (which may have been superfluous, since I had already disabled IPv6 in YaST. I do not know if the line for 127.0.0.2, because I don't know what it is.
It is useless for you, it just doubles name resolution queries, ie. slows down browsing. I remove it as soon as computer is on, system wide in YaST and then specially for Firefox (see some other tips http://en.opensuse.org/Firefox ).
Done.
I'm wondering how long it will take for IPv6 to pick up and finally make a day to those that push it. It is good idea that many years after introduction is just another layer of frustration for Internet users.
I note that this notice was for one single optional file, whereas past notices were for two, showing me that failed upgrades are being lost to me, not merely deferred.
It is probably software management related, and masks other. Again, use YOU, install that update first.
While updater applet is nice to have, I can't recall that it survives long in my tray. Recently I let it live, and more or less it works, but first few months it was most of the time off. YOU is the law. Stick with it and live happy.
There is no man page for "YOU", and the many google hits for the term do not seem to consider how to use it. When you say "YOU", do you mean the "Online Updates" in YaST > Software Management? As far as I can understand from looking at the GUI there, it seems that a package list should appear automatically when there are updates, because I don't see a way to enter package names. Is that correct?
Second, update repo has priority 20, while any other is 99 (default) which is not good for people that want to use extra repositories, including Packman.
No. The priorities are listed as follows: openSUSE-0 99 -Update 99 -Debug 100 -NonOss 100 -Oss 100 -Source 100 Only the Packman repository had priority 20. I have now changed it to 99 as well.
High priority is masking other repos, which is good if you don't have any extra repos, but in particular case it often leads to strange effects. Change update priority to be the same as other. If you don't play with priorities, then it would mean to 99 (default).
The second attachment ("YaSTSW.log") is for an attempt to reinstall XMMS with YaST (which is why I added the Packman repository). YaST went through its usual stages, telling me what it was going to install, etc, and crashed only at the end.
YaST in 11.1 has new behavior. It disappears as soon as it is done. There is feature request to change that, so that user doesn't need to start it for each package, and to give few words what happened.
It may be that I was blindsided by the new behavior. I thought that XMMS had not been reinstalled because YsST didn't stop (as I expected) and ask me if I wanted to do anything more. In fact, XMMS turns out to be installed: When I opened an online audio stream, the XMMS GUI came up with beautiful music. On the other hand, clicking on the XMMS icon in my second Panel does nothing. Since this application is accessible in this way, I see no need for RealPlayer, and have deleted its icon.
YaST now tells me that XMMS is installed, but I think that is incorrect, as calling XMMS from a CLI does nothing. But the apparent failure has restored the XMMS icon that I kept on a second panel on my screen.
I guess when you fix repository priority, restart YaST Software Management, and force XMMS update it should work.
I hope I have done properly what you asked, and have supplied some hints for going further.
Not much to see. There is a lot of activity around interface binding. I don't have it here, nor I know much about, so I can't say is it normal to see every 2 seconds something about binding.
No-flame disclaimer: I've seen some complaints on the forum deploring the use of attachments here. The two files I have attached are not text files; I see no way to convey them other than as attachments.
Both are < 56kB, so I can't see a problem.
Nor do I. I thought a small attachment would be more convenient for the reader, and less disruptive of the body of the message. I still do.
For bigger files, you can make tar.gz and upload on your server in some obscure directory and then post the link
Exactly. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, May 02, 2009 at 07:54:10PM +0300, Stan Goodman wrote:
At 03:17:46 on Saturday Saturday 02 May 2009, "Rajko M."
[deletia]
While updater applet is nice to have, I can't recall that it survives long in my tray. Recently I let it live, and more or less it works, but first few months it was most of the time off. YOU is the law. Stick with it and live happy.
There is no man page for "YOU", and the many google hits for the term do not seem to consider how to use it. When you say "YOU", do you mean the "Online Updates" in YaST > Software Management?
Yes. YOU = "YaST Online Updates" [much snippage] -- Fats Loves Madelyn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R. -
Daniel Bauer -
Kurt Wall -
Patrick Shanahan -
Rajko M. -
Stan Goodman