If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc).
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
I just installed cinelerra .deb with GDebi Package Installer from their website, only where did it install to and how can I open it? it isn't in the start menu...
it will then ask you for your root pw (likley same as login pw)
[sudo] password for user:
then a lot of stuff will fly by in the terminal screen Step 2:
username@pcnamenix:~$ sudo apt-get update
More fly by stuff then
Step 3:
username@pcnamenix:~$ sudo apt-get install cinelerra
(then this stuff will appear)
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
akiradnews cinelerracv liba52-0.7.4 libavcodec51 libavutil49 libfaad0
libgsm1 libguicastcv libmjpegtools0c2a libmpeg3cv libquicktime1
libquicktimecv libswscale0 optlibx11-noxcb-6 optlibx11-noxcb-data
The following NEW packages will be installed:
akiradnews cinelerra cinelerracv liba52-0.7.4 libavcodec51 libavutil49
libfaad0 libgsm1 libguicastcv libmjpegtools0c2a libmpeg3cv libquicktime1
libquicktimecv libswscale0 optlibx11-noxcb-6 optlibx11-noxcb-data
0 upgraded, 16 newly installed, 0 to remove and 0 not upgraded.
Need to get 18.7MB of archives.
After this operation, 42.9MB of additional disk space will be used. Do you want to continue [Y/n]? y (say Y)
then a lot of stuff will be flying by
and then
Setting up cinelerra (1:2.1.0-1svn20081017akirad2) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
username@pcnamenix:~$
Step 4 check multimedia menu Sweet its installed !!!
Why doesn't it explain this process on the website?
Right or wrong, an assumption is made by packagers, that the user has at least a basic understanding of the OS and how things work. For those new to Linux, this assumption creates a lot of confusion. To illustrate, think about the auto owner who, while not a certified auto mechanic, can change the oil, check fluids, very basic stuff. He goes to the dealer and purchases a service manual for his car, thinking it will provide him with everything he needs to know. He begins a process on the car, following the manual. Everything goes along just fine until he gets to step 7. Something seems to be missing. He doesn't know how to do step 7 because this step doesn't seem to have a direct connection to the other six steps he followed.
This happens because the service manual is written for certified mechanics - those who have been trained. And in this training, some things are taught that are then assumed to be known by any certified mechanic, and it's those things that aren't put into the manuals.
In some respects, using Linux is similar. How one gains the insight into these 'undocumented' pieces of knowledge is by using the system, searching resources (manuals, readme files, experiences of others, the 'Net', friends, trial-and-error, ...).
Linux, even the more "user friendly" versions, tends to be (more of) a working mans OS. And by that, I mean that if you like/enjoy tinkering with things, are (more) prone to ask "why does it do this" questions and aren't afraid to 'dig into' things to find out, Linux is an OS you will like to use/play with.
Windows no longer obstructs my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
Why doesn't it explain this process on the website?
Right or wrong, an assumption is made by packagers, that the user has at least a basic understanding of the OS and how things work. For those new to Linux, this assumption creates a lot of confusion. To illustrate, think about the auto owner who, while not a certified auto mechanic, can change the oil, check fluids, very basic stuff. He goes to the dealer and purchases a service manual for his car, thinking it will provide him with everything he needs to know. He begins a process on the car, following the manual. Everything goes along just fine until he gets to step 7. Something seems to be missing. He doesn't know how to do step 7 because this step doesn't seem to have a direct connection to the other six steps he followed.
This happens because the service manual is written for certified mechanics - those who have been trained. And in this training, some things are taught that are then assumed to be known by any certified mechanic, and it's those things that aren't put into the manuals.
In some respects, using Linux is similar. How one gains the insight into these 'undocumented' pieces of knowledge is by using the system, searching resources (manuals, readme files, experiences of others, the 'Net', friends, trial-and-error, ...).
Linux, even the more "user friendly" versions, tends to be (more of) a working mans OS. And by that, I mean that if you like/enjoy tinkering with things, are (more) prone to ask "why does it do this" questions and aren't afraid to 'dig into' things to find out, Linux is an OS you will like to use/play with.
Thank you for this explanation. To be honest, I have always wondered how people gain information on using Linux. I hope to stick around and learn!
You will find that KFN is a good source of information on Kubuntu Linux. Lot's of members here with varying degrees of knowledge/experience, and most more than willing to assist a new user.
Before you ask questions, please 'do your homework' first. Gather the information that will make the question understandable and useful for those who will be looking at it. You will find it useful to search through KFN on the single word solved in the subject line. Look at the initial post and then read through the rest of the replies to get a sense of how the process went. You'll begin to see how good questions are asked and how not-so-good questions were asked.
Think of this forum as a large estate you have been invited into. The host has told you to 'make yourself at home.' Well, do as your host said - make yourself at home - and that means exploring. Open doors, go down passageways. Peer into cupboards. Look behind tapestries. You know, be nosey. You won't discover what is to be found unless you start exploring.
Windows no longer obstructs my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
Combinations of Exit Status
One of the more obscure parts of bash syntax allows you to combine exit statuses logically, so that you can test more than one thing at a time.
The syntax statement1 && statement2 means "execute statement1, and if its exit status is 0, execute statement2.
Exit status 0 means that the command completed successfully.
Windows no longer obstructs my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
Comment