On Wed, May 9, 2012 at 10:53 AM, Paul E Condon <pecon...@mesanetworks.net> wrote: > On 20120509_012529, Tom H wrote: >> On Tue, May 8, 2012 at 5:14 PM, Paul E Condon <pecon...@mesanetworks.net> >> wrote: >>> On 20120506_230937, Paul E Condon wrote: >>>> >>>> I have a long and troubled relation to Netatalk. I live in a family >>>> where everyone else loves the Mac, and I have a need to communicate >>>> with them. I once had netatalk running on Debian back in 2004, I >>>> think, but lost that ability about the time my daughter bought her >>>> first MacBook in 2006. I'm revisiting the problem now using an i386 >>>> box running Wheezy. >>>> >>>> I've installed netatalk from a Debian repository and started looking >>>> at /usr/share/doc/netatalk and the looking for a man page. The >>>> .../doc/netatalk files all date from 2010 or earlier, which is well >>>> before the version of netatalk in Wheezy was released. There is not >>>> 'man netatalk', but there is a 'man netatalk.conf', and that page >>>> begins with: >>>> >>>> " SYNOPSIS >>>> /etc/netatalk/netatalk.conf " >>>> >>>> But no such file was installed by the netatalk package, and I can find >>>> no mention of netatalk.conf at .../doc/netatalk/ >>>> >>>> According to Aptitude, the version of netatalk that I installed >>>> is 2.2.2-1. From searching the web, I pick up statements that >>>> things do work in it that never worked before. But I can't see >>>> anything different in the documentation. I remember that, when I >>>> did have it working long ago, I didn't have to do anything in >>>> order to have it advertise its services and to have it actually >>>> serve files. My problems then were with serving a printer. Now I >>>> use CUPS for that. But I don't see my Macs picking up an advert. >>>> (They do pickup adverts from one of the Macs, so I know that they >>>> are listening.) >>>> >>>> So, my questions: >>>> >>>> Does anyone have netatalk 2.2.2-1 working under Wheezy? Can you point >>>> me to some debugging instructions? Or, can you lead me through some >>>> tests to discover what is going wrong? >>> I posted this, below, a couple of days ago. I'm hoping to find someone >>> who follows this list and who actually has netatalk v. 2.2.2-1 >>> installed from the Debian package in Wheezy. I would very much like to >>> get it working, but ... I can't. All the documentation that I can find >>> is two or more years old, and does not pertain to the packaged >>> version. >>> >>> P.S. Thanks Tom, but I need more than the fact that >>> /etc/netatalk/netatalk.conf once existed as part of an earlier version >>> of the package. It may still be part of a properly configured >>> netatalk, but it doesn't seem to be included in this package. >> >> Please bottom-post. >> >> You misunderstood. I said that I remember that the config files on >> Debian are "/etc/default/netatalk" and /etc/netatalk/afpd.conf". >> Perhaps I should've also said that I remember >> "/etc/netatalk/netatalk.conf" to be the Fedora equivalent of >> "/etc/default/netatalk". > > Thanks, Tom. > > I certainly did misunderstand, and calling it to my attention is much > appreciated. I my defense, I note that the package does add to the man > pages a page for netatalk.conf, and that man page does say it is > located in /etc/netatalk/, which begs the question, What is a default? > In other places than Debian, default behavior of a program is the way > it behaves if there is not a configuration file. Live and learn.
You're welcome. I was wondering whether a bug should be filed against the man page of "netatalk.conf". Not having netatalk installed and feeling too lazy to instal it in a spare Vm, I googled the "netatalk.conf" Debian man page and landed on the project's original man page [1] and it has the following text: "If netatalk has been configured with --enable-debian, it is not netatalk.conf but etc/default/netatalk". I don't quite understand what you mean by "default behavior" but in Debian, files in "/etc/default" are often used to control the behavior of init daemons. (In RHEL/Fedora, "/etc/sysconfig" is used so it's surprising that the maintainer didn't relocate "/etc/netatalk/netatalk.conf" to "/etc/sysconfig/netatalk". He/she could even convince upstream to add a "--redhat" compilation flag and a explanatory line in the man page!) AFAIK/AFAIR, it's "/etc/netatalk/afpd.conf" that's the more important file and someone posted an example for you so I hope you have netatalk running. 1. http://netatalk.sourceforge.net/2.2/htmldocs/netatalk.conf.5.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=swn7oaq9uay1npjo01sexdvxrufiw8bnhse4owqu2d...@mail.gmail.com