Re: HEADSUP: ibcs2 and svr4 compat headed for history

From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 06/30/04

  • Next message: Mark Johnston: "cvs-src summary for June 21 - 28" 
    To: Charles Swiger <cswiger@mac.com>
Date: Wed, 30 Jun 2004 00:41:43 +0200

    In message <46A7D8A4-C9EF-11D8-99F8-003065ABFD92@mac.com>, Charles Swiger write
    s:

    >> The future of ibcs2 and svr4 has been in doubt for a long time (and
    >> still is pending developer attention), but appearantly most of the
    >> previous discussion and warnings have not been noticed:
    >[ ...cvs annotate... ]
    >> Searching the major mailing lists (bugs, stable, current etc) failed
    >> to return any hits about this.
    >
    >End-users may not read /usr/src/UPDATING or the published release notes
    >either, but at least those are the places they are _expected_ to look
    >at if they want to know what is changing. I don't think we can
    >reasonably expect an end-user to look though the output of "cvs
    >annotate"... :-)

    The warning would appear if you tried to config a kernel containing
    COMPAT_SVR4, and since there is no email, I conclude that nobody
    who cared about COMPAT_SVR4 (in -current) has done that since the
    message was added. 

    -- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: Mark Johnston: "cvs-src summary for June 21 - 28"

    Relevant Pages

    • Re: freebsd 7 release process
      ... current and cvs mailing lists. ... but the FreeBSD bug tracking system is very crappy (compared to ... no way to look at bugs by reported-in version or target release. ... It's not like we need to "advertise" for someone to fix the ...
      (freebsd-current)
    • Re: HEADS UP! 6.0 Schedule, 6.0-CURRENT Snapshot
      ... > The long anticipated and much feared 6.0 code freeze is about to begin! ... > From June 10 until the release, the number one priority is fixing bugs. ... A stroll through the mailing lists and PR ...
      (freebsd-current)
    • Re: HEADS UP! 6.0 Schedule, 6.0-CURRENT Snapshot
      ... > The long anticipated and much feared 6.0 code freeze is about to begin! ... > From June 10 until the release, the number one priority is fixing bugs. ... A stroll through the mailing lists and PR ...
      (freebsd-hackers)
    • Re: challenge: end of life for 6.2 is premature with buggy 6.3
      ... "Hardware XYZ isn't working for me anymore. ... Scott, you are missing the point in your apparent desire to be rude. ... When there are bugs where something does not work I do open bugs. ... This is why I rarely bother with the mailing lists -- flame wars produce no code. ...
      (freebsd-stable)
    • Re: php extensions compile error - another compile bug?
      ... >email addresses and mailing lists with dozen of messages. ... Seeing as the two bugs appear to be in your php Makefile and that other people ... Overall I take what is, so far, your first and only response, to these two ...
      (freebsd-questions)