On Wed, Oct 30, 2024 at 06:41:35PM +0100, наб wrote:
> rm -
> unideal, sure, but.
The bare - will cause rm confusion, you probably need:
rm ./-
--
Brett Lymn
--
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
On Thu, Oct 31, 2024 at 12:35:01AM +0100, Steffen Nurpmeso wrote:
> наб wrote in
>.xyz>:
> |You can still write this portably:
> | echo crontab > ./-
> | crontab - < -
> | rm -
> |unideal, sure, but.
> OpenIndiana says
> #?1|oi-2024:steffen$ crontab -
> crontab: can't open your cron
наб wrote in
:
|On Thu, Oct 31, 2024 at 12:35:01AM +0100, Steffen Nurpmeso wrote:
|> наб wrote in
|>\
|> .xyz>:
|>|You can still write this portably:
|>| echo crontab > ./-
|>| crontab - < -
|>| rm -
|>|unideal, sure, but.
|> OpenIndiana says
|> #?1|oi-2024:steffen$ crontab -
наб wrote in
:
|On Wed, Oct 30, 2024 at 06:29:57PM +0100, Edgar Fuß wrote:
|>> If NetBSD "crontab" errors with
|>> "use crontab - to replace your crontab from the standard input stream"
|>> then that's an improvement over both the standard and the status quo IMO
|> While I agree that what PO
On Wed, Oct 30, 2024 at 06:29:57PM +0100, Edgar Fuß wrote:
> > If NetBSD "crontab" errors with
> > "use crontab - to replace your crontab from the standard input stream"
> > then that's an improvement over both the standard and the status quo IMO
> While I agree that what POSIX demands is not idea
> If NetBSD "crontab" errors with
> "use crontab - to replace your crontab from the standard input stream"
> then that's an improvement over both the standard and the status quo IMO
While I agree that what POSIX demands is not ideal, NetBSD's crontab(1)
behaviour prevents me from writing portable
On Tue, Oct 29, 2024 at 07:11:10PM +0100, Edgar Fuß wrote:
> > Those are not inconsistent, unless SUS specifies other behaviour for
> > the case of a bare -, or NetBSD's version doesn't read from stdin when
> > no (pseudo-)filename is given.
They are, POSIX says something like
97851 STDIN
9785
> crontab(5)? I'll assume that should be crontab(1).
Sorry, yes.
> Those are not inconsistent, unless SUS specifies other behaviour for
> the case of a bare -, or NetBSD's version doesn't read from stdin when
> no (pseudo-)filename is given.
NetBSD's version complains if no filename is given.
> It appears to me that NetBSD's crontab(5) uses the pseudo-filename
> "-" for installing a crontab from stdin, while SUS defines taht
> crontab reads from stdin if no filename is specified.
crontab(5)? I'll assume that should be crontab(1).
Those are not inconsistent, unless SUS specifies other
It appears to me that NetBSD's crontab(5) uses the pseudo-filename "-" for
installing a crontab from stdin, while SUS defines taht crontab reads from
stdin if no filename is specified.
10 matches
Mail list logo
