-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Boyd Stephen Smith Jr." writes:
> In <87fx6mkfhn@merciadriluca-station.merciadriluca>, Merciadri Luca wrote:
>>$ cp *.*
>>is equivalent to
>>$ cd . ; cp *
>
> Not true.
>
> The second misses a file named "foo", as the shell glob "*.*" only match
In <87fx6mkfhn@merciadriluca-station.merciadriluca>, Merciadri Luca wrote:
>$ cp *.*
>is equivalent to
>$ cd . ; cp *
Not true.
The second misses a file named "foo", as the shell glob "*.*" only matches
filenames with at least one '.' character in their name.
>$ cp .*
>is equivalent to
>$ c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Using rsync is easier, I admit it. When one needs to do something
quicky, he often looks for the easiest solution to do it. Sometimes,
he does not understand wholly this easiest solution. But he does not
care: it works. Another solution would be fine,
On Dec 29, 2009, at 10:38 PM, Alex Samad wrote:
> I did suggest this, but
rsync is magic. Don't like magic :-)
Actually, rsync's magic is wonderful. I use it in a script that runs several
times a day to back up an entire disk over a slow connection. Speedup often
approaches 1000. Thank $
On Tue, Dec 29, 2009 at 03:58:56PM -0700, Paul E Condon wrote:
> On 20091229_011737, Osamu Aoki wrote:
> > On Mon, Dec 28, 2009 at 05:57:00PM +0200, Andrei Popescu wrote:
> > > On Tue,29.Dec.09, 00:25:06, Osamu Aoki wrote:
> > ...
> > > > $ cd /path/to/source ; cp -a ./ destination/
> > > >
> > >
On 20091229_011737, Osamu Aoki wrote:
> On Mon, Dec 28, 2009 at 05:57:00PM +0200, Andrei Popescu wrote:
> > On Tue,29.Dec.09, 00:25:06, Osamu Aoki wrote:
> ...
> > > $ cd /path/to/source ; cp -a ./ destination/
> > >
> > > This does trick since adding ./ after destination/ is still destination/
>
On Mon, Dec 28, 2009 at 05:57:00PM +0200, Andrei Popescu wrote:
> On Tue,29.Dec.09, 00:25:06, Osamu Aoki wrote:
...
> > $ cd /path/to/source ; cp -a ./ destination/
> >
> > This does trick since adding ./ after destination/ is still destination/ :-)
>
> Why is this better than 'cd /path/to/source
On Tue,29.Dec.09, 00:25:06, Osamu Aoki wrote:
> On Mon, Dec 28, 2009 at 04:17:01PM +0200, Andrei Popescu wrote:
> > On Mon,28.Dec.09, 06:27:32, Glenn English wrote:
> >
> > > I still don't understand how 'source/.' would work, though.
>
> Yah ... it will create destination/source/*
At least on
On Mon, Dec 28, 2009 at 04:17:01PM +0200, Andrei Popescu wrote:
> On Mon,28.Dec.09, 06:27:32, Glenn English wrote:
>
> > I still don't understand how 'source/.' would work, though.
>
> I discovered that by chance, but I don't see any reason why it shouldn't
> work.
Yah ... it will create destin
On Mon,28.Dec.09, 06:27:32, Glenn English wrote:
> I still don't understand how 'source/.' would work, though.
I discovered that by chance, but I don't see any reason why it shouldn't
work.
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.or
On Dec 28, 2009, at 5:48 AM, Andrei Popescu wrote:
> Unless I'm doing something wrong 'cp -a .*' will try to copy the parent
> directory as well
Hmm. Bears looking into. But I swear I've been doing '.*' forever. Maybe that
explains the high disk drive bills :-)
> The correct solution
> from
On Mon,28.Dec.09, 04:49:07, Glenn English wrote:
>
> On Dec 28, 2009, at 3:37 AM, Andrei Popescu wrote:
>
> >> I always just say 'cp -a .* ' in addition to what you
> >> already did to copy (recursively) everything beginning with a period.
> >
> > Why would '.*' be better than a simple '*'?
>
On Dec 28, 2009, at 3:37 AM, Andrei Popescu wrote:
>> I always just say 'cp -a .* ' in addition to what you
>> already did to copy (recursively) everything beginning with a period.
>
> Why would '.*' be better than a simple '*'?
Because '*' doesn't get the invisible files, and Merciadri'd alr
On Fri,25.Dec.09, 15:25:56, Glenn English wrote:
>
> On Dec 25, 2009, at 2:40 PM, Merciadri Luca wrote:
>
> > You were right. I just made a diff, and folders beginning with a dot
> > were not copied. I was simply using
> > $ cp --recursive --update *.* [...] [...]
> >
> > What would be these app
On Sun, Dec 27, 2009 at 11:33:13PM +0100, Merciadri Luca wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Alex Samad writes:
>
> > I wonder why the reliance upon cp, I would have throught rsync was a
> > much better choice ?
> That is a question of point of view, isn't it? That is fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Celejar writes:
> You also need to distinguish between the list itself, which is an
> official Debian-provided service, and any news gateways that mirror it,
> which have no official connection to Debian, AFAIK.
For sure, but as speeds were the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex Samad writes:
> I wonder why the reliance upon cp, I would have throught rsync was a
> much better choice ?
That is a question of point of view, isn't it? That is for me like
preferring emacs to vi(m): a matter of taste.
- --
Merciadri Luca
Se
On Sat, Dec 26, 2009 at 11:52:17AM +0900, Osamu Aoki wrote:
> Hi,
>
[snip]
> The root cause of problem is you used "cp --recursive --update * blh ...".
> Since things may have messed up somewhere, it is better to do it over.
I wonder why the reliance upon cp, I would have throught rsync was a
m
On Sun, 27 Dec 2009 15:35:52 +0100
Merciadri Luca wrote:
...
> way. However, everything that I can say is that my messages are
> published in a really slower way on this list than on any other one I
> could try (matlab, gnus, etc.). It is quite possible for my news
> server to dislike the linux.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glenn English writes:
> Well, it's *claimed* to be deterministic and repeatable. So you
> almost certainly didn't repeat the same things, not exactly. It
> might be productive in your CS studies to see if you could figure
> out what went wrong. I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Celejar writes:
> Not sure exactly what you mean by 'moderated', but the Debian mailing
> lists are not moderated in the typical sense of the word:
>
> http://www.debian.org/MailingLists/disclaimer
Okay, I just read it, and it appears not to be moder
On Fri, 25 Dec 2009 22:40:54 +0100
Merciadri Luca wrote:
...
> /Post scriptum/: sorry for the delay between my answers but it seems
> to be due to the fact that this group is moderated.
Not sure exactly what you mean by 'moderated', but the Debian mailing
lists are not moderated in the typical
On Sat, Dec 26, 2009 at 05:51:29PM +0100, Merciadri Luca wrote:
> Osamu Aoki writes:
> >> > # cd /mnt/mymnttosdc5
> >> > # rm -rf * .*
> >> > rm: cannot remove directory `.'
> >> > rm: cannot remove directory `..'
> >> > # cd
> >> > # cp -a ./ /mnt/mymnttosdc5
(This style of cp avoid such trouble
On Dec 26, 2009, at 6:31 AM, Merciadri Luca wrote:
> It now works like a charm.
Congratulations! But don't trust it for a second :-)
> I repeated the operation, doing the same
> things, and it worked, this time. Computer science is sometimes
> mysterious. That is why we like it, isn't it?
Well
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lisi writes:
> On Friday 25 December 2009 22:42:18 Merciadri Luca wrote:
>> Hope you will be
>
>> combled
>
> I assume this was meant to mean the same as comblé? Combled doesn't make
> sense!!
Yes. Sorry, `satiated' was really not the right word,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Osamu Aoki writes:
> Hi,
>
> On Sat, Dec 26, 2009 at 10:04:48AM +0100, Merciadri Luca wrote:
>> Osamu Aoki writes:
>>
>> > On Fri, Dec 25, 2009 at 11:20:49PM +0100, Merciadri Luca wrote:
>> >> I re-tried exactly the same thing, but with the same co
On Friday 25 December 2009 22:42:18 Merciadri Luca wrote:
> Hope you will be
> combled
I assume this was meant to mean the same as comblé? Combled doesn't make
sense!!
> when you will see my previous message.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subjec
Hi,
On Sat, Dec 26, 2009 at 10:04:48AM +0100, Merciadri Luca wrote:
> Osamu Aoki writes:
>
> > On Fri, Dec 25, 2009 at 11:20:49PM +0100, Merciadri Luca wrote:
> >> I re-tried exactly the same thing, but with the same contents on both
> >> HDDs (proved with a diff). I had to use
> >>
> >> # cp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It now works like a charm. I repeated the operation, doing the same
things, and it worked, this time. Computer science is sometimes
mysterious. That is why we like it, isn't it?
Thanks all.
- --
Merciadri Luca
See http://www.student.montefiore.ulg.a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hartwig Atrops writes:
> No, nothing will be erased. Umount your new disk - the old data will be there
> again. I.e. - if you want to reuse the disk space, you explicitly have to
> delete data in the old directory.
Thanks, Hartwig.
- --
Merciadri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Osamu Aoki writes:
> On Fri, Dec 25, 2009 at 11:20:49PM +0100, Merciadri Luca wrote:
>> I re-tried exactly the same thing, but with the same contents on both
>> HDDs (proved with a diff). I had to use
>>
>> # cp --recursive --update .[a-zA-Z0-9]* /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glenn English writes:
> My belief is that a symlink is to be used when you want to refer to
> a single file or filesystem from more than one place or by more than
> one name. If you're wanting to use a newly added disk or partition
> to replace a dir
Hi,
I have not investigated all the postings ...
On Fri, Dec 25, 2009 at 11:20:49PM +0100, Merciadri Luca wrote:
> I re-tried exactly the same thing, but with the same contents on both
> HDDs (proved with a diff). I had to use
>
> # cp --recursive --update .[a-zA-Z0-9]* /mnt/mymnttosdc5
The ro
Klistvud put forth on 12/25/2009 2:59 PM:
> Dne, 25. 12. 2009 20:29:39 je Hartwig Atrops napisal(a):
>> Hi.
>>
>> Why don't you mount the new disk on /home/merciadriluca/ ?
>>
>
> I second that. To elaborate a little: it's quite common to copy the
> entire contents of your current /home to a new
Sorry. This:
sda is the disk that boots and is the disk with the / filesystem on it. And the
/home dir, and your current home directory /mnt/merciadriluca.
should say "your current home directory /home/merciadriluca"
--
Glenn English
g...@slsware.com
--
To UNSUBSCRIBE, email to debian-user
On Dec 25, 2009, at 3:20 PM, Merciadri Luca wrote:
> I re-tried exactly the same thing, but with the same contents on both
> HDDs (proved with a diff). I had to use
>
> # cp --recursive --update .[a-zA-Z0-9]* /mnt/mymnttosdc5
I believe this would copy all files beginning with a '.', followed b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glenn English writes:
> I always just say 'cp -a .* ' in addition to what you
> already did to copy (recursively) everything beginning with a period. If
> there are switches to do this, I've missed them in my reading of the man page.
Hope you will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I re-tried exactly the same thing, but with the same contents on both
HDDs (proved with a diff). I had to use
# cp --recursive --update .[a-zA-Z0-9]* /mnt/mymnttosdc5
as there were already many files in /dev/sdc5 (obviously mounted in
/mnt/mymnttosd
On Dec 25, 2009, at 2:40 PM, Merciadri Luca wrote:
> You were right. I just made a diff, and folders beginning with a dot
> were not copied. I was simply using
> $ cp --recursive --update *.* [...] [...]
>
> What would be these appropriate switches to achieve this?
I always just say 'cp -a .*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Merriam writes:
> Your preferences may be in "hidden" directories, directories whose name
> starts with a period. ls -a will show them. Did the method you used to
> copy your home directory contents copy everything? cp *.* will not copy
> every
On 12/25/2009 03:54 PM, Merciadri Luca wrote:
> Thanks for all your answers. I tested the no-symlinks-are-used option,
> by merely mounting my new HDD into /home/merciadriluca/. It worked,
> but not as much as I wanted. After being logged, my
> /home/merciadriluca/'s content was the content of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Merriam writes:
> Kudos for the use of Latin in a question, especially Latin used in
> philosophy. Linux is very big on the use of abstraction, and separates
> the concepts of disks, file systems, and directories. Unlike Windows
> they are n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for all your answers. I tested the no-symlinks-are-used option,
by merely mounting my new HDD into /home/merciadriluca/. It worked,
but not as much as I wanted. After being logged, my
/home/merciadriluca/'s content was the content of the new HDD
Hi.
> Concerning the first answer: let's say that I copy everything from
> /home/merciadriluca/ on the new HDD. If I mount the new HDD on
> /home/merciadriluca/, will the (previous) content of
> /home/merciadriluca/ be overwritten?
No, nothing will be erased. Umount your new disk - the old data w
On Friday 25 December 2009 02:48 pm, Merciadri Luca wrote:
> Thanks for the two answers. They are both really nice. The first
> appears to be even `cleaner.' I thought my session would never boot if
> my folder was `nowhere.'
>
> Concerning the first answer: let's say that I copy everything from
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the two answers. They are both really nice. The first
appears to be even `cleaner.' I thought my session would never boot if
my folder was `nowhere.'
Concerning the first answer: let's say that I copy everything from
/home/merciadriluca/ on
On 12/25/2009 11:49 AM, Merciadri Luca wrote:
> Hi,
>
> After some data manipulation, I now have a free ext3 disk. My aim is
> to put the entire content of my /home/merciadriluca/ in it, at the
> place of on the HDD where /etc/, /sys/, and other stuff resides.
>
> The problem is that I have a lot o
Dne, 25. 12. 2009 20:29:39 je Hartwig Atrops napisal(a):
Hi.
Why don't you mount the new disk on /home/merciadriluca/ ?
I second that. To elaborate a little: it's quite common to copy the
entire contents of your current /home to a new disk or partition, and
then modify your fstab so as t
Hi.
Why don't you mount the new disk on /home/merciadriluca/ ?
Did I miss something?
Hartwig
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Friday 25 December 2009 11:49 am, Merciadri Luca wrote:
> Hi,
>
> After some data manipulation, I now have a free ext3 disk. My aim is
> to put the entire content of my /home/merciadriluca/ in it, at the
> place of on the HDD where /etc/, /sys/, and other stuff resides.
>
> The problem is that I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
After some data manipulation, I now have a free ext3 disk. My aim is
to put the entire content of my /home/merciadriluca/ in it, at the
place of on the HDD where /etc/, /sys/, and other stuff resides.
The problem is that I have a lot of apps and
51 matches
Mail list logo
