Date: Thu, 6 Nov 1997 10:17:24 -0700 (MST) From: Brandon Gillespie <brandon@roguetrader.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: NetAtalk doesn't work!? take two Message-ID: <Pine.BSF.3.96.971106101453.10649A-100000@roguetrader.com> In-Reply-To: <4398.878788481@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Nov 1997, Jordan K. Hubbard wrote: > > Ok, I have a fresh/cleanly installed 2.2.5-R server. I recompiled the > > kernel to include the atalk option, I installed the netatalk package. All > > I want to do is to have this server be a unix->mac print spooler. I've > > dug through http files EVERYWHERE--I have read a ton of linux files on > > And you read the 2.2.5 ERRATA as I've been practically begging everyone > to do, right? :-) AUGH, feh, ok, something better needs to be done. Last I checked the 2.2.5 ERRATA it was empty. What about creating a xxx-errata mailing list, for each release? I.e. 2.2.5-errata, and have any changes placed in the errata mailed to the list as well, so we dont have to check it every day? There is no other easy way I can think of for one to learn of updates to the errata file--since the last time one checks it.. Just make it a sysconfig option of 'do you want to be added to the errata list for x release?' if yes, ask for an email address and shoot off an email submission request (if it fails, tell them user what to do). -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971106101453.10649A-100000>