headers
Frank Lahm | 19 Jun 2012 15:22

Release planning: Netatalk 3

Hi,

Debian Wheezy freeze is sheduled for June so we may want to release
Netatalk 3 before that date. Any cons?

Distro packagers ( <at> Jonas) beware: this is a version upgrade without a
clean upgrade path as the configuration file syntax and names have
changed.

-f

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply |
headers
HAT | 19 Jun 2012 18:05
Picon
Gravatar

Re: Release planning: Netatalk 3

Hi,

Frank Lahm <franklahm <at> googlemail.com>, 19 Jun 2012 15:22:39 +0200
> Debian Wheezy freeze is sheduled for June so we may want to release
> Netatalk 3 before that date. Any cons?

#3521177 - Netatalk 3 on FreeBSD 9
#3519622 - Netatalk 2.2.2 - Ubuntu - Fault during Auth
Are these problems Pending? > Frank

I thought that I would implement only one.
Though regrettable, it's impossible for me now...
If cnid scheme is cdb or dbd, and volume paths are duplicated or nested,
the volume should be disabled.
Can this be implemented easily? > Frank

> Distro packagers ( <at> Jonas) beware: this is a version upgrade without a
> clean upgrade path as the configuration file syntax and names have
> changed.

deb package use --enable-fhs option.
If this option is used, the paths of bin, sbin and lib may be wrong.
Be fully careful! > Jonas

--

-- 
HAT

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
(Continue reading)

Permalink | Reply |
headers
Frank Lahm | 26 Jun 2012 15:11

Re: Release planning: Netatalk 3

2012/6/19 HAT <hat <at> fa2.so-net.ne.jp>:
> Frank Lahm <franklahm <at> googlemail.com>, 19 Jun 2012 15:22:39 +0200
>> Debian Wheezy freeze is sheduled for June so we may want to release
>> Netatalk 3 before that date. Any cons?
>
> #3521177 - Netatalk 3 on FreeBSD 9

FreeBSD folks will have to fix this one.

> #3519622 - Netatalk 2.2.2 - Ubuntu - Fault during Auth

Closed.
<https://sourceforge.net/tracker/index.php?func=detail&aid=3519622&group_id=8642&atid=108642>

> I thought that I would implement only one.
> Though regrettable, it's impossible for me now...
> If cnid scheme is cdb or dbd, and volume paths are duplicated or nested,
> the volume should be disabled.
> Can this be implemented easily? > Frank

This is a minor feature which can be added later with a 3.0.x point release.

Proposal:
release 3.0 early next week.

Any cons ?
-f

------------------------------------------------------------------------------
Live Security Virtual Conference
(Continue reading)

Permalink | Reply |
headers
HAT | 26 Jun 2012 15:32
Picon
Gravatar

Re: Release planning: Netatalk 3

Frank Lahm <franklahm <at> googlemail.com>, 26 Jun 2012 15:11:34 +0200
> 2012/6/19 HAT <hat <at> fa2.so-net.ne.jp>:
>> Frank Lahm <franklahm <at> googlemail.com>, 19 Jun 2012 15:22:39 +0200
>>> Debian Wheezy freeze is sheduled for June so we may want to release
>>> Netatalk 3 before that date. Any cons?
>>
>> #3521177 - Netatalk 3 on FreeBSD 9
> 
> FreeBSD folks will have to fix this one.

agree.

>> #3519622 - Netatalk 2.2.2 - Ubuntu - Fault during Auth
> 
> Closed.
> <https://sourceforge.net/tracker/index.php?func=detail&aid=3519622&group_id=8642&atid=108642>

agree.

>> I thought that I would implement only one.
>> Though regrettable, it's impossible for me now...
>> If cnid scheme is cdb or dbd, and volume paths are duplicated or nested,
>> the volume should be disabled.
>> Can this be implemented easily? > Frank
> 
> This is a minor feature which can be added later with a 3.0.x point release.

agree.

> Proposal:
(Continue reading)

Permalink | Reply |
headers
HAT | 4 Oct 2012 16:02
Picon
Gravatar

Re: Release planning: Netatalk 3

>>> I thought that I would implement only one.
>>> Though regrettable, it's impossible for me now...
>>> If cnid scheme is cdb or dbd, and volume paths are duplicated or nested,
>>> the volume should be disabled.
>>> Can this be implemented easily? > Frank
>> 
>> This is a minor feature which can be added later with a 3.0.x point release.

implemented in git.
http://sourceforge.net/p/netatalk/code/ci/f4436fa67103541b7ea5aee14bfe748ae19f6caa/

However, cnid scheme is not checked.

--

-- 
HAT

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
Permalink | Reply |
headers
HAT | 25 Oct 2012 14:03
Picon
Gravatar

nested volume (was: Release planning: Netatalk 3)

>>>> If cnid scheme is cdb or dbd, and volume paths are duplicated or nested,
>>>> the volume should be disabled.
>>>> Can this be implemented easily? > Frank
>>> 
>>> This is a minor feature which can be added later with a 3.0.x point release.
> 
> implemented in git.
> http://sourceforge.net/p/netatalk/code/ci/f4436fa67103541b7ea5aee14bfe748ae19f6caa/
> 
> However, cnid scheme is not checked.

commit db568ec6e05d9b7a5274b7d9a2338eaa146eb867
Author: Frank Lahm <franklahm <at> googlemail.com>
Date:   Wed Oct 10 15:34:34 2012 +0200
>Ensure the volume path is '/' terminated and allow nested volumes
>
>The previos change to the way checking for duplicate and nested paths only
>works if the path is terminated with a '/'.
>Allow nested volumes. This was working in 2.2 and can be used eg for sharing
>a ZFS snapshot directory of a volume. Afaict it only works with sane AFP
>semantics by adding 'cnid sheme = tdb' to the nested volume which also
>makes it read-only and by adding the name of the nested directory to
>the veto name list.

I understood that tdb must be used.
Is it necessary to make it read-only?

--

-- 
HAT
(Continue reading)

Permalink | Reply |
headers
Frank Lahm | 25 Oct 2012 16:26
Picon
Gravatar

Re: nested volume (was: Release planning: Netatalk 3)

2012/10/25 HAT <hat <at> fa2.so-net.ne.jp>:
>>>>> If cnid scheme is cdb or dbd, and volume paths are duplicated or nested,
>>>>> the volume should be disabled.
>>>>> Can this be implemented easily? > Frank
>>>>
>>>> This is a minor feature which can be added later with a 3.0.x point release.
>>
>> implemented in git.
>> http://sourceforge.net/p/netatalk/code/ci/f4436fa67103541b7ea5aee14bfe748ae19f6caa/
>>
>> However, cnid scheme is not checked.
>
> commit db568ec6e05d9b7a5274b7d9a2338eaa146eb867
> Author: Frank Lahm <franklahm <at> googlemail.com>
> Date:   Wed Oct 10 15:34:34 2012 +0200
>>Ensure the volume path is '/' terminated and allow nested volumes
>>
>>The previos change to the way checking for duplicate and nested paths only
>>works if the path is terminated with a '/'.
>>Allow nested volumes. This was working in 2.2 and can be used eg for sharing
>>a ZFS snapshot directory of a volume. Afaict it only works with sane AFP
>>semantics by adding 'cnid sheme = tdb' to the nested volume which also
>>makes it read-only and by adding the name of the nested directory to
>>the veto name list.
>
> I understood that tdb must be used.
> Is it necessary to make it read-only?

Because the set of CNIDs from both databases will be distinct but the
set of AppleDouble files/EAs where the CNID is stored as well is
(Continue reading)

Permalink | Reply |
headers
HAT | 7 Nov 2012 12:55
Picon
Gravatar

Re: nested volume

Frank Lahm <franklahm <at> gmail.com>, 25 Oct 2012 16:26:33 +0200
>> commit db568ec6e05d9b7a5274b7d9a2338eaa146eb867
>> Author: Frank Lahm <franklahm <at> googlemail.com>
>> Date:   Wed Oct 10 15:34:34 2012 +0200
>>>Ensure the volume path is '/' terminated and allow nested volumes
>>>
>>>The previos change to the way checking for duplicate and nested paths only
>>>works if the path is terminated with a '/'.
>>>Allow nested volumes. This was working in 2.2 and can be used eg for sharing
>>>a ZFS snapshot directory of a volume. Afaict it only works with sane AFP
>>>semantics by adding 'cnid sheme = tdb' to the nested volume which also
>>>makes it read-only and by adding the name of the nested directory to
>>>the veto name list.
>>
>> I understood that tdb must be used.
>> Is it necessary to make it read-only?
>
> Because the set of CNIDs from both databases will be distinct but the
> set of AppleDouble files/EAs where the CNID is stored as well is
> shared.

I see. I'm implementing it now.
If both are tdb, does one of the two need to be read-only?

--

-- 
HAT

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
(Continue reading)

Permalink | Reply |
headers
Frank Lahm | 7 Nov 2012 13:07
Picon
Gravatar

Re: nested volume

2012/11/7 HAT <hat <at> fa2.so-net.ne.jp>:
> Frank Lahm <franklahm <at> gmail.com>, 25 Oct 2012 16:26:33 +0200
>>> commit db568ec6e05d9b7a5274b7d9a2338eaa146eb867
>>> Author: Frank Lahm <franklahm <at> googlemail.com>
>>> Date:   Wed Oct 10 15:34:34 2012 +0200
>>>>Ensure the volume path is '/' terminated and allow nested volumes
>>>>
>>>>The previos change to the way checking for duplicate and nested paths only
>>>>works if the path is terminated with a '/'.
>>>>Allow nested volumes. This was working in 2.2 and can be used eg for sharing
>>>>a ZFS snapshot directory of a volume. Afaict it only works with sane AFP
>>>>semantics by adding 'cnid sheme = tdb' to the nested volume which also
>>>>makes it read-only and by adding the name of the nested directory to
>>>>the veto name list.
>>>
>>> I understood that tdb must be used.
>>> Is it necessary to make it read-only?
>>
>> Because the set of CNIDs from both databases will be distinct but the
>> set of AppleDouble files/EAs where the CNID is stored as well is
>> shared.
>
> I see. I'm implementing it now.

Implementing what? Just remember to be careful in this case as I know
of one pretty big customer relying on this functionality of sharing
subvolumes read-only without risking CNID issues!

> If both are tdb, does one of the two need to be read-only?
(Continue reading)

Permalink | Reply |
headers
HAT | 7 Nov 2012 13:17
Picon
Gravatar

Re: nested volume

Frank Lahm <franklahm <at> gmail.com>, 7 Nov 2012 13:07:02 +0100
> 2012/11/7 HAT <hat <at> fa2.so-net.ne.jp>:
>> Frank Lahm <franklahm <at> gmail.com>, 25 Oct 2012 16:26:33 +0200
>>>> commit db568ec6e05d9b7a5274b7d9a2338eaa146eb867
>>>> Author: Frank Lahm <franklahm <at> googlemail.com>
>>>> Date:   Wed Oct 10 15:34:34 2012 +0200
>>>>>Ensure the volume path is '/' terminated and allow nested volumes
>>>>>
>>>>>The previos change to the way checking for duplicate and nested paths only
>>>>>works if the path is terminated with a '/'.
>>>>>Allow nested volumes. This was working in 2.2 and can be used eg for sharing
>>>>>a ZFS snapshot directory of a volume. Afaict it only works with sane AFP
>>>>>semantics by adding 'cnid sheme = tdb' to the nested volume which also
>>>>>makes it read-only and by adding the name of the nested directory to
>>>>>the veto name list.
>>>>
>>>> I understood that tdb must be used.
>>>> Is it necessary to make it read-only?
>>>
>>> Because the set of CNIDs from both databases will be distinct but the
>>> set of AppleDouble files/EAs where the CNID is stored as well is
>>> shared.
>>
>> I see. I'm implementing it now.
> 
> Implementing what?

If paths are nested, the longer path is changed into tdb and read-only by default.
If one is tdb and read-only, nothing will be done.
(Continue reading)

Permalink | Reply |

Gmane