1 This is a README for the major platforms where Netatalk is in use.
12 ----------------------------------------------------------------
16 We no longer include linux kernel code with netatalk, since Linux now
17 includes AppleTalk support.
19 1. MAKE CONFIG. Configure your kernel with "make config". Answer yes
20 to "AppleTalk DDP" support.
22 2. INSTALL KERNEL. Make and install your kernel. Be sure to update
25 3. Linux 2.2.x provides the sendfile() call. This reduces overhead
26 when sending/copying files. This option will be autoconfigured on
27 compile. NOTE: you might run into problems if you have this option
28 compiled in and you switch to a machine running an os < 2.2.x.
31 Netatalk supplies two different types of Appletalk servers and both
32 can run at the same time. Classic Appletalk requires afpd and
33 atalkd. Appletalk over IP only requires afpd.
35 Classic Appletalk on GNU/Linux requires that CONFIG_ATALK is compiled
36 into the kernel or as a kernel module. To check to see if the kernel
37 has Appletalk installed:
40 This just parses the boot messages for any line containing
43 To see all the loaded modules (as root):
46 If you don't find it, you may have to compile a kernel and turn on
47 Appletalk in Networking options -> Appletalk DDP. You have an option
48 to install as a module or directly into the kernel.
50 Some default distribution kernels have already compiled Appletalk DDP
51 as a module, you may have to edit your /etc/modules.conf to include:
52 "alias net-pf-5 appletalk ".
54 Note: check your distribution documentation about editing
57 For more complete information about the Linux kernel see the
59 http://www.linuxdoc.org/HOWTO/Kernel-HOWTO.html
61 ----------------------------------------------------------------
65 This is the Tru64 README file for netatalk.
67 1. Unfortunately, AppleTalk is not available for Digital Unix or Tru64.
68 The reason for this is the kernel patches which Netatalk requires
69 cannot be ported to Tru64. If anyone has the kernel source of Tru64
70 they are welcomed to port the AppleTalk modules themselves.
72 As a result, only AppleShare over IP (ASIP) works with Tru64. That
73 is, the program afpd. papd and atalkd compile, but doesn't really
74 work. Anything that requires AppleTalk doesn't work.
76 2. Netatalk compiles on Tru64 V4.0D or higher using either the built-in
77 DEC C compiler or GCC V2.95.3. Also, either the Tru64 make command or
78 GNU make can be used. Netatalk supports Tru64's Security Integration
79 Architecture (SIA) and runs on machines configured for Base (BSD) or
80 Enhanced (OSFC2) Security without recompilation.
82 3. A peculiar bug in Netatalk has been noticed on a single Tru64
83 machine. However, because other Tru64 machines have not affected, a
84 patch will not be forthcoming until the circumstances where the bug
85 hits is isolated and a more elegant and appropriate patch can be
86 found. In the meantime, there is a description of the bug below. Any
87 users affected can attempt the workarounds provided. The user is
88 urged to report this to the mailing list so that this bug can be
93 It appears that memcpy() under Tru64 can fail under some
94 circumstances. This maybe due to the fact that Netatalk is compiled
95 with gcc, but since only gcc can compile Netatalk, this is a mute
99 The symptoms of this bug is that a 18432 byte file uploaded to
100 the server would upload correctly, but a 18433 byte file would
101 result in a sparse file many megabytes big (16MB+). However, due to
102 the low-level nature of memcpy(), there is no reason why other
103 symptoms could not occur.
106 There are two known workarounds at this stage.
107 - The first is to #define the macro HAVE_GCC_MEMCPY_BUG. This forces
108 netatalk to use bcopy() in a few (but not all) cases within the code
109 and is enough to stop the bug from occurring. This is the easiest
110 workaround and would merely alter the standard compilation steps to
112 ./configure --with-cflags="-DHAVE_GCC_MEMCPY_BUG"
116 - The second workaround is to manually remove the optimisation flag
117 "-O2" from within configure and/or configure.in. Although, this
118 isn't the preferred workaround, it shows that the compiler is
119 (at least) partially at fault.
121 ----------------------------------------------------------------
125 1. SELECT COMPILER. This distribution is configured to build with
126 gcc. It should also work with cc. At the present time only cc
127 v5.0 and above can build the 64-bit kernel module.
129 1a. SELECT KERNEL TYPE. Edit sys/solaris/Makefile and set KCFLAGS to
130 include sparcv9 support if you run a 64-bit kernel, or leave it
131 commented out for a 32-bit kernel. Only UltraSPARC systems
132 running Solaris 7 and above support a 64-bit kernel. If you're
133 not sure what kernel you use, run "isainfo -v". You're running a
134 64-bit kernel if the result includes 64-bit (sparcv9), otherwize
137 NOTE: If you want both the 32-bit and 64-bit kernel modules to be
138 installed, first compile and install the version appropriate to
139 the kernel that you're currently running, then make clean,
140 compile and install the other version.
142 2. EDIT NETCONFIG. Add the following line to /etc/netconfig:
144 ddp tpi_clts - appletalk ddp /dev/ddp -
146 This makes the socket library aware of the AppleTalk protocol
149 3. INSTALL DRIVER. Since the STREAMS ddp driver must be installed as
150 root, we've separated that portion of the build. Type
154 to install the driver. This copies the driver and its config file
155 into /usr/kernel/drv and /usr/kernel/strmod, runs "add_drv ddp" to
156 make the kernel aware of the new driver, and adds an rc file to
157 /etc/rc?.d. Watch out for error messages after it runs add_drv.
158 If you see something like
159 devfsadm: driver failed to attach: ddp
160 Warning: Driver (ddp) successfully added to system but failed to attach
161 then recheck sys/solaris/Makefile and/or try a different compiler.
163 4. ATALKD.CONF. Under Solaris, you must create atalkd.conf, since
164 Solaris provides no method for determining the names of the
165 available interfaces. It is sufficent to name the available
166 interfaces in atalkd.conf, one per line. E.g.
170 on a line by itself on many Suns. hme0 on Ultras. See atalkd(8).
172 5. PRINTING. Netatalk can use any postscript printer that has been set
173 up for use by Solaris. If you haven't already set up a printer,
174 type admintool then select Browse --> Printers, and then Edit --> Add
175 and fill in the form for either a local or remote printer. If adding
176 a local printer, set the Printer Type to PostScript. Then find a
177 postscript file and test your printer from the command line. For
178 example if you created a printer called "fred" your print command
179 would be something like: lp -d fred some_file.ps
181 Once you have a printer that works under Solaris, you need to create
182 a papd.conf file. For example
185 :pr=|/usr/bin/lp -d fred:\
187 :pd=/usr/local/etc/HPLJ_4M.PPD:
189 See doc/CONFIGURE for more information on papd.conf.
190 Once you have this set up, and assuming netatalk starts up after
191 /etc/rc2.d/S79atalk start
192 you should be able to see the printer from the Macintosh Chooser.
194 ----------------------------------------------------------------
198 1. KERNEL SUPPORT. Note that kernel support for netatalk appears in
199 OpenBSD 2.2, or openbsd-current dated after Aug 1, 1997. But the
200 'comment out' character must be removed and the kernel must be
203 The kernel file that needs to be edited is usually located in:
206 Remove the first comment (#) from this line:
207 # option NETATALK # AppleTalk
209 Generally this is the GENERIC kernal. If you decide to rename
210 the kernel, don't forget to go to
211 /usr/src/sys/arch/<your arch>/conf/NEWNAME, and change the
212 ../../../conf/GENERIC line to your NEWNAME. See
213 http://www.openbsd.org/faq/faq5.html for more information on
214 compiling a new kernel.
216 2. STARTING NETATALK. The rc scripts that come with openbsd to
217 start netatalk are specific to an older version of netatalk.
218 So, if you use the initscript provided in a current netatalk's
219 distrib/initscripts directory, you must either add the lines
220 from rc.atalk.bsd by hand into /etc/rc.local (or wherever you
221 want to launch the daemons from) or modify your /etc/rc.local
227 if [ -f /etc/netatalk/rc.atalk ]; then
228 . /etc/netatlk/rc.atalk
234 if [ -f /etc/rc.atalk ]; then
238 and copy netatalk/distrib/initscripts/rc.atalk.bsd to /etc/rc.atalk.
242 1. KERNEL SUPPORT. Note that kernel support for netatalk appears in
243 FreeBSD 2.2-current dated after 12 September 1996.
249 to the config file for your kernel. Rebuild and install your
252 ----------------------------------------------------------------
256 1. KERNEL MODULE. This version of netatalk requires that your kernel
261 The loadable kernel module is made and installed during the normal
262 make and make install. NOTE: Unloading the kernel module may not
263 work correctly and may cause your kernel to panic, hang, or do
266 ----------------------------------------------------------------
270 (It's unknown how applicable this is compared to the current codebase)
272 The generic system profile is for use on systems that don't have native
273 appletalk support. For those systems, it should still be possible to get
274 the AFP/tcp portion of netatalk to still work.
276 To do that, you will need the following information:
278 1) Endian order: If your machine does not specify the
279 byte-order in netinet/in.h, you may need to modify
282 2) Integer sizes: If your machine does not define intX_t and
283 u_intX_t, you will need to define them in
284 netatalk/endian.h. To ease matters, you can specify
285 _ISOC9X_SOURCE if you have inttypes.h, HAVE_64BIT_LONGS for
286 64 bit machines, or HAVE_32BIT_LONGS for 32 bit
287 machines. NOTE: you should only use HAVE_32/64BIT_LONGS on
288 machines that don't have a header file somewhere with the
289 integer sizes. If you have a file with all the relevant
290 bits, modify netatalk/endian.h to include it.
292 3) Quota/statfs information: You may be able to get away with
293 either BSD4_4 or __svr4__, but that's unlikely if your os
294 is some bizarre hybrid. If you don't have quota support,
295 just specify NO_QUOTA_SUPPORT. In addition, if you'll need
296 to specify the include file that gets statfs() (usually
297 either USE_VFS_H or USE_STATFS_H although BSD4_4 and
298 __svr4__ bring in a set of include files for that). Look at
299 etc/afpd/quota.c, unix.c, and unix.h for more information.
300 Finally, if you have a really old version of rquota, you
301 can define USE_OLD_RQUOTA as well.
303 4) path information for lock/spool/printer files. you'll need
304 to specify -D_PATH_LOCKDIR if include/atalk/paths.h doesn't
305 have the correct paths specified for printer info and lock
308 Beyond that, you should make sure that your operating system looks and
309 smells like a Un*x POSIXy operating system. The only operating systems
310 that netatalk supports that don't quite fit that description are
311 sunos 4 and ultrix. If your operating system is peculiar, you may need
312 to add in compatibility routines (libatalk/compat,
313 include/atalk/compat.h) to make it look more like the others.
315 If you would like native AppleTalk support, you will need kernel support
316 for your operating system. Look at the Solaris STREAMS module if your
317 operating system supports that framework. Otherwise, look at the ddp
318 code in FreeBSD, NetBSD, or OpenBSD if your operating system is BSDish
319 in nature. If your operating system looks different than these two
320 cases, you'll have to roll your own implementation.