Re: Need to build some systems this week. Snapshots?

From: Brett Glass (brett_at_lariat.org)
Date: 08/28/03

  • Next message: Harald Schmalzbauer: "Re: Please test: USB floppies" 
    Date: Thu, 28 Aug 2003 13:54:08 -0600
To: Colin Percival <colin.percival@wadham.ox.ac.uk>, Colin Percival <colin.percival@wadham.ox.ac.uk>, stable@freebsd.org

    At 12:16 PM 8/28/2003, Colin Percival wrote:
      
    >At 12:01 28/08/2003 -0600, Brett Glass wrote:
    >>Will this fix everything that needs to be recompiled to avoid the realpath()
    >>bug?
    >
    > Yes, that's the whole point of FreeBSD Update. Read my paper, or come to BSDCon, for details; but rest assured that if you start with a binary install from the official FTP or ISO releases, and don't recompile any of the world locally, FreeBSD Update will update any binaries which are affected by modifications in the security branch.

    That's great.

    What does one do about packages and ports? It appears that the binary packages on the FreeBSD servers are never updated between releases... which means that if a bug is in a package or is compiled into a package (as with the realpath problem), the FreeBSD servers keep sending out exploitable copies of that package indefinitely. The situation with ports is a bit better, but how does one know which ones to recompile and reinstall? Does your update system handle this situation and/or warn about it?

    --Brett

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Harald Schmalzbauer: "Re: Please test: USB floppies"

    Relevant Pages

    • Re: Problem with printer on parallel port.
      ... Please avoid top posting on fedora-list. ... >>even try the fix? ... To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list ...
      (Fedora)
    • Re: Blow-out correction
      ... have flaws in them was a bit supercilious, ... kinds in many situations) we learn to avoid, protect, correct, construe, ... We certainly don't blame others who can't fix our errors as you are wont ... You don't wait for an important shot to learn how to rescue. ...
      (rec.photo.digital)
    • Re: Xilinx FPGA editor tips?
      ... Not necessarily because it's a bad tool, but even if it were awesome it's still an unwise design practice to hand-route--as you have found, it will take hours and hours to fix one net, and you will never save time in the long run. ... the hours spend hand-routing are in vain if you ever change the source again. ... make explicit all multicycle paths and ignored paths to free up routing resources. ... Try to avoid any sort of manual routing or routing guide files. ...
      (comp.arch.fpga)
    • Re: Xilinx FPGA editor tips?
      ... My advice is to avoid FPGA Editor at all costs. ... Not necessarily because it's a bad tool, but even if it were awesome it's still an unwise design practice to hand-route--as you have found, it will take hours and hours to fix one net, and you will never save time in the long run. ... the hours spend hand-routing are in vain if you ever change the source again. ... Try to avoid any sort of manual routing or routing guide files. ...
      (comp.arch.fpga)
    • Re: Toolbar Buttons Too Wide
      ... MS has always said that they could not "reproduce" the problem and thus they could not fix it. ... Is the cause of the bug is known; I mean in a way that would allow me to avoid it in the future? ... or grab the bottom of the toolbar with the double arrow ... arrows at the right end of the toolbar: ...
      (microsoft.public.windows.inetexplorer.ie6_outlookexpress)