Date: Wed, 12 Apr 2000 11:35:11 -0400 From: "Gail M. Pickett" <gmpicket@icx.net> To: FreeBSD-Questions@FreeBSD.ORG Subject: RE: Macintosh access to FreeBSD over TCP/IP ?? Message-ID: <3.0.6.32.20000412113511.00797910@mailhub.icx.net>
next in thread | raw e-mail | index | archive | help
Thanks for help from both David Kelly and Chris Hill. <big snip> I got the netatalk uninstalled and did pkg_add for the netatalk-1.4b2 only. I don't have the CD's unfortunately. I checked Walnut Creek's website for ordering CD's and they only listed the CD set for 4.0 as being available which would mean upgrading. If I could get 3.3 Release on CD, I would be extremely happy. So, I see my choices for building a custom kernel: 1. Package (binary) upgrade from 3.3 to 3.4 by downloading the bin, man, boot floppies, and src/ssys (kernel source) and installing. 2. Use another machine running 3.3 Release (which is available) to CVSup, build and install world, build the custom kernel there, and then port the kernel (via floppy) to my file server. Would this actually work? 3. Get a modem (requires installing a new serial port and configuring with boot -c at boot time) and do CVSup directly on the file server (back-up first, of course), build/install world, then build custom kernel. 4. It is possible to manually configure the kernel for hardware at boot time, why isn't it possible to manually configure the kernel for other stuff at boot time, i.e. add the netatalk support? That it doesn't "stick" and has to be done each boot is no big deal as the file server stays on 24x7. That said, I will play with CAPS first and if that fails for me, I will try to build a custom kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.6.32.20000412113511.00797910>