I’m using a SPARC20, which has a two-in-one serial port. In that case, much of the following dial-up setup will be done by your hardware. If you were using this box as a dial-up server for an ISP, you might look at implementing something like a Livingston unit for banks of modems. You connect an external modem to the built-in serial port or add S-bus serial MUXes, such as those made by Aurora and others, to have multiple serial ports. Most SPARCs do not come with internal modems. Now suppose you want to share this newfound power with some friends or access your server from work or while on vacation? You can readily do that by configuring the machine to act as a dial-up server and with some additional software, you can make it look like a native Windows or MacOS server. You have a Web server and a database server running, and with PHP you can do some neat things by tying the two together. You have Solaris up and running and set up to your internal network. Stew Benedict walks you through setting up a dial-up server with Solaris and then makes the connection with an array of operating systems. These are all things that a package management tool does (as well as making sure dependencies are met etc.For enterprise-level IT departments, setting up a dial-up server is critical to business. To not use a binary package means that you will have to keep track of where all the files are installed yourself, tar them up somehow and then hope that untarring that tar file won't overwrite things at the destination. Here's a HOWTO for dpkg, and here's another that the Rasbian people link to from their own pages. If it isn't available, or you just don't want to contact the maintainer, you could consider building a package with whatever package managing system Rasbian uses (seems to be Debian packages).If it is available, but the version is too old, then I would contact the package maintainer about an update.If it is available, that would be your first port of call.I'm not a Rasbian user and I don't know if netatalk is available as a package for the system (checking. This is why packaging tools like yum, dpkg and rpm exists. make a note of the libraries you need to install separately to get everything working.on each Raspberry Pi, run make install.copy the tarball to the other Raspberry Pis.If checkinstall doesn't work, there's always the pre-built tarball approach: deb should have the appropriate dependencies. That way you know that the required libraries are already installed, and the resulting. Install it again using checkinstall: checkinstall -D make install There's a simpler variant if the netatalk Makefile has a working uninstall target: in that case, on the first Raspberry Pi, packages (not -dev!) are installed on the second one. I'm not sure how well this will work if any of the required libraries are missing, so you may want to run ldd on the binaries on your first Raspberry Pi beforehand, and make sure that the corresponding lib. deb package to other Raspberry Pi systems. This last step will install the binaries copied across in the pre-built source from your first Raspberry Pi (which shouldn't require any -dev package), and build a. Install the binaries using checkinstall checkinstall -D make install
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |