From: "Jeff Merkey" <jmerkey@timpanogas.org>
To: <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] NetWare File System Module Version NWFS v4.0 Posted
Date: Sat, 17 Nov 2001 00:22:50 -0700 [thread overview]
Message-ID: <002601c16f38$aa3d7290$f5976dcf@nwfs> (raw)
The NetWare File System NWFS v4.0 module driver and utility sources has
posted at ftp.timpanogas.org/nwfs/nwfs.tar.gz and
ftp.utah-nac.org:/nwfs/nwfs.tar.gz. This version has been tested on Linux
2.4.14 running the RedHat SeaWolf version 7.1 Release. Hard Links are
disabled and so is the page cache. Hard Links will be allowed in a future
version.
Those folks who need to perform NetWare to Linux migrations can download
NWIMAGE and other useful server migration tools from ftp.utah-nac.org and
ftp.timpanogas.org. NWIMAGE runs under DOS, W2K and Linux and allows a
server administrator to remote image NetWare Volumes onto a networked master
archive server, then restore entire system configurations onto newly
installed Linux and W2K servers (preferably Lunux). :-)
A Kernel Patch incorporating NWFS into Linux 2.4.15/16 as a compatibility
file system is under construction.
Do-na-da Go-hv-e
Wa-do
Jeff V. Merkey
TRG/Utah NAC
Waya Ge-tlv-hv-s-di
BUILD METHOD USING THE BUILD SCRIPT
-----------------------------------
NOTE: The new build procedure allows you to simply type
#
# ./build <option>
#
from the directory where you install the NWFS sources. This
newer model auto detects modversioning, smp, version, etc. There is
an assumption made that a symbolic link to /usr/src/linux ->
exists that points to your Linux build area. Some of the
newer Red Hat kernels no longer use this syntax. For the
NWFS build to work properly, you will need to have a
pre-configured Linux source tree present with a symbolic
link to the /usr/src/linux directory.
Simply type ./build for a list of build options.
reply other threads:[~2001-11-17 7:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002601c16f38$aa3d7290$f5976dcf@nwfs' \
--to=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox