[netatalk-admins] current netatalk plans


Subject: [netatalk-admins] current netatalk plans
From: a sun (asun@saul2.u.washington.edu)
Date: Thu Mar 12 1998 - 17:25:48 EST


i thought i'd clue people into my current plans for my patches to
netatalk. these plans are all somewhat contingent upon available
time. in addition, some of them are very much in the long-term view of
things.

the scoop on my part:
        1) i'll probably merge in the new solaris driver if the folks
           at umich don't mind. i had planned on doing it by just
           merging against 1.4b3, but i haven't received a reply on
           when that will appear. i know there's still a problem with
           setsockopt(SO_BROADCAST) as of the 971027 snapshot. wes?

        2) i'll probably add in things like timeouts and finer scale
           control of number of users, etc at some point.

        3) i'll probably add stubs to afpd to talk to a file catalogue
           daemon for lookup and updating directories. the catalog
           daemon will probably take a little longer to actually
           write. this should solve three problems of which i'm
           aware:
                a) we should be able to add in persistent file id's.
                b) we should be able to tag filename lengths as short
                   (11 mac chars), medium (31 mac chars), and long
                   (255 unicode chars). this should help prepare afpd
                   for long filename support.
                c) directory lookups should get faster.

        4) more preparation for long filename unicode support. a spec
           doesn't really exist yet, but i can pretty much guess some
           of the bits that need changing. the folks at apple say that
           a few of the functions will need continuations due to
           afp/asp restrictions, but that should be easy enough to
           handle.

        5) merge in of ascii mappings so that netatalk and samba
           interact better. i asked the folks at whistle for their
           patches, but i haven't received them yet. this will
           probably munged with #4 to some extent.

        6) make afpd buildable without appletalk support needed. this
           should allow many more machines to use afpd.

        7) OPI support. as far as i can, all that really needs to be
           done is to make the printing OPI aware. that is, papd and
           psf need to recognize OPI comments and substitute files
           on the fly. what other uses are OPI servers used for?

-a



This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:31:34 EST