The scp man page is not very verbose ;-) I want to copy a directory, recursively, over the lan, but only those files that are new or updated. MS-DOS could do this back in ...Ummm.... so I can't believe it can't be done in scp, but I can't see how to do it.
Anne
Anne Wilson wrote:
The scp man page is not very verbose ;-) I want to copy a directory, recursively, over the lan, but only those files that are new or updated. MS-DOS could do this back in ...Ummm.... so I can't believe it can't be done in scp, but I can't see how to do it.
Use rsync for such tasks. It natively understands how to move files over ssh. Eg
rsync -avz mysourcedir user@desthost:/path/on/destination
will just update/transmit files changed in the source dir compared to the destination.
-Andy
On Saturday 18 March 2006 15:27, Andy Green wrote:
Anne Wilson wrote:
The scp man page is not very verbose ;-) I want to copy a directory, recursively, over the lan, but only those files that are new or updated. MS-DOS could do this back in ...Ummm.... so I can't believe it can't be done in scp, but I can't see how to do it.
Use rsync for such tasks. It natively understands how to move files over ssh. Eg
rsync -avz mysourcedir user@desthost:/path/on/destination
will just update/transmit files changed in the source dir compared to the destination.
The reason I don't want to use rsync is, AIUI, rsync would delete files on the remote box when they are deleted on the local one. I don't want that to happen.
On Sat, Mar 18, 2006 at 04:05:20PM +0000, Anne Wilson wrote:
The reason I don't want to use rsync is, AIUI, rsync would delete files on the remote box when they are deleted on the local one. I don't want that to happen.
it only does that with the --delete option, not by default.
On Saturday 18 March 2006 17:01, Dave Mitchell wrote:
On Sat, Mar 18, 2006 at 04:05:20PM +0000, Anne Wilson wrote:
The reason I don't want to use rsync is, AIUI, rsync would delete files on the remote box when they are deleted on the local one. I don't want that to happen.
it only does that with the --delete option, not by default.
Really? I had completely misunderstood, then.
Any advice/caveats? With a man page running to 34 pages it will take a bit of digesting ;-)
Anne
Anne Wilson wrote:
Really? I had completely misunderstood, then.
Any advice/caveats? With a man page running to 34 pages it will take a bit of digesting ;-)
Anne
Here's a sample of what I use every day to sync my home directory to another machine where ssh runs on port 8090, excluding the Cache of any mozilla based browser (--exclude=Cache) , deleting any excluded files that by accident may have been sent to the destination and files that have been removed (--delete-excluded includes --delete) and copying the contents of symlinks, instead of copying the links (--copy-links). rsync -avz -e 'ssh -p 8090' /home/pmacedo/ my_other_machine:~/sync/ --delete-excluded --exclude=Cache --copy-links
One caveat: you must be running rsync either from the source or the destination machine, since rsync wont do remote to remote syncs using ssh. That's usually what I use and I've never needed any other options besides those to do any type of sync.
-- Pedro Macedo
On Saturday 18 March 2006 17:34, Pedro Fernandes Macedo wrote:
Anne Wilson wrote:
Really? I had completely misunderstood, then.
Any advice/caveats? With a man page running to 34 pages it will take a bit of digesting ;-)
Anne
Here's a sample of what I use every day to sync my home directory to another machine where ssh runs on port 8090, excluding the Cache of any mozilla based browser (--exclude=Cache) , deleting any excluded files that by accident may have been sent to the destination and files that have been removed (--delete-excluded includes --delete) and copying the contents of symlinks, instead of copying the links (--copy-links). rsync -avz -e 'ssh -p 8090' /home/pmacedo/ my_other_machine:~/sync/ --delete-excluded --exclude=Cache --copy-links
One caveat: you must be running rsync either from the source or the destination machine, since rsync wont do remote to remote syncs using ssh. That's usually what I use and I've never needed any other options besides those to do any type of sync.
Hmm - I'm getting something badly wrong here:
[anne@david ~]$ rsync -auvz /home/anne/ ssh:anne@borg:/home/anne/ --exclude .* > ~/Desktop/rsynctest.txt
gives
rsync: link_stat "/home/anne/ssh:anne@borg:/home/anne/." failed: No such file or directory (2)
Then it goes on to try to access the other users' directories:
rsync: opendir "/home/anne/../gillian" failed: Permission denied (13) rsync: opendir "/home/anne/../lost+found" failed: Permission denied (13) rsync: opendir "/home/anne/../david" failed: Permission denied (13) ERROR: destination must be a directory when copying more than 1 file rsync error: errors selecting input/output files, dirs (code 3) at main.c(410) rsync: connection unexpectedly closed (8 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(420)
(I'm deliberately leaving out the -r, for the moment.)
Anne
On Sat, 2006-03-18 at 18:01 +0000, Anne Wilson wrote:
On Saturday 18 March 2006 17:34, Pedro Fernandes Macedo wrote:
Anne Wilson wrote:
Really? I had completely misunderstood, then.
Any advice/caveats? With a man page running to 34 pages it will take a bit of digesting ;-)
Anne
Here's a sample of what I use every day to sync my home directory to another machine where ssh runs on port 8090, excluding the Cache of any mozilla based browser (--exclude=Cache) , deleting any excluded files that by accident may have been sent to the destination and files that have been removed (--delete-excluded includes --delete) and copying the contents of symlinks, instead of copying the links (--copy-links). rsync -avz -e 'ssh -p 8090' /home/pmacedo/ my_other_machine:~/sync/ --delete-excluded --exclude=Cache --copy-links
One caveat: you must be running rsync either from the source or the destination machine, since rsync wont do remote to remote syncs using ssh. That's usually what I use and I've never needed any other options besides those to do any type of sync.
Hmm - I'm getting something badly wrong here:
[anne@david ~]$ rsync -auvz /home/anne/ ssh:anne@borg:/home/anne/ --exclude .* > ~/Desktop/rsynctest.txt
try:
rsync -e "/usr/bin/ssh" --exclude=.* -auvz /home/anne/ ann@borg:/home/anne/ >~/Desktop/rsynctest.txt
gives
rsync: link_stat "/home/anne/ssh:anne@borg:/home/anne/." failed: No such file or directory (2)
Then it goes on to try to access the other users' directories:
rsync: opendir "/home/anne/../gillian" failed: Permission denied (13) rsync: opendir "/home/anne/../lost+found" failed: Permission denied (13) rsync: opendir "/home/anne/../david" failed: Permission denied (13) ERROR: destination must be a directory when copying more than 1 file rsync error: errors selecting input/output files, dirs (code 3) at main.c(410) rsync: connection unexpectedly closed (8 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(420)
(I'm deliberately leaving out the -r, for the moment.)
Anne
fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Anne Wilson wrote:
Hmm - I'm getting something badly wrong here:
[anne@david ~]$ rsync -auvz /home/anne/ ssh:anne@borg:/home/anne/
The ssh: is bogus.
Your best plan is to set up a test dir and get the simplest case working first to your satisfaction.
It looks like .* in the exclude causes it to start poking in .., maybe this is shell expansion: try --exclude ".*"
-Andy
Try to use the -e flag :
rsync -auvz -e ssh from where -- Luc MAIGNAN /*WinXpert*/ Directeur technique
Tél : +33-1 69 51 39 50 e-mail : luc.maignan@winxpert.com
Andy Green a écrit :
Anne Wilson wrote:
Hmm - I'm getting something badly wrong here:
[anne@david ~]$ rsync -auvz /home/anne/ ssh:anne@borg:/home/anne/
The ssh: is bogus.
Your best plan is to set up a test dir and get the simplest case working first to your satisfaction.
It looks like .* in the exclude causes it to start poking in .., maybe this is shell expansion: try --exclude ".*"
-Andy
On Saturday 18 March 2006 19:20, Luc MAIGNAN wrote:
Try to use the -e flag :
rsync -auvz -e ssh from where
I've hit a brick wall there, Luc. I set up keychain to monitor both ssh-keys and gpg-keys, but I keep getting messages that one of my gpg keys is not found. When I tried a command with the -e flag as you suggested it immediately failed with "/home/anne/.keychainrc: line 1: 2F62DB48: command not found".
I had put this problem aside for the moment, thinking that the gpg-key was not important in this situation, but it looks as though I was wrong. It looks as though I may have to address this problem first.
Anne
On Sat, 2006-03-18 at 13:37, Anne Wilson wrote:
On Saturday 18 March 2006 19:20, Luc MAIGNAN wrote:
Try to use the -e flag :
rsync -auvz -e ssh from whereI've hit a brick wall there, Luc. I set up keychain to monitor both ssh-keys and gpg-keys, but I keep getting messages that one of my gpg keys is not found. When I tried a command with the -e flag as you suggested it immediately failed with "/home/anne/.keychainrc: line 1: 2F62DB48: command not found".
I had put this problem aside for the moment, thinking that the gpg-key was not important in this situation, but it looks as though I was wrong. It looks as though I may have to address this problem first.
That sounds like a local keychain problem. If you don't use it at all or don't use ssh keys, it should just prompt you for the remote password.
Test with somethng like 'ssh remote_server id'. Once that works you should be able to use 'rsync -e ssh ...'.
On Saturday 18 March 2006 21:42, Les Mikesell wrote:
On Sat, 2006-03-18 at 13:37, Anne Wilson wrote:
On Saturday 18 March 2006 19:20, Luc MAIGNAN wrote:
Try to use the -e flag :
rsync -auvz -e ssh from whereI've hit a brick wall there, Luc. I set up keychain to monitor both ssh-keys and gpg-keys, but I keep getting messages that one of my gpg keys is not found. When I tried a command with the -e flag as you suggested it immediately failed with "/home/anne/.keychainrc: line 1: 2F62DB48: command not found".
I had put this problem aside for the moment, thinking that the gpg-key was not important in this situation, but it looks as though I was wrong. It looks as though I may have to address this problem first.
That sounds like a local keychain problem. If you don't use it at all or don't use ssh keys, it should just prompt you for the remote password.
Test with somethng like 'ssh remote_server id'. Once that works you should be able to use 'rsync -e ssh ...'.
I can do 'ssh anne@borg' and connect to the remote box - no problem, and the key is passed. What I'm trying to do is find the commands I will need so that I can put together a script to do regular copies across the lan.
I'll struggle on with the docs - it's no worse than the first time I got gpg-agent going ;-)
Anne
On Sat, 2006-03-18 at 15:53, Anne Wilson wrote:
Test with somethng like 'ssh remote_server id'. Once that works you should be able to use 'rsync -e ssh ...'.
I can do 'ssh anne@borg' and connect to the remote box - no problem, and the key is passed. What I'm trying to do is find the commands I will need so that I can put together a script to do regular copies across the lan.
I'll struggle on with the docs - it's no worse than the first time I got gpg-agent going ;-)
You need to make the keys with no passphrase if you want it to run automatically when no one will be able to supply it.
Or you could just nfs mount the remote space and use it directly. That might be more convenient, but perhaps more susceptible to operator-error deletions.
On Sat, 2006-03-18 at 18:01 +0000, Anne Wilson wrote:
On Saturday 18 March 2006 17:34, Pedro Fernandes Macedo wrote:
Anne Wilson wrote:
Really? I had completely misunderstood, then.
Any advice/caveats? With a man page running to 34 pages it will take a bit of digesting ;-)
Anne
Here's a sample of what I use every day to sync my home directory to another machine where ssh runs on port 8090, excluding the Cache of any mozilla based browser (--exclude=Cache) , deleting any excluded files that by accident may have been sent to the destination and files that have been removed (--delete-excluded includes --delete) and copying the contents of symlinks, instead of copying the links (--copy-links). rsync -avz -e 'ssh -p 8090' /home/pmacedo/ my_other_machine:~/sync/ --delete-excluded --exclude=Cache --copy-links
One caveat: you must be running rsync either from the source or the destination machine, since rsync wont do remote to remote syncs using ssh. That's usually what I use and I've never needed any other options besides those to do any type of sync.
Hmm - I'm getting something badly wrong here:
[anne@david ~]$ rsync -auvz /home/anne/ ssh:anne@borg:/home/anne/ --exclude .* > ~/Desktop/rsynctest.txt
The .* includes all hidden (.xxxx) files, the .. (parent) directory, and the . (current) directory. It may not have been what you wanted.
gives
rsync: link_stat "/home/anne/ssh:anne@borg:/home/anne/." failed: No such file or directory (2)
Then it goes on to try to access the other users' directories:
rsync: opendir "/home/anne/../gillian" failed: Permission denied (13) rsync: opendir "/home/anne/../lost+found" failed: Permission denied (13) rsync: opendir "/home/anne/../david" failed: Permission denied (13) ERROR: destination must be a directory when copying more than 1 file rsync error: errors selecting input/output files, dirs (code 3) at main.c(410) rsync: connection unexpectedly closed (8 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(420)
(I'm deliberately leaving out the -r, for the moment.)
Anne
fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
On Sunday 19 March 2006 02:38, Jeff Vian wrote:
Hmm - I'm getting something badly wrong here:
[anne@david ~]$ rsync -auvz /home/anne/ ssh:anne@borg:/home/anne/ --exclude .* > ~/Desktop/rsynctest.txt
The .* includes all hidden (.xxxx) files, the .. (parent) directory, and the . (current) directory. It may not have been what you wanted.
Of course - I had overlooked the . and .. directories. That explains what happened. So, how can I rsync all my home folder, excluding the hidden files and, say Desktop and Download directories? I'd realy appreciate an example.
I'm managing to get workable recursive directory copies now, but if I have to do a manual listing of those transfers I would miss any new ones created.
Anne
Anne Wilson wrote:
Hmm - I'm getting something badly wrong here:
[anne@david ~]$ rsync -auvz /home/anne/ ssh:anne@borg:/home/anne/ --exclude .* > ~/Desktop/rsynctest.txt
Jeff Vian told her:
The .* includes all hidden (.xxxx) files, the .. (parent) directory, and the . (current) directory. It may not have been what you wanted.
Anne replied:
Of course - I had overlooked the . and .. directories. That explains what happened. So, how can I rsync all my home folder, excluding the hidden files and, say Desktop and Download directories? I'd realy appreciate an example.
I should have thought --exclude .[a-z]* or --exclude .??* would have got rid of most hidden files and directories. A quick check on my home directory suggests both would do the job [1]
I'd also suspect that for the test, you need to --exclude ~/Desktop : things could get odd if you repeatedly try to syncronise all of your home directory to somewhere underneath it.
Hope this helps,
James.
[1] Assuming that you haven't changed LANG or LC_COLLATE to C, in which case .[a-z]* won't get .DCOP*.
On Tuesday 21 March 2006 07:28, James Wilkinson wrote:
I should have thought --exclude .[a-z]* or --exclude .??* would have got rid of most hidden files and directories. A quick check on my home directory suggests both would do the job [1]
Thanks for the suggestion - I'll try it today.
I'd also suspect that for the test, you need to --exclude ~/Desktop : things could get odd if you repeatedly try to syncronise all of your home directory to somewhere underneath it.
Hope this helps,
James.
[1] Assuming that you haven't changed LANG or LC_COLLATE to C, in which case .[a-z]* won't get .DCOP*.
For the test I will direct it to another folder that can be deleted once I'm sure everything is as I wanted it.
I don't seem to have done too much damage with that first error. Perhaps it's fortunate that I hadn't emptied Trash before I started, and I had done a lot of culling. I always leave things in Trash for a day or two after an exercise like that, in case I've made a mistake :-) Anyway, I was able to interrupt while it was still copying Trash, which may have saved the day. As it is, the only thing I've noticed is that I can't get back the default Fedora Core wallpaper, which I like to keep on the server box. It makes a clear visual differentiation between that and my own desktop box. It isn't offered along with the other wallpapers, and I don't know its name, so it's difficult to search. I tried a few guesses but without success.
Anne
On Tuesday 21 March 2006 07:28, James Wilkinson wrote:
I should have thought --exclude .[a-z]* or --exclude .??* would have got rid of most hidden files and directories. A quick check on my home directory suggests both would do the job [1]
For the test I dropped the '-r', but forgot to exclude ~/Desktop, though it wasn't important at this point because it was being re-directed to another directory. Here is what I gave:
rsync -e "/usr/bin/ssh" --exclude=.[a-z]* -auvz /home/anne/ anne@borg:/home/anne/Test
yet it started to act recursively. Most of the hidden files were excluded by the filter, but it let .DOCPSERVER_box.domain.lan, .ICEauthority and .Xauthority. I don't think that the first one is a problem, since it is linked to the box, but the other ones probably are. What do you think?
I'd also suspect that for the test, you need to --exclude ~/Desktop : things could get odd if you repeatedly try to syncronise all of your home directory to somewhere underneath it.
I haven't spotted the relevant bit in the man page, so do you list the two excludes simply space-separated?
Anne
On Tue, 2006-03-21 at 17:51 +0000, Anne Wilson wrote:
On Tuesday 21 March 2006 07:28, James Wilkinson wrote:
I should have thought --exclude .[a-z]* or --exclude .??* would have got rid of most hidden files and directories. A quick check on my home directory suggests both would do the job [1]
For the test I dropped the '-r', but forgot to exclude ~/Desktop, though it wasn't important at this point because it was being re-directed to another directory. Here is what I gave:
rsync -e "/usr/bin/ssh" --exclude=.[a-z]* -auvz /home/anne/ anne@borg:/home/anne/Test
yet it started to act recursively. Most of the hidden files were excluded by the filter, but it let .DOCPSERVER_box.domain.lan, .ICEauthority and .Xauthority. I don't think that the first one is a problem, since it is linked to the box, but the other ones probably are. What do you think?
If you want to exclude the ones that start with an uppercase letter, change .[a-z]* to .[a-zA-Z]*. This is caused by the fact that shell globbing is case sensitive, so you need to explicitly list both cases in your expression.
I'd also suspect that for the test, you need to --exclude ~/Desktop : things could get odd if you repeatedly try to syncronise all of your home directory to somewhere underneath it.
I haven't spotted the relevant bit in the man page, so do you list the two excludes simply space-separated?
Anne
fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
I wrote:
I should have thought --exclude .[a-z]* or --exclude .??* would have got rid of most hidden files and directories. A quick check on my home directory suggests both would do the job [1].
Anne Wilson replied to it, dropping the footnote:
[1] Assuming that you haven't changed LANG or LC_COLLATE to C, in which case .[a-z]* won't get .DCOP*.
Jeff Vian wrote:
If you want to exclude the ones that start with an uppercase letter, change .[a-z]* to .[a-zA-Z]*. This is caused by the fact that shell globbing is case sensitive, so you need to explicitly list both cases in your expression.
Actually, I should have said .[a-Z]* .
But that's why I added the footnote. File globbing (at least in bash) observes the LC_COLLATE environment variable, or LANG if LC_COLLATE is not set. And that dictates how letters sort. The "C" locale observes traditional case sensitivity, the way you suggest. But en_GB.UTF-8 (which I imagine both Anne and I are using), en_GB, en_US, fr_FR, and (I imagine) most other locales sort "aAbBcCdD...", with other accented characters in there, too.
So [a-Z]* gets the lot.
That's also why ls no longer lists the filenames beginning with capital letters before the rest.
Hope this helps,
James.
On Wednesday 22 March 2006 13:08, James Wilkinson wrote:
Actually, I should have said .[a-Z]* .
But that's why I added the footnote. File globbing (at least in bash) observes the LC_COLLATE environment variable, or LANG if LC_COLLATE is not set. And that dictates how letters sort. The "C" locale observes traditional case sensitivity, the way you suggest. But en_GB.UTF-8 (which I imagine both Anne and I are using), en_GB, en_US, fr_FR, and (I imagine) most other locales sort "aAbBcCdD...", with other accented characters in there, too.
Ah - I didn't really understand the footnote. Thanks for the explanation.
So [a-Z]* gets the lot.
That's also why ls no longer lists the filenames beginning with capital letters before the rest.
Side issue, James. Are you having any problems displaying accented letters? I have language=British English, and character set=utf8. When I should see an accented letter I get a double space instead.
Anne
Anne Wilson wrote:
Side issue, James. Are you having any problems displaying accented letters? I have language=British English, and character set=utf8. When I should see an accented letter I get a double space instead.
Not usually, no. But it sounds as though you've got problems with part of your computing environment using UTF8 and part of it using ISO 8859 variants. UTF8 is undoubtedly superior, but the transition period is a bit sticky...
Can you open a shell and type echo $LANG It should return en_GB.UTF-8 which should confirm your settings.
And you'd probably better check /etc/sysconfig/i18n, too.
With this set up, you should be good to enter and save accented letters. You should also be able to receive (properly formatted) e-mails with accents in, since the e-mails should contain headers describing the encoding used.
So, for example, уоυ ѕhουld ье аьlе to read that (with any luck, and a good font) even though it contains quite a few Greek and Cyrillic letters, because this message will have a header saying that it's encoded in UTF8.
The problem comes when you have text files that come from non-UTF8 systems, or filenames from non-UTF8 systems, or applications which don't understand UTF8. If you're seeing double spaces, then you're probably seeing UTF8 data displayed in a non-UTF8 program (or system).
In which case, it would be helpful to know precisely which program or system that is, so we can recommend better settings.
Hope this helps,
James.
On Wednesday 22 March 2006 17:32, James Wilkinson wrote:
Anne Wilson wrote:
Side issue, James. Are you having any problems displaying accented letters? I have language=British English, and character set=utf8. When I should see an accented letter I get a double space instead.
Not usually, no. But it sounds as though you've got problems with part of your computing environment using UTF8 and part of it using ISO 8859 variants. UTF8 is undoubtedly superior, but the transition period is a bit sticky...
Can you open a shell and type echo $LANG It should return en_GB.UTF-8 which should confirm your settings.
And you'd probably better check /etc/sysconfig/i18n, too.
Both say that I'm using en_US.UTF-8. I have kde set to use en_GB.UTF-8, I believe, but if I run system-config-language only en_US.UTF-8 is present. How can I change it?
With this set up, you should be good to enter and save accented letters. You should also be able to receive (properly formatted) e-mails with accents in, since the e-mails should contain headers describing the encoding used.
So, for example, уоυ ѕhουld ье аьlе to read that (with any luck, and a good font) even though it contains quite a few Greek and Cyrillic letters, because this message will have a header saying that it's encoded in UTF8.
The problem comes when you have text files that come from non-UTF8 systems, or filenames from non-UTF8 systems, or applications which don't understand UTF8. If you're seeing double spaces, then you're probably seeing UTF8 data displayed in a non-UTF8 program (or system).
In which case, it would be helpful to know precisely which program or system that is, so we can recommend better settings.
I've seen it mostly in konqueror file manager, but yesterday I received an email where one name showed the same problem.
Maybe I have two language settings slogging it out. What do I need to change to get it into sync, James?
Anne
I asked Anne Wilson:
Can you open a shell and type echo $LANG It should return en_GB.UTF-8 which should confirm your settings.
And you'd probably better check /etc/sysconfig/i18n, too.
She replied:
Both say that I'm using en_US.UTF-8. I have kde set to use en_GB.UTF-8, I believe, but if I run system-config-language only en_US.UTF-8 is present. How can I change it?
Change that value in /etc/sysconfig/i18n. Although the difference is simply that you'll occasionally get American content / spelling / preferences. You shouldn't have problems with accents or unusual characters due to the difference.
(Having said that, I'm still on FC4. Check /usr/lib/locale and make sure there's an en_GB.utf8 directory there if you're on FC5).
I've seen it mostly in konqueror file manager, but yesterday I received an email where one name showed the same problem.
So from where did you get those files? Were they generated on another computer?
What happens if you ls them from the command line?
As for the single e-mail -- I'd blame the other end, personally.
Hope this helps,
James.
On Thursday 23 March 2006 08:53, James Wilkinson wrote:
I asked Anne Wilson:
Can you open a shell and type echo $LANG It should return en_GB.UTF-8 which should confirm your settings.
And you'd probably better check /etc/sysconfig/i18n, too.
She replied:
Both say that I'm using en_US.UTF-8. I have kde set to use en_GB.UTF-8, I believe, but if I run system-config-language only en_US.UTF-8 is present. How can I change it?
Change that value in /etc/sysconfig/i18n. Although the difference is simply that you'll occasionally get American content / spelling / preferences. You shouldn't have problems with accents or unusual characters due to the difference.
My i18n file contains
LANG="en_US.UTF-8" SYSFONT="latarcyrheb-sun16" SUPPORTED="en_US.UTF-8:en_US:en"
I presume the font line stays unchanged, and the top line seems straightforward, but what does your SUPPORTED: line look like?
(Having said that, I'm still on FC4. Check /usr/lib/locale and make sure there's an en_GB.utf8 directory there if you're on FC5).
I'm on FC4 too, but there is such an entry in /usr/lib/locale.
I've seen it mostly in konqueror file manager, but yesterday I received an email where one name showed the same problem.
So from where did you get those files? Were they generated on another computer?
Some on this computer, some on what is now the server box. The email I mentioned arrived in kmail, showing the same symptoms, a couple of days ago.
What happens if you ls them from the command line?
Here's a sample -
../Mp3/marisa_monte/rose_and_charcoal/06_dan�_da_solid�.mp3
The title should read
06_dança_da_solidäo.mp3
As for the single e-mail -- I'd blame the other end, personally.
Maybe. Maybe he has the same problem as I do.
Anne
Anne Wilson wrote:
My i18n file contains
LANG="en_US.UTF-8" SYSFONT="latarcyrheb-sun16" SUPPORTED="en_US.UTF-8:en_US:en"
I presume the font line stays unchanged, and the top line seems straightforward, but what does your SUPPORTED: line look like?
Odd. I don't have one on this system, and I haven't noticed any problems...
A backup from an FC3 machine listed SUPPORTED="en_GB.UTF-8:en_GB:en:en_US.UTF-8:en_US:en" although I doubt both en references are strictly necessary.
I can't find any references as to where it is used...
I asked (about files that were apparently incorrectly named)
So from where did you get those files? Were they generated on another computer?
Anne replied:
Some on this computer, some on what is now the server box. The email I mentioned arrived in kmail, showing the same symptoms, a couple of days ago.
Here's a sample -
../Mp3/marisa_monte/rose_and_charcoal/06_dan�_da_solid�.mp3
The title should read
06_dança_da_solidäo.mp3
That's actually a different symptom of the same problem. UTF8 takes two bytes to store most common non-ASCII characters, whereas the ISO-8859 family always uses one byte.
What you first described was seeing the two UTF8 bytes in an ISO-8859 program, so each accented character shows as two ISO-8859 characters (some of which will probably be "illegal", so you'll see spaces or something similar there).
What you've just illustrated is an ISO-8859 name viewed in an UTF-8 environment, where two ISO-8859 characters are interpreted as one illegal UTF-8 character.
My first reaction is to blame the generating program (what was it?) In my experience, many MP3 programs, following Winamp's example, have gone flat-out for skins and custome text-handling. Too many of them don't support UTF8 in $LANG properly.
Alternatively, what did the server box use to run? How did you transfer the files? Red Hat went to UTF-8 early, and many other distros took a lot longer to upgrade. And transferring files might not get the conversion right.
(You used to use Mandriva, didn't you? I'm not sure when they adopted UTF-8...)
I wrote:
As for the single e-mail -- I'd blame the other end, personally.
Anne said:
Maybe. Maybe he has the same problem as I do.
Um. Mail clients have no business not knowing which encoding they're using. And if they know that, they've no business not putting it into the headers of outgoing e-mail properly.
We've proved that your e-mail client can receive UTF-8. I suppose there's still the chance that your correspondent used a weird encoding that your client didn't understand. But you're not going to get the "right" message anyway in those situations, except by blind luck.
James.
On Friday 24 March 2006 13:34, James Wilkinson wrote:
A backup from an FC3 machine listed SUPPORTED="en_GB.UTF-8:en_GB:en:en_US.UTF-8:en_US:en" although I doubt both en references are strictly necessary.
OK, I've altered the file.
Here's a sample -
../Mp3/marisa_monte/rose_and_charcoal/06_dan�_da_solid�.mp3
The title should read
06_dança_da_solidäo.mp3
That's actually a different symptom of the same problem. UTF8 takes two bytes to store most common non-ASCII characters, whereas the ISO-8859 family always uses one byte.
What you first described was seeing the two UTF8 bytes in an ISO-8859 program, so each accented character shows as two ISO-8859 characters (some of which will probably be "illegal", so you'll see spaces or something similar there).
It's quite possible that the two different displays were because, when first attempting to troubleshoot this, I experimented by setting different character sets in kde.
What you've just illustrated is an ISO-8859 name viewed in an UTF-8 environment, where two ISO-8859 characters are interpreted as one illegal UTF-8 character.
My first reaction is to blame the generating program (what was it?)
Grip generated the mp3s. I first saw the problem in k3b, but then in konqueror and kmail, all under FC4.
In my experience, many MP3 programs, following Winamp's example, have gone flat-out for skins and custome text-handling. Too many of them don't support UTF8 in $LANG properly.
Alternatively, what did the server box use to run? How did you transfer the files? Red Hat went to UTF-8 early, and many other distros took a lot longer to upgrade. And transferring files might not get the conversion right.
It was running Mandriva 10.0. In truth, though, I can't remember whether the box that generated the files was running Mdv 10.1 or 10.2. I don't think 10.0 had utf-8 (could be wrong) but it's very likely that I never elected to use utf-8 when it first became available.
(You used to use Mandriva, didn't you? I'm not sure when they adopted UTF-8...)
I wrote:
As for the single e-mail -- I'd blame the other end, personally.
Anne said:
Maybe. Maybe he has the same problem as I do.
Um. Mail clients have no business not knowing which encoding they're using. And if they know that, they've no business not putting it into the headers of outgoing e-mail properly.
We've proved that your e-mail client can receive UTF-8. I suppose there's still the chance that your correspondent used a weird encoding that your client didn't understand. But you're not going to get the "right" message anyway in those situations, except by blind luck.
Well thanks for the insights I've got, anyway. And finding convmv was another good thing to come out of it. It all helps.
Anne
-- E-mail address: james | In the Royal Air Force a landing's OK, @westexe.demon.co.uk | If the pilot gets out and can still walk away.
| But in the Fleet Air Arm the outlook is grim, | If your landings are duff and you've not learnt to | swim.
On Wednesday 22 March 2006 02:42, Jeff Vian wrote:
yet it started to act recursively. Most of the hidden files were excluded by the filter, but it let .DOCPSERVER_box.domain.lan, .ICEauthority and .Xauthority. I don't think that the first one is a problem, since it is linked to the box, but the other ones probably are. What do you think?
If you want to exclude the ones that start with an uppercase letter, change .[a-z]* to .[a-zA-Z]*. This is caused by the fact that shell globbing is case sensitive, so you need to explicitly list both cases in your expression.
Yes, I suspected that would be the solution, but held off until I resolve the multiple exclusion question and recursivity. I will make local backups to RW of any config files I suspect I'd want to keep. However, can you see any reason why the command I gave would act recursively? That was totally unexpected, and undesired at this stage. I need to workout the exclusion list first.
What about multiple exclusions, Jeff? Do they get listed space-separated? Or is there some way to pass a file as the parameter?
Anne
On Wed, 2006-03-22 at 09:13, Anne Wilson wrote:
Yes, I suspected that would be the solution, but held off until I resolve the multiple exclusion question and recursivity. I will make local backups to RW of any config files I suspect I'd want to keep. However, can you see any reason why the command I gave would act recursively? That was totally unexpected, and undesired at this stage. I need to workout the exclusion list first.
See the rsync man page about all of the other options that '-a' implies. Recursion is one of them. But, I thought earlier you said you wanted it to always pick up new additions.
On Wednesday 22 March 2006 16:49, Les Mikesell wrote:
On Wed, 2006-03-22 at 09:13, Anne Wilson wrote:
Yes, I suspected that would be the solution, but held off until I resolve the multiple exclusion question and recursivity. I will make local backups to RW of any config files I suspect I'd want to keep. However, can you see any reason why the command I gave would act recursively? That was totally unexpected, and undesired at this stage. I need to workout the exclusion list first.
See the rsync man page about all of the other options that '-a' implies.
Ah yes - I had read it, but missed the fact that -r is included.
Recursion is one of them. But, I thought earlier you said you wanted it to always pick up new additions.
Yes, finally. I just hadn't intended it at that stage. It's a matter of trying to make sure that I understand all the implications ;-)
That only leaves the question of how to set multiple exclusions. It looks to me as though exclude-from=filename is going to be the best way to do it. Is that right? With a man page this long you can read until you are bog-eyed ;-)
Anne
I'm running FC8. Why would one of my removable USB devices (an external hard drive) be creating two identical icons on my gnome desktop each time I boot? Is there some way around this?
On Thu, 07 Feb 2008 14:56:45 -0800 Gerhard Magnus magnus@agora.rdrop.com wrote:
I'm running FC8. Why would one of my removable USB devices (an external hard drive) be creating two identical icons on my gnome desktop each time I boot? Is there some way around this?
I thought it was a bug when I first saw it:
https://bugzilla.redhat.com/show_bug.cgi?id=389411
I don't see any comments on the bug since it was entered, so I have no clues to offer.
On Feb 8, 2008 12:13 AM, Tom Horsley tom.horsley@att.net wrote:
On Thu, 07 Feb 2008 14:56:45 -0800 Gerhard Magnus magnus@agora.rdrop.com wrote:
I'm running FC8. Why would one of my removable USB devices (an external hard drive) be creating two identical icons on my gnome desktop each time I boot? Is there some way around this?
I thought it was a bug when I first saw it:
https://bugzilla.redhat.com/show_bug.cgi?id=389411
I don't see any comments on the bug since it was entered, so I have no clues to offer.
I'm seeing this also for my hard drive paritions on Fedora 8. On Rawhide I don't see it, so it looks it is some fix that didn't get still back in F8.
Valent.
On Saturday 18 March 2006 12:09, Anne Wilson wrote:
On Saturday 18 March 2006 17:01, Dave Mitchell wrote:
On Sat, Mar 18, 2006 at 04:05:20PM +0000, Anne Wilson wrote:
The reason I don't want to use rsync is, AIUI, rsync would delete files on the remote box when they are deleted on the local one. I don't want that to happen.
it only does that with the --delete option, not by default.
Really? I had completely misunderstood, then.
Any advice/caveats? With a man page running to 34 pages it will take a bit of digesting ;-)
So print it & take it to the middle of the house, where you can read while attending to other bodily needs. Around my place its also called the reading room. :)
Anne
On Saturday 18 March 2006 17:37, Gene Heskett wrote:
On Saturday 18 March 2006 12:09, Anne Wilson wrote:
On Saturday 18 March 2006 17:01, Dave Mitchell wrote:
On Sat, Mar 18, 2006 at 04:05:20PM +0000, Anne Wilson wrote:
The reason I don't want to use rsync is, AIUI, rsync would delete files on the remote box when they are deleted on the local one. I don't want that to happen.
it only does that with the --delete option, not by default.
Really? I had completely misunderstood, then.
Any advice/caveats? With a man page running to 34 pages it will take a bit of digesting ;-)
So print it & take it to the middle of the house, where you can read while attending to other bodily needs. Around my place its also called the reading room. :)
:-) It may take a few such visits to absorb it all
Anne
Anne Wilson wrote:
On Saturday 18 March 2006 15:27, Andy Green wrote:
Anne Wilson wrote:
The scp man page is not very verbose ;-) I want to copy a directory, recursively, over the lan, but only those files that are new or updated. MS-DOS could do this back in ...Ummm.... so I can't believe it can't be done in scp, but I can't see how to do it.
Use rsync for such tasks. It natively understands how to move files over ssh. Eg
rsync -avz mysourcedir user@desthost:/path/on/destination
will just update/transmit files changed in the source dir compared to the destination.
The reason I don't want to use rsync is, AIUI, rsync would delete files on the remote box when they are deleted on the local one. I don't want that to happen.
Clearly, you have not learned to read the documentation.
On Saturday 18 March 2006 15:27, Andy Green wrote:
Anne Wilson wrote:
The scp man page is not very verbose ;-) I want to copy a directory, recursively, over the lan, but only those files that are new or updated. MS-DOS could do this back in ...Ummm.... so I can't believe it can't be done in scp, but I can't see how to do it.
Use rsync for such tasks. It natively understands how to move files over ssh. Eg
rsync -avz mysourcedir user@desthost:/path/on/destination
will just update/transmit files changed in the source dir compared to the destination.
Oops - I think I've just made a terrible mistake. I rsync'd my home directory, forgetting that it would take the hidden files and config files with it. Now I'll have to see what damage is done.
Anne
Anne Wilson wrote:
Oops - I think I've just made a terrible mistake. I rsync'd my home directory, forgetting that it would take the hidden files and config files with it. Now I'll have to see what damage is done.
Anne
This reminded me of another option that is very useful , specially when you use --delete: --dry-run.. It will only show what would be done when running the sync and wont execute it for real. Excellent for checking if you didn't do any wrong exclude.
-- Pedro Macedo
On Saturday 18 March 2006 17:36, Pedro Fernandes Macedo wrote:
Anne Wilson wrote:
Oops - I think I've just made a terrible mistake. I rsync'd my home directory, forgetting that it would take the hidden files and config files with it. Now I'll have to see what damage is done.
Anne
This reminded me of another option that is very useful , specially when you use --delete: --dry-run.. It will only show what would be done when running the sync and wont execute it for real. Excellent for checking if you didn't do any wrong exclude.
That sounds very useful indeed ;-) Thanks
Anne
On Saturday 18 March 2006 10:21, Anne Wilson wrote:
The scp man page is not very verbose ;-) I want to copy a directory, recursively, over the lan, but only those files that are new or updated. MS-DOS could do this back in ...Ummm.... so I can't believe it can't be done in scp, but I can't see how to do it.
Anne
rsync can do that, files get copied by a checksum compare, if they are different, than that 64k block is pulled from the src. If no changes, no update. New files get a full copy. But you will need scratchpad space for the biggest file available to do this. rsync is pretty bulletproof, I've been using it here to make backup dirs of important dirs on other machines on my own LAN for several years now. I have it as a cron job & it sends me an email every morning showing what it did.
On Saturday 18 March 2006 15:51, Gene Heskett wrote:
Anne
rsync can do that, files get copied by a checksum compare, if they are different, than that 64k block is pulled from the src. If no changes, no update. New files get a full copy. But you will need scratchpad space for the biggest file available to do this. rsync is pretty bulletproof, I've been using it here to make backup dirs of important dirs on other machines on my own LAN for several years now. I have it as a cron job & it sends me an email every morning showing what it did.
I do a lot of photo-processing and video-processing, which takes up a lot of disk space, so I've put a large drive on the remote box and want to collect everything together there. Wouldn't rsync delete files on the remote box when I remove them here to make space?
Anne
On Saturday 18 March 2006 11:45, Anne Wilson wrote:
On Saturday 18 March 2006 15:51, Gene Heskett wrote:
Anne
rsync can do that, files get copied by a checksum compare, if they are different, than that 64k block is pulled from the src. If no changes, no update. New files get a full copy. But you will need scratchpad space for the biggest file available to do this. rsync is pretty bulletproof, I've been using it here to make backup dirs of important dirs on other machines on my own LAN for several years now. I have it as a cron job & it sends me an email every morning showing what it did.
I do a lot of photo-processing and video-processing, which takes up a lot of disk space, so I've put a large drive on the remote box and want to collect everything together there. Wouldn't rsync delete files on the remote box when I remove them here to make space?
Anne
Let me rephrase that, my other reply is wrong and you are correct. If you want to then save them on the remote end, you should manually move them to a directory not in the rsync path, or not use the --delete option.
Anne Wilson wrote:
The scp man page is not very verbose ;-) I want to copy a directory, recursively, over the lan, but only those files that are new or updated. MS-DOS could do this back in ...Ummm.... so I can't believe it can't be done in scp, but I can't see how to do it.
Another option is to use sitecopy, I use it to maintain my web sites (which I keep a local copy of). I think you'll run into the same problems as you are seeing now so it may not work any better.
fullsync uses sftp - i like it. http://fullsync.sourceforge.net I use it for win to linux syncing but i imagine it would work on any configuration as it runs off java. atomi
On 3/18/06, Neil Cherry ncherry@comcast.net wrote:
Anne Wilson wrote:
The scp man page is not very verbose ;-) I want to copy a directory, recursively, over the lan, but only those files that are new or updated. MS-DOS could do this back in ...Ummm.... so I can't believe it can't be
done
in scp, but I can't see how to do it.
Another option is to use sitecopy, I use it to maintain my web sites (which I keep a local copy of). I think you'll run into the same problems as you are seeing now so it may not work any better.
-- Linux Home Automation Neil Cherry ncherry@linuxha.com http://www.linuxha.com/ Main site http://linuxha.blogspot.com/ My HA Blog http://home.comcast.net/~ncherry/ Backup site
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
-
Andy Green -
Anne Wilson -
atomi -
Dave Mitchell -
Gene Heskett -
Gerhard Magnus -
James Wilkinson -
Jeff Vian -
John Summerfield -
Les Mikesell -
Luc MAIGNAN -
Neil Cherry -
Pedro Fernandes Macedo -
Tom Horsley -
Valent Turkovic -
Warren Sturm