Sorry for bringing up the old topic. I made a proposition to extend mv and
cp programs with options from install command:
(something like) -p to create parent folder
-m to set mode as in mkdir
--rename to rename a file
https://lists.gnu.org/archive/html/coreutils/2023-07/msg0.html
Thread with
On 8/15/23 17:18, Pádraig Brady wrote:
+1
thanks, pushed.
On 15/08/2023 13:09, Bernhard Voelker wrote:
On 8/12/23 14:05, Sergey Ponomarev wrote:
For sure it would be good to add mention of the install into man cp "SEE
ALSO".
Good idea. Patch attached ... pushing soon.
Have a nice day,
Berny
+1
thanks
On 8/12/23 14:05, Sergey Ponomarev wrote:
For sure it would be good to add mention of the install into man cp "SEE
ALSO".
Good idea. Patch attached ... pushing soon.
Have a nice day,
BernyFrom d428096a6ade1acfc6537ab5f138ef1a3531a0fc Mon Sep 17 00:00:00 2001
From: Bernhard Voelker
Date:
e solution in place?
>>> 1. Use placeholder like asterisk to refer the source dir inside of the
>>> dest dir
>>> 2. Use -F arg to create directory if not exists
>>>
>>> Have a nice weekend
>>>
>>> On Sat, Jul 1, 2023 at 6:44 PM Glenn Gol
out in the first
>> place.
>> >> Autocomplete doesn't work, but this is a bash issue.
>> >>
>> >> Still, the placeholder would be kind of more clear but it's an
>> additional
>> >> feature so you probably WONTFIX it.
>> >>
>>
rote:
> >>
> >>> Thank you for the fast response. Nice tricks, didn't know about the
> >>> direxpand. Probably most regular users don't know either :(
> >>> As you may see, even with a workaround this usability can be improved.
> >>> So what abo
>> On Sat, Jul 1, 2023 at 7:23 PM Sergey Ponomarev
> >> wrote:
> >>
> >>> Thank you for the fast response. Nice tricks, didn't know about the
> >>> direxpand. Probably most regular users don't know either :(
> >>> As you may see, even with
er like asterisk to refer the source dir inside of the
>>> dest dir
>>> 2. Use -F arg to create directory if not exists
>>>
>>> Have a nice weekend
>>>
>>> On Sat, Jul 1, 2023 at 6:44 PM Glenn Golden wrote:
>>>
>>>>
>>>&
rote:
On Sat, Jul 1, 2023, at 09:03, Bernhard Voelker wrote:
On 7/1/23 14:12, Sergey Ponomarev wrote:
> To rename a file a user need to use mv command and specify
the DEST
dir:
>
> mv /some/very/long/path/file /some/very/long/path/
>
> This makes it not so easy to us
eholder like asterisk to refer the source dir inside
of
the
dest dir
2. Use -F arg to create directory if not exists
Have a nice weekend
On Sat, Jul 1, 2023 at 6:44 PM Glenn Golden
wrote:
On Sat, Jul 1, 2023, at 09:03, Bernhard Voelker wrote:
On 7/1/23 14:12, Sergey Ponomarev wrote:
> To re
kend
On Sat, Jul 1, 2023 at 6:44 PM Glenn Golden wrote:
On Sat, Jul 1, 2023, at 09:03, Bernhard Voelker wrote:
> On 7/1/23 14:12, Sergey Ponomarev wrote:
> > To rename a file a user need to use mv command and specify the DEST
dir:
> >
> > mv /some/very/long/p
placeholder like asterisk to refer the source dir inside of the
>> dest dir
>> 2. Use -F arg to create directory if not exists
>>
>> Have a nice weekend
>>
>> On Sat, Jul 1, 2023 at 6:44 PM Glenn Golden wrote:
>>
>>>
>>>
>>> On Sa
t;>
>>
>> On Sat, Jul 1, 2023, at 09:03, Bernhard Voelker wrote:
>> > On 7/1/23 14:12, Sergey Ponomarev wrote:
>> > > To rename a file a user need to use mv command and specify the DEST
>> dir:
>> > >
>> > > mv /some/very/long/path/f
ename a file a user need to use mv command and specify the DEST
> dir:
> > >
> > > mv /some/very/long/path/file /some/very/long/path/
> > >
> > > This makes it not so easy to use when typing a command but also makes
> a
> > > script line l
On Sat, Jul 1, 2023, at 09:03, Bernhard Voelker wrote:
> On 7/1/23 14:12, Sergey Ponomarev wrote:
> > To rename a file a user need to use mv command and specify the DEST dir:
> >
> > mv /some/very/long/path/file /some/very/long/path/
> >
> > This
On 7/1/23 14:12, Sergey Ponomarev wrote:
> To rename a file a user need to use mv command and specify the DEST dir:
>
> mv /some/very/long/path/file /some/very/long/path/
>
> This makes it not so easy to use when typing a command but also makes a
> script line longer.
To rename a file a user need to use mv command and specify the DEST dir:
mv /some/very/long/path/file /some/very/long/path/
This makes it not so easy to use when typing a command but also makes a
script line longer.
Newcomers like students may not figure out quickly that renaming is
indeed
?
On Sat, Jan 14, 2023, 04:57 Kaz Kylheku <962-396-1...@kylheku.com> wrote:
> On 2022-12-22 07:59, Stéphane Archer wrote:
> > Dear Gnu Coreutils community,
> >
> > I would like to contribute to the project a feature I miss a lot in the
> > `mv` command.
> > I
On 2022-12-22 07:59, Stéphane Archer wrote:
> Dear Gnu Coreutils community,
>
> I would like to contribute to the project a feature I miss a lot in the
> `mv` command.
> I currently have a working patch but it's clearly not perfect. I would like
> to have feedback on it and
you think?
Mary Christmas!
Stéphane Archer
On Thu, Dec 22, 2022 at 4:15 PM Pádraig Brady wrote:
> On 22/12/2022 15:59, Stéphane Archer wrote:
> > Dear Gnu Coreutils community,
> >
> > I would like to contribute to the project a feature I miss a lot in the
> > `mv` co
On 22/12/2022 15:59, Stéphane Archer wrote:
Dear Gnu Coreutils community,
I would like to contribute to the project a feature I miss a lot in the
`mv` command.
I currently have a working patch but it's clearly not perfect. I would like
to have feedback on it and would like to know if you
Dear Gnu Coreutils community,
I would like to contribute to the project a feature I miss a lot in the
`mv` command.
I currently have a working patch but it's clearly not perfect. I would like
to have feedback on it and would like to know if you are willing to accept
this change.
Do you think it's
severity 14628 wishlist
retitle 14628 mv: safeguard against renaming dir with open files
close 14628
stop
(triaging old bugs)
On 15/06/13 05:35 PM, Pádraig Brady wrote:
On 06/15/2013 09:02 PM, S. Dara wrote:
With this email, I would like to suggest a feature for the mv command. I
believe
2015-08-31 11:50:36 +0100, Pádraig Brady:
> On 31/08/15 06:57, Abhilash Mhaisne wrote:
> > Hey all.
> >
> > When the cp or mv command is executed, no progress of copying is shown.
> > The verbose option shows the source and destination, but not the progress.
> &g
:
> > > Hey all.
> > >
> > > When the cp or mv command is executed, no progress of copying is shown.
> > > The verbose option shows the source and destination, but not the
> progress.
> > >
> > > In the wget tool, download prog
Hey all.
When the cp or mv command is executed, no progress of copying is shown.
The verbose option shows the source and destination, but not the progress.
In the wget tool, download progress is shown. Can we have the similar
feature integrated on cp and mv?
Regards,
Abhilash Mhaisne
On 31/08/15 06:57, Abhilash Mhaisne wrote:
> Hey all.
>
> When the cp or mv command is executed, no progress of copying is shown.
> The verbose option shows the source and destination, but not the progress.
>
> In the wget tool, download progress is shown. Can we have t
Hello all,
On 08/31/2015 06:50 AM, Pádraig Brady wrote:
On 31/08/15 06:57, Abhilash Mhaisne wrote:
When the cp or mv command is executed, no progress of copying is shown.
The verbose option shows the source and destination, but not the progress.
This comes up periodically.
I think
On 31/08/15 15:15, Assaf Gordon wrote:
> Hello all,
>
> On 08/31/2015 06:50 AM, Pádraig Brady wrote:
>> On 31/08/15 06:57, Abhilash Mhaisne wrote:
>>>
>>> When the cp or mv command is executed, no progress of copying is shown.
>>> The verbo
Pádraig Brady wrote:
Charles Rogers wrote:
Is it ever possible for the mv command ( without using the –u
option ) to leave the file(s) in the source directory, while also
copying to the destination directory?
...
Any comments appreciated!
Your description implies that your destination
of Renata Karciauskaite )
-Original Message-
From: Bob Proulx [mailto:b...@proulx.com]
Sent: Thursday, March 12, 2015 1:46 PM
To: Rogers, Charles (MAN-Corporate-CON); 20...@debbugs.gnu.org
Subject: Re: bug#20091: mv command
Pádraig Brady wrote:
Charles Rogers wrote:
Is it ever
Rogers, Charles (MAN-Corporate-CON) wrote:
Thank you all so much for the explanation. It is as you describe.
1. We had insufficient permissions on the source directory
2. The destination directory was indeed on a different file system
Ah! All is explained.
So, our question is
Is it ever possible for the mv command ( without using the -u option ) to
leave the file(s) in the source directory, while also copying to the
destination directory?
We were experiencing this under zsh and GNU/Linux
2.6.32-358.18.1.el6.x86_64.
Any comments appreciated!
thanks
On 11/03/15 21:02, Rogers, Charles (MAN-Corporate-CON) wrote:
Is it ever possible for the mv command ( without using the –u option ) to
leave the file(s) in the source directory, while also copying to the
destination directory?
We were experiencing this under zsh and GNU
Dear authors of the mv command,
With this email, I would like to suggest a feature for the mv command. I
believe this command should contain a safeguard feature which will deny
renaming a directory that contains files which are currently opened by
the user.
For example, I have a directory
On 05/14/2013 10:15 AM, Koteswararao Nelakurthi wrote:
lchown(/media/sda2/aaa, 0, 0) = 0
write(2, mv: , 4mv: ) = 4
write(2, failed to preserve ownership for..., 48failed to preserve
ownership for /media/sda2/aaa) = 48
write(2, : Function not implemented, 26:
On 05/14/2013 11:14 AM, Koteswararao Nelakurthi wrote:
On Tue, May 14, 2013 at 3:39 PM, Pádraig Brady p...@draigbrady.com
mailto:p...@draigbrady.com wrote:
On 05/14/2013 10:15 AM, Koteswararao Nelakurthi wrote:
lchown(/media/sda2/aaa, 0, 0) = 0
write(2, mv: , 4mv: )
Dear Padraig Brady,
Thank you very much for your response.
I attached the strace log for mv command.
Regards
koteswararao
On Tue, May 14, 2013 at 2:31 PM, Pádraig Brady p...@draigbrady.com wrote:
On 05/14/2013 06:31 AM, Koteswararao Nelakurthi wrote:
Dear All,
I am trying to do mv(move
Dear Padraig Brady,
Thanks again for your valuable response.
May I know to how to check the difference
(May be patches wise) between r6.0.6 to
r6.0.7 of coreutils package
Probably..by looking at git web interface
of coreutils package ?
can we find the same?
Koteswararao Nelakurthi wrote:
Thanks again for your valuable response.
May I know to how to check the difference
(May be patches wise) between r6.0.6 to
r6.0.7 of coreutils package
Probably..by looking at git web interface
of coreutils package ?
can we find the same?
What distribution are
files. But this solution is far from good for all the reasons that
differentiate a copy from a move.
So I propose to add a --parents option to mv command in order to create the
parents directories as needed. In the case of acceptance, I could write a
patch to add this feature.
Maybe, but I'm
.
So I propose to add a --parents option to mv command in order to create
the parents directories as needed. In the case of acceptance, I could write
a patch to add this feature.
Maybe, but I'm not sold on the need TBH.
At first glance it seems like it's uncommon enough
that using cp might
to mv command in order to create
the parents directories as needed. In the case of acceptance, I could write a
patch to add this feature.
Maybe, but I'm not sold on the need TBH.
At first glance it seems like it's uncommon enough
that using cp might suffice? You could even do
that
differentiate a copy from a move.
So I propose to add a --parents option to mv command in order to create the
parents directories as needed. In the case of acceptance, I could write a
patch to add this feature.
Regards,
Rémy.
On Mon, 20 Jun 2011 22:21:57 +0800
Susanto Wijaya susanto.hu...@gmail.com wrote:
May I ask question about mv * command?
I dont understand your set of questions.
I think you try to experiment the expansion of *, but I cant assume.
Could you be more precise?
--
RMA.
* Susanto Wijaya (susanto.hu...@gmail.com) [20110620 16:25]:
If I use mv * command using root user in root directory /, the result is
all files and directory in / root directory will gone.
I think most if not all won't understand what you're asking for, so could
you give precise examples
a
symbolic
link back to the shared object file would be worth pursuing.
I'm still not sure I understand the exact settings you had before you ran
your mv command. A transcript of the session that has the events that you
are questioning would go a long way to understand what you are even
Begin forwarded message:
Date: Wed, 3 Mar 2010 13:58:59 -0500
From: Derick Centeno dcent...@ydl.net
To: Eric Blake ebl...@redhat.com
Subject: Re: side-effect implementing the mv command
On Wed, 03 Mar 2010 08:08:55 -0700
Eric Blake ebl...@redhat.com wrote:
[please keep replies on the list
settings you had before you ran
your mv command. A transcript of the session that has the events that you
are questioning would go a long way to understand what you are even asking
about.
By the term, side effect, I mean unexpected/undocumented/ambiguous results
generated by malformed
designed for PowerPC systems, as I'm running
Linux on a PowerPC. That plugin is known as: libjavaplugin_oji.so
Originally it was installed into: /opt/ibm/java-ppc-60/jre/plugin/ppc/ns7
It is supposed to be moved into: /usr/lib/mozilla/plugins
When I executed the mv command from within the ns7
the original location of *.so but
created in fact a link from the within the plugins directory to *.so
within the ns7 directory! I don't have a theory why this happened other
than to guess that as I did not provide a new filename for
the mv command to rename the *.so file mv proceeded to create
than to guess that as I did not provide a new filename for
the mv command to rename the *.so file mv proceeded to create a link to
the original *.so file.
Ideas?
Thanks.
=
Refranes/Popular sayings:
The Taino say:No hay mal que por bien no venga.
There is no evil out of which good cannot
I'm trying to move large files from one filesystem to another and the mv
command fails with the message File size limit exceeded. The partial
destination file is not removed and is 4,294,967,295 bytes in size.
mv (GNU coreutils) 5.93
openSuse 10.1 x86
v/r,
Rich Morgan
OpenAddict.com
Rich Morgan [EMAIL PROTECTED] writes:
I'm trying to move large files from one filesystem to another and the mv
command fails with the message File size limit exceeded. The partial
destination file is not removed and is 4,294,967,295 bytes in size.
Most likely that's not a bug in mv; it's
Paul Eggert wrote:
Rich Morgan [EMAIL PROTECTED] writes:
I'm trying to move large files from one filesystem to another and the mv
command fails with the message File size limit exceeded. The partial
destination file is not removed and is 4,294,967,295 bytes in size.
Most likely
I think I found a bug in the mv command.
Here's the scenario:
I have the following in a bash script that is run as a root cronjob:
--- begin bash script code, contents of myuserbackup.sh ---
#!/bin/bash
# this bash script is intended to be run as a cronjob for root
# line 1 - backup the entire
Ian MacGregor [EMAIL PROTECTED] wrote:
I think I found a bug in the mv command.
...
When I change line #9 in the bash script from
mv /home/storage/backup.tar.gz /home/storage/`date +%Y%m%d-%k%M`-backup.tar.gz
to
mv /home/storage/backup.tar.gz /home/storage/`date +%Y%m%d-%I%M`-backup.tar.gz
58 matches
Mail list logo
