waffle-faq

关于黑客的论坛的下载资料

cash for any but the most trusting sites.  unfortunately, it
does not work with 1.64-compatible config files.  it does work
with a variety of config files, including 1.65-compatible ones.

maybe with some messing about, it will work with 1.64 as well,
but it's probably easier to either write 1.65-compatible ones or
write one of the simpler supported formats from scratch.

uu_waf - long ago, I found patches to uupc's UUCICO which handled
waffle-style filename munging instead of uupc-style.  it was
[e-mail] -- I am verifying this address.


------------------------------

Subject: waffle: Miscellaneous
From: [e-mail]

1. How can I set my mail and news signatures to be different ?

It's built-in already.

The mailsig file is for mail, the sig file is for news.

The \waffle\system\sig file gets inserted if it's there and you
don't have a personal sig or mailsig file.

If you want to be able to pick which sig goes on which message,
try Roy Silvernail's APPSIG.ZIP .

2. Why doesn't /waffle/system/mailsig work?

The different names are only for the user's personal signature.
If you have a system default signature, /waffle/system/sig, it
is applied to *all* messages.

3. Can I use 16-bit compression ?

Sure, if you have enough memory and can find a 16-bit compression
program.

One is provided with 1.65 and there are a variety of add-in
16-bit compress programs for 1.64 and earlier available on SimTel.

If you use 16-bit compress, be sure you have the `compress' flag
in the static file set correctly for the compress you're using.
See \waffle\docs\comp16.doc .

4. What are all those files in \waffle\* anyway ?

See \waffle\docs\roadmap.doc for descriptions of almost every
file that comes with the software.

5. What document in \waffle\docs contains what ?

\waffle\docs\index.doc has the table of contents of each of
the other documents.  Use a text editor or something similar
to look for keywords in index.doc, then it will point you to
which file to look in.

If you have a version of the UNIX utility `grep', it's best
to do something like `grep keyword \waffle\docs\*', to find
even obscure references to things.

You'll find a lot of neat but obscure references in HISTORY.DOC.

6. Can I alter my headers after composing a message ?

Some of them are editable in 1.65 via the `alter' static parameter.
Don't put `To:', `CC:' or `Newsgroups:' in `alter'; it won't work.

Of course, third-party packages tend to not have these restrictions.

7. Does DOS Waffle support control messages ?

Other than cancelling a message you posted that hasn't been
batched up yet, no.  You might want to look at the contents of
the control newsgroup once in a while to see what control
messages you received that Waffle didn't process.

There's a program called procc, `PROCess Control' which will
handle control messages for you.  Look for procc-NN.zip where
NN is the version number.

There's also wafctl, Waffle Control, which does more than procc.
It will create files for nwreader to use to present users with
notices of new groups when the control messages come in.

8. What does this `Splash file before login' flag do?  I can't find it in
   the docs.

If a user logs in with the `Splash file before login' flag, and
a file exists in /waffle/text named after that user, it will be
displayed (`splashed') immediately after the user enters their
password correctly.  Example: user falken has `Splash file ...'
set in his profile:

        hogbbs!login: falken
        Password: 

        [this is /waffle/text/falken]
        (>

        Greetings, Professor Falken.  Would you like to play a game?

        [this is /waffle/text/welcome, which everyone sees]
        Welcome to the Heart of Gold
        ...


------------------------------

Subject: waffle: Waffle bugs
From: [e-mail]

As with any large system, Waffle has bugs.  Since the source is available,
some users have fixed some of the bugs that have cropped up.  In this
section, the notation `Patch: <user>' means that the mentioned user has
a patch to the source code available that will fix the problem.  You need
to already have the source code for this to be useful to you.  `BPatch: <user>'
means that the mentioned user has a binary patch available, which anyone
should be able to use.  `Fixed: 1.xx' means that the bug is fixed as of
the mentioned version.  `Workaround:' means that there is a way to avoid
the bug in normal operation.

1.  When I mail to a | post alias from within Waffle, it only posts the headers.

    This is a bug having to do with external editors.
    Workaround: use the internal editor when mailing to such an alias.
    Patch: [e-mail]
    Fixed: 1.66

2.  When I mail to a | post alias from within Waffle, it only works the
    first time; the second time it doesn't do *anything*.

    Workaround: none known.
    Patch: [e-mail]
    Fixed: 1.66

3.  I configured my modem to work with FAX, but Waffle keeps saying
    [Hayes code -2] and hangs up.

    This occurs if you have Auto-ATA: in your static file.
    Workaround: make your modem answer the phone (no Auto-ATA: in the
        static file and ATS0=1 in the initialize string).
    Patch: [e-mail]
    Fixed: 1.66

4.  I have personal aliases for `mom' and `dad', and when I type
    `mail mom dad' Waffle complains `No such user', even though I can
    type `mail mom' or `mail dad' and it works fine.

    Waffle's implementation of personal aliases isn't complete.
    Workaround: put the aliases in /waffle/system/aliases
    WARNING: This makes your aliases available to all users, so
    be _careful_ with what you put there.

5.  I have `finger_ok: 3' in my static file but anyone can use the FINGER
    command.

    Apparently, this check got lost somewhere; Waffle completely
        ignores the finger_ok: static variable.
    Workaround: None, save writing an extern to duplicate the
        functionality that you want, and controlling access to
        that via the extern files.

    [e-mail] says:

        Yes, this is not true for version 1.65. If you have an
        account with an user/access level less than finger_ok, you
        can finger the person but will not see their phone number,
        and, of course, you will see the phone number/etc. when you
        have the level greater or equal to finger_ok. I just even
        tried it.



6.  uux -b gives me garbage

    uux -b doesn't work.  try to use uux -i (if the files are on
    the same physical drive, ugh) or get a replacement uux.  one
    is ruux, hopefully on halcyon.

7.  rmail messes up headers with more than one space after the `To:'

    it doesn't hurt delivery, just makes the headers ugly

8.  rnews has a bunch of problems

    try the patched one from ftp://wiretap.spies.com/waffle/rnews.zip
    I still haven't tested all of these situations:

    outright errors:

        - long headers cause random crashes/exceptions

          -> these articles are now discarded, with a log entry in
             a new file called `badnews' in the admin directory

        - Path: checking does a too-sloppy substring match, so
          a site bar.foo.domain won't batch news for foo.domain
          (but there are no problems batching for news.foo.domain)

        - continuation lines are stripped

          -> still not fixed

        - batches articles with extra CRs in them cause spurious
          `truncated batch' warnings

    things that would be nice, and are already covered in other packages:

        - history

        - overview files

        - updating an active file, so that expiring every message in a
          group doesn't cause the counter to start back at `1'

        - filing control messages in control.<verb> groups
          (e.g., control.cancel, control.newgroup, control.rmgroup)
          if they have an entry in the active file


------------------------------

Subject: waffle: Transition to 1.65
From: [e-mail]

1. I updated my config files, but they didn't work.

Some of the config files, notably `paths', moved in 1.65 to the
new \waffle\uucp directory.  Make sure you aren't editing the file
in the old 1.64 location.

2. I'm going to run makebox.  Anything I should know ?

Yes.  Makebox deletes the old mail files after it assembles the 
new mailbox.  If you're paranoid, you might want to zip up your 
1.64 mail messages before running makebox if you're not sure you'll 
stay at 1.65.

In case you mess up, try to find a copy of `explode.zip' (it's on
ftp.halcyon.com in /pub/waffle/mail); it will take a 1.65 mailbox
back to 1.64 format.

3. 1.65 sure seems scary, why should I bother?

Lots of reasons.  See history.doc and release.165 for details.

Of course, if you're happy with the version you run, there's
not a lot of rush to get updated, though most of the c.b.w
readers keep at the current version and you'll get better help
from c.b.w by staying current.  In addition, there are
increasingly many utilities that will only work with version
1.65 .  However, there are still some Waffle sites at v1.61,
so obviously old versions still work.


------------------------------

Subject: waffle: Waffle and OS/2
From: [e-mail]

==begin FAQ caption==
  From: [e-mail] (Harrison Page)
  Newsgroups: comp.bbs.waffle
  Subject: Re: Waffle and OS/2?
  Message-ID: <[e-mail]>
  Date: Sun, 24 Jul 94 16:46:14 PDT

I've had good experiences with OS/2 and Waffle, through I am not running
a bulletin board system - just a site for news, mail, and a mail-based
archive server. I use the scheduler built into a Shareware utility for
OS/2 called FILEBAR (works great) and the stock UUCICO that comes with
Waffle.

Here's what I've gathered from comp.bbs.waffle over the last few months:

[e-mail] (Terry Stockdale) wrote:

> I similarly use Waffle for polling, but FXUUCICO under Waffle, and an
> external cron (cron213.zip) to handle rnews and rmail, as well as
> administrative tasks. I'm using RNF (now v.77beta9) and am very pleased
> with it.  Plus, it can keep my Waffle "join" file in sync with its
> rnfjoin file.  I've had good experience with Ray Gwinn's SIO/VSIO/VX00
> comm drivers (now sio126e.zip).

[e-mail] (KA6ETB Steve Harding) wrote:

[this section deleted -- see Steve's separate entry later]
==end FAQ caption==

==begin FAQ caption==
  From: [e-mail] (Mike Shirley)
  Newsgroups: comp.bbs.waffle
  Subject: Waffle & OS/2 Specific Mailing List; was Re: os/2 CRON
  Message-ID: <[e-mail]>
  Date: Wed, 07 Dec 94 20:50:03 -0800

To join the Waffle - OS/2 Mailing List, send a letter to:
[e-mail]     In the body on the first two lines enter:

join WaffOS2-L          (Case not important)
quit
==end FAQ caption==

==begin FAQ caption==
  To:     [e-mail] (Comp.Bbs.Waffle FAQ)
  From:   [e-mail] (KA6ETB Steve Harding)
  Message-ID: <[e-mail]>
  Date:   Sun, 22 Jan 1995 07:49:39 -0700

After doing some research, I have amended my portion of the OS/2 stuff.


Setting up Waffle in OS/2:
=========================

1.      Change the shell entry in your ~/waffle/extern file to read:

        shell   /command="x:\OS2\MDOS\COMMAND"

        where x: is the drive holding your OS/2 directories.

2.      If you are using a fossil driver, turn it off.

3.      Migrate Waffle to OS/2, and test.

4.      If you are using a CRON utility, migrate it, and test.  There
        are CRON utilities available for OS/2.

        Personally, I haven't had much luck with OS/2 versions starting
        DOS programs, but YMMV.  Using a CRON will allow you to let
        waffle handle the phone, and the second window do all the housework
        (uuxqt, batching, etc.).

Once Waffle passes the test, you can begin to tweak.

o       Install the SIO driver, available wherever fine OS/2 shareware
        is found.  The latest version is SIO142.ZIP.
o       Test.
o       If you must have a fossil, install VX00.SYS from SIO.
o       Test.

Once all tests are passed, create a shadow app of Waffle (and your CRON),
and place it in your Start Up folder.

TIPS:
====

o       If you have the disk space, and the patience, install wafcnews.

o       Most sites are using FXUUCICO.  I do not, as I notice no real
        gain here in throughput, and FX uses a different scheme for the
        UUCICO log file.

o       If you install OS2SPEED, set your STATIC multitask entry to
        multitask: desqview.  If not, set it to multitask: windows.

DOS SETTINGS:
============

DOS_AUTOEXEC            Create a special batch file containing appropriate
                        settings for Waffle, (WAFFLE emvironment variable,
                        etc.)  Do the same for your CRON, or put then in
                        the same batch file.

DOS_BACKGROUND_EXECUTION        on

IDLE_SECONDS            0

IDLE-SENSITIVITY        Experiment with this on your system.  The default (75)
                        is way too high.  I have mine set at 3.  Others use