On Sat, 1 Aug 2020, Christian Weisgerber wrote:
Public service announcement: The original BSD repository can be
browsed here (converted from SCCS):
https://svnweb.freebsd.org/csrg/
Wanna know what those hippies at Berkeley really did?
You can look it up.
Thanks for the nice repo with the
On Sat, 1 Aug 2020, Theo de Raadt wrote:
Christian Weisgerber wrote:
On 2020-08-01, Roderick wrote:
It is not documented in 4.4BSD. I suppose this is not original BSD?
Public service announcement: The original BSD repository can be
browsed here (converted from SCCS):
Christian Weisgerber wrote:
> On 2020-08-01, Roderick wrote:
>
> > It is not documented in 4.4BSD. I suppose this is not original BSD?
>
> Public service announcement: The original BSD repository can be
> browsed here (converted from SCCS):
> https://svnweb.freebsd.org/csrg/
>
> Wanna know
On 2020-08-01, Roderick wrote:
>
> On Sat, 1 Aug 2020, Theo de Raadt wrote:
>
>> People should really use rsync (which has it's own oddities), ...
>
> For example the ugly behaviour when the source file ends with / ?
That's not ugly, it's flexible! And it teaches you to type what you mean.
On 2020-08-01, Roderick wrote:
> It is not documented in 4.4BSD. I suppose this is not original BSD?
Public service announcement: The original BSD repository can be
browsed here (converted from SCCS):
https://svnweb.freebsd.org/csrg/
Wanna know what those hippies at Berkeley really did?
You
On Sat, 1 Aug 2020, Theo de Raadt wrote:
People should really use rsync (which has it's own oddities), ...
For example the ugly behaviour when the source file ends with / ?
Also FreeBSD's cp behave like rsync and is documented in its man page:
-R If source_file designates a directory, cp
On Aug 01 09:34:52, dera...@openbsd.org wrote:
> Unfortunately, that is how it works.
>
> I think you are making an assumption that 'scp' means 'cp over ssh'.
> You think it should therefore work maximum like cp. But it doesn't.
> It has hundreds of ways it doesn't work like cp. It is totally
>
pying multiple files from a remote host using scp(1)
> into a local directory that does not exist, or to local file,
> the result is that the last copied file wins.
>
> For example, with file1 and file2 at host,
> and /tmp/nonexistent not existing at the destination,
>
>
,
scp host:file* /tmp/nonexistent
will result in /tmp/nonexistent being a copy of file2
and file1 being nowhere.
In case /tmp/nonexistent exists and is a file,
the same happens.
In case /tmp/nonexistent exists and is a dir,
both file1 and file2 get copied there, as with cp(1).
Is this behaviour
9 matches
Mail list logo