Re: FreeBSD Security Advisory FreeBSD-SA-02:43.bind

From: Amit Rao (arao@niksun.com)
Date: 11/14/02 

From: Amit Rao <arao@niksun.com>
To: "Jack L. Stone" <jacks@sage-american.com>, "Jacques A. Vidrine" <nectar@FreeBSD.ORG>, Masachika ISHIZUKA <ishizuka@ish.org>
Date: Thu, 14 Nov 2002 12:28:06 -0500

On Thursday 14 November 2002 12:10 pm, Jack L. Stone wrote:
> At 10:33 AM 11.14.2002 -0600, Jacques A. Vidrine wrote:
> >On Thu, Nov 14, 2002 at 04:19:25PM +0900, Masachika ISHIZUKA wrote:
> >> Hi, this is ishizuka@ish.org.
> >>
> >> I cannot patch with above commands for 4.7-RELEASE.
> >> The correct commands are as follows?
> >>
> >> # cd /usr/src
> >> # patch < /path/to/patch
> >> # cd /usr/src/lib/libisc
> >> # make
> >
> >Rather:
> > # make depend && make
> >
> >> # cd /usr/src/lib/libbind
> >> # make
> >
> >Rather:
> > # make depend && make
> >
> >> # cd /usr/src/usr.sbin/named
> >> # make depend && make && make install
> >> # cd /usr/src/libexec/named-xfer
> >> # make depend && make && make install
> >
> >Cheers,
> >--
> >Jacques A. Vidrine <nectar@celabo.org> http://www.celabo.org/
>
> I believe the "&&" construct is now deprecated in FBSD-4.7.....

I think you are referring to:
"sh(1) no longer accepts invalid constructs as command & && command, &&
command, or || command." from freebsd 4.7 relnotes.

It just means that you cannot do anymore in sh:
$ echo hello & && echo world
$ && echo hello world
etc

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

Relevant Pages

  • Re: Persisting env vars in cmd windows
    ... more about batch files as you go on, ... echo The time is %time::=.% ... But the piece de resistance was the "start" command, ... echo:: ERROR ERROR ERROR ERROR ...
    (microsoft.public.win2000.general)
  • Re: Persisting env vars in cmd windows
    ... But the piece de resistance was the "start" command, ... - Have all code for the one project in one single batch file. ... @echo off ... echo:: ERROR ERROR ERROR ERROR ...
    (microsoft.public.win2000.general)
  • Re: Persisting env vars in cmd windows
    ... even though it applies to any command, e.g. echo, copy, ... Similarly the syntax for the extremely powerful "for" command ... more about batch files as you go on, ... echo:: ERROR ERROR ERROR ERROR ...
    (microsoft.public.win2000.general)
  • Re: Persisting env vars in cmd windows
    ... even though it applies to any command, e.g. echo, copy, ... Similarly the syntax for the extremely powerful "for" command ... more about batch files as you go on, ... echo:: ERROR ERROR ERROR ERROR ...
    (microsoft.public.win2000.general)
  • Re: Persisting env vars in cmd windows
    ... I open several Command windows in succession. ... Drag the name of C000_CreateSymbols.bat into a new command window ... @echo off ... echo:: ERROR ERROR ERROR ERROR ...
    (microsoft.public.win2000.general)