Re: net/netatalk afpd causes abort on amd64?
Avahi was the problem, and wasn't working on my system. After I started avahi relevant daemons, afpd is working fine now. I still have another problem using TimeMachine with OS X Lion. Current portversion of netatalk supports AFP 3.3, right? Anyway, thank you for your instructions. I'll try timemachining on my own. On Mon, Aug 08, 2011 at 11:15:21AM -0400, Joe Marcus Clarke wrote: On 8/8/11 7:46 AM, Kouichiro Iwao wrote: Hi. After upgraded to current portversion of netatalk, I cannot start netatalk. I do rc.d/netatalk start then afpd fails SIGABRT. On i386 freebsd, netatalk/afpd works fine. Any solutions to use netatalk on amd64? pid 19160 (afpd), uid 0: exited on signal 6 (core dumped) pid 19175 (afpd), uid 0: exited on signal 6 (core dumped) pid 19188 (afpd), uid 0: exited on signal 6 (core dumped) If you compiled with Zeroconf support (the default), then you need to make sure Avahi is running. Add avahi_daemon_enable=YES and avahi_dnsconf_enable=YES to rc.conf and reboot (or run the two rc.d scripts). Alternatively, you can rebuild netatalk without Zeroconf support. Joe -- Joe Marcus Clarke FreeBSD GNOME Team:: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- kiwao m...@club.kyutech.ac.jp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
net/netatalk afpd causes abort on amd64?
Hi. After upgraded to current portversion of netatalk, I cannot start netatalk. I do rc.d/netatalk start then afpd fails SIGABRT. On i386 freebsd, netatalk/afpd works fine. Any solutions to use netatalk on amd64? pid 19160 (afpd), uid 0: exited on signal 6 (core dumped) pid 19175 (afpd), uid 0: exited on signal 6 (core dumped) pid 19188 (afpd), uid 0: exited on signal 6 (core dumped) -- kiwao m...@club.kyutech.ac.jp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: net/netatalk afpd causes abort on amd64?
On 8/8/11 7:46 AM, Kouichiro Iwao wrote: Hi. After upgraded to current portversion of netatalk, I cannot start netatalk. I do rc.d/netatalk start then afpd fails SIGABRT. On i386 freebsd, netatalk/afpd works fine. Any solutions to use netatalk on amd64? pid 19160 (afpd), uid 0: exited on signal 6 (core dumped) pid 19175 (afpd), uid 0: exited on signal 6 (core dumped) pid 19188 (afpd), uid 0: exited on signal 6 (core dumped) If you compiled with Zeroconf support (the default), then you need to make sure Avahi is running. Add avahi_daemon_enable=YES and avahi_dnsconf_enable=YES to rc.conf and reboot (or run the two rc.d scripts). Alternatively, you can rebuild netatalk without Zeroconf support. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: net/netatalk afpd causes abort on amd64?
Heya, I just struggled with this the last few days and found that the problem lies in zeroconf. I didn't get any error message at all. Adding the flag -nozeroconf to the share the afpd.conf file made it work for me. I use avahi now to make the share available on the network. greets Arno Beekman On 8 aug 2011, at 13:46, Kouichiro Iwao wrote: Hi. After upgraded to current portversion of netatalk, I cannot start netatalk. I do rc.d/netatalk start then afpd fails SIGABRT. On i386 freebsd, netatalk/afpd works fine. Any solutions to use netatalk on amd64? pid 19160 (afpd), uid 0: exited on signal 6 (core dumped) pid 19175 (afpd), uid 0: exited on signal 6 (core dumped) pid 19188 (afpd), uid 0: exited on signal 6 (core dumped) -- kiwao m...@club.kyutech.ac.jp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Fwd: [Netatalk-devel] Fwd: unable to install netatalk
Thank you very much, Joe. After update my ports tree again I got the patch and the issue was resolved. Regards, Thiago On Wed, Jun 9, 2010 at 9:55 PM, Thiago Esteves thgeste...@gmail.com wrote: It seems that there isn't any patch for dsi.h on netatalk/files directory: Prescott:files root$ ls -la total 16 drwxr-xr-x 2 root wheel 512 Jun 4 18:24 . drwxr-xr-x 4 root wheel 512 Jun 9 21:34 .. -rw-r--r-- 1 root wheel 1987 Mar 26 21:13 netatalk.in -rw-r--r-- 1 root wheel 929 May 30 14:03 patch-config_Makefile.in -rw-r--r-- 1 root wheel 1320 May 30 14:03 patch-config_netatalk.conf -rw-r--r-- 1 root wheel 428 May 30 14:03 patch-configure -rw-r--r-- 1 root wheel 512 May 30 14:03 patch-etc-uams_Makefile.in -rw-r--r-- 1 root wheel 585 May 30 14:03 patch-etc_afpd_afp_options.c Prescott:files root$ I am going to try to update ports tree again. Regards, Thiago On Wed, Jun 9, 2010 at 9:48 PM, Joe Marcus Clarke mar...@freebsd.orgwrote: On 6/9/10 8:38 PM, Thiago Esteves wrote: Hello Joe, Thanks for your time. I have updated the ports tree, cleaned up the netatalk package on distfiles and tried to build the port again but I am got the same error: It builds for me on 6-STABLE. I thought it would build on all 6.X, but 6.3 is too old to be properly supported. That said, you might not have gotten the necessary updates. Make sure you have a patch for include/atalk/dsi.h in your netatalk/files directory. Joe In file included from dsi_attn.c:17: ../../include/atalk/dsi.h:63: error: field `server' has incomplete type ../../include/atalk/dsi.h:63: error: field `client' has incomplete type gmake[3]: *** [dsi_attn.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk/dsi' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/net/netatalk/work/netatalk-2.1.1' gmake: *** [all] Error 2 *** Error code 1 Many thanks, Thiago On Wed, Jun 9, 2010 at 7:49 PM, Joe Marcus Clarke mar...@freebsd.org mailto:mar...@freebsd.org wrote: On 6/9/10 3:16 PM, Thiago Esteves wrote: Hello Marcus, Sorry to disturb you, but I have posted that issue on three mailing lists and haven't got any answers. I saw that you are the maintainer for netatalk port on FreeBSD, probably you can help me. Please check the issue described on the email below. I just committed a fix for this. Joe Thanks for your time. Regards, Thiago -- Forwarded message -- From: *Thiago Esteves* thgeste...@gmail.com mailto:thgeste...@gmail.com mailto:thgeste...@gmail.com mailto:thgeste...@gmail.com Date: Wed, Jun 9, 2010 at 3:12 PM Subject: [Netatalk-devel] Fwd: unable to install netatalk To: netatalk-de...@lists.sourceforge.net mailto:netatalk-de...@lists.sourceforge.net mailto:netatalk-de...@lists.sourceforge.net mailto:netatalk-de...@lists.sourceforge.net Hello all, I don't know if it is the correct place to request such kind of support, but I haven't got any answers from netatalk-admins. Could someone help me with the issue described below? Thanks, Thiago -- Forwarded message -- From: *Thiago Esteves* thgeste...@gmail.com mailto:thgeste...@gmail.com mailto:thgeste...@gmail.com mailto:thgeste...@gmail.com Date: Tue, Jun 8, 2010 at 10:41 AM Subject: unable to install netatalk To: netatalk-adm...@lists.sourceforge.net mailto:netatalk-adm...@lists.sourceforge.net mailto:netatalk-adm...@lists.sourceforge.net mailto:netatalk-adm...@lists.sourceforge.net Hello all, I am trying to install netatalk on FreeBSD 6.3 p15 but I am experiencing difficulties, it seems that some code can not be compiled, please check output attached. /I would appreciate any help/ that is given, if you can explain that's even better. Many thanks, Thiago Output: *libtool: link: (cd .libs/libcnid.lax/libcnid_tdb.a ar x /usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk/cnid/tdb/.libs/libcnid_tdb.a) libtool: link: ar cru .libs/libcnid.a .libs/cnid.o .libs/cnid_init.o .libs/libcnid.lax/libcnid_dbd.a/cnid_dbd.o .libs/libcnid.lax/libcnid_last.a/cnid_last.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_add.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_close.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_delete.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_get.o .libs/libcnid.lax
unable to install netatalk
Hello all, I am getting errors while trying to install netatalk from ports collection. I am running release 6.3 p15 (I know it has already passed its end-of-life date, I will update it as soon as possible). My ports tree is updated. Any help is welcome. Here is the output: *libtool: link: (cd .libs/libcnid.lax/libcnid_tdb.a ar x /usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk/cnid/tdb/.libs/libcnid_tdb.a) libtool: link: ar cru .libs/libcnid.a .libs/cnid.o .libs/cnid_init.o .libs/libcnid.lax/libcnid_dbd.a/cnid_dbd.o .libs/libcnid.lax/libcnid_last.a/cnid_last.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_add.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_close.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_delete.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_get.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_lookup.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_open.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_resolve.o .libs/libcnid.lax/libcnid_tdb.a/cnid_tdb_update.o libtool: link: ranlib .libs/libcnid.a libtool: link: rm -fr .libs/libcnid.lax libtool: link: ( cd .libs rm -f libcnid.la ln -s ../libcnid.la libcnid.la ) gmake[4]: Leaving directory `/usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk/cnid' gmake[3]: Leaving directory `/usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk/cnid' Making all in dsi gmake[3]: Entering directory `/usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk/dsi' /bin/sh /usr/local/bin/libtool --tag=CC --mode=compile cc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../../sys-I../../include -D_U_=__attribute__((unused)) -O2 -fno-strict-aliasing -pipe -I../../sys -MT dsi_attn.lo -MD -MP -MF .deps/dsi_attn.Tpo -c -o dsi_attn.lo dsi_attn.c libtool: compile: cc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../../sys -I../../include -D_U_=__attribute__((unused)) -O2 -fno-strict-aliasing -pipe -I../../sys -MT dsi_attn.lo -MD -MP -MF .deps/dsi_attn.Tpo -c dsi_attn.c -fPIC -DPIC -o .libs/dsi_attn.o In file included from dsi_attn.c:17: ../../include/atalk/dsi.h:63: error: field `server' has incomplete type ../../include/atalk/dsi.h:63: error: field `client' has incomplete type gmake[3]: *** [dsi_attn.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk/dsi' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/net/netatalk/work/netatalk-2.1.1/libatalk' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/net/netatalk/work/netatalk-2.1.1' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/net/netatalk. *** Error code 1 Stop in /usr/ports/net/netatalk. BSD-Server-01:/usr/ports/net/netatalk root# * Regards, Thiago ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2
On 23 August 2009, at 10:56, andrew clarke wrote: On Sun 2009-08-23 10:24:53 UTC+0200, Vincent Zee (zen...@xs4all.nl) wrote: === Vulnerability check disabled, database not found === Extracting for netatalk-2.0.4,1 = MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2. = SHA256 Checksum mismatch for netatalk-2.0.4.tar.bz2. I'm getting a checksum mismatch here too. This probably means the tarball was modified. I checked the distinfo file and it is the same as on my other machine. On which the update went fine. Solution #1: Use make NO_CHECKSUM=yes, just ignore the mismatch and hope it will build. Solution #2: Copy /usr/ports/distfiles/netatalk-2.0.4.tar.bz2 from your other machine and rebuild. Solution #3: Don't bother building from ports if you already have a working binary on your other machine. Use pkg_create -vb netatalk\*, copy the resulting file to the new machine, then use pkg_add. This assumes the same architecture (eg. i386) on both machines. Hi Andrew, thanks for your answer. I think I'll go with solution number two since the machine have different architectures. /\ Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2
Hi, I'm trying to update the netatalk port to its newest version. uname -a FreeBSD piggie.int.daemon.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I use portmaster -a to update the ports but when it reaches netatalk it gives this error message: - === Vulnerability check disabled, database not found === Extracting for netatalk-2.0.4,1 = MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2. = SHA256 Checksum mismatch for netatalk-2.0.4.tar.bz2. [snip] === Giving up on fetching files: netatalk-2.0.4.tar.bz2 netatalk-2.0.4.tar.bz2 Make sure the Makefile and distinfo file (/usr/ports/net/netatalk/distinfo) are up to date. If you are absolutely sure you want to override this check, type make NO_CHECKSUM=yes [other args]. *** Error code 1 Stop in /usr/ports/net/netatalk. *** Error code 1 Stop in /usr/ports/net/netatalk. === make failed for net/netatalk === Aborting update === Update for netatalk-2.0.3_5,1 failed === Aborting update --- I checked the distinfo file and it is the same as on my other machine. On which the update went fine. Anyone any idea how to solve this? Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2
On Sun 2009-08-23 10:24:53 UTC+0200, Vincent Zee (zen...@xs4all.nl) wrote: === Vulnerability check disabled, database not found === Extracting for netatalk-2.0.4,1 = MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2. = SHA256 Checksum mismatch for netatalk-2.0.4.tar.bz2. I'm getting a checksum mismatch here too. This probably means the tarball was modified. I checked the distinfo file and it is the same as on my other machine. On which the update went fine. Solution #1: Use make NO_CHECKSUM=yes, just ignore the mismatch and hope it will build. Solution #2: Copy /usr/ports/distfiles/netatalk-2.0.4.tar.bz2 from your other machine and rebuild. Solution #3: Don't bother building from ports if you already have a working binary on your other machine. Use pkg_create -vb netatalk\*, copy the resulting file to the new machine, then use pkg_add. This assumes the same architecture (eg. i386) on both machines. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Netatalk
On 24 Sep 2007, at 06:16, Ted Mittelstaedt wrote: Gabriel, Ignore Martin he doesen't know how to get it running so he's pulling the old spurning what he cannot do refer to the Aesop fable Fox and the Grapes for more information. If you run OS9 emulation under OSX you need AFP. Many older print servers only speak AFP AFP handles the split resource/data fork properly, Samba does not. You will see this in a number of minor ways. To get it running: define NETATALK in kernel and recompile cd /usr/ports/net/netatalk make WITH_SRVLOC=yes install add the following in /etc/rc.conf: slpd_enable=YES netatalk_enable=YES atalkd_enable=YES cnid_metad_enable=YES afpd_enable=YES cd /usr/ports/net/howl make install cd /etc vi rc.conf add in mdnsresponder_enable=YES mdnsresponder_flags=-f /usr/local/etc/mDNSResponder.conf then create the config file as such vi /usr/local/etc/mDNSResponder.conf BigMac _afpovertcp._tcp local. 548 BigMac _ssh._tcpServers. 548 MUST BE TABS BETWEEN ITEMS and NEWLINE AT END! BigMac is your servername test with slptool findsrvs service:service-agent and mDNSResponder lookups your problem is that afpd only advertises over appletalk, not over tcp/ip. Since your Macs are all OSX they don't listen to appletalk announcements. They listen to appletalk-over-tcp/ip announcements which use the rendezevous protocol which is what mdnsresponder is all about. One important note - try to keep the samba shares separate from the appletalk shares. Samba clients do not update the desktop file when they move/change/delete files which will result in a corrupted desktop file. (ie: CNID database) If that happens do this: /usr/local/etc/rc.d/netatalk.sh stop cat /usr/local/etc/AppleVolumes.default (shares are listed at the bottom) go to each share with the problem and rename the directory, ie: cd /home/shares/Public mv .AppleDB .AppleDB-temp-backup restart netatalk /usr/local/etc/rc.d/netatalk.sh start verify people can mount the shares and get to their files Delete the .AppleDB-temp-backup dirs. Ted PS: Appletalk is older networking technology but there is nothing wrong with it and it works no worse than newer technologies. Thank you so much for this comprehensive reply. I can see there are several things in there that I didn't get, as they were missed out in my other guides. Seems like a small nightmare setting up netatalk, hope it will be worth it! Thanks again, I really appreciate it. Gabe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Netatalk
Martin Hepworth ha scritto: the filetyping goes alot better using smb than appletalk with MacOS X I have to disagree. I think I'm dropping the last Mac OS 9 box very soon, so I could go to a samba only setup, but in the past I had several problems with it: filetyping is something I could work around, but for filenames encoding I could not find a solution. netatalk, on the other side, works flawlessly. I'm still trying to educate my users to avoid exotic characters in file names, but I cannot ask them to rename thousands of files they already have. (Just my two cents, but if someone can suggest something...). bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Netatalk
Why you need netatalk - you still got some old MacOS 8/9 machines about? -- martin On 9/22/07, Gabriel Dragffy [EMAIL PROTECTED] wrote: I've been following several different tutorials on the net for getting netatalk working. I've compiled in the neccessary option to the kernel, installed the port. Added various things to rc.conf, run / usr/local/etc/rc.d/netatalk start and... nothing :( I think the problem is that all the tutorials I have found are years our of date. Does someone know how to get the modern port of netatalk on 6.2 working? Many thanks Gabriel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Netatalk
On 23 Sep 2007, at 16:13, Martin Hepworth wrote: Why you need netatalk - you still got some old MacOS 8/9 machines about? -- no, they are all os x macbook pros. However we sometimes access over the internet using AFP, and this uses encrypted passwords which is safer. Also, afp integrates very well with the mac machines, better than samba and far better than NFS. I've been using FreeNAS which has worked well, but unfortunately freezes every few hours, so it's useless. Trying to build my own version of it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Netatalk
Beg to differ on the AFP vs samb issues from what we use at work using a mixed environment (*nix, windoze and Mac's). the filetyping goes alot better using smb than appletalk with MacOS X, and smb will use encrypted passwds (however poorly encoded) by default, and even SMB is alot faster than AFP which is horrible slow. You'll find that using a VPN to access over the internet alot more secure in any case. anyway a quick google gives this.. http://www.caboo.se/articles/2006/1/18/apple-file-sharing-via-freebsd -- martin On 9/23/07, Gabriel Dragffy [EMAIL PROTECTED] wrote: On 23 Sep 2007, at 16:13, Martin Hepworth wrote: Why you need netatalk - you still got some old MacOS 8/9 machines about? -- no, they are all os x macbook pros. However we sometimes access over the internet using AFP, and this uses encrypted passwords which is safer. Also, afp integrates very well with the mac machines, better than samba and far better than NFS. I've been using FreeNAS which has worked well, but unfortunately freezes every few hours, so it's useless. Trying to build my own version of it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Netatalk
On 23 Sep 2007, at 19:14, Martin Hepworth wrote: Beg to differ on the AFP vs samb issues from what we use at work using a mixed environment (*nix, windoze and Mac's). the filetyping goes alot better using smb than appletalk with MacOS X, and smb will use encrypted passwds (however poorly encoded) by default, and even SMB is alot faster than AFP which is horrible slow. You'll find that using a VPN to access over the internet alot more secure in any case. anyway a quick google gives this.. http://www.caboo.se/articles/2006/1/18/apple-file-sharing-via-freebsd Thanks, I've already read that link, what was suggested didn't work. I don't mind using smb, but I have a question or two I would be glad if you could answer: Can you connect to a smb server over the internet? For example in OS X give the address as smb://example.com? Also, how would you get the passwords encrypted? Is this done by default. Best regards Gabe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Netatalk
Le 23/09/2007 à 19:55:37+0100, Gabriel Dragffy a écrit On 23 Sep 2007, at 19:14, Martin Hepworth wrote: Beg to differ on the AFP vs samb issues from what we use at work using a mixed environment (*nix, windoze and Mac's). the filetyping goes alot better using smb than appletalk with MacOS X, and smb will use encrypted passwds (however poorly encoded) by default, and even SMB is alot faster than AFP which is horrible slow. You'll find that using a VPN to access over the internet alot more secure in any case. anyway a quick google gives this.. http://www.caboo.se/articles/2006/1/18/apple-file-sharing-via-freebsd Thanks, I've already read that link, what was suggested didn't work. I don't mind using smb, but I have a question or two I would be glad if you could answer: Can you connect to a smb server over the internet? For example in OS X give the address as smb://example.com? Also, how would you get the passwords encrypted? Is this done by default. It's yes for this two questions Best regards. -- Albert SHIH Observatoire de Paris Meudon SIO batiment 15 Heure local/Local time: Dim 23 sep 2007 23:03:48 CEST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Netatalk
Gabriel, Ignore Martin he doesen't know how to get it running so he's pulling the old spurning what he cannot do refer to the Aesop fable Fox and the Grapes for more information. If you run OS9 emulation under OSX you need AFP. Many older print servers only speak AFP AFP handles the split resource/data fork properly, Samba does not. You will see this in a number of minor ways. To get it running: define NETATALK in kernel and recompile cd /usr/ports/net/netatalk make WITH_SRVLOC=yes install add the following in /etc/rc.conf: slpd_enable=YES netatalk_enable=YES atalkd_enable=YES cnid_metad_enable=YES afpd_enable=YES cd /usr/ports/net/howl make install cd /etc vi rc.conf add in mdnsresponder_enable=YES mdnsresponder_flags=-f /usr/local/etc/mDNSResponder.conf then create the config file as such vi /usr/local/etc/mDNSResponder.conf BigMac _afpovertcp._tcp local. 548 BigMac _ssh._tcpServers. 548 MUST BE TABS BETWEEN ITEMS and NEWLINE AT END! BigMac is your servername test with slptool findsrvs service:service-agent and mDNSResponder lookups your problem is that afpd only advertises over appletalk, not over tcp/ip. Since your Macs are all OSX they don't listen to appletalk announcements. They listen to appletalk-over-tcp/ip announcements which use the rendezevous protocol which is what mdnsresponder is all about. One important note - try to keep the samba shares separate from the appletalk shares. Samba clients do not update the desktop file when they move/change/delete files which will result in a corrupted desktop file. (ie: CNID database) If that happens do this: /usr/local/etc/rc.d/netatalk.sh stop cat /usr/local/etc/AppleVolumes.default (shares are listed at the bottom) go to each share with the problem and rename the directory, ie: cd /home/shares/Public mv .AppleDB .AppleDB-temp-backup restart netatalk /usr/local/etc/rc.d/netatalk.sh start verify people can mount the shares and get to their files Delete the .AppleDB-temp-backup dirs. Ted PS: Appletalk is older networking technology but there is nothing wrong with it and it works no worse than newer technologies. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gabriel Dragffy Sent: Sunday, September 23, 2007 9:42 AM To: freebsd-questions@freebsd.org Subject: Re: Netatalk On 23 Sep 2007, at 16:13, Martin Hepworth wrote: Why you need netatalk - you still got some old MacOS 8/9 machines about? -- no, they are all os x macbook pros. However we sometimes access over the internet using AFP, and this uses encrypted passwords which is safer. Also, afp integrates very well with the mac machines, better than samba and far better than NFS. I've been using FreeNAS which has worked well, but unfortunately freezes every few hours, so it's useless. Trying to build my own version of it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Netatalk
I've been following several different tutorials on the net for getting netatalk working. I've compiled in the neccessary option to the kernel, installed the port. Added various things to rc.conf, run / usr/local/etc/rc.d/netatalk start and... nothing :( I think the problem is that all the tutorials I have found are years our of date. Does someone know how to get the modern port of netatalk on 6.2 working? Many thanks Gabriel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hosts.allow and netatalk/cups
On Tue, Jan 11, 2005 at 02:37:23PM +0700, Olivier Nicole wrote: To my knowledge, the effects in /etc/hosts.allow are immediate as soon as you save the modified file. And I have been using it that way for many years. No need to killall -HUP inetd, no need to reboot. If after a change the service is still not available: - you did not allow the right thing - the servcie would not be working even without tcp wrapper Try to add ALL : ALL : allow at the top of /etc/hosts/allow. Does the service work? Then you made a mistake when trying to open tcp wrapper for that specific service. Else the problem is not with tcp wrapper / hosts.allow. Thanks for the comments, but changes to /etc/hosts.allow don't take effect until the system is rebooted. And when the system is rebooted, they definitely take effect. Two entries that take effect if and only if the system is rebooted: smbd : .krig.net : allow afpd : .krig.net : allow Commenting these out and saving the file has no effect. Rebooting the system stops Windows and Mac file sharing. Uncommenting them and saving the file has no effect. Rebooting the system restores Windows and Mac file sharing. uname -a FreeBSD kongemord.krig.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Sep 13 00 :17:04 EDT 2004 kongemord.krig.net:/usr/obj/usr/src/sys/KONGEMORD0 i386 Bob Hall ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hosts.allow and netatalk/cups
On Tue, Jan 11, 2005 at 02:31:47AM -0500, Bob Hall wrote: Three questions: How do I cause changes in the hosts.allow file to take effect without rebooting? Everything I've seen says to restart inetd, but I'm not using inetd. I searched with different keywords and found the answer to this in the archives. Searching the archives, Googling, and experimentation still haven't turned up an answer to the two below. How do I compile netatalk without CUPS? I don't see any obvious switches, but there has to be something that tells Make to use CUPS, because it gives a message saying that it's checking if CUPS can be included. How do I get netatalk to use the dbd cnid scheme? It ignores the path name cnidscheme:dbd setting in AppleVolumes.default and the - -cnidserver localhost:4700 setting in afpd.conf. Regardless of what the cnidscheme setting is, it announces that's there's no cnid scheme selected and uses the default. Bob Hall ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: netatalk, NFS, OS X and backup
have you looked at amanda? Uses it's daemons to transfer the data, and you can select where to comress (on client or server). works well when used with hfstar on MacOS X ... restores are normally done by the admin and currently its a cli...no plans AFAIK to make this a gui. --- Martin On Fri, 7 Jan 2005 11:29:59 -0500, Alan Curtis [EMAIL PROTECTED] wrote: I need some advice about integrating my FreeBSD server with some Macs running OS X. I have a server running FreeBSD 5.3 with NFS and netatalk enabled, a Powerbook G4 running OS X 10.3.7 and they are connected through a wireless network. I used the Powerbook to administer the server using ssh, which works well. I would also like to use the server to backup files (for multiple users) from the Powerbook. I have played around with both NFS and netatalk (afpd) and both seem to be working, in that I can manually mount the shares on the Powerbook. I have got the NFS share to automount on the Powerbook but not the afp share. I can copy files to and from both the nfs and afp mounted shares, including resource forks. I have played with various backup utilities including rsync, psync and rdiff-backup with varying degrees of success. Some observations/questions 1. netatalk afp seems consistently and significantly faster than nfs. Is this to be expected or might I have a problem with nfs? If so how do I diagnose and fix it? 2. I would prefer to use nfs, because I can automount it on the Powerbook and run a cron (actually anacron) script to backup the multiple users. I haven't yet worked out how (or if) I can do this with afp (this is really a Mac question I know). 3. I would like to use a backup scheme which is automatic, invisible to the user, yet configured in a way that the archive can be navigated, and files appear in folders on the Mac finder in a consistent way (with resource forks set up correctly). All of this seems almost possible, yet I don't seem to have got it just right yet. Has anyone one any insight they can spread or experiences they can share of a similar set up? Alan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: netatalk, NFS, OS X and backup
Personally I use a combination of applescript and cli. With applescript you create a script that mounts the remote afp volume. Eg in script editor On run try mount volume afp://server/sharepoint as user name name with password crypt on error -- end try End run Personally I put the mount command inside the try block to prevent error dialogs coming up - that is why the -- (a comment line) is after on error - it tricks the script into doing nothing on error. As you might guess this is plain text - for security when you save it you can save as application and tick the run only box - this prevents the file being opened in the script editor and read - you can open and run it but not see the source. This will mount the specific share point - it shows up in /volumes/sharepoint - which can then be copied to/from I then use the cli to compress/copy files - personally I use stuffit deluxe for compression as the deluxe version includes the cli tools and handles resource forks / meta data etc. #! /bin/sh /usr/local/bin/stuff -f sitx -n /pathto/backupfile /pathto/filestobackup cp /pathto/backupfile /volumes/sharepoint/backupfile Of course you put the date/numbers into the filename as you prefer. One gotcha to look out for is if the sharepoint doesn't mount for whatever reason the cp step will create a folder in /volumes and will copy locally instead of to the server. There is also the option of using scp to get the files to the server. There is a cli - mount_afp - when I tried it some time ago I had some problem(can't remember what now) so I used the applescript instead. You then setup cron to run the applescript and the shell script when you want. With the applescript it is a gui app so in cron you need /usr/bin/open /pathto/applescript.app Remember the .app is not shown in the finder but is needed for the cli, easy to miss. On 11/1/05 2:15 AM, Martin Hepworth [EMAIL PROTECTED] wrote: have you looked at amanda? Uses it's daemons to transfer the data, and you can select where to comress (on client or server). works well when used with hfstar on MacOS X ... restores are normally done by the admin and currently its a cli...no plans AFAIK to make this a gui. --- Martin On Fri, 7 Jan 2005 11:29:59 -0500, Alan Curtis [EMAIL PROTECTED] wrote: I need some advice about integrating my FreeBSD server with some Macs running OS X. I have a server running FreeBSD 5.3 with NFS and netatalk enabled, a Powerbook G4 running OS X 10.3.7 and they are connected through a wireless network. I used the Powerbook to administer the server using ssh, which works well. I would also like to use the server to backup files (for multiple users) from the Powerbook. I have played around with both NFS and netatalk (afpd) and both seem to be working, in that I can manually mount the shares on the Powerbook. I have got the NFS share to automount on the Powerbook but not the afp share. I can copy files to and from both the nfs and afp mounted shares, including resource forks. I have played with various backup utilities including rsync, psync and rdiff-backup with varying degrees of success. Some observations/questions 1. netatalk afp seems consistently and significantly faster than nfs. Is this to be expected or might I have a problem with nfs? If so how do I diagnose and fix it? 2. I would prefer to use nfs, because I can automount it on the Powerbook and run a cron (actually anacron) script to backup the multiple users. I haven't yet worked out how (or if) I can do this with afp (this is really a Mac question I know). 3. I would like to use a backup scheme which is automatic, invisible to the user, yet configured in a way that the archive can be navigated, and files appear in folders on the Mac finder in a consistent way (with resource forks set up correctly). All of this seems almost possible, yet I don't seem to have got it just right yet. Has anyone one any insight they can spread or experiences they can share of a similar set up? Alan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Shane Ambler Sales Department 007Marketing.com [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hosts.allow and netatalk/cups
Three questions: How do I cause changes in the hosts.allow file to take effect without rebooting? Everything I've seen says to restart inetd, but I'm not using inetd. How do I compile netatalk without CUPS? I don't see any obvious switches, but there has to be something that tells Make to use CUPS, because it gives a message saying that it's checking if CUPS can be included. How do I get netatalk to use the dbd cnid scheme? It ignores the path name cnidscheme:dbd setting in AppleVolumes.default and the - -cnidserver localhost:4700 setting in afpd.conf. Regardless of what the cnidscheme setting is, it announces that's there's no cnid scheme selected and uses the default. Bob Hall ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hosts.allow and netatalk/cups
To my knowledge, the effects in /etc/hosts.allow are immediate as soon as you save the modified file. And I have been using it that way for many years. No need to killall -HUP inetd, no need to reboot. If after a change the service is still not available: - you did not allow the right thing - the servcie would not be working even without tcp wrapper Try to add ALL : ALL : allow at the top of /etc/hosts/allow. Does the service work? Then you made a mistake when trying to open tcp wrapper for that specific service. Else the problem is not with tcp wrapper / hosts.allow. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
netatalk, NFS, OS X and backup
I need some advice about integrating my FreeBSD server with some Macs running OS X. I have a server running FreeBSD 5.3 with NFS and netatalk enabled, a Powerbook G4 running OS X 10.3.7 and they are connected through a wireless network. I used the Powerbook to administer the server using ssh, which works well. I would also like to use the server to backup files (for multiple users) from the Powerbook. I have played around with both NFS and netatalk (afpd) and both seem to be working, in that I can manually mount the shares on the Powerbook. I have got the NFS share to automount on the Powerbook but not the afp share. I can copy files to and from both the nfs and afp mounted shares, including resource forks. I have played with various backup utilities including rsync, psync and rdiff-backup with varying degrees of success. Some observations/questions 1. netatalk afp seems consistently and significantly faster than nfs. Is this to be expected or might I have a problem with nfs? If so how do I diagnose and fix it? 2. I would prefer to use nfs, because I can automount it on the Powerbook and run a cron (actually anacron) script to backup the multiple users. I haven't yet worked out how (or if) I can do this with afp (this is really a Mac question I know). 3. I would like to use a backup scheme which is automatic, invisible to the user, yet configured in a way that the archive can be navigated, and files appear in folders on the Mac finder in a consistent way (with resource forks set up correctly). All of this seems almost possible, yet I don't seem to have got it just right yet. Has anyone one any insight they can spread or experiences they can share of a similar set up? Alan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem connecting with Netatalk 2.0
This is what helped in my case: If you used an earlier version of Netatalk before (like 1.6) then there are hidden Mac files in the Linux home directories (e.g. .AppleDB). This happens because typically all home directories are shared by the standard version of the AppleVolumes.default. Those hidden files obviously led to the behavior of Netatalk 2 you and I observed: it doesn't offer any directories on the Mac client. I deleted all of those files in all of the home directories (not just in the one I was trying to connect). I think this issue is sort of described on the Netatalk developer's page: http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html. However, I didn't get all the details there and simply deleted the hidden files. Didn't do any damage in my case. A good solution probably is: Copy the entire directory contents to a Mac. Clear the Linux directories (including hidden Mac-relavant files, but not the Linux-relevant files). Upgrade to Netatalk 2. Move back the original contents. Frank ___ Gesendet von Yahoo! Mail - Jetzt mit 250MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
starting netatalk
I am trying to use netatalk-2.0.1 on FreeBSD 4.10-RELEASE.
I can start afpd manually by
/usr/local/sbin/afpd -s /usr/local/etc/AppleVolumes.system -f
/usr/local/etc/AppleVolumes.default
and can access the share from my Mac OS X machine.
There is a script /usr/local/etc/rc.d/netatalk.sh that is supposed to
start afpd at startup. I cannot get that to work.
I tried adding a netatalk.conf file with afpd=yes. I tried editing
the netatalk.sh file line
afpd_enable=${afpd_enable-NO}
to
afpd_enable=${afpd_enable-YES}
and a number of other things. But as I obviously don't know what I'm
doing, I thought I'd ask.
Thanks
Alan
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: starting netatalk
On Fri, Dec 03, 2004 at 12:01:54PM -0500, Alan Curtis wrote:
I am trying to use netatalk-2.0.1 on FreeBSD 4.10-RELEASE.
I can start afpd manually by
/usr/local/sbin/afpd -s /usr/local/etc/AppleVolumes.system -f
/usr/local/etc/AppleVolumes.default
and can access the share from my Mac OS X machine.
There is a script /usr/local/etc/rc.d/netatalk.sh that is supposed to
start afpd at startup. I cannot get that to work.
I tried adding a netatalk.conf file with afpd=yes. I tried editing
the netatalk.sh file line
afpd_enable=${afpd_enable-NO}
to
afpd_enable=${afpd_enable-YES}
and a number of other things. But as I obviously don't know what I'm
doing, I thought I'd ask.
You shouldn't modify the netatalk.sh file. Just add the following
lines to /etc/rc.conf
netatalk_enable=YES
atalkd_enable=YES
papd_enable=YES
afpd_enable=YES
and the /usr/local/etc/rc.d/netatalk.sh startup script should start
things fine.
(You might not need all of the above, if you don't want to start all
the services.)
See rc.subr(8) for some more information on how such startup-scripts
work.
--
Insert your favourite quote here.
Erik Trulsson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: starting netatalk
Do you have options NETATALK in your kernel? It's not in the GENERIC kernel, and you'll need to compile a new kernel (or at least I did, the last time I installed netatalk). Mike Squires ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem connecting with Netatalk 2.0
I upgraded netatalk from 1.5 to 2.0 and now cannot
connect to my FreeBSD box.
I've altered the netatalk.sh file to this:
netatalk_enable=${netatalk_enable-YES}
atalkd_enable=${atalkd_enable-YES}
papd_enable=${papd_enable-NO}
cnid_metad_enable=${cnid_metad_enable-NO}
afpd_enable=${afpd_enable-YES}
timelord_enable=${timelord_enable-NO}
When I start netatalk I do get this warning -
spike# /usr/local/etc/rc.d/netatalk.sh start
dc0: multicast may not work correctly.
- but it then starts up
jim 72165 0.0 0.7 4044 1740 ?? I 9:41AM
0:00.01 /usr/local/sbin/afpd -s
/usr/local/etc/AppleVolumes.system -f
/usr/local/etc/AppleVolumes.default
root72163 0.0 0.6 4036 1564 ?? I 9:41AM
0:00.01 /usr/local/sbin/afpd -s
/usr/local/etc/AppleVolumes.system -f
/usr/local/etc/AppleVolumes.default
When I connect from my Mac (10.3.5) I get the dialog
box to enter in my login and password
for the volume on the FreeBSD box, but the box to
select the volumes I want to mount is empty.
I do have a tilde at the end of the
AppleVolumes.default file.
I tried to use NFS and it worked without a hitch,
except transferring files to the FreeBSD box via NFS
is
MUCH slower than using netatalk. I still have another
box running the older netatalk so I could time a file
copying to each system and was surprised to see how
slow NFS is compared to using Netatalk.
Any ideas what I'm missing?
Thanks,
Jim
___
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
How to start netatalk?
Hi, I want to share files between FreeBSD 5.3 and Mac OS X. I have compiled my kernel with the NETATALK option, and installed netatalk 2.0 from the port. What should I do now? --- Choy Kho Yee url: http://dotkoyi.infoseek.ne.jp/ blog: http://dotkoyi.blogspot.com/ There are only 10 types of people in the world, i.e. those who understand binary numbers and those who do not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to start netatalk?
On Mon, Oct 18, 2004 at 07:37:30PM +0900, Choy Kho Yee wrote: Hi, I want to share files between FreeBSD 5.3 and Mac OS X. I have compiled my kernel with the NETATALK option, and installed netatalk 2.0 from the port. What should I do now? Forget all about netatalk -- that's a hold over from the old MacOS 9 days. MacOS X does both NFS and Samba out of the box. Either of which would be a better choice. NFS is native to both platforms and probably the quickest to set up, but you'll have to synchronise UID and GID numbers between server and client for the user accounts that use it. Samba requires your installing some 3rd party software on the FreeBSD side, and working out how you're going to authenticate one to the other. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpBU9hUloP5E.pgp Description: PGP signature
Re: How to start netatalk?
On 2004/10/18, at 20:33, Matthew Seaman wrote: On Mon, Oct 18, 2004 at 07:37:30PM +0900, Choy Kho Yee wrote: Hi, I want to share files between FreeBSD 5.3 and Mac OS X. I have compiled my kernel with the NETATALK option, and installed netatalk 2.0 from the port. What should I do now? Forget all about netatalk -- that's a hold over from the old MacOS 9 days. MacOS X does both NFS and Samba out of the box. Either of which would be a better choice. NFS is native to both platforms and probably the quickest to set up, but you'll have to synchronise UID and GID numbers between server and client for the user accounts that use it. Samba requires your installing some 3rd party software on the FreeBSD side, and working out how you're going to authenticate one to the other. Cheers, Matthew Thanks for your advice. I have tried NFS but I am learning about IPFW on the FreeBSD box, and I heard that it is hard to properly configure IPFW to let through NFS packets, so I was thinking to switch to netatalk. I haven't tried Samba, though. Anyway, I just successfully setup netatalk to serve files to my iBook G4(Yes it is Mac OS X :D). I think I will stay with netatalk for a while. Thanks again :) --- Choy Kho Yee url: http://dotkoyi.infoseek.ne.jp/ blog: http://dotkoyi.blogspot.com/ There are only 10 types of people in the world, i.e. those who understand binary numbers and those who do not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
help with Netatalk
Hi guys I gwould like to configure netatalkd to downcase all the name files whe they are created. Is it passible?. I am running freebsd 5.1. Greetings and thanks in advance __ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Netatalk with 5.0?
Having upgraded a non-critical system to 5.1-BETA from 4.8 by wiping the drives and starting from scratch, just how does one add NETATALK to the new kernel config? I don't see it in /usr/src/sys/i386/conf/NOTES and we no longer have LINT... I do see netatalk at /usr/src/sys/netatalk/ but nothing other than a COPYRIGHT file and no hints as to how to apply. Or at least I think Protocol not supported is telling me the kernel is missing something: AndrAIa: [1005] /usr/local/etc/rc.d/netatalk.sh start netatalksocket: Protocol not supported socket: Protocol not supported atalkd: can't get interfaces, exiting. AndrAIa: [1006] I'd like to get netatalk working again. Then we'll figure out why Samba doesn't... -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with Netatalk 1.6
I want to have netatalk 1.6 to run on it. But after ./configure comes only: error Berkeley DB3 not found What can I do? Helmut -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems with Netatalk 1.6
On Wed, 22 Jan 2003 [EMAIL PROTECTED] wrote: I want to have netatalk 1.6 to run on it. But after ./configure comes only: error Berkeley DB3 not found What can I do? Helmut Are you installing it from the ports-system? Did you go to /usr/ports/net/netatalk and run make? If you want to install the app not using the ports-system you could try to install /usr/ports/databases/db3 and then once again try to ./configure Netatalk. Best regards, Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problems with Netatalk 1.6
On Wed, 2003-01-22 at 10:44, [EMAIL PROTECTED] wrote: I want to have netatalk 1.6 to run on it. But after ./configure comes only: error Berkeley DB3 not found What can I do? Build Netatalk from ports: # cd /usr/ports/net/netatalk # make install clean Else, you can patch the default distribution up so it can find libdb3 on FreeBSD. Joe Helmut -- PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
This is baffling. I have a OS X 10.2.3 machine that can connect just fine (as do you). The sniffer traces are more or less identical. Since it looks like the OS X client is initiating the disconnect, can you bring up the OS X console under Applications-Utilities-Console, and see if any messages show up there? Joe Rebooting my Mac solved the problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Netatalk - Mac OS X connection problem
I am running netatalk-1.6.0_1,1 from the FreeBSD ports systems on two
boxes and connecting from Mac OS X 10.2.3.
Now when I connect from one box I get the following error on the mac:
Connection failed
An AppleShare system error occurred.
I can connect to the other box without any problems. Netatalk is
configured the same on both boxes. This problem came on suddenly.
Below is the log file showing netatalk starting up.
This is a stumper.
Please also cc me on any email as I can no longer subscribe to the list.
Thanks,
Jim
Jan 11 17:37:32 atalkd[88690][logger.c:409]: I:Logger: doing
syslog_setup, type 0, level 50
Jan 11 17:37:32 atalkd[88690][logger.c:434]: D7:Logger:
log_file_arr[0] now contains: {log_filename:, log_file:0x0,
log_level: 50}
Jan 11 17:37:32 atalkd[88690][logger.c:437]: D5:Logger: syslog_setup[0] done
Jan 11 17:37:32 atalkd[88690][main.c:1090]: I:ATalkDaemon: restart (1.6.0)
Jan 11 17:37:34 atalkd[88690][zip.c:910]: I:ATalkDaemon: zip_getnetinfo for dc0
Jan 11 17:37:44 atalkd[88690][zip.c:910]: I:ATalkDaemon: zip_getnetinfo for dc0
Jan 11 17:37:54 atalkd[88690][zip.c:910]: I:ATalkDaemon: zip_getnetinfo for dc0
Jan 11 17:38:04 atalkd[88690][main.c:278]: I:ATalkDaemon: config for no router
Jan 11 17:38:06 atalkd[88690][main.c:659]: I:ATalkDaemon: ready 0/0/0
Jan 11 17:38:06 afpd[88691][logger.c:409]: I:Logger: doing
syslog_setup, type 0, level 50
Jan 11 17:38:06 afpd[88691][logger.c:434]: D7:Logger: log_file_arr[0]
now contains: {log_filename:, log_file:0x0, log_level: 50}
Jan 11 17:38:06 afpd[88691][logger.c:437]: D5:Logger: syslog_setup[0] done
--
Jim Arnold - Ohio.com - [EMAIL PROTECTED]
Cell: 330.730.0797 Voice: 330.572.2822
AOL IM: instantjim/Yahoo: jim0266
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
On Sat, 2003-01-11 at 18:00, Jim Arnold wrote: I am running netatalk-1.6.0_1,1 from the FreeBSD ports systems on two boxes and connecting from Mac OS X 10.2.3. Now when I connect from one box I get the following error on the mac: Connection failed An AppleShare system error occurred. I can connect to the other box without any problems. Netatalk is configured the same on both boxes. This problem came on suddenly. Below is the log file showing netatalk starting up. This is a stumper. Please also cc me on any email as I can no longer subscribe to the list. The log isn't too helpful, but a sniffer trace might be. Can you capture the client connection to the bad server with tcpdump, and send me the raw capture file. I recommend the following command line: tcpdump -s 1518 -w /tmp/outfile host IP address of client Note, this assumes you're connecting over TCP (which you really should be with OS X). Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Netatalk - Mac OS X connection problem
On Sat, 2003-01-11 at 19:12, Jim Arnold wrote: The log isn't too helpful, but a sniffer trace might be. Can you capture the client connection to the bad server with tcpdump, and send me the raw capture file. I recommend the following command line: tcpdump -s 1518 -w /tmp/outfile host IP address of client Note, this assumes you're connecting over TCP (which you really should be with OS X). Attached is the outfile as run on the FreeBSD box with the command line from above. tcpdump -s 1518 -w /tmp/outfile host 192.168.0.4 .4 is the Mac OS X box I hope this is what you meant. :) Do you have a custom volume icon on this server? If so, try deleting it, then reconnection. Joe Thanks, Jim -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Netatalk - Mac OS X connection problem
Do you have a custom volume icon on this server? If so, try deleting it, then reconnection. Nope. Nothing fancy. Just a straight install of Netatalk and I didn't change any of the icons. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
On Sat, 2003-01-11 at 20:40, Jim Arnold wrote: Do you have a custom volume icon on this server? If so, try deleting it, then reconnection. Nope. Nothing fancy. Just a straight install of Netatalk and I didn't change any of the icons. When exactly do you see the message? Right after you login? Can you send your AppleVolumes.default as well as your afpd.conf files? Does the user you're logging in as have a valid shell? Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Netatalk - Mac OS X connection problem
When exactly do you see the message? Right after you login? As soon as I hit the connect button after typing in the IP address of the FreeBSD box or using the afp address. Can you send your AppleVolumes.default This just has the ~ (tilde) at the end so the home directory will get mounted as well as your afpd.conf files? Everything in this file is commented out. In the file this is noted: The simplest case is to not have an afpd.conf I've always run Netatalk without anything in this file without any problems. Does the user you're logging in as have a valid shell? Yes. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Netatalk - Mac OS X connection problem
On Sat, 2003-01-11 at 21:56, Jim Arnold wrote: When exactly do you see the message? Right after you login? As soon as I hit the connect button after typing in the IP address of the FreeBSD box or using the afp address. Can you send your AppleVolumes.default This just has the ~ (tilde) at the end so the home directory will get mounted as well as your afpd.conf files? Everything in this file is commented out. In the file this is noted: The simplest case is to not have an afpd.conf I've always run Netatalk without anything in this file without any problems. Does the user you're logging in as have a valid shell? Yes. This is baffling. I have a OS X 10.2.3 machine that can connect just fine (as do you). The sniffer traces are more or less identical. Since it looks like the OS X client is initiating the disconnect, can you bring up the OS X console under Applications-Utilities-Console, and see if any messages show up there? Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Netatalk - Mac OS X connection problem
This is baffling. I have a OS X 10.2.3 machine that can connect just fine (as do you). The sniffer traces are more or less identical. Since it looks like the OS X client is initiating the disconnect, can you bring up the OS X console under Applications-Utilities-Console, and see if any messages show up there? No messages are appearing under the console when I try to mount the volume in question. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
netatalk port and remote printing
I'm trying to use my FreeBSD, 4.7 release, box as a remote print server for a Mac box on the network. Printing is fine with the FBSD box, using HP812C deskjet printer and apsfilter. I want to make sure I'm going down the correct path and not wasting time doing something that's *obviously* not right (though not obvious to me). I have installed the netatalk port, and am having problems identifying the printer to the add_netatalk_printer program. Does anyone know: 1) is this the correct way to configure a printer so the Mac can use it? 2) is there any good documentation anywhere on this? I've tried to follow Chuck's Tips at: http://lantech.geekvenue.net/chucktips/jason/chuck/986883054.html, but haven't had any luck Thanks for any help or pointers. Michael Heyes To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
