[Thread Prev][Thread Next][Thread Index]
Re: Y2K
- To: Alan.Harder@xxxxxxxxxxxx, Gary.Foster@xxxxxxxxxxxx, robert.anderson@xxxxxxxxxxx, dyep@xxxxxxx
- Subject: Re: Y2K
- From: Rob Anderson <robert.anderson@xxxxxxxxxxx>
- Date: Tue, 22 Jun 1999 15:32:52 -0700 (PDT)
- Cc: dyep@xxxxxxx, pilotmgr@xxxxxxxxxxxxxxxxxxxx
- Reply-to: Rob Anderson <robert.anderson@xxxxxxxxxxx>
> Date: Tue, 22 Jun 1999 17:23:17 -0400 (EDT)
> From: Dennis Yep <dyep@xxxxxxx>
>
> Do you mean that my Sun Calendar Manager can't schedule anything
> beyond the year 2000? I am using Pilot Manager V. 1.106 with
> OpenWindows V. 3.6 on a Ultra5 Sparc.
Opps! Looks like I created FUD with my mail. My apologies.
Sun has two possible Calendar Manager "clients" in Solaris, OpenWindows
cm(1) and CDE dtcm(1). They both support having your calendar local on your
machine via rpc.cmsd(1M). Client options for the Sun Calendar Server
product include Sun Web Access and Solaris Common Desktop Environment
(dtcm) client, using the "Internet Calendaring" (iCalendar) data format.
The Sun Calendar Server is Y2K compliant (yes, you can schedule beyond the
year 2000).
http://www.sun.com/y2000/warranty.html
http://www.sun.com/y2000/cpl.html
See also
http://www.sun.com/software/calendaring/faqs.jhtml#18
rob a.