Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had the 32 bit Veetle plugin working on my AMD64 Mythbuntu 8.10 system 0just fine using the instruction described in this thread.
At the time I had 32bit Flash 10 plugin installed and working fine with nspluginwrapper at the same time.
I then upgraded to the 64 bit Flash 10 alpha and it worked just fine. I think all I did was to put the .so into the ~/.mozilla/plugins directory and remove the flashplugin-nonfree package through Synaptic.
However, now the Veetle plugin no longer seems to work and I get the following errors when opening a Veetle site from Firefox in the terminal:
Actually, what I expect you do is copy and paste the line with the command as well as the entire output - that way there is no confusion about what you have done.
I'm going to try to teach you, by example, basic concepts of commandline. Notice in what follows how I paste the command as well as the result.
$ ls -l veetle*
ls: cannot access veetle*: No such file or directory
... this result tells me that I am in the wrong directory. ls lists the content of the directory that corresponds to what comes after. I am asking the computer to tell me what files in the current directory start with the word "veetle" and and in anything at all.
I can tell what the current directory is with the pwd command
If I try to do what you did I get:
$ sudo sh veetle-0.9.16-linux-install.sh
sh: Can't open veetle-0.9.16-linux-install.sh
... this is expected - sh cannot open the veetle script because it is not there. The bourne shell (sh) is not that great with error messages. If I tried using bash (the default terminal in Ubuntu) I'd get:
$ sudo ./veetle-0.9.16-linux-install.sh
bash: Can't open veetle-0.9.16-linux-install.sh: No such file or directory
Notice the ./ that replaces "sh" of the previous example? This is to tell bash to look in the current directory. The output provides more information - so is more helpful.
note: sh is short for Bourne shell, bash, which came after, is short for bourne-again shell.
What happened was: I actually put the veetle install script in a subdirectory of my home directory called "scripts" so I have to cd into that directory first vis:
$ cd scripts
$ ls -l veetle*
-rw-r--r-- 1 simon simon 3266 2010-01-10 01:48 veetle-0.9.16-linux-install.sh
... this result shows me the version of the script as well as its permissions. You'll see that the script is not executable, so I need to change it's mode thus:
sudo chmod +x veetle-0.9.16-linux-install.sh
before I can run it.
To run a script in a shell, you have to have permission to do so, and you have to have access to the script... you get access by telling the shell where the script is (the ./ in bash when you are in the same directory) or by putting the script someplace that is in your PATH. You can tell which directories are in your path by doing: echo $PATH - in this case, stick to changing directory.
Our ability to help you is being hampered by your insistence on providing minimal or no information at all. We are forced to guess from a wide range of possibilities. You have also shown no willingness to try to work anything out for yourself - you seem content to blindly follow exact directions rather than think around the problem or even learn the basics of what is needed to carry out your desired task. As a result, this problem is taking too long to solve.
Perhaps you are worried that if you reveal more detail you will make yourself look stupid? Relax, you are among friends: we've all been there and nobody will judge you.
However, now the Veetle plugin no longer seems to work
That would be expected - you've changed the OS in a fundamental way so you can expect unsupported applications to break.
Please note: your question is only periferally related to this one. I know we prefer you to post to an existing thread rather than start a new one, but that makes no sense when you have a new question.
I get the following errors when opening a Veetle site from Firefox in the terminal:
Invesigating this question I began to wonder why not use VLC to access veetle streams.
It turns out that this is what veetle actually does. Since veetle is distributed under a non-free license (see below), there have been concerns raised about compliance with the GPL (VLC code).
The issue was brought to the attention of VLC maintainers in November last year ... and to Veetle shortly after. The issue was still in the process of being resolved as of January this year.
The discussion continues. VLC and veetle code are asserted to run side-by-side so the non-free licence applies to the veetle part and the gpl applies to the vlc part. Its just that the documentation in the tarball says the opposite... it says that all the programs accompanying it are covered, and that it is the only relevant agreement involved.
Since Veetle is really just VLC, then VLC must be a veetle player - and it should be possible to stream veetle channels in VLC. And, indeed, this seemsto be the case.
Licence distributed with veetle 0.9.16 (released Jan28)
This EULA grants you the following rights:
A. You may install, use, access, display and run the Software, on a single computer, workstation or terminal ("Computer") for your personal use only. The primary user of the Computer on which the Software is installed may make a second copy for his or her exclusive use for archival purposes only.
B. You may store or install a copy of the Software on a storage device, such as a network server, used only to run the Software on your other Computers over an internal network. You must, however, acquire a license for each separate Computer on which the Software is run, displayed or utilized from the server or similar device. A license for the Software may not be
shared or used concurrently on different Computers.
C. Your license rights under this EULA are non-exclusive. All rights not expressly granted herein are reserved by Licensor.
D. You may not sell, transfer or convey the Software to any third party without Licensor's prior express written consent.
Last edited by Simon Bridge; 02-20-2010 at 12:12 AM.
I am using Linux Mint and just installed Veetle in just a few steps. Linux Mint is really Ubuntu in a different look so this should work for Ubuntu also.
In the terminal first cd to the directory where you have the Veetle file.
Then do this: chmod +x veetle-0.9.17-linux-install.sh
Then do this: sh veetle-0.9.17-linux-install.sh
The install will start.
You will have to go through the terms of agreement by hitting 'enter' about a dozen or more times and then it will finish up.
Exit out, start Firefox and enjoy.
The above is the latest version of Veetle that I used. Any newer versions should make the necessary changes but the steps should be the same.
thanks a lot for this post, i was having the same problem with veetle and this fixed it right up. i really appreciate these boards for learning about how linux works. could someone post a quick description on what those commands actually mean? i like knowing what the actual steps meant, instead of just blindly following commands. thanks!
Please help me. I'm a complete newbie and I followed what simon bridge said to do and I successfully installed veetle. now my home directory has a lock emblem on it and I can't delete the veetle install file which is in my home directory.
I know I changed some permissions but can someone help me change them back.
I really only did the following commands:
sudo chmod +x veetle-0.9.16-linux-install.sh
sudo sh veetle-0.9.16-linux-install.sh