Re: AppleTalk status
On Tue, May 25, 2010 at 6:25 AM, Stefan Bethke wrote: > Hi, > > I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that comes > out the next couple of days), and I'm wondering what state AppleTalk support > is in these days. Is anybody still using it, or would now be the time to > make all AppleTalk support in that port optional, and just focus on the file > server component? > > I haven't used AppleTalk for at least eight years now, and I don't quite see > which setting it still would be used in nowadays... Snow Leopard (10.6) dropped support for AppleTalk, so I think that making it compile-time optional would be the best way to go. Just my 2c. Thanks -- Chris - http://twitter.com/chrisattack http://chrisattack.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: AppleTalk status
On 25 May 2010, at 17:48, Julian Elischer wrote: >> I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when >> that comes out the next couple of days), and I'm wondering what >> state AppleTalk support is in these days. Is anybody still using >> it, or would now be the time to make all AppleTalk support in that >> port optional, and just focus on the file server component? >> >> I haven't used AppleTalk for at least eight years now, and I don't >> quite see which setting it still would be used in nowadays... > > I did the original port to freeBSD (from a netbsd port from memory) > I haven't checked recently but it was used by several companies running > legacy stuff in some industrial control situations. > In any case it's good having a working example of another protocol > as the world is getting a bit too focused on IP these days > and having a different protocol in the sources keeps us honest. FWIW, I have no intention of removing the kernel support for appletalk (or, perhaps more properly, ethertalk). It does want to be changed to use our link layer improvements in 8.x, but what is there today works fine and should continue to work fine for the forseeable future. Virtualizing for VIMAGE will probably take someone a couple of afternoons, and I tentatively plan to do it "at some point" before 9.0. Robert___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: AppleTalk status
On 5/25/10 4:25 AM, Stefan Bethke wrote: Hi, I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that comes out the next couple of days), and I'm wondering what state AppleTalk support is in these days. Is anybody still using it, or would now be the time to make all AppleTalk support in that port optional, and just focus on the file server component? I haven't used AppleTalk for at least eight years now, and I don't quite see which setting it still would be used in nowadays... I did the original port to freeBSD (from a netbsd port from memory) I haven't checked recently but it was used by several companies running legacy stuff in some industrial control situations. In any case it's good having a working example of another protocol as the world is getting a bit too focused on IP these days and having a different protocol in the sources keeps us honest. Thanks, Stefan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: AppleTalk status
> > On 25/05/2010, at 20:55, Stefan Bethke wrote: > >> I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that > >> comes out the next couple of days), and I'm wondering what state AppleTalk > >> support is in these days. Is anybody still using it, or would now be the > >> time to make all AppleTalk support in that port optional, and just focus > >> on the file server component? > >> > >> I haven't used AppleTalk for at least eight years now, and I don't quite > >> see which setting it still would be used in nowadays... > > > > I use it so I can back my Macbook Pro to my FreeBSD server on a ZFS > > partition.. > > (But that is all) > > You're using the sys/netatalk AppleTalk protocol for that, or TCP? The > netatalk port's afpd (Apple File Protocol daemon) can speak AFP over both > DDP/ASP and TCP, and I'll keep afpd working over TCP of course. I'm talking > about disabling AppleTalk protocol support. > > I think that making it optional would be smartest choice. I think only people with older equipment that cannot do TCP would need it and that most likely is a select few. definitely better than flat out removing completely. _ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: AppleTalk status
Stefan Bethke wrote: Hi, I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that comes out the next couple of days), and I'm wondering what state AppleTalk support is in these days. Is anybody still using it, or would now be the time to make all AppleTalk support in that port optional, and just focus on the file server component? I haven't used AppleTalk for at least eight years now, and I don't quite see which setting it still would be used in nowadays... Thanks, Stefan I use it successfully on a router to connect my antique AppleTalk-only laser printer. It seems to work quite well still. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: AppleTalk status
On 25 May 2010, at 14:13, Nathan Whitehorn wrote: >> I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that >> comes out the next couple of days), and I'm wondering what state AppleTalk >> support is in these days. Is anybody still using it, or would now be the >> time to make all AppleTalk support in that port optional, and just focus on >> the file server component? >> >> I haven't used AppleTalk for at least eight years now, and I don't quite see >> which setting it still would be used in nowadays... > I use it successfully on a router to connect my antique AppleTalk-only laser > printer. It seems to work quite well still. I can confirm that whenever kernel netatalk gets broken, I get bug reports. :-) However, it hasn't gotten broken in a year or two so I've not polled recently. Robert___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: AppleTalk status
On 25/05/2010, at 22:05, Stefan Bethke wrote: > You're using the sys/netatalk AppleTalk protocol for that, or TCP? The > netatalk port's afpd (Apple File Protocol daemon) can speak AFP over both > DDP/ASP and TCP, and I'll keep afpd working over TCP of course. I'm talking > about disabling AppleTalk protocol support. Ahh, sorry, yes I am using TCP! -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: AppleTalk status
Am 25.05.2010 um 13:41 schrieb Daniel O'Connor: > On 25/05/2010, at 20:55, Stefan Bethke wrote: >> I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that >> comes out the next couple of days), and I'm wondering what state AppleTalk >> support is in these days. Is anybody still using it, or would now be the >> time to make all AppleTalk support in that port optional, and just focus on >> the file server component? >> >> I haven't used AppleTalk for at least eight years now, and I don't quite see >> which setting it still would be used in nowadays... > > I use it so I can back my Macbook Pro to my FreeBSD server on a ZFS > partition.. > (But that is all) You're using the sys/netatalk AppleTalk protocol for that, or TCP? The netatalk port's afpd (Apple File Protocol daemon) can speak AFP over both DDP/ASP and TCP, and I'll keep afpd working over TCP of course. I'm talking about disabling AppleTalk protocol support. Stefan -- Stefan BethkeFon +49 151 14070811 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: AppleTalk status
On 25/05/2010, at 20:55, Stefan Bethke wrote: > I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that comes > out the next couple of days), and I'm wondering what state AppleTalk support > is in these days. Is anybody still using it, or would now be the time to > make all AppleTalk support in that port optional, and just focus on the file > server component? > > I haven't used AppleTalk for at least eight years now, and I don't quite see > which setting it still would be used in nowadays... I use it so I can back my Macbook Pro to my FreeBSD server on a ZFS partition.. (But that is all) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
AppleTalk status
Hi, I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that comes out the next couple of days), and I'm wondering what state AppleTalk support is in these days. Is anybody still using it, or would now be the time to make all AppleTalk support in that port optional, and just focus on the file server component? I haven't used AppleTalk for at least eight years now, and I don't quite see which setting it still would be used in nowadays... Thanks, Stefan -- Stefan BethkeFon +49 151 14070811 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
