From: Masato Motoike <Masato.Motoike@unisys.co.jp>
Real-Date: Mon, 23 Oct 1995 21:22:46 +0900
Subject: [infotalk,06147] Re: NTP (Re: real time? )
Message-Id: <199510231222.VAA01228@phoenix.22n.unisys.co.jp>
本池＠日本ユニシスです。
よろしくお願いします。
From: Kenji Rikitake <kenji@rcac.tdi.co.jp>
Subject: [infotalk,06044] NTP (Re: real time? )
Date: Tue, 17 Oct 95 20:32:18 +0900
> In message <199510170916.SAA10411@centipede.cs.shiga-pc.ac.jp>
> t2@cs.shiga-pc.ac.jp (Takaoka Tadashi) writes:
> ] え、皆さんのところはNTP (xntpd) は使ってらっしゃらないんでしょうか…。
>
> もちろん使っていますが :)
>
> UDPベースのNTPは同期が取れるまで時間がかかりますから、ダイヤルアップで
> は使えません。この場合は、TCPでNTPサーバに時刻を聞きます。これがntpdate。
>
> ntpdateで間欠的に時刻を修正しているホストでは、xntpdは使用ポート番号が
> かちあうので使えません。そこで、こういうローカルネットワークでは、
> timed (なんとなつかしい)を使います。4.4BSDのtimedは、自分がmasterであ
> ると宣言することもできるので、xntpdやntpdateで合わせた時刻情報の組織内
> での伝播にも使えます。
xntpもtimedもよくわかりませんので、教えて頂きたいのですが、
組織内にStratum1を立ち上げた場合に、timedとxntpdを同じサーバで
動かしてかまわないのでしょうか？
*** 本池正人[Masato.Motoike@unisys.co.jp] Nihon Unisys,Ltd. ***
From: Yutaka.Matsumoto@sun.co.jp (MATSUMOTO Yutaka - Sun JTC)
Real-Date: Mon, 23 Oct 95 10:46:03 JST
Subject: [infotalk,06146] Re: Q:ServerPush Amine contorol
Message-Id: <9510230146.AA20650@katsu.Japan.Sun.COM>
>ただ、コードを作るのが大変なようなことをいわれました。(^^;
>OOPSと言ってましたが、Objectもコードで記述するのかな ?
>そのうち簡単に作れるJavaエディタなんて出るんでしょうね。(^^
うーん、C++ ができる人なら、Java は難しくないと思います。
それから、既存の class を使っても結構いろいろとできるのでは
ないでしょうか？
# FYI: Computer Today の 1995/11 No.70 に解説記事がありました。
-- taka@Japan.Sun.COM
From: KOYAMA Noriaki / 小山徳章 <nori@ssel.toshiba.co.jp>
Real-Date: Mon, 23 Oct 1995 10:25:48 +0900
Subject: [infotalk,06145] Why is that mailcap ignored by netscape2.0b ?
Message-Id: <9510230124.AA10819@sel0.ssel.toshiba.co.jp>
小山@東芝と申します。
mailcap について質問させてください。
以下のようなMetaMAIL パッケージに付属していた mailcap を利用していたの
ですが、netscape2.0b でこれを利用すると、起動時に
Netscape: Ignoring unsupported format code in mailcap file: %{
というメッセージが表示されます。
1. この記述は一般的ではないのでしょうか?
2. 一般的な mailcap はどこから入手可能でしょうか?
情報をお待ちしております。
--
株式会社 東芝 システム・ソフトウェア生産技術研究所
小山 徳章 http://www.red.ssel.toshiba.co.jp/~nori/
nori@ssel.toshiba.co.jp, TEL:044-548-5479
--- mailcap here ---
# Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
#
# Permission to use, copy, modify, and distribute this material
# for any purpose and without fee is hereby granted, provided
# that the above copyright notice and this permission notice
# appear in all copies, and that the name of Bellcore not be
# used in advertising or publicity pertaining to this
# material without the specific, prior written permission
# of an authorized representative of Bellcore. BELLCORE
# MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
# OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS IS",
# WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.
#
# Prototype Mailcap file
# Note that support for text & multipart are "built in" to metamail,
# as are rudimentary support for message, and application.
# However, any of these may be overridden in mailcap.
#
# Note that users may override or extend this with a .mailcap
# file in their own directory. However, there is NO NEED
# for them to copy entries from this file, as metamail will
# pick up entries from both the system and personal mailcap files.
#
# Note that the effect of the following is to send ALL audio subtypes to the
# showaudio program, but to compose audio (e.g. in the mailto program)
# using "audio/basic" as the type.
audio/*; showaudio %s
audio/basic; showaudio %s; compose=audiocompose %s; edit=audiocompose %s; description="An audio fragment"
# The following line is for sites where xv understands jpeg but xloadimage is preferred.
image/jpeg; showpicture -viewer xv %s
# The following sends all other image subtypes to showpicture.
image/*; showpicture %s
# The following all appear AFTER the corresponding READING entries, and
# are for use in messages composition, e.g. in the "mailto" program
# In the following lines, the exit 0 junk is necessary because xwd
# doesn't always exit with a valid exit status!
# For sites with current (X11R5) pbm utilities
image/gif; showpicture %s; compose="xwd -frame | xwdtopnm | ppmtogif > %s\; exit 0"; description="An X11 window image dump in GIF format"
# The following line should be used instead of the previous by sites
# with old (X11R4) pbm utilities
#image/gif; showpicture %s; compose="xwd -frame | xwdtoppm | ppmtogif > %s\; exit 0"; description="An X11 window image dump in GIF format"
# For receiving X11 window image dumps from older versions of Andrew messages
image/x-xwd; showpicture %s; description="An X11 window image dump in X-XWD format"
message/partial; showpartial %s %{id} %{number} %{total}
message/external-body; showexternal %s %{access-type} %{name} %{site} %{directory} %{mode} %{server}; \
needsterminal; composetyped = extcompose %s; \
description="A reference to data stored in an external location"
# You can alter the above entry to only use certain access-types by
# adding a clause like the following before the "description=" line:
# test=test %{access-type} = mail-server; \
# If you have an interactive Postscript interpreter, you should think carefully
# before replacing lpr with it in the following line, because PostScript
# can be an enormous security hole. It is RELATIVELY harmless
# when sent to the printer...
application/postscript ; lpr %s \; echo SENT FILE TO PRINTER ; description="A Postscript File";\
compose="getfilename Postscript %s"
# The following should be commented out if you do NOT have safe-tcl
# and should be uncommented if you DO have safe-tcl
#multipart/enabled-mail; show-enabled %F
#application/safe-tcl; swish -safe -messaging -f %s
# The following should be commented out if you do NOT have atomicmail
# and should be uncommented if you DO have ATOMICMAIL
#application/atomicmail; atomicmail %s; compose=surveyor.am -p %s; description="An interactive ATOMICMAIL survey"
# The following should be used instead if you have atomicmail but not TK.
#application/atomicmail; atomicmail %s ; needsterminal
#application/atomicmail; atomicmail %s; compose=surveyor.am -p %s; description="An interactive ATOMICMAIL survey"; needsterminal
# The following give rudimentary capabilities to read old andrew format
# even to non-Andrew sites, since "ezview" comes with metamail.
x-be2; ezview %s ; copiousoutput
application/andrew-inset; ezview %s ; copiousoutput; edit=ez -d %s; compose="ez -d %s"; description="An Andrew inset/document"
# The following gives rudimentary capability for receiving
# text mail in the ISO-8859-1 character set, which covers many European
# languages, and the ISO-8859-8 character set, which includes Hebrew
# Note that the pipe to tr ensures that the "ISO" is case-insensitive.
text/richtext; shownonascii iso-8859-8 -e richtext -p %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-8; copiousoutput
text/richtext; shownonascii iso-8859-1 -e richtext -p %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-1; copiousoutput
text/plain; shownonascii iso-8859-8 %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-8; copiousoutput
text/plain; shownonascii iso-8859-1 %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-1; copiousoutput
text/enriched; shownonascii iso-8859-8 -e richtext -e -p %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-8; copiousoutput
text/enriched; shownonascii iso-8859-1 -e richtext -e -p %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-1; copiousoutput
# The following displays Japanese text at sites where the "kterm" program is installed:
text/plain; kterm -geometry +0+0 -e more %s /dev/null; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-2022-jp
text/richtext; richtext %s; copiousoutput
# If you have Andrew at your site, you MIGHT prefer to replace the
# above line with the following one, but probably won't because
# ez takes so long to start up.
# text/richtext; richtoatk < %s | ezview - ; copiousoutput
text/enriched; richtext -e %s; copiousoutput
# The following is a VERY rough cut at showing mail from Sun's openwindows mailtool
# Old version
# x-sun-attachment; sun-to-mime %s
x-sun-attachment; sun2mime %s
audio-file; sun-audio-file %s
postscript-file; lpr %s \; echo SENT FILE TO PRINTER
default; sun-message.csh %s %{encoding}; needsterminal
mail-file; sun-message.csh %s %{encoding}; needsterminal
sun-deskset-message; sun-message.csh %s %{encoding}; needsterminal
# The following is used for distributing metamail patches
# It should probably be used only by those administering metamail at a site.
# You will need to replace "source-tree-root" with the real root of your
# actual metamail source tree.
# You can also modify this line to get metamail patches from some trusted
# server other than thumper, if there is one -- man patch-metamail" for help.
application/x-metamail-patch; cat %s > /dev/null \; patch-metamail source-tree-root %{patchnumber}; needsterminal
# The following is for support of MacMIME, especially those
# the Columbia AppleTalk package (CAP) installed.
# For more info about MacMIME, send email to paf@nada.kth.se
#
# If you don't have CAP, and haven't changed rcvAppleSingle
# or sndAppleSingle, you should comment out this line.
application/applefile; rcvAppleSingle %s; compose="sndAppleSingle %s";description="An Apple Macintosh file in AppleSingle format"
#
# The following is for interoperability with Z-Mail version 3.0 and beyond.
# To enable this compatibility, uncomment all of the following lines.
#
# For more info about Z-Mail, send email to info@z-code.com
#
#application/x-movie; movieplayer %s; compose=moviemaker %s; \
# description="Movie"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/movie.xbm"
#application/x-inventor; examine %s; description="Inventor file"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/inventor.xbm"
#application/x-zm-fax; zfax %s; description="Z-Fax document"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/fax.xbm"
#application/x-showcase; showcase %s; compose=showcase %s; \
# description="Showcase document"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/showcase.xbm"
#application/x-jot; jot %s; compose=jot %s; description="Jot document"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/jot.xbm"
#image/x-sgi; ipaste %s; compose=imgworks %s; description="SGI image"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/image.xbm"
#audio/x-aiff; playaiff %s; compose=recordaiff -t 60 %s; \
# description="AIFF Audio"; x11-bitmap="/usr/lib/Zmail/bitmaps/sound.xbm"
#image/x-bitmap; bitmap %s; description="X11 bitmap"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/bitmap.xbm"
#image/x-xpm1; olpixmap %s; description="OL pixmap"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/bitmap.xbm"
#application/x-island-write; IslandWrite %s; compose=IslandWrite %s; \
# description="IslandWrite document"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/islwrite.xbm"
#application/x-island-draw; IslandDraw %s; compose=IslandDraw %s; \
# description="IslandDraw document"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/isldraw.xbm"
#application/x-island-paint; IslandPaint %s; compose=IslandPaint %s; \
# description="IslandPaint document"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/islpaint.xbm"
#application/x-framemaker; maker -f %s; compose=maker -f %s; \
# description="FrameMaker document"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/frame.xbm"
#application/x-wingz; Wingz %s; compose=Wingz %s; \
# description="Wingz document"; \
# x11-bitmap="/usr/lib/Zmail/bitmaps/wingz.xbm"
# Old Z-mail format
#x-zm-multipart: sun-to-mime %s
#Another suggested way to use FrameMaker
# application/x-framemaker; clclient -f %s \; sleep 60 ; \
# compose="getfilename FrameMaker %s"
# A common problem with the mailcap mechanism is getting differential
# behavior from different programs. This problem is compounded by the fact
# that some programs, notably Mosaic, do not implement the "test" clause in
# mailcap files. The following two mailcap entries should give you a model
# for a hack that will allow you to get differential behavior from Mosaic and
# metamail in spite of this fact. It exploits the fact that metamail always
# sets the MM_MAILER variable (if only to "unknown") while Mosaic does not.
#
# foo/bar; echo mosaic; test=test "$MM_MAILER" = ""
# foo/bar; echo not mosaic
From: ando@mc.nbu.ac.jp (ando)
Real-Date: Mon, 23 Oct 1995 09:44:08 +0900
Subject: [infotalk,06144] Q:Perl Beginer's guide (^^;
Message-Id: <199510230046.JAA17088@nbu-post.mc.nbu.ac.jp>
毎度！
私はMacユーザーなのですが、cgiはAppleScriptでいいかな ?と
思っていたのですが、やはりPerlの方がいいのかななんて思って
ます。(^^;
そこで、全然Perlを知らない私にナイスなPerlのオンラインドキ
ュメントなんてのがあれば教えて下さい。
＃ Perlを使えば、メールに自動応答なんてのが簡単に出来るそう
＃ ですね。(^^
大分県 安東
大分県 安東（NBUMUG参加者募集中 ! (^^)/）
MailingList - NBUMUG-request@mc.nbu.ac.jpへhelpメールを (^^
NetNews - nbu.nbumug
From: ando@mc.nbu.ac.jp (ando)
Real-Date: Mon, 23 Oct 1995 09:36:28 +0900
Subject: [infotalk,06143] Re: Q:ServerPush Amine contorol
Message-Id: <199510230038.JAA17041@nbu-post.mc.nbu.ac.jp>
皆さん、情報ありがとうございます。
私の作ったアニメションはcgiは使ってないのです。
（複数のGIFをまとめているだけなのです）
BINARY .PUSH * * multipart/x-mixed-replace;boundary=EOM
>>ページ全体がrefleshされるので、いやなんですよね...
同感です。(^^ この間、HotJavaを見せてもらったのですが、いいですね。
ただ、コードを作るのが大変なようなことをいわれました。(^^;
OOPSと言ってましたが、Objectもコードで記述するのかな ?
そのうち簡単に作れるJavaエディタなんて出るんでしょうね。(^^
ところで、日経Macなどで、NetScape2.0の新機能紹介で『インラインプラグイン』
が紹介されてましたが、これってもう使えるのでしょうか ?
HotJavaみたいにまだだめなのかな ? > Mac版 ?
大分県 安東 (^^)/
大分県 安東（NBUMUG参加者募集中 ! (^^)/）
MailingList - NBUMUG-request@mc.nbu.ac.jpへhelpメールを (^^
NetNews - nbu.nbumug
From: anchor@open.rd.nttdata.jp (Tatsuya Nakamura)
Real-Date: Mon, 23 Oct 95 08:23:25 JST
Subject: [infotalk,06142] Re: Q: how to make perl4
Message-Id: <9510222323.AA23865@mint.info.open.rd.nttdata.jp>
中村＠NTTデータ.技術開発本部です。いつもお世話になっております。
perl の件で多くの方からお返事を頂きました。津嶋さん(m2@soum.co.jp)に
頂きましたお返事にあるように、Configure で聞かれてくる
Do you wish to attempt to use the malloc that comes with perl?[n]
に "y" で答えるようにしましたところ、Solaris2.4 で無事 perl4.036 が動く
ようになりました。また、松田@阪大医学部分子生理化学教室さんか頂きました、
> solaris 2.4でperl5.001mは簡単にcompileできました。
perl5 は当方でも作ることができました。
ありがとうございました。
---
Tatsuya Nakamura : anchor@open.rd.nttdata.jp
NTT DATA COMMUNICATIONS SYSTEMS CORPORATION
Open Systems Center, R & D Headquarters
phone: +81 3 5546 9566, fax: +81 3 5546 9567