Results 1 to 8 of 8

Thread: Two things

Threaded View

  1. #1
    Join Date
    Jan 2012

    Two things


    why oh why do Linux not have an easy App-install set-up such as download said .tgz.... extract .tgz to App/Program folder... et Voila!!!


    Why must I waste another 2 days of my precious life trying to install (what has become) a multitude of programmes, NONE of which have been installed btw.

    Where should I download the files to?
    Where should I unpack the files to?
    How do I navigate to which folder?
    Do I need sudo command?
    Do I need to be Root?
    Etcetera, etcetera, etcetera.......

    Why are Linux FORCING me to use <snip> WINDOWS????????

    All I want is a program (not installed) that generates a Square Wave that I can view in Xoscope (installed).

    How difficult should that be??

    Why am I -once again- feeling like smashing my computer and am generally thoroughly pissed off? Thanks for that.

    Why do the Linux Admin do this to people?

    The following excerpt is an example of the 'BASIC' app install instructions. Herein is the single clearest reason that unless Linux HELPS Joe Public (who are time-restricted and not Computer components), that Linux shall never evolve past the Geek and Tech world.
    Maybe that's cool for Linux snobs but what an incredible and ironic shame that Linux FORCE people to use Widows!!!!

    Anyway here's the 'Basic' instructions......


    If what I downloaded from the net is a Linux source code in the form of a compressed tarball (*.tar.gz or *.tgz), the installation procedure is longer and more troublesome than with the binary-only rpm. I typically install the program as root.
    First, I change my current working directory to /usr/local :

    cd /usr/local

    , I decompress the tarball that I downloaded from the net:

    tar -xvzf /home/the_dir_where_the_tarball_is/my_tarball.tar.gz

    This extracts (option "x") the contents of the *.tar.gz (or *.tgz) tarball, unzips it (option "z"), while talking to me more than usual (option "v" = verbose). Please note that the option "f" means "file", so the filename must immediately follow the letter "f". The contents of the tarball are extracted into a subdirectory which tar creates under my current working directory, which in the typical case is /usr/local/ . The tarball knows what the new subdirectory should be called.

    If the tarball is not compressed (e.g., *.tar), I may use:

    tar -xvf /home/the_dir_where_the_tarball_is/my_tarball.tar

    Third, I have to figure how the new directory is called, then I cd into it:

    cd the_new_program_subdir

    Since some of the directories have long names, I use the great autocompletion option to save on typing--I just type the first few letters and then press .

    Fourth, most programs are compiled by executing these three commands:

    make install

    The above commands can take some time to complete (1 min? 0.5 h?). If any of them fail, it might be an idea to read the README or INSTALL or whatever info is provided with the new program. Some programs may require customization of the environment (e.g. definition of their path) or installation of an additional library, or yet something else. It can sometimes be a pain. Very simple programs might not need the "./configure" or/and "make install" step, in which case "make" alone will do.

    Fifth, if everything goes well, I find the new executable which I just compiled. The names of executables display in green when running this command:

    ls --color

    Now, I can run the executable, for example:


    Some programs automatically install the executable to /usr/local/bin, so I may want to try:
    Sixth, if I plan to run the program more often, I create a symbolic link to the executable from the directory /usr/local/bin :
    cd /usr/local/bin
    ln -s /usr/local/the_new_program_subdir/the_executable .

    This way, the executable (actually, a symbolic link to it) is on my PATH and it can be run by simply typing its name (no need to type the full path to the executable any more). Some programs will install the executable (or a link to it) in a "bin" directory in which case you skip the last step.

    ..... Basically incomprehensible ??????????????????????????

    So, I have an idea,

    Why don't you just write Linux instructions in the secret Klagarian code of the Universal and multi-dimensional, Great White Brotherhood?

    I shall now turn this computer off and leave the house before I put my fist through it's screen (again).

    Happy New Year!!
    Last edited by Sef; January 27th, 2013 at 04:33 AM. Reason: removed profanity


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts