Re: 5.1-RELEASE TODO

From: Luigi Rizzo (rizzo_at_icir.org)
Date: 05/31/03

  • Next message: Sean Kelly: "USB Quirk Patch: SanDisk ImageMate CF SDDR31 (V:0x0781, P:0x0002)"
    Date: Sat, 31 May 2003 14:24:59 -0700
    To: re@FreeBSD.org
    
    

    On Sat, May 31, 2003 at 09:00:16AM -0400, Robert Watson wrote:
    > This is an automated bi-daily mailing of the FreeBSD 5.1 open issues list.
    > The live version of this list is available at:
    >
    > http://www.FreeBSD.org/releases/5.1R/todo.html
    >
    > Automated mailing of this list will continue through the release of
    > FreeBSD 5.1.
    >
    >
    > FreeBSD 5.1 Open Issues
    >
    > Open Issues
    >
    > This is a list of open issues that need to be resolved for FreeBSD 5.1. If
    > you have any updates for this list, please e-mail re@FreeBSD.org.
    >
    > Must Resolve Issues for 5.1-RELEASE
    >
    > +------------------------------------------------------------------------+
    > | Issue | Status | Responsible | Description |
    > |------------------+-------------+-------------+-------------------------|
    > | | | | There are reports of |
    > | ipfw/ipfw2 | | | alignment problems with |
    > | alignment issues | In progress | Luigi Rizzo | ipfw and/or ipfw2 on |
    > | on alpha/sparc64 | | | 64-bit platforms |
    > | | | | (specifically alpha and |
    > | | | | sparc64). |
    > +------------------------------------------------------------------------+

    i posted patches and a detailed description for this item
    3 weeks ago to re@ and then the same was forwarded a couple of weeks
    ago to the relevant lists (ipfw, sparc64, alpha) and got no
    useful feedback (in detail, two message: one 'cannot apply the patch',
    the other one 'it dumps core' without further details).

    As i do not have access to these platforms, all i can do is provide
    code and make sure that it compiles (which i did, using a cross-build),
    but for running it (part of the problem involves the kernel) i need
    someone with root&console access to test them.

    I would interpret the absence of feedback as a "nobody cares enough"
    (which is perfectly fine given that these platforms are a negligible
    fraction of the installed base, there are more important issues to
    address and these particular ones should have a relatively trivial
    fix).

            cheers
            luigi

    > Desired Features for 5.1-RELEASE
    >
    > +------------------------------------------------------------------------+
    > | Issue | Status | Responsible | Description |
    > +------------------------------------------------------------------------+
    >
    > Documentation items that must be resolved for 5.1
    >
    > +------------------------------------------------------------------------+
    > | Issue | Status | Responsible | Description |
    > +------------------------------------------------------------------------+
    >
    > Areas requiring immediate testing
    >
    > +------------------------------------------------------------------------+
    > | Issue | Status | Responsible | Description |
    > |-------------------+--------+---------------+---------------------------|
    > | | | | The 20030228 vendor |
    > | Fresh ACPI-CA | -- | -- | sources have been |
    > | import | | | imported. Further testing |
    > | | | | is appreciated. |
    > |-------------------+--------+---------------+---------------------------|
    > | | | | PAE support allows the |
    > | | | | use of up to 64GB of RAM |
    > | PAE support for | -- | -- | on Pentium Pro and above |
    > | i386 | | | systems. Virtual |
    > | | | | addresses are still |
    > | | | | constrained to 32-bits. |
    > |-------------------+--------+---------------+---------------------------|
    > | | | | The recently upgraded |
    > | | | | if_wi driver is more |
    > | | | | tuned to Prism hardware |
    > | | | | than to Lucent hardware, |
    > | if_wi problems on | | | resulting in system |
    > | Lucent hardware | -- | -- | lockups and poor |
    > | | | | performance when using |
    > | | | | Lucent hardware. These |
    > | | | | problems are believed to |
    > | | | | be fixed but more testing |
    > | | | | is welcome. |
    > |-------------------+--------+---------------+---------------------------|
    > | | | | For 5.1-RELEASE, the |
    > | | | | default file system type |
    > | | | | for newly created file |
    > | | | | systems is UFS2 rather |
    > | UFS2 as | | | than UFS1. newfs(8) and |
    > | installation, | -- | Robert Watson | sysinstall(8) have been |
    > | newfs default | | | updated to use this new |
    > | | | | default. Testing to make |
    > | | | | sure all goes well after |
    > | | | | the change (committed on |
    > | | | | April 20, 2003) is vital. |
    > |-------------------+--------+---------------+---------------------------|
    > | | | | Support for pluggable |
    > | | | | directory services using |
    > | | | | NSS, including |
    > | | | | adaptations of current |
    > | | | Jacques | directory services (local |
    > | NSSwitch support | -- | Vidrine | databases, NIS), and |
    > | | | | support for new services |
    > | | | | (LDAP, Active Directory, |
    > | | | | etc). This change has |
    > | | | | been committed, and |
    > | | | | requires broader testing. |
    > |-------------------+--------+---------------+---------------------------|
    > | | | | Kris Kennaway reports |
    > | | | | that he has seen several |
    > | | | | unique panics on the |
    > | Spurious alpha | | | alpha machines, but since |
    > | panics | -- | -- | gdb -k doesn't work on |
    > | | | | alpha I haven't been able |
    > | | | | to get more than a DDB |
    > | | | | traceback. No-one has |
    > | | | | looked into them. |
    > +------------------------------------------------------------------------+
    >
    > ----------------------------------------------------------------------
    >
    > freebsd-qa@FreeBSD.ORG
    > Copyright (c) 1995-2003 The FreeBSD Project. All rights reserved.
    > Last modified: 2003/05/31 07:19:32
    _______________________________________________
    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: Sean Kelly: "USB Quirk Patch: SanDisk ImageMate CF SDDR31 (V:0x0781, P:0x0002)"

    Relevant Pages

    • RE: PAWS security vulnerability
      ... FreeBSD security list" isn't grammatically correct. ... "I told you to post the patch and info to the appropriate FreeBSD security ... "...This point and others are often discussed on the mailing lists, ...
      (freebsd-questions)
    • Re: freebsd-questions Digest, Vol 246, Issue 44
      ... Is aio or vm broken for FreeBSD 7-STABLE? ... Re: error: field 'aio_sigevent' has incomplete type (Mel) ... change root pasword ... # idiot autoresponder on freebsd lists, ...
      (freebsd-questions)
    • Re: cvsuping ports problem
      ... FreeBSD technical discussions mailing list.", ... cvsup, but it took me easy here. ... > When in doubt about which of the freebsd mailing lists is the correct ...
      (freebsd-hackers)
    • Re: file system setup for new system - recommendations?
      ... Your planned usage sounds alot like the way I use FreeBSD. ... config files and your personal data (unless you want to backup other boxes to ... very often like disklabel to partition or newfs, ... Web pages and mailing lists would be in home. ...
      (freebsd-questions)
    • Re: Cross platform building best practices (building 6 on 7)
      ... I've done a lot of Googling and scouring the lists about this ... No dice (and I'm still debugging why since this binutils ... need to bootstrap my dev environment for 6.x development on 7.x. ... I've run a FreeBSD 1.1 chroot on a freeBSD 7 system ...
      (freebsd-hackers)