HyperNews: Source: Installation

Table of Contents

• Overview of the Installation process
• Unpacking the source code
• Fixing the Perl Paths
• Setting up the HyperNews Document Directory
• Configuring HyperNews - setting the options that control how HyperNews works.
• Reinstalling HyperNews - when upgrading or fixing problems.
• Multiple Installations of Hypernews - when you want different groups of users or different configuration options.
• What's Next - Other installation related topics, including creating forums, adding members, writing instructions.
• Typical Problems - Look here first for problems that you might encounter while installing HyperNews.

Overview of Installation

These instructions are rather detailed, and many of the details may not apply to your situation. But you should skim over them just so you know what you are missing. With the state of web servers and browsers still changing rapidly, it is difficult to make systems that work in all possible situations, and so your best tool is knowledge.

Installation involves first unpacking the source code into a directory that allows CGI programs. Then you may have to fix the Perl paths in the scripts.

An important consideration is setting up the HyperNews Document Directory, referred to as $hndocs in this document and elsewhere. This is where all your forums, messages, and member info files are stored.

Then you will configure HyperNews to set the options that control how HyperNews works. You can do this via a web-based form or via direct editing of the configuration file, hnrc. When you eventually reinstall HyperNews to upgrade or fix problems, you can use a slightly easier process. You can also do Multiple Installations of Hypernews when you want different groups of users or different configuration options for sets of related forums.

See What's Next for an overview of other installation related topics, including creating forums, adding members, writing instructions. Also look in the section on Typical Problems that you might encounter while installing HyperNews.

Unpack the HyperNews Source Code

cd .../cgi-bin
gunzip hypernews.tar.gz
tar xf hypernews.tar

That will create the directory "cgi-bin/HyperNews###" where the "###" is the version number. You should change the directory name to remove the version number (e.g. just "HyperNews") before announcing availability. We don't recommend you leave the version number intact since you may later upgrade, and then the old version number would be inappropriate so every reference to your forums would have to be updated too.

All the scripts are stored in the "HyperNews###/.scripts" subdirectory, which may be invisible to you (use ls -a to see it). Make sure your tar extraction created a symbolic link from HyperNews/.scripts/.scripts to HyperNews/.scripts. Use ls -F to see symbolic link files with appended '@'.

You may want to change how your server is configured so you can avoid including "cgi-bin" in your URLs (or any other prefix, for that matter). Instructions for how to do that, and other server configurations, are given in the following sections.

After HyperNews is fully configured by running the setup.pl script (don't do it now), the other scripts in the .scripts directory will be "used" via the HyperNews directory and the Admin and SECURED directories. Not all scripts are available in all those directories, depending on the access control settings you choose. There are three ways that the scripts may be used: by pointing to them with "symbolic links", which is the easiest and the default, by so-called "hard links", and by copying them. You will need to use setup.pl with the --hardlink or --copy options to use the scripts that way. Copying the scripts is more awkward to deal with if you have to make any changes to the code or if you have multiple installations, but it is necessary on some servers that restrict use of links. The "hnrc" file will remember which way you set this option and do the same each time you run setup.pl or use a setup form. See more about running setup.pl below.

Apache and NCSA httpd

ScriptAlias /HyperNews/ <Your Directory>/HyperNews/

You may need to configure your server to loosen the restrictions on what scripts are allowed to do in your HyperNews directory. For example, in recent versions of Apache (1.1.1) the default for cgi-bin in access.conf is:

Options None
AllowOverride None

<Directory  <your-path-to>/HyperNews>
AllowOverride All
Options FollowSymLinks
</Directory>

For Apache 1.3 you may need to use 'Options +FollowSymLinks' instead, depending on how your server configures other directories. If you don't want to allow FollowSymLinks, or you are not permitted to change the restrictions, you can instead use the --hardlink or --copy options to setup.pl, described above.

Finally, restart (or kill -HUP) the server to cause the server to use your configuration changes.

CERN httpd

# HyperNews Protect clauses
??

# HyperNews Exec clauses
Exec    /HyperNews/SECURED/*    <Your Directory>/HyperNews/SECURED/*
Exec    /HyperNews/.scripts/*   <Your Directory>/HyperNews/.scripts/*
Exec    /HyperNews/*            <Your Directory>/HyperNews/*

# A version of the following line is already in the .conf file,
# and must remain at the end.
<Pass /*  /local/Web/* >

Depending on your configuration, you may also have to create .www_acl files in the HyperNews, .scripts, SECURED, and Admin directories. The setup.pl script may do this correctly for you already. It should probably contain:

 * : GET,POST : @*.*.*.*

Netscape Commerce Server

<Object ppath="/usr/ns-home/cgi-bin/HyperNews/SECURED/*">
AuthTrans fn="basic-ncsa" userfile="/usr/local/etc/httpd/htdocs/hn/hnpeople/.htpasswd" auth-type="basic"
PathCheck fn="require-auth" realm="HyperNews" auth-type="basic" auth-user="*"
Error reason="Unauthorized" fn="query-handler" path="/usr/ns-home/cgi-bin/pentauth.cgi"
AddLog fn="common-log" name="log0"
</Object>

Fix the Perl Paths

Set up the HyperNews Document Directory

Users and Access Restrictions

But we don't recommend you do the above if your server is shared by many other users or virtual hosts. This is because HyperNews writes its data onto disk, and so other users on the same system might otherwise have read or write access. Instead, use some setuid mechanism, described in the following sections.

There are two distinct sets of users to keep in mind, by the way. Unix users are one set; we are particularly concerned with the person who installs HyperNews via some Unix account (called the "installer" from now on) and the "user" (e.g. httpd) who runs the server. There may be many other Unix users on your machine that may have read, write, or execute permission on your files and directories. The other set of users are the people that access HyperNews via the web. This set of Web users includes all the users who identify themselves with User IDs as well as the anonymous users with no User IDs. It also includes the HyperNews administrators with special administrative powers. The Unix users and Web users are unrelated to each other although they may just happen to have the same identifiers used by the same people in some cases. Similarly, there are two different unrelated sets of groups: Unix groups and HyperNews or Web groups. The Web Server Groups are not used by HyperNews, except in old versions - instead, HyperNews defines and uses its own group mechanism.

If you wish to protect the privacy of messages, membership information, and all HyperNews data, and thus prevent unauthorized use, we need to arrange to change the Unix ownership of the files as they are written so they can only be read or written by the installer. The problem is that the server is typically run by another user, such as root, nobody, httpd, or something else. One solution is live with it as described above. The better solution is to arrange to have HyperNews be run as the same user who owns the scripts, namely the installer. Given this motivation, we can now describe several possible ways to make this happen.

Cgiwrap

To use cgiwrap (version 3.6 or later) with HyperNews symbolic links, you will need to make sure that it is configured using the --without-check-symlink option. Either that, or don't use symbolic links with HyperNews. (See setup.pl command line options below.)

The following instructions assume you are installing HyperNews in a cgi-bin directory that is accessed via your login ID. For example, the URL for HyperNews might be /loginID/cgi-bin/HyperNews, where loginID is replaced by your login ID. Or if you have a virtual (or real) domain, the URL might simply be http://your.domain/cgi-bin/HyperNews. If necessary, you might be able to make a symbolic link from cgi-bin in your personal public_html directory to the place where HyperNews is installed. There are other ways that cgiwrap can be used with different ways of configuring the server and installing HyperNews, but you're on your own for now.

If you are using server-based authentication (i.e. not using the HyperNews form-based $manualSecurity option), we need to do a bit more configuration. To get the server to authenticate users when using the cgiwrap program, we need to arrange that cgiwrap is accessed from inside the HyperNews subdirectories protected by the .htaccess files - this will cause the server's authentication (and access restrictions) to be applied. Here is what must be done:

cd cgi-bin
ln -s /full/path/to/cgiwrap cgiwrap

With that done, now we could access one of the scripts, say edit-article.pl, with the following URL:

http://your.domain/cgi-bin/HyperNews/SECURED/cgiwrap/<your-login>/HyperNews/SECURED/edit-article.pl

ScriptAlias /HyperNews/SECURED/ /full/path/to/HyperNews/SECURED/cgiwrap/<your-login>/HyperNews/SECURED/
ScriptAlias /HyperNews/Admin/ /full/path/to/HyperNews/Admin/cgiwrap/<your-login>/HyperNews/Admin/
ScriptAlias /HyperNews/.scripts/ /full/path/to/HyperNews/.scripts/cgiwrap/<your-login>/HyperNews/.scripts/
ScriptAlias /HyperNews/ /full/path/to/HyperNews/cgiwrap/<your-login>/HyperNews/

http://your.domain/cgi-bin/HyperNews/SECURED/edit-article.pl

ScriptAliasMatch ^/HyperNews(/SECURED|/Admin|/\.scripts)?/(.*) /full/path/to/HyperNews$1/cgiwrap/<your-login>/HyperNews$1/$2

ScriptAliasMatch ^/HyperNewsDebug(/SECURED|/Admin|/\.scripts)?/(.*) /full/path/to/HyperNews$1/cgiwrapd/<your-login>/HyperNews$1/$2

Setuid

suEXEC

Also, due to a possible bug in suexec, the symbolic links to HyperNews scripts will not work. Instead, you must use setup.pl with --copy or --hardlink to copy or hard link the scripts instead of symbolically linking to them.

One more thing: the script directories might have to be made non-group-writable before the scripts will execute. This may mean that you cannot use setup-form.pl to do the installation via the web; if so, you must use setup.pl from the command line instead.

Other Access Restriction Issues

You might want to restrict read access for the HyperNews document directory so the server only allows HyperNews members or admin to read the files directly. HyperNews setup will do this for you if you make reading restricted to members only.

The Icons directory needs to be accessible via the server, and it should probably not be restricted (you don't want users to get an authentication dialog for each icon), so you should probably put it somewhere outside of the $hndocs directory if the document directory is restricted.

Bug: If you change your $hndocs directory between multiple calls to setup, the setup process may not change the $hniconsURL accordingly so it will not point to the same directory as $hnicons. For now, just fix it manually in the hnrc file.

The hnpeople directory (in your $hndocs directory by default), where all the member information goes, is protected by the same .htaccess file as the HyperNews/.scripts directory so only administrators have access to it. The HyperNews/SECURED directory is protected by hnpeople/.htgroupmembers, and you can also use this in other directories just by linking to it.

Configuring HyperNews

The result of configuring HyperNews is that directories will be created as needed to contain links to scripts, access restrictions, icons, forums and messages. Also, a configuration file named "hnrc" is created in your HyperNews/Admin directory that sets all the variables that control how HyperNews works.

HyperNews is configured by executing a setup script in one of two ways. The first way is via the command line (i.e. in a unix "shell"): HyperNews/.scripts/setup.pl. (Also HyperNews/Admin/setup.pl after version 1.9.4.) The second way, via the web with a browser, is discussed below. You can actually use both ways of calling setup.pl one after the other, and you will need to run from the command line to do many options not available via the web interface.

Running setup.pl

The first time you run setup.pl, if no hnrc file exists, one will be created with default values. Edit this file to set the values to what you want and run setup.pl again. The comments in the hnrc file are probably not sufficient for you to know what to set the values to. It would be best for you to use the second way of configuring HyperNews, described next, at least to read the documentation it contains. But there are several configuration options only available in the hnrc file, at least for now.

The setup.pl script also has several options that can be used from the command line. To see a description of these, run setup.pl --help.

Running setup-form.pl

  http://<your.server>/HyperNews/.scripts/setup-form.pl/

If you see code instead of the HTML text and form that was supposed to result from executing the code, then you need to do something to make the server execute the code instead. You might need to change your server configuration regarding cgi-bin executables; see the earlier discussion on that issue. An alternative is to use setup-form.cgi instead; it is linked to setup-form.pl, so you can use that instead if your server requires a ".cgi" suffix.

Here is a (somewhat obsolete) sample of what the setup-form looks like.

The setup-form provides many of the common configuration options, but there is a simpler form with fewer option available, called setup-short-form.pl, that you may try instead.

After you fill out the form and submit it, several things will be checked, and if all is OK, several things will be created or updated. The results of that process will be displayed to you.

You will need to make your HyperNews cgi directory and the .scripts and Admin subdirectory writable by the server temporarily before you submit the form, so it can build the appropriate links to the scripts and add access restrictions to the directories. However, it is not wise to leave the directories in this writable state after you are done configuring HyperNews.

After you submit the setup-form.pl form the first time (or after you run setup.pl from the command line for a second time), HyperNews will create the access restriction files, so you will have to authenticate as one of the administrators for subsequent attempts. New administrators (i.e. those who do not have a password already) will be given empty passwords. Remember to change your admin password. You won't be able to use any admin userid until you do change the password.

If you forget all your administrator passwords, you have a problem since HyperNews doesn't store unencrypted passwords for security reasons. You can manually edit the member info file for an administrator to make the Password field empty, but this will work only if HyperNews is doing the authentication rather than your server. Or you can remove an admin member info file entirely and run setup.pl again from the command line. That will create a new member info record for you with a blank password.

[The CERN server requires that user IDs must be nicknames only - no email addresses (or no dots in the user ID anyway). (This is not checked by HyperNews, unfortunately.) So the passwords that will be generated for new administrators will not be emailed to them - even more reason to remember the passwords when they are given to you. The CERN server is no longer recommended anyway.]

Other Configuration Issues

When you consider what access permissions to allow for your installation, note that there is a conflict in allowing anyone to join while only allowing members to read. We wanted to leave the 'get' script where it is whether or not there are access restrictions, so you would not have to change URLs if you change the access restrictions from public to private or vice versa. Therefore, when reading is restricted to members only, everything is restricted including the registering of new members. You can work around this problem by manually putting links to the edit-member.pl and change-member.pl scripts in another directory that does not have access restrictions (i.e. not a subdirectory of your HyperNews directory), and also make links in that directory to the hnrc file and to the .scripts directory so that the scripts can execute properly. (You may also need to change the link to the change-member.pl script in the hnrc file, but I believe that should not be necessary.)

If your server restricts access independent of HyperNews, you might be able to use that with HyperNews. If the restriction is by domain, then the server only knows that users come from the specified domain(s). But if the restriction is to a set of users, HyperNews can use the info for its authentication. Just configure HyperNews to allow reading, etc by anyone, and HyperNews will detect that users have been authenticated by the server already. However, server authentication will not by itself provide personal info, such as the user's name and home page, and more importantly, whether the user is an administrator. So you will have to use the edit-member.pl form to join members using the same user IDs. Administrators are identified only in the setup process.

If you want HyperNews to manage the same password file as is used outside of HyperNews, you should probably be able to do this by configuring HyperNews to use the same file. See $hnPassword in the hnrc file. Managing the group files is a different story; HyperNews checks whether a user is a group member itself rather than using the server's mechanism. (Also see the $externalSecurity option in hnrc file.)

HyperNews includes optional use of DBM password files with the Netscape server.

Caching

You must first set $supportCaching = 1 in the hnrc file. The default is 0 because people still have problems dealing with caches, and it is better if they are at least aware of the presense of caching.

# Whether HN should support cachability of HN pages.
$supportCaching = 1;

You should also consider setting up a caching server to run in front of HyperNews. This is one of the best ways to easily improve performance of your HyperNews installation since the generation of pages can add up for a large forum. Squid is a very good free software caching server that can be configured as "an httpd accelerator". Nothing more needs to be changed in HyperNews to support server-side caching; the remainder of the setup resides in your caching server and regular HyperNews server. Make your caching server run as if it were the real server, and have the cache forward requests to your HyperNews server, which might run on the same machine but with a different port number.

Reinstall New HyperNews Source Code

You may want to copy the hnrc file from the old version over to the new version before running the configuration script; this way you will get whatever settings were used previously by default. (Note that the location of hnrc in older versions was in the HyperNews or HyperNews/.scripts directory. The setup scripts will look for it both old places. In 1.9.4, we moved it to the Admin directory, where I think it will stay.)

If you are using cgiwrap, you will need to make a new link to it in the new installation.

When you are satisfied that the new installation works, then just swap it in by changing directory names (e.g. mv HyperNews HyperNews.old; mv HyperNews1.9.6 HyperNews). (Actually, you probably don't want to do this casually because someone might be in the middle of an operation such as writing a message; this could be a problem when security options change or the names of scripts or form fields change. To be extra safe, shut your server down temporarily.) Let us know if you have any problems doing this.

Makefile

When installing HyperNews for the first time, it is typically more work because many issues need to be worked out. It would be nice if an autoconfig or Perl Makefile.PL installation process could be used, but I don't know one that has been adapted to know about CGI programs and web servers. Please let me know if you come across one.

Nevertheless, I use the following procedure:

cd HyperNews###/.scripts
# Edit fixPerlPath, then do:
make fix
make setup
# Edit Admin/hnrc, fix other things, such as hndocs, then do:
make setup
make install

cd HyperNews###/.scripts
make copyconf  # This copies configuration info from HyperNews.
make fix
make setup     # Repeat as needed to change configuration.
make install

make undoinstall

cd HyperNews/.scripts
make clone
make copyconf
make setup
make install

make dist   # Create hypernews.tar.gz
make docs   # Create hndocs.tar.gz

Multiple Installations

A future version of HyperNews will make multiple installations even easier, but for now, you have to do it manually. First install HyperNews normally as described above with the group (specified in $hnGroup) having no name. This will establish the "root" level and corresponding root level administrators.

Then, for each new installation, make a new directory. This directory may be anywhere, and in particular, it may be a subdirectory of the HyperNews directory (though that might make upgrading HyperNews more complex because you cannot just replace the HyperNews directory). You may want to add more ScriptAlias directives to your server configuration (or whatever is appropriate for your server) for these additional script directories.

In the directory for an installation, make an Admin subdirectory, and copy the hnrc file from the first installation into Admin, if you want to use that for default configuration. What you change in the configuration of this installation depends on why you are doing a separate installation - change whatever is appropriate and share the rest. Make a symbolic link from the ".scripts" subdirectory to wherever the .scripts directory in the first installation was (e.g. ln -s ../HyperNews/.scripts .scripts). Then open setup-form.pl in the new directory, just as for a normal installation. In the $hnGroup field, you can specify the name of a group if you want the membership to be different than that of the "root" installation. Otherwise, you can leave $hnGroup as it is.

If you are running setup.pl from the command line, since the .scripts directory is a link, running "setup.pl" or "./setup.pl" in that directory will assume you mean the root installation. So try ".scripts/setup.pl" or "Admin/setup.pl" instead, starting from the correct parent directory. If you use the setup form, and you link all the subgroup .scripts directories to the root level .scripts, then the administrators for the root level are the only ones who can setup subgroups.

For example, let's make an installation of HyperNews for a group called 'Staff. We already have 'HyperNews' installed in one directory as the 'root' installation, and we want the Staff installation at the same level. Do the following:

$ cd cgi-bin
$ mkdir Staff
$ ls -F
HyperNews/    Staff/
$ cd Staff
$ mkdir Admin
$ ln -s ../HyperNews/.scripts .scripts
$ ls -aF
./         ../        .scripts@  Admin/
$ cp ../HyperNews/Admin/hnrc Admin
$ cd Admin
$ ln -s ../.scripts .scripts
$ vi hnrc     # Change configuration of this installation.
$ ./.scripts/setup.pl  # Execute setup.pl from the command line.

You can use the .htaccess files that HyperNews already produces by linking to them. To protect your "hn" directory, do:

cd hn; ln -s hnpeople/Admin/.htgroupaccess .htaccess

If you restrict access to your $hndocs directory, you should probably also change $hnicons and $hniconsURL to be outside of the $hndocs directory then, so they will remain publically accessible, and sharable. The Icons should probably *not* be protected, otherwise people may get authentication requests for the first 4 icons (if the brower makes 4 simultaneous requests).

To share membership files across installations, and thus share password files, in each installation, simply assign the $hnPeople variable to the same directory. You should probably move the $hnPeople directory out of the $hndocs directory for this purpose. (Note that the default value for $hnPeople in the setup-form is relative to the $hndocs.) The $hnGroup subdirectory of $hnPeople will list only the members of that group. Use the edit-member.pl function for the group to add members to that group. Adding a member to a group also adds the same member to parent levels all the way up to the root.

Since adding a new group requires some manual installation in the file system, there is no risk that anyone but the installer could do so. In the future, we will supply a script to do this more automatically, and then only the admin for a group would be allowed to add a subgroup.

Cookies

To enable this use of cookies, you must edit your hnrc file to change the $UseCookies and $HNCookiePassword variables. (You don't need to run setup.pl after making this change.) If you set $UseCookies to 'sometimes', each user will have the option to use cookes for their own access.

What's Next?

You also may want to add some additional members via your browser using the edit-member.pl program. See the instructions for becoming a member. Alternatively, there is a batch-add-members.pl script for adding many members at once.

In the current version of HyperNews, the only way to remove members once you have added them is manually. To do that, go into your hnpeople directory and remove the files corresponding to members you want to remove. Also remove them from the .htpasswd file.

Next, create some forums (also called base articles). If that fails, you probably have an installation problem so return here to check that you did everything correctly.

HyperNews provides support for a two-way email gateway. If you want to allow only outgoing email or also incoming email, see that page for documentation.

A number of additional customizations are available in the hnrc file. One feature that is frequently asked for is reversing the order of the messages. See $reverseMessages for that.

Another frequent request is for a way to notify all members. Please see the discusion on the All-Member notification feature. (This needs to be properly written up, as do many other features.)

User Instructions

By default, the variable $instructionsURL in hnrc references our instructions at " http://www.hypernews.org/HyperNews/get/hypernews/instructions.html". The $instructionsURL variable could point to either a HyperNews page that you create, or to a normal page. You can continue to point to our instructions, but I would prefer that you not do that because users often get lost on my server thinking they are on your server. On the other hand, if you don't customize your instructions, you might as well point to ours.

(But please do not just copy the HTML of the instruction forums themselves; although it will appear to be a working forum to users, the copy you get will not be updated even though the controls will work to add messages to the HyperNews.org instruction forums. Everyone will be confused.)

• Creating and Editing Forums (also called base articles).
• Two-way E-mail gateway.
• Membership - how to register at a HyperNews site, and what it means.
• Other Security Issues regarding HyperNews.
• Installation instructions in Japanese - old version

Typical Problems

If you get a permission problem saying that some file could not be written, or perhaps files are silently not being written, this is probably a permission problem. Most likely, the user:group running your server is incompatible with the owner:group of the files or directories it is trying to modify. See the section above on setting up your Documents Directory. The same issues apply to the HyperNews program directory and subdirectories, although after installation is completed, these directories and script files should not be modified.

If you get an error about an UnknownUser when you try to create a forum, this is probably because the server is not properly authenticating you. Check how your server is set up to do authentication and then check whether HyperNews has set up the access files correctly to use the server's authentication. The HyperNews programs should see the REMOTE_USER if all is correct.

If you get an error when adding a message but the message gets added anyway (do a reload to find out), one cause for this is that outgoing email is failing for some reason. One reason it fails on some systems is that you have not set up an email alias for the address named by your $mail_to variable, which is 'HyperNews' by default, and for $mail_from, which is 'Owner-HyperNews' by default. See your hnrc file and the email gateway forum for details. You can also fix this by turning off email subscription and notification either in the setup form or in the hnrc file.

1 HyperNews' setup-form wants to tack on a unix path to a URL. by Steven Peterson, 1996, Feb 01

1 SCRIPT_NAME inconsistency by liberte@hypernews.org, 1996, Feb 01

Hoping to avoid further problems . . . by peterson@frontier-news.com, 1996, Feb 01

No end of problems, from my perspective anyway by liberte@hypernews.org, 1996, Feb 01

Oops - my mistake by liberte@hypernews.org, 1996, Feb 01

hndocsURL still used by jay mortensen, 1996, Feb 08

2 hypernews and NT , 1996, Feb 01

3 I'm having problems getting the program to use .cgi files by Steven Peterson, 1996, Feb 02

1 Should work now by liberte@hypernews.org, 1996, Apr 05

4 re-building group/password files makes bad group files for NCSA httpd by Blaine Price, 1996, Feb 11

1 1.9B5.2 might fix it by liberte@hypernews.org, 1996, Feb 12

5 Dutch FreeNet seelks help installing HyperNews by Digitaal Limburg, 1996, Feb 14

1 Dutch FreeNet has succeeded in installation by digilimb@dds.nl, 1996, Feb 21

6 HyperNews Problem by Lorne Dmitruk, 1996, Feb 15

1 Partial Fix so Far by dmitruk@ccism.pc.athabascau.ca, 1996, Jan 28

Try these versions by tanaka@ngdc.noaa.gov, 1996, Feb 05

7 Can I install HyperNews? I am not an administrator. by Young Jik Kwon, 1996, Feb 15

1 yes you can , 1995, Dec 17

3 Slightly different problem by gcle@eo.net, 1996, Apr 23

1 Installation Requirements by liberte@hypernews.org, 1996, Apr 23

... 2 Message(s)

4 I did, here's how by krowitz@tiac.net, 1996, Oct 01

5 Has anyone installed HN with CGIWrap ? by cls@greens.org, 1996, Nov 20

8 Snags in configuration for Linux by Larry Mills-Gahl, 1995, Oct 18

1 problems resolved (for now) by lmg@webfarm.com, 1995, Oct 19

some comments by nesta@cynico.com, 1995, Nov 03

9 What to add to NCSA's srm.conf by Ken Tanaka, 1996, Feb 23

1 Dan fixed it by tanaka@ngdc.noaa.gov, 1996, Feb 24

10 I'm having problems with Perl when running setuid HN scripts by Patrick Petit, 1996, Mar 11

11 add-article: Error 403 Forbidden - access to file is never allowed [no ACL entry] by Greg Houston, 1996, Mar 12

1 Internet Office Server == CERN? by liberte@hypernews.org, 1996, Mar 15

12 adm with no password by Samba DIALLO, 1996, Mar 12

1 I have the same problem by cismas@ba-is.gsu.edu, 1996, Apr 17

1 It scrolls off by debbiev@3hourtour.com, 1998, Jan 15

... 1 Message(s)

2 found fix for missed initial password by ktohg@tritarget.com, 1998, Jun 09

13 Adding Icons by Magnus Rydin, 1996, Mar 20

1 You just .... by webmaster@itk.mh.se, 1996, Mar 20

2 How about multiple icons per message by cls@truffula.sj.ca.us, 1996, Nov 21

1 Idea: How about multiple icons per message by liberte@hypernews.org, 1996, Nov 22

...

14 Problems with .htgroupmembers creation by Francisco M. De La Vega, 1996, Mar 22

15 HyperNews and Caldera desktop.... by David Black, 1996, Mar 27

1 Never mind - just needed to add a perl link by dblack@icarus.shu.edu, 1996, Mar 27

16 Untitled , 1996, Apr 02

17 Problem setting up notification on UnixWare system by Kurt Schweitzer, 1996, Apr 03

1 I'm not much help by liberte@hypernews.org, 1996, Apr 08

18 Unable to add Response by Nazim Rahemtulla, 1996, Apr 01

1 Member only responses works in 1.9B5.6 by liberte@hypernews.org, 1996, Apr 08

non-member responses? by dma@aei.ca, 1996, Jun 19

19 My .hngroupmembers keeps being flushed! by Johan Edbäck, 1996, Apr 03

1 I got the same problem!! by fvega@gene.cinvestav.mx, 1996, Apr 18

Perl 5.000 is at fault by liberte@hypernews.org, 1996, Apr 18

20 Help - I cant get B5.6 to use B5.1 articles by Robert Thompson, 1996, Apr 11

1 Socket problem by liberte@hypernews.org, 1996, Apr 11

21 Changing the background colour by Graham Cleverley, 1996, Apr 17

1 Customize $bodytag in hnrc or using setup-form.pl by Daniel LaLiberte, 1996, Apr 17

is it impossible from base-article.pl? , 1997, Oct 28

1 This is pretty cool by trician@usa.net, 1998, Aug 03

2 Untitled by trician@usa.net, 1998, Aug 04

3 URL by trician@usa.net, 1998, Aug 04

22 The bottom of the main page...? by Haralds Jass, 1996, Apr 20

23 Can't even get setup-form.pl to run without an error by Randy Burgess, 1996, Apr 21

24 Removing the "Frames" option by Graham Cleverley, 1996, Apr 21

1 Piece of Cake by liberte@hypernews.org, 1996, Apr 22

2 Starting in Frames by vick@blau.net, 1997, Jan 21

25 1.9B5.5 My $defaultNotification checkbox is not working by Gonzalo Perez C., 1996, Apr 22 [Moved]

26 Running HyperNews under Netscape Server, anyone? by Roland Siebelink, 1996, Apr 23

1 Fix posted already by liberte@hypernews.org, 1996, Apr 23

27 Server protection setup error , 1996, May 05

1 Position of additions to httpd.conf is critical by Nigel.Gilbert@soc.surrey.ac.uk, 1996, May 12

28 setup.pl has syntax errors according to my perl v. 5.002 , 1996, May 07

1 I have the same problem. Have you solved it? by gorlando@calnet.it, 1997, Mar 20

Solution is to make sure you are using Perl 5.002 or later. by liberte@hypernews.org, 1997, Mar 20

29 base article no show, instead 'connection timed out' , 1996, May 07

1 Fetching via http confusion by liberte@hypernews.org, 1996, May 16

30 Password not accepted , 1996, May 12

1 Authorization fails by rfwilson@wilsonweb.com, 1996, Jun 14

More authorization woes by dma@aei.ca, 1996, Jun 19

31 Add article prob after upgrade , 1996, May 16

32 Problem with Solaris 2.5 , 1996, May 20

33 Setup under Pre-Protected area , 1996, May 22

34 problem with member change form , 1996, May 23

1 further diagnosis: it's Mosaic's fault by bailin@faraday.physics.utoronto.ca, 1996, May 23

1 Which Mosaic? by liberte@hypernews.org, 1996, May 23

...

2 I was afraid of this by liberte@hypernews.org, 1996, May 23

1 clarification and partial solutions by bailin@faraday.physics.utoronto.ca, 1996, May 23

...

35 Internal error: execve() failed , 1996, May 23

1 Not sure - things to check by liberte@hypernews.org, 1996, May 23

36 Multiple Installations , 1996, May 24

1 Build your own index of forums by liberte@hypernews.org, 1996, May 24

1 This is very site-specific by jtara@stockclub.com, 1996, May 25

...

2 hnroot.html by hu, 1997, Mar 17

...

37 Why do I need to log in to see my icons , 1996, May 31

1 Access restriction probably accidental by liberte@hypernews.org, 1996, May 31

Thanks by carryer@vdr.stanford.edu, 1996, May 31

38 Adding / Deleting and administrator for a HN site , 1996, May 31

1 It's crude, I know by liberte@hypernews.org, 1996, May 31

39 need to change how membership info is stored , 1996, Jun 05

1 Don't forget the htgroupmembers file by liberte@hypernews.org, 1996, Jun 05

one file bad. directories? by bailin@faraday.physics.utoronto.ca, 1996, Jun 06

Question: one file bad. directories? by liberte@hypernews.org, 1996, Jun 06

40 Problem of reinstallation , 1996, Jun 06

41 HELP! I cannot execute setup.pl wihtin Indy and perl 5.002 , 1996, Jun 11

1 Must not be Perl 5.002 by liberte@hypernews.org, 1996, Jun 11

42 Lost Icons , 1996, Jun 15

1 Full URLs are the cause by liberte@hypernews.org, 1996, Jun 17

43 setup-form.pl NOT a html document , 1996, Jun 17

1 setup-form.pl should be executable by liberte@hypernews.org, 1996, Jun 17

How to make HyperNews and .scripts cgi-bin directories? by ktuoc@nosc.mil, 1996, Jun 24

44 I can't find out how to display "default" page by eks, 1996, Jun 18

1 Untitled by liberte@hypernews.org, 1996, Jun 18

45 Intermittent "Document contains no data" error by Jonas Larsson, 1996, Jun 25

46 Install fails at fixPerlPath (CND 1.0) , 1996, Jun 30

47 Workaround for fixPerlPath problem by Tim Bird, 1996, Jul 01

1 Great, it worked! by tallyho@voicenet.com, 1996, Jul 08

1 fixPerlPath changes by lmg@webfarm.com, 1996, Jul 12

...

2 Thankyou so much you little beatuityti! by jonhassall@innotts.co.uk, 1996, Sep 13

49 problem with 'get' , 1996, Jul 05

1 Must be server problem by liberte@hypernews.org, 1996, Jul 05

50 Setup fails at end (can't write to Admin/shlock? by Lee Marzke, 1996, Jul 08

1 Setup error by tallyho@voicenet.com, 1996, Jul 10

2 Fixed by tallyho@voicenet.com, 1996, Jul 26

51 setup is fine but cannot create base articles or members by Maida, 1996, Jul 17

1 TCP Error sounds unrelated to HyperNews by liberte@hypernews.org, 1996, Jul 23

52 Get scripts does not get! by Eric RAGONE, 1996, Jul 17

1 SPINNER's fault by Robert.Andersson@cling.gu.se, 1997, Jan 22

2 Solution... by Robert.Andersson@cling.gu.se, 1997, Jan 22

53 Help to install Hypernews by B. Raven, 1996, Jul 28

54 lock error while adding users by Brian Swail, 1996, Jul 30

55 Notification...All postings to all users? by jvolkmann, 1996, Aug 02

56 Newbie: Why does it send e-mail to HyperNews? by Brian O'Neill, 1996, Aug 08

1 Because it has to go somewhere by liberte@hypernews.org, 1996, Aug 08

57 Help - need flush.pl! by Ryan Huebsch, 1996, Aug 14

58 Error creating base article and edit member by KhongTuoc M. Tran, 1996, Aug 14

1 Authentication problem? by liberte@hypernews.org, 1996, Aug 15

59 installation problem by Brian, 1996, Aug 15

1 More details please by liberte@hypernews.org, 1996, Aug 15

61 INSTALL ON UUNET?? by hari sekhar, 1996, Aug 28

1 What's rbox? by liberte@hypernews.org, 1996, Aug 28

62 Install problem, Can't locate NDBM_File.pm by Lee Marzke, 1996, Aug 28

1 Perl problem? by liberte@hypernews.org, 1996, Aug 29

1 Possible Fix for Perl Problem .. Can't find .. NDBM_File.pm .. by thompson@ids-scheer.com, 1996, Oct 01

...

2 It worked before... by alex@turing.kronos.com, 1996, Sep 18

3 HPUX Can't locate NDBM_File.pm in @INC by stevei@fourgen.com, 1996, Nov 01

1 Some Perls have it, some don't by liberte@hypernews.org, 1996, Nov 01

...

63 would like to remove HTML/URL options from setup by Eric Lofland, 1996, Aug 29

64 1.9.1 under AIX: weird hnrc problem by Kenneth C. Schalk, 1996, Sep 03

1 1.9.1 under AIX: weird hnrc problem by liberte@hypernews.org, 1996, Sep 04

Nope, no single quotes here. by ken@imlab.landarch.uiuc.edu, 1996, Sep 04

More: Nope, no single quotes here. by liberte@hypernews.org, 1996, Sep 04

65 1.9.1 under AIX: wierd hnrc problem by Kenneth C. Schalk, 1996, Sep 03

66 How to setup by Guillermo Schwarz, 1996, Sep 05

1 Missing flush.pl , 1996, Sep 09

67 How does hnrc relate to setup-lib.pl when running setup.pl ? by Donald Payne, 1996, Sep 10

1 Running from command line vs running from web by liberte@hypernews.org, 1996, Sep 10

68 Anyway to disable all email stuff thru hypernews ? I don't have mail on my web account by Jon Hassall, 1996, Sep 11

69 I'm Sorry, but Isn't HyperNews a bit difficult to install by Jon Hassall, 1996, Sep 11

1 Possibly, but for select configurations only by liberte@hypernews.org, 1996, Sep 11

4 Isnt HyperNews.org. a bit difficult to install? by Kdelphi95@aol.com., 1999, Apr 22

70 Help ! What is the code for this server ? by Jon Hassall, 1996, Sep 12

71 Non-profit org needs tech to install Hypernew to new web site.HELP! by Scott Morris, 1996, Sep 13

72 Another problem. Fix perl paths. Please help by Jon Hassall, 1996, Sep 13

73 Inside BODY tag ?? by Nick Pollitt, 1996, Sep 14

1 Body tags by kellyj@bah.com, 1996, Sep 30

74 requiring 5.002 is silly, i have perl 5.003! by jon madison, 1996, Sep 25

1 requiring 5.002 is silly, i have perl 5.003! by liberte@sdgmail.ncsa.uiuc.edu, 1996, Sep 26

75 Problem with HN 1.9B5.7 by Petter Gisslen, 1996, Sep 26

1 Problem with configuration? by liberte@hypernews.org, 1996, Sep 26

No trailing '/' by webmaster@itk.mh.se, 1996, Sep 30

Check permissions by liberte@hypernews.org, 1996, Oct 01

Same problem! by pedlefsen@wesleyan.edu

76 Are the all the pages CGI generated when requested by michael swertfager, 1996, Oct 01

1 no by jim@rollercoaster.com, 1996, Oct 02

Appearances are deceiving by liberte@hypernews.org, 1996, Oct 02

77 Frame layout - can it be changed? by Donald Payne, 1996, Oct 03

1 Question: Frame layout - can it be changed? by liberte@hypernews.org, 1996, Oct 17

78 Bugs During CERN Installation by Miles Fidelman, 1996, Oct 03

79 Can't run setup-form.pl by Ender Oezguer, 1996, Oct 16

1 Things to verify by ulrich@eiba.com, 1996, Oct 23

80 Need someone to install HyperNews $$$ by Ron Wilson, 1996, Oct 20

81 On a MAC? by Sharon Thurgood, 1996, Oct 20

1 Not on a Mac, not on a PC, Sam let me be! by liberte@hypernews.org, 1996, Oct 21

82 Problem with move/copy by Fred Brittain, 1996, Oct 23 [Moved]

83 Navigation graphics do not appear by Martin Grogg, 1996, Oct 25

1 What is your browser? by liberte@hypernews.org, 1996, Oct 25

84 Can I translate the code to Spanish by Alberto de Poo, 1996, Oct 28

85 $hnicons-bug by Philipp Bachmann, 1996, Oct 30

1 It's a bug by liberte@hypernews.org, 1996, Oct 30

86 hroberts@alumni.princeton.edu by Hal Roberts, 1996, Nov 04

1 lock error on deletion by liberte@hypernews.org, 1996, Nov 04

87 Setting up a SubGroup?? by Brian K. Swail, 1996, Nov 07

1 Most is documented already by liberte@hypernews.org, 1996, Nov 07

88 My Help is broken, no files /hn/*.html by Bernd Beier, 1996, Nov 11

89 Tar file called hypernew by E. Charters, 1996, Nov 15

1 Scripts untar to HyperNews/.scripts by liberte@hypernews.org, 1996, Nov 15

90 missing newline in .htgroupaccess by Bob Kemp, 1996, Nov 27

91 Can I configure notification messages? by Chris Brown, 1996, Nov 28

1 Do you mean new-member messages? by liberte@hypernews.org, 1996, Dec 02

92 Subscribers aren't receiving mail. What should I check? by Steve Isaacson, 1996, Dec 05

1 Members are not subscribers by liberte@hypernews.org, 1996, Dec 06

93 Background Image and $bodytag by Ron, 1996, Dec 08

1 Be careful about relative URLs by liberte@hypernews.org, 1996, Dec 09

94 Hypernews on Novell Web server by Andre Beley, 1996, Dec 12

95 hnrc file not being created, can't install by Doug Archell, 1996, Dec 12

1 Did you submit the setup-form? by liberte@hypernews.org, 1996, Dec 12

Perl 5.001 issue, partially resolved now! by darchell@netcent.com, 1996, Dec 12

96 Problem running setup.pl form setup-short-form by Etienne Delagrave, 1996, Dec 12

1 hnrc missing by liberte@hypernews.org, 1996, Dec 12

97 Serious Install Problems, Instability by Doug Archell, 1996, Dec 13

98 Can't load Fcntl.so, Help Me! by Etienne Delagrave, 1996, Dec 16

99 User <me> has incorrect permissions? , 1995, Jul 18

1 Permissions to $hndocs? by pwiseman@mindspring.com, 1995, Jul 18

Problem solved? But in an unsatisfactory way! by pwiseman@mindspring.com, 1995, Jul 19

1 Not unsatisfactory . . . necessary by pwiseman@mindspring.com, 1995, Aug 02

...

2 Another Good reason to do this.. by jeffh@ee.pdx.edu, 1996, Jan 03

...

100 Want to configure out "Copy | Delete | Membership" , 1995, Aug 29

1 Good idea by Daniel LaLiberte, 1995, Aug 29

sirve para crear foros limitando accesos? by enrique, 2002, May 07

101 Authentication failure creating base article , 1996, May 23

1 Check authentication path by liberte@hypernews.org, 1996, May 23

Check authentication path reply by mgrogg@novell.com, 1996, May 29

Groupmembers missing? by