From owner-freebsd-bugs Sun Feb 8 12:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28030 for freebsd-bugs-outgoing; Sun, 8 Feb 1998 12:10:04 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28024; Sun, 8 Feb 1998 12:10:03 -0800 (PST) (envelope-from gnats) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27550 for ; Sun, 8 Feb 1998 12:04:07 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id UAA03842; Sun, 8 Feb 1998 20:03:59 GMT (envelope-from nik) Message-Id: <199802082003.UAA03842@nothing-going-on.demon.co.uk> Date: Sun, 8 Feb 1998 20:03:59 GMT From: Nik Clayton Reply-To: nik@nothing-going-on.demon.co.uk To: FreeBSD-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: 3.2 Subject: docs/5681: Y2K bug / page submission Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 5681 >Category: docs >Synopsis: There is no FreeBSD Y2K statement on the web >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Feb 8 12:10:02 PST 1998 >Last-Modified: >Originator: Nik Clayton >Organization: Nik at home >Release: FreeBSD 2.2.5-STABLE i386 >Environment: N/A >Description: There is no (or at least, I can't find it) FreeBSD Year 2000 compliance statement available on the FreeBSD web site. There have been a few people posting messages to the -questions mailing list asking for one and receiving comments both from members of -core and from regular users of FreeBSD, some of which have been contradictory and/or vague. As the year 2000 approaches it seems reasonable to suppose that these sort of questions will increase. Hence my tagging of this PR with a severity of 'serious' and a priority of 'high'. Several people have said "Wouldn't it be a good idea to have something on the web site". No one appears to have done anything. So, being quite handy with HTML (and having a local copy of the web site available in CVS) I thought I'd dedicate a spare half hour to the task. Hence this PR. I've uploaded a file to ftp.freebsd.org that contains the following: - A new page for the website, y2kbug.sgml (yes, .sgml, I understand how the FreeBSD web site is generated). This page contains a quote from David Greenman, taken from e-mail sent to -questions, message-id <199802052355.PAA02722@implode.root.com>. I realise this is probably not the final form that -core will want, but it's probably a good starting point. - A diff to docs.sgml which links to the new page (since 'Documentation' seemed to be the best place to put it). This is docs.diff. - A diff to newsflash.sgml which talks about the new page (and will need changing before committing, because I couldn't state what day of February the newsflash will be updated. This is newsflash.diff - A diff to Makefile to reference the new file. Makefile.diff What I haven't done yet is make any changes to the FAQ. I imagine it'll be something like Q: Is FreeBSD Year 2000 compliant? A: The short answer is "Yes, with caveats". The long answer is "See the page at . Note: My suggested y2kbug.sgml page includes a section (currently empty) for listing applications which are known to have Y2K problems. I also suggest a new e-mail address, y2kbug@freebsd.org to be publicised as the contact point for people who have y2k questions about FreeBSD, and/or who have discovered that a particular application is not y2k compliant. I am volunteering to maintain this section and to be the contact point for that e-mail address (unless people think it would be better run as a mailing list). My proposed changes and additions can be found at: >How-To-Repeat: N/A >Fix: N/A >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message