netatalk

29 jan 2012 kl. 13.34 skrev Simon Hobson:

> System is Debian Squeeze running as a Xen PV guest. On trying to 
> start atalkd, I get :
>> eth0: disabled.
>> atalkd: zero interfaces, exiting.
> 
> If I add eth0 to the end of atalkd.conf, I get :
>> eth0: Invalid argument
>> Can't configure multicast.
>> eth0: disabled.
> 
> It's the same with 2.1.2 from Squeeze stable, or 2.2.1 from Testing.
> 
> Any suggestions how to debug this ? Searches don't throw up anything 
> particularly useful, and nothing recent.

Perhaps a stupid question, but is the AppleTalk (ddp) kernel module loaded?

Christian Huldt wrote:

>Perhaps a stupid question, but is the AppleTalk (ddp) kernel module loaded?

Not a stupid question, but I believe it is loaded, I assume you do 
mean the "appletalk" module :
># modprobe -l | grep -i apple
>kernel/drivers/net/appletalk/ipddp.ko
>kernel/drivers/usb/misc/appledisplay.ko
>kernel/drivers/input/mouse/appletouch.ko
>kernel/drivers/hwmon/applesmc.ko
>kernel/drivers/hid/hid-apple.ko
>kernel/net/appletalk/appletalk.ko


Also, ifconfig says multicast is on, and nothing changes if I put the 
I/F in promiscuous mode (by running tshark). Two of the things I 
found suggested in the past.

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

On Sat, 21 Jan 2012, Ryan Hoagland wrote:

> Hi good folks,
>
> I'm at a dead end in getting a Netatalk service running correctly.  It's
> running and I can connect to it from my Lion Mac, but when I try to write a
> file to it, the Mac says I need to Authenticate and then says that I don't
> have permission to write.
>
> The logs are filled with
> Jan 21 05:45:16 tequila afpd[15829]:
> getnamefromuuid(61C4BD64-BEA9-450D-9C04-2C1
> 9EA8F6545): no result from ldap_getnamefromuuid
> Jan 21 05:45:16 tequila afpd[15829]: getnamefromuuid(uuid, &username,
> &uuidtype)
> failed: Resource temporarily unavailable
>
> I was trying to avoid setting up a LDAP service because there isn't much
> documentation on how to make that work with netatalk, so I've linked my
> dhx.so files to the passwd versions hoping to avoid PAM.
> -rwxr-xr-x 1 root root 17128 Aug 19 00:25 uams_dhx2_pam.so
> -rwxr-xr-x 1 root root 13000 Aug 19 00:25 uams_dhx2_passwd.so
> lrwxrwxrwx 1 root root    19 Jan 20 09:16 uams_dhx2.so ->
> uams_dhx2_passwd.so
> -rwxr-xr-x 1 root root 16328 Aug 19 00:25 uams_dhx_pam.so
> -rwxr-xr-x 1 root root  9512 Aug 19 00:25 uams_dhx_passwd.so
> lrwxrwxrwx 1 root root    18 Jan 20 09:16 uams_dhx.so -> uams_dhx_passwd.so
>
> But I still get the getnamefromuuid failures.  My configuration is pretty
> vanilla: just creating some time machine shares.
>
> [root@... netatalk]# rpm -q netatalk
> netatalk-2.2.0-2.fc16.x86_64
>
> AppleVolumes.default:
> :DEFAULT: options:upriv,usedots
> /timemachines/RyanTM    "RyanTM"        options:tm
>
> netatalk.conf is unchanged from the factory except for:
> ATALK_NAME=filer
>
> afpd.conf is factory, so it doesn't have any lines uncommented.
>
> All the other config files are factory.  afp_ldap.conf is all commented out.
>
> So what's the simplest secret sauce to make Netatalk grant me write
> privileges to my share?  Do I really have to implement a LDAP server?  What
> ports then will I need to open up in iptables to make that work?  What
> ports do I need to have open for Netatalk?  I currently have all of these,
> but there isn't good documentation to say what is really needed.
>
> # AFP Netatalk
> -A INPUT -m state --state NEW -m udp -p udp --dport 427 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 427 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 548 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 5353 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 201 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 202 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 204 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 206 -j ACCEPT
> -A INPUT -m state --state NEW -m tcp -p tcp --dport 4700 -j ACCEPT
> -A INPUT -m state --state NEW -m udp -p udp --dport 4700 -j ACCEPT
>
> Thanks for the help,
> -Ryan.

All Linux distributions that I know of use PAM, so you should be pointing 
your UAMs to PAM.  Using PAM does not mean using LDAP.  Your PAM 
configuration is stored in /etc/pam.d/<servicename>.  Most of them point 
to the common-* files to use the system-wide PAM config.

All you really need to run afpd is port 548 allowed.

Are you connecting as a user that is present on your linux system?

I'm not familiar with the FC16 package.  Perhaps it has some unusual 
defaults that have LDAP lookups enabled?  Do you have an afp_ldap.conf 
file?  You probably want to remove it.

 	Andy

Thanks Andy,

Yeah following Kim Culhan's recommendation, I've restored the dhx files to
the pam versions.  But I still end up with the same permission problem and
errors in the logs.
[root@... pam.d]# ls -l /usr/lib64/atalk/
total 124
lrwxrwxrwx 1 root root    11 Jan 19 07:18 uams_clrtxt.so -> uams_pam.so
-rwxr-xr-x 1 root root 17128 Aug 19 00:25 uams_dhx2_pam.so
-rwxr-xr-x 1 root root 13000 Aug 19 00:25 uams_dhx2_passwd.so
lrwxrwxrwx 1 root root    16 Jan 21 10:47 uams_dhx2.so -> uams_dhx2_pam.so
-rwxr-xr-x 1 root root 16328 Aug 19 00:25 uams_dhx_pam.so
-rwxr-xr-x 1 root root  9512 Aug 19 00:25 uams_dhx_passwd.so
lrwxrwxrwx 1 root root    15 Jan 21 10:48 uams_dhx.so -> uams_dhx_pam.so
-rwxr-xr-x 1 root root 12048 Aug 19 00:25 uams_gss.so
-rwxr-xr-x 1 root root  6944 Aug 19 00:25 uams_guest.so
-rwxr-xr-x 1 root root 11352 Aug 19 00:25 uams_pam.so
-rwxr-xr-x 1 root root  9376 Aug 19 00:25 uams_passwd.so
-rwxr-xr-x 1 root root 12528 Aug 19 00:25 uams_randnum.so

Here is my /etc/pam.d/netatalk:
#%PAM-1.0
auth     include system-auth
account  include system-auth
password include system-auth
session  include system-auth

My afp_ldap.conf file has every line commented out with a #, which was the
default.

I've stopped iptables to remove that as a possible problem.

Yes the username, uid, and gid are all the same on both the Fedora server
and Lion client.  NFS works fine.

Any other things I can try?
Thanks,
-Ryan.

On Sun, Jan 22, 2012 at 9:42 AM, Andrew Morgan <morgan@...> wrote:

> On Sat, 21 Jan 2012, Ryan Hoagland wrote:
>
>  Hi good folks,
>>
>> I'm at a dead end in getting a Netatalk service running correctly.  It's
>> running and I can connect to it from my Lion Mac, but when I try to write
>> a
>> file to it, the Mac says I need to Authenticate and then says that I don't
>> have permission to write.
>>
>> The logs are filled with
>> Jan 21 05:45:16 tequila afpd[15829]:
>> getnamefromuuid(61C4BD64-BEA9-**450D-9C04-2C1
>> 9EA8F6545): no result from ldap_getnamefromuuid
>> Jan 21 05:45:16 tequila afpd[15829]: getnamefromuuid(uuid, &username,
>> &uuidtype)
>> failed: Resource temporarily unavailable
>>
>> I was trying to avoid setting up a LDAP service because there isn't much
>> documentation on how to make that work with netatalk, so I've linked my
>> dhx.so files to the passwd versions hoping to avoid PAM.
>> -rwxr-xr-x 1 root root 17128 Aug 19 00:25 uams_dhx2_pam.so
>> -rwxr-xr-x 1 root root 13000 Aug 19 00:25 uams_dhx2_passwd.so
>> lrwxrwxrwx 1 root root    19 Jan 20 09:16 uams_dhx2.so ->
>> uams_dhx2_passwd.so
>> -rwxr-xr-x 1 root root 16328 Aug 19 00:25 uams_dhx_pam.so
>> -rwxr-xr-x 1 root root  9512 Aug 19 00:25 uams_dhx_passwd.so
>> lrwxrwxrwx 1 root root    18 Jan 20 09:16 uams_dhx.so ->
>> uams_dhx_passwd.so
>>
>> But I still get the getnamefromuuid failures.  My configuration is pretty
>> vanilla: just creating some time machine shares.
>>
>> [root@... netatalk]# rpm -q netatalk
>> netatalk-2.2.0-2.fc16.x86_64
>>
>> AppleVolumes.default:
>> :DEFAULT: options:upriv,usedots
>> /timemachines/RyanTM    "RyanTM"        options:tm
>>
>> netatalk.conf is unchanged from the factory except for:
>> ATALK_NAME=filer
>>
>> afpd.conf is factory, so it doesn't have any lines uncommented.
>>
>> All the other config files are factory.  afp_ldap.conf is all commented
>> out.
>>
>> So what's the simplest secret sauce to make Netatalk grant me write
>> privileges to my share?  Do I really have to implement a LDAP server?
>>  What
>> ports then will I need to open up in iptables to make that work?  What
>> ports do I need to have open for Netatalk?  I currently have all of these,
>> but there isn't good documentation to say what is really needed.
>>
>> # AFP Netatalk
>> -A INPUT -m state --state NEW -m udp -p udp --dport 427 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 427 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 548 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 5353 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 201 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 202 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 204 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 206 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 4700 -j ACCEPT
>> -A INPUT -m state --state NEW -m udp -p udp --dport 4700 -j ACCEPT
>>
>> Thanks for the help,
>> -Ryan.
>>
>
> All Linux distributions that I know of use PAM, so you should be pointing
> your UAMs to PAM.  Using PAM does not mean using LDAP.  Your PAM
> configuration is stored in /etc/pam.d/<servicename>.  Most of them point to
> the common-* files to use the system-wide PAM config.
>
> All you really need to run afpd is port 548 allowed.
>
> Are you connecting as a user that is present on your linux system?
>
> I'm not familiar with the FC16 package.  Perhaps it has some unusual
> defaults that have LDAP lookups enabled?  Do you have an afp_ldap.conf
> file?  You probably want to remove it.
>
>        Andy
>

I believe this problem is sorted out now.  Kim Culhan pointed out that a
share with options:tm isn't like a traditional file share.  I was trying to
test out the read/write permissions before unleashing my time machine
client on it, but a share with options:tm doesn't operate like that.

So my problem is only my ignorance.

To avoid future support questions like this, I might suggest that some
documentation be added to the tm option indicating that a share with this
option cannot be used for normal file sharing from Finder.

Thanks
-Ryan.

On Sun, Jan 22, 2012 at 9:42 AM, Andrew Morgan <morgan@...> wrote:

> On Sat, 21 Jan 2012, Ryan Hoagland wrote:
>
>  Hi good folks,
>>
>> I'm at a dead end in getting a Netatalk service running correctly.  It's
>> running and I can connect to it from my Lion Mac, but when I try to write
>> a
>> file to it, the Mac says I need to Authenticate and then says that I don't
>> have permission to write.
>>
>> The logs are filled with
>> Jan 21 05:45:16 tequila afpd[15829]:
>> getnamefromuuid(61C4BD64-BEA9-**450D-9C04-2C1
>> 9EA8F6545): no result from ldap_getnamefromuuid
>> Jan 21 05:45:16 tequila afpd[15829]: getnamefromuuid(uuid, &username,
>> &uuidtype)
>> failed: Resource temporarily unavailable
>>
>> I was trying to avoid setting up a LDAP service because there isn't much
>> documentation on how to make that work with netatalk, so I've linked my
>> dhx.so files to the passwd versions hoping to avoid PAM.
>> -rwxr-xr-x 1 root root 17128 Aug 19 00:25 uams_dhx2_pam.so
>> -rwxr-xr-x 1 root root 13000 Aug 19 00:25 uams_dhx2_passwd.so
>> lrwxrwxrwx 1 root root    19 Jan 20 09:16 uams_dhx2.so ->
>> uams_dhx2_passwd.so
>> -rwxr-xr-x 1 root root 16328 Aug 19 00:25 uams_dhx_pam.so
>> -rwxr-xr-x 1 root root  9512 Aug 19 00:25 uams_dhx_passwd.so
>> lrwxrwxrwx 1 root root    18 Jan 20 09:16 uams_dhx.so ->
>> uams_dhx_passwd.so
>>
>> But I still get the getnamefromuuid failures.  My configuration is pretty
>> vanilla: just creating some time machine shares.
>>
>> [root@... netatalk]# rpm -q netatalk
>> netatalk-2.2.0-2.fc16.x86_64
>>
>> AppleVolumes.default:
>> :DEFAULT: options:upriv,usedots
>> /timemachines/RyanTM    "RyanTM"        options:tm
>>
>> netatalk.conf is unchanged from the factory except for:
>> ATALK_NAME=filer
>>
>> afpd.conf is factory, so it doesn't have any lines uncommented.
>>
>> All the other config files are factory.  afp_ldap.conf is all commented
>> out.
>>
>> So what's the simplest secret sauce to make Netatalk grant me write
>> privileges to my share?  Do I really have to implement a LDAP server?
>>  What
>> ports then will I need to open up in iptables to make that work?  What
>> ports do I need to have open for Netatalk?  I currently have all of these,
>> but there isn't good documentation to say what is really needed.
>>
>> # AFP Netatalk
>> -A INPUT -m state --state NEW -m udp -p udp --dport 427 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 427 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 548 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 5353 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 201 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 202 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 204 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 206 -j ACCEPT
>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 4700 -j ACCEPT
>> -A INPUT -m state --state NEW -m udp -p udp --dport 4700 -j ACCEPT
>>
>> Thanks for the help,
>> -Ryan.
>>
>
> All Linux distributions that I know of use PAM, so you should be pointing
> your UAMs to PAM.  Using PAM does not mean using LDAP.  Your PAM
> configuration is stored in /etc/pam.d/<servicename>.  Most of them point to
> the common-* files to use the system-wide PAM config.
>
> All you really need to run afpd is port 548 allowed.
>
> Are you connecting as a user that is present on your linux system?
>
> I'm not familiar with the FC16 package.  Perhaps it has some unusual
> defaults that have LDAP lookups enabled?  Do you have an afp_ldap.conf
> file?  You probably want to remove it.
>
>        Andy
>

Can you try v. 2.2.2?
Probably you have a problem due to a bug that has been fixed.

On 1/23/12 11:09 AM, David Cake wrote:
> 	I'm running a netatalk server on debian stable. Files are also shared to PCs via Samba, but that does not appear to be connected.
> 	For some files (definitely seems to be files that are copied direct in from email, may occur with some others), when users attempt to delete or rename, they get an error "The operation can't be completed because an unexpected error occurred (error code -50)". The logs reveal
> Jan 23 17:16:36.611174 afpd[21626] {ea.c:724} (E:AFPDaemon): ea_open('.AppleDouble/FILENAME.xlsx::EA'): bogus EA header file
> Jan 23 17:16:36.611246 afpd[21626] {ea.c:1329} (E:AFPDaemon): ea_deletefile('FILENAME.xlsx'): error calling ea_open
> (where filename is the name of the file, obviously)
> 	I've tried handrolling a 2.2.1 compile in the hopes this error (reported by others) was fixed, but it is now.
> 	Any suggestions?
> 	Regards
> 		David
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Netatalk-admins mailing list
> Netatalk-admins@...
> https://lists.sourceforge.net/lists/listinfo/netatalk-admins

Am 19.01.12 17:23, schrieb HAT:

> I'm writing a conversion-table.
> http://www003.upp.so-net.ne.jp/hat/netatalk/netatalk2to3.draft.html
>

I would not do that!

Maybe it is better to give infos before installing the new 
netatalk-version about changes in the netatalk-configs and publish a big 
warning:
"WUUUAAAH - your old config doesn't work after this update!!!! Read the 
fucking manual!!!" ;)

-- 
Gruß Michael

...der auch immer die eierlegende Wollmilchsau sucht. Aber entweder sind 
die Eier faul, die Wolle verfilzt oder die Sau gehört schon längst als 
Gammelfleisch entsorgt

Hi, all.

Although configuration of current netatalk is very difficult,
you have succeeded in configuration.
You will be able to write a certainly new conf file.

I propose a new format for future administrator, not you.
Please consider netatalk's future.

-- 
HAT

I think it would be a good change.  As so many other programs in Linux 
fall under this method, I think it would help new users with learning 
Netatalk.

Jeremy



From:   Frank Lahm <franklahm@...>
To:     netatalk-devel@..., netatalk-admins 
<netatalk-admins@...>, 
Date:   01/19/2012 04:46 AM
Subject:        [Netatalk-admins] [POLL] Use ini stye format in 
configuration files     in Netatalk 3



@netatalk-devel subscribers: reply-to netatalk-admins

Dear all,

we're currently considering the switch to ini style (cf Samba config)
in Netatalk's config files accompanied merging afpd.conf,
netatalk.conf and AppleVolumes.default to a single ini style config
file named afp.conf (though I'd prefer netatalk.conf but that would
seriously hinder 2.2 -> 3.0 upgrades).

The config file might look like this:
---8<---

[global]
       unix charset = UTF8
       mac charset = MAC_ROMAN
       vol charset = UTF8

;       max clients = 20

;       ext mapping = no

;       afp uam list = uam_dhx.so uam_dhx2.so
;       afp guest = nobody

;       afp volumes system =      ; (default is not defined)
;       afp volumes default =     ; (default is this file)

       vol unix priv = yes
       vol use dot = yes

;       vol directory perm = 0000
;       vol file perm = 0000

;       log type = default
;       log level = note
;       log file =

[AFP Server]
;       afp server name = $h

[CNID Server]

;[LDAP]
;       ldap server      = localhost
;       ldap auth method = simple
;       ldap auth dn     = cn=admin,dc=domain,dc=org
;       ....

;[EXT Mapping]
;       txt = "TEXT"  "ttxt"
;       zip = "ZIP "  "SITx"

[homes]
;       home name = $u

;[share sample]
;       vol path = /somewhere/my/share/directory

;[time machine sample]
;       vol path = /somewhere/backup/directory
;       vol time machine = yes
;       vol size limit = 1000
---8<---

Please vote whether you like to see this change or if not. Thanks!

-f

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Netatalk-admins mailing list
Netatalk-admins@...
https://lists.sourceforge.net/lists/listinfo/netatalk-admins

Am 19.01.12 18:52, schrieb HAT:
> Hi, all.
>
> Although configuration of current netatalk is very difficult,
> you have succeeded in configuration.

a textfile is a textfile

> You will be able to write a certainly new conf file.
>
> I propose a new format for future administrator, not you.
> Please consider netatalk's future.
>

i hope i understand you right - this is the same what i mean: a new 
configfile (easier as before) and thats it

i think the old configfile wasn't difficult. but ... try to dock some 
other tools (webmin, maybe) to netatalk ... it's difficult

ONE configfile!

@HAT: we are talking about the same :)

-- 
Gruß Michael

...der auch immer die eierlegende Wollmilchsau sucht. Aber entweder sind 
die Eier faul, die Wolle verfilzt oder die Sau gehört schon längst als 
Gammelfleisch entsorgt

On Thu, 2012-01-19 at 10:48 +0100, Frank Lahm wrote:
> @netatalk-devel subscribers: reply-to netatalk-admins
> 
> Dear all,
> 
> we're currently considering the switch to ini style (cf Samba config)
> in Netatalk's config files accompanied merging afpd.conf,
> netatalk.conf and AppleVolumes.default to a single ini style config
> file named afp.conf (though I'd prefer netatalk.conf but that would
> seriously hinder 2.2 -> 3.0 upgrades).
<<< snip >>>
> Please vote whether you like to see this change or if not. Thanks!
----
gosh yes... but a few things come to mind...

1 - comments in the default config(s) are presently quite good and would
want to see that they are preserved.

2 - a utility such as samba's 'testparm' which allows you to output a
configuration with all default (ie testparm -v), all uncommented
directives (ie, normal testparm). This could either be a separate script
or binary file or could be a built-in command like puppet as in 'puppet
--genconfig'

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

On 20/01/2012, at 12:19 PM, Craig White wrote:

> On Thu, 2012-01-19 at 10:48 +0100, Frank Lahm wrote:
>> @netatalk-devel subscribers: reply-to netatalk-admins
>> 
>> Dear all,
>> 
>> we're currently considering the switch to ini style (cf Samba config)
>> in Netatalk's config files accompanied merging afpd.conf,
>> netatalk.conf and AppleVolumes.default to a single ini style config
>> file named afp.conf (though I'd prefer netatalk.conf but that would
>> seriously hinder 2.2 -> 3.0 upgrades).
> <<< snip >>>
>> Please vote whether you like to see this change or if not. Thanks!
> ----
> gosh yes... but a few things come to mind...
> 
> 1 - comments in the default config(s) are presently quite good and would
> want to see that they are preserved.
+1
> 
> 2 - a utility such as samba's 'testparm' which allows you to output a
> configuration with all default (ie testparm -v), all uncommented
> directives (ie, normal testparm). This could either be a separate script
> or binary file or could be a built-in command like puppet as in 'puppet
> --genconfig'

Also +1.

I'm happy for the change to .ini, but I wouldn't call it a high priority.

I also thing afp.conf is a good name, like samba has smb.conf; afp is the main protocol netatalk is used for these days.

-Matt

Dear All,

>> gosh yes... 
++

>> 1 - comments in the default config(s) are presently quite good and would
>> want to see that they are preserved.
> +1
++

Personally i would like to name the .ini
"Jobs-wanted-for-Macs-to-keep-working" but maybe "netatalk.cf" oder
.conf is more conveniant.


>> 2 - a utility such as samba's 'testparm' which allows you to output a
>> configuration with all default (ie testparm -v), all uncommented
>> directives (ie, normal testparm). This could either be a separate script
>> or binary file or could be a built-in command like puppet as in 'puppet
>> --genconfig'
> Also +1.
++

Since testparm is gone (the name) i'd like to suggest "Birn-Test" or
"checksmacs".

SCNR & thanks for Your work!
Thomas

From: tr <tr@...>, 20 Jan 2012 09:05:05 +0100
> Personally i would like to name the .ini
> "Jobs-wanted-for-Macs-to-keep-working" but maybe "netatalk.cf" oder
> .conf is more conveniant.

afp_signature.conf and afp_voluuid.conf don't have change on netatalk3.
~/.AppleVolumes is renamed to ~/.afp_volumes because of ini format.

   afp.conf
   afp_signature.conf
   afp_voluuid.conf
   ~/.afp_volumes

I think these are very simple filename.

-- 
HAT