Installing and Uninstalling Packages and Activation and Deactivation of Daemons in Fonz fun. Preinstalled Packages. The main packages included in the fun. In a moment we will use rsync. Downloading packages. For you convinience, there is a script available from Uli which provides the functionality for downloading the additional packages by Fonz and Uli: mkdir- p/ffp/pkg/cd/ffp/pkg/wget http: //wolf- u. O/ffp/pkg/updater. Or can do it manually in the following sections: 1. Downloading additional packages provided by Fonz. You have downloaded or otherwise acquired a software package. Most likely it is archived (tarred) and compressed (gzipped), in.tar.gz or.tgz form (familiarly known as a 'tarball'). Home » Articles » Linux » Here Installing Software Packages (rpm, yum) This article provides an overview of the rpm and yum commands for installing software packages on Linux, with specific reference to the information. Downloading of the ffp packages. First make sure, you entered valid gateway & DNS servers in the CH3. SNAS configuration (browser - > enter name or IP address of your CH3. SNAS - > Setup - > LAN). Your CH3. SNAS needs this information in order to access the Internet. You can fill in these values manually (e. See tutorial page for details on how to do this. Download additional packages from fonz’ site using the “rsync” file transfer command. The the “.” at the end of the 3rd line is essential (Linux shorthand notation for the current folder): mkdir- p/ffp/pkg/cd/ffp/pkg//ffp/bin/rsync - av- -delete inreto. Note that the packages are together over 1. MBytes, so it can take a while. After the last file you get some statistics and return to the command prompt. This step results in roughly 1. To log in as the root user and enable remote display, complete one of the following procedures: If you are installing the software from an X Window System workstation or X terminal, then: Start a new X terminal session (xterm. My problem happened after installing Visual Studio 2015 Update 1. I tried all suggested solutions without luck, The solution which worked for me was a one from Eric Knox (Microsoft team) This is it. Download the correct. Installing and Uninstalling Packages and Activation and Deactivation of Daemons in Fonz fun Downloading additional packages provided by Uli. Many packages used in the tutorials on this site were created by Uli and are found in his repository. Before you execute the following commands, please make sure that you meet the prerequisites as described in the previous section. Download additional packages from Uli’s site using the “rsync” file transfer command. Note: The “.” at the end of the 3rd line is essential (Linux shorthand notation for the current folder): mkdir- p/ffp/pkg/cd/ffp/pkg//ffp/bin/rsync - av- -delete ffp. After the last file you also get some statistics and return to the command prompt. This step results in a few packages being copied (as tarballs) to the folder /ffp/pkg/additional/ and its subdirectories. See PACKAGES. txt for the available packages. Downloading packages from other sources. Make sure, you trust the source of any package that you download: a malicious (or just buggy) package can cause your NAS to fail, cause loss of data or worse! Package management. Package management is done by a program by fonz called “funpkg“. Typing “funpkg” on the command line lists the flags and options that it supports: Copyright (c)2. Tobias Poschwatta < tp@fonz. Install: funpkg - i< packages..>. Reinstall: funpkg - I< packages..>. Upgrade: funpkg - u< packages..>. Remove: funpkg - r< packages..>. D< path> System root directory (default: /)Important: once you start using funpkg to install Fonz’ packages, you have to complete the entire procedure described in this tutorial in one session. In other words, once you proceed with any of the steps beyond this point, you have to complete all steps of the Package management part of this tutorial: initial update for packagesinstall new packages, save any configuration changes that you need to save for existing packages that will be upgraded,upgrade existing packages, and (most important of all). Initial package updating. After the Installation you need to upgrade the installed packages ”’before”’ installing new packages. This is especially important for the funpkg tool itself, as new packages may require new features in funpkg. This is done by the parameter - u for the funpkg- tool. It updates any installed packages, but doesn’t install new ones. Now you can proceed with the next steps. Package installation. After a package has been downloaded (as a tarball or . The reason why Fonz recommends this route, rather than letting you install only what you want, is that some packages require other packages or updated versions of these packages to run correctly. Such dependencies are not automatically resolved by funpkg. Thus, for example, you can get into trouble if you update to the latest version of Open. SSH without updating the uclibc package (a library of utilities used by Open. SSH): if the SSH daemon fails to launch properly the next time you reboot the CH3. SNAS, you will be “locked out”. Which in turn means that you cannot use Pu. TTY to login and fix the problem (Hint: Turn on Telnet before updating SSH). The file /ffp/pkg/packages/MANIFEST. TXT contains a list of all the files installed by each package. You may want to have a look to get a feel for where all these roughly 2. Package configuration. During the installation, certain packages tend to add an ASCII file with configuration settings to the folder /ffp/etc/. This can be viewed from Windows using Word. Pad or a programming editor like Note. Pad++. The latter can edit ASCII files with the Linux end- of- line convention. Alternatively, you can use the Joe editor provided as one of these packages. Any modifications can obviously lead to “interesting” results, so be careful, especially with important daemons. Some packages place example configuration files into folder /ffp/etc/examples/ instead of putting actual configuration files into /ffp/etc/. Such files are ignored by the application: you are expected to read them and copy them (possibly after renaming or even editing) to folder /ffp/etc/ yourself. Examples for a package called PHP as listed in the MANIFEST. Package updating. Note that the names of the tarball files for packages end in an (often elaborate) version number. When you use funpkg - i packagename. Installing package lighttpd- 1. Skipping lighttpd- 1. Lighttpd is already installed. Or you may get. Skipping lighttpd- 1. You can force funpkg to install a different version (upgrade or downgrade) with the - u option: root@NAS: /mnt/HD. Again, this can be important because other installed packages may require this upgrade. But please beware of a number of pitfalls: This may overwrite any changes you made to configuration files (probably in folder /ffp/etc/). So you may want to create a copy of these first. This may overwrite access privileges you made to files (particularly to the scripts that start daemons in folder /ffp/start/). We will discuss the role of the - x flag below (when discussing how to enable/disable daemons) and now only concentrate on avoiding a very real pitfall which happens when you runfunpkg - u Open. SSH- versionnumber. If you look into MANIFEST. This would be fine if you don’t need to run the SSH server yet. The problem is that, after running funpkg - u for Open. SSH, a next reboot will not start the SSH daemon (server) and you will be locked out of funplug: Pu. TTY for example cannot connect using the ssh protocol unless there is a running SSH server. This server can only start with the - x (execute) bit on the file set. Remember that we set that bit for exactly this file in the fun? So we now need to do that again after you have upgraded whatever packages needed upgrading but BEFORE you exit ssh (or worse reboot the CH3. SNAS). So, to ensure that the file sshd. CH3. SNAS in the future: chmod a+x /ffp/start/sshd. This gives all users (a) the right to execute (x) the file /ffp/start/sshd. The folder listing will include- rw- r- -r- -1 root root 4. Jul 1. 51. 4: 4. 4 samba. Apr 2. 42. 0: 1. 6 smartd. Jul 2. 91. 6: 3. 0 sshd. Aug 1. 22. 2: 1. 7 syslogd. Aug 1. 22. 2: 1. 7 telnetd. If the entry for sshd. Package removals. If you want to (e. To remove a package completely, use: funpkg - r packagename. Again, some packages (like uclibc) may be needed to run other packages, so removing packages using funpkg is not foolproof. Fortunately, application packages which a non- expert is likely to be aware of because they do something for the end user (e. The example (from the file /ffp/start/sshd. PROVIDE: sshd# REQUIRE: LOGINsuggests that you shouldn’t remove the LOGIN package because it is required to run the sshd (=Open. SSH) package. 2. What are Daemons? Many packages can be used as “”Daemons””, which are basically programs running in the background. So lighttpd is not a light tpd (whatever that would be), but a light http (protocol) d(aemon) with a few letters mashed together. Every daemon that is capable of running in the background delivers a “starter file” which is located in /ffp/start/. These starter files are again simple scripts that control the startup and shutdown of the corresponding daemons. Some starter files provide additional capabilities and options, which are displayed by simply invoking the starter file without any parameters. Copy and paste the following one line at a time, and try a few more: cd/ffp/start. This works because starter files normally expect a “start” or “stop” parameter. Don’t try this trick with just any shell script: it may do something, because that is what it is there for. Starting Daemons manually. You can start every daemon manually by executingsh/ffp/start/desired. Stopping Daemons manually. You can stop every daemon manually by executingsh/ffp/start/desired. Permanent activation of Daemons. If you want to activate a Daemon permanently so that it gets executed during the bootup- process, you simply set the execution- right: chmod a+x desired. It will contain lines like*/ffp/start/sshd. Permanent deactivation of Daemons. Deactivation of a Daemon (no automatic execution during bootup) is done as follows: chmod a- x desired. It will contain lines like*/ffp/start/telnetd.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |