(I'd have nine new posts, and that's probably a bit much. Here goes. Mods retitle if necessary please)
Hi folks, I'm Yet Another Guy Who Started Using Linux Because He Hates Windows. I actually have been playing with Linux since back when Caldera had a distribution, and because I toyed with Linux sometimes and mainly used Windows I developed a lopsided knowledge. There are things I know, so sometimes I ask a 'how' question, and other times I ask "I know _how_ but I never really understood why so can someone summarize it" questions. BTW, Kubuntu 6.10 though I doubt that's relevant.
I'd appreciate any help or insight I can get.
Question 1. Pasting text into the console
Why doesn't CTRL + V work, why do I have to use Edit, Paste? Is CTRL + V not universal among apps?
Question 2. Screwed up file associations
I mistakenly associated .DEB files with Kate. How do I fix that? .PY too. In fact the more I use the system, the more things I discover to my endless delight open with Kate.
Question 3. Something like the Windows Registry
Windows had a Registry. There are plenty of negative things that can be said about it, but it did have one thing going for it -- it was a central location for operating system tweaks (including fixing screwed up file associations). I know that there is no central way of doing handy things in the Linux variants, but is there a utility that will a. launch all of or b. somehow find and let me see a list of config files for me to pick from?
Q4a,b. Menu items
When installing a new program, invariably an icon for the program will NEVER be placed in the K menu.
Question 4a. Why the *^#%&? not?!?!?!!! (see also question 10)
Question 4b. How do I find the binary, create an icon, and add it to the K menu... (drumroll) WITHOUT using the console? (((without without without?)))
Question 5. Running programs
Why is putting an icon in a menu anathema? Every tutorial site that tells me how to install new software says to open the console and type the program's name to start it. WHAT IS SO BAD ABOUT USING THE MENU?!?! Will people somewhere die because I click icons?
Question 6. A 'how' question. When I open the console, and I type a program name to start the program, how does the system know where to find it? What if I have more than one version? How come I don't have to type a path like I used to have to do in Windows? And yet... I also read somewhere that sometimes you DO have to tell Linux a path. When do I do this, and/or where would I edit a config file to tell it about a new path I made?
Question 7. apt-get update
I understand the concept of apt-get. It's the Advanced Package Tool. Before I officially ask "why the 'update' part of the command (it's to refresh the list, I know that) let me make an observation. Every tutorial puts this line before apt-get anything else. So why the heck doesn't the Adv. Pack. Tool just *assume* that it should do a refresh automatically? Would it be far off the mark to say that it seems a bit like having an automaker include separate switches for each headlight? We have two things to do -- apt-get update and then apt-get whatever the package you want is, so why two separate commands?
Question 8. Learning, for really real
Can anyone recommend exhaustive and graphical how-to sites?
There are Linux guides all over the Internet and I have seen an awful lot of them. They seem to fail noobs primarily for two reasons:
8a. No graphical how-to's, just "paste this text into the CLI and be done." Even sites that take GUIs into account, whether KDE or Gnome or xfce, will usually tell noobs to do something by pasting text that they quote into the console. (Now I know screenshots take up more bandwidth than a line of text, but if you're teaching about a GUI, why TF would you never show how to do something in that GUI?)
8b. Premature tutorial endings. I will read with great interest about how to do something. For example, I'll read about the organization of files. I read about the various directories like /usr, /var, /etc. Cool, now I'm getting somewhere. The tutorial will say I can browse with Konqueror. Great! I always wanted to know why I couldn't seem to see all of my directories and files at once instead of just my home directory.
Then, all of a sudden, BAM! That particular tutorial is over. It usually ends with something to the effect of "and there is certainly more you can learn about [whatever]!" Uh, I was hoping for a little more than "Konqueror can also be used to surf the web. Ok, tutorial's over! Bye!"
9. The future of installers
First, an aside as to why I am asking this. When I played with Red Hat back in 1999 or so, I recall having to mount my drives. One by one including the CDRom. I would ask in some forums if this was ever going to change. The answer was a resounding no, because there were too many inherent problems with automounting, and besides, what was so hard about writing a script to do it automatically? The prevailing wisdom at the time was that it was a pipe dream and really not even necessary.
Bring us to 2007. I (still) see three prominent methods of installing, including grabbing a tarred file, getting a DEB or getting a RPM. I see lots of disagreement over which is better. Will this be solved one day, like what we noobs used to complain about in 1999 that the experienced users said 'it ain't never gonna change?'
Thanks for any input.
Hi folks, I'm Yet Another Guy Who Started Using Linux Because He Hates Windows. I actually have been playing with Linux since back when Caldera had a distribution, and because I toyed with Linux sometimes and mainly used Windows I developed a lopsided knowledge. There are things I know, so sometimes I ask a 'how' question, and other times I ask "I know _how_ but I never really understood why so can someone summarize it" questions. BTW, Kubuntu 6.10 though I doubt that's relevant.
I'd appreciate any help or insight I can get.
Question 1. Pasting text into the console
Why doesn't CTRL + V work, why do I have to use Edit, Paste? Is CTRL + V not universal among apps?
Question 2. Screwed up file associations
I mistakenly associated .DEB files with Kate. How do I fix that? .PY too. In fact the more I use the system, the more things I discover to my endless delight open with Kate.
Question 3. Something like the Windows Registry
Windows had a Registry. There are plenty of negative things that can be said about it, but it did have one thing going for it -- it was a central location for operating system tweaks (including fixing screwed up file associations). I know that there is no central way of doing handy things in the Linux variants, but is there a utility that will a. launch all of or b. somehow find and let me see a list of config files for me to pick from?
Q4a,b. Menu items
When installing a new program, invariably an icon for the program will NEVER be placed in the K menu.
Question 4a. Why the *^#%&? not?!?!?!!! (see also question 10)
Question 4b. How do I find the binary, create an icon, and add it to the K menu... (drumroll) WITHOUT using the console? (((without without without?)))
Question 5. Running programs
Why is putting an icon in a menu anathema? Every tutorial site that tells me how to install new software says to open the console and type the program's name to start it. WHAT IS SO BAD ABOUT USING THE MENU?!?! Will people somewhere die because I click icons?
Question 6. A 'how' question. When I open the console, and I type a program name to start the program, how does the system know where to find it? What if I have more than one version? How come I don't have to type a path like I used to have to do in Windows? And yet... I also read somewhere that sometimes you DO have to tell Linux a path. When do I do this, and/or where would I edit a config file to tell it about a new path I made?
Question 7. apt-get update
I understand the concept of apt-get. It's the Advanced Package Tool. Before I officially ask "why the 'update' part of the command (it's to refresh the list, I know that) let me make an observation. Every tutorial puts this line before apt-get anything else. So why the heck doesn't the Adv. Pack. Tool just *assume* that it should do a refresh automatically? Would it be far off the mark to say that it seems a bit like having an automaker include separate switches for each headlight? We have two things to do -- apt-get update and then apt-get whatever the package you want is, so why two separate commands?
Question 8. Learning, for really real
Can anyone recommend exhaustive and graphical how-to sites?
There are Linux guides all over the Internet and I have seen an awful lot of them. They seem to fail noobs primarily for two reasons:
8a. No graphical how-to's, just "paste this text into the CLI and be done." Even sites that take GUIs into account, whether KDE or Gnome or xfce, will usually tell noobs to do something by pasting text that they quote into the console. (Now I know screenshots take up more bandwidth than a line of text, but if you're teaching about a GUI, why TF would you never show how to do something in that GUI?)
8b. Premature tutorial endings. I will read with great interest about how to do something. For example, I'll read about the organization of files. I read about the various directories like /usr, /var, /etc. Cool, now I'm getting somewhere. The tutorial will say I can browse with Konqueror. Great! I always wanted to know why I couldn't seem to see all of my directories and files at once instead of just my home directory.
Then, all of a sudden, BAM! That particular tutorial is over. It usually ends with something to the effect of "and there is certainly more you can learn about [whatever]!" Uh, I was hoping for a little more than "Konqueror can also be used to surf the web. Ok, tutorial's over! Bye!"
9. The future of installers
First, an aside as to why I am asking this. When I played with Red Hat back in 1999 or so, I recall having to mount my drives. One by one including the CDRom. I would ask in some forums if this was ever going to change. The answer was a resounding no, because there were too many inherent problems with automounting, and besides, what was so hard about writing a script to do it automatically? The prevailing wisdom at the time was that it was a pipe dream and really not even necessary.
Bring us to 2007. I (still) see three prominent methods of installing, including grabbing a tarred file, getting a DEB or getting a RPM. I see lots of disagreement over which is better. Will this be solved one day, like what we noobs used to complain about in 1999 that the experienced users said 'it ain't never gonna change?'
Thanks for any input.
Comment