Command line problems.

[Steven Vollom]

On Thursday 13 August 2009 02:03:27 pm Frans Ketelaars wrote:
> On Thu, 13 Aug 2009 12:07:26 -0500, Roy Smith wrote:
> > Steven Vollom wrote:
> >> When I attempt to install anything, I get an error that line 52 is
> >> malformed. When I attempt to open Kate to read line 52 of
> >> /etc/apt/sources.lst, it opens in Kate with no data in the page.
> >
> > That's to be expected.  Why?  Because you're using the wrong filename!
> > The correct path/filename should be " not
> > /etc/apt/sources.lst.  When you started Kate with the filename
> > /etc/apt/sources.lst you told it the wrong filename so Kate thought you
> > were creating a new file because it did not find an exact match for the
> > filename you had specified.  

When I cut and paste, I sometimes carry an unintended error by someone helping 
me.  I am pretty sure that is what happened.  .lst did not stand out as an 
error when I read it.  Many times abbreviated forms of of words are used.  
When it was pointed out, I tried it and it solved the dilemma.  I accept 
blame, but it is not a mistake I mind taking responsibility for; it happens in 
computing.

> > Another thing to watch out for is
> > capitalization.  To Linux THISfile, Thisfile and thisfile would all be
> > seen as separate files because of the use, or absence of capital letters
> > in the filename.

I have become reasonably careful about that.  I just didn't see .lst as a 
potential wrong entry for list.  Kind of like BTW.
>
> True. That said, Steven recently had problems with the file
> "/boot/grub/menu.lst", and now had problems with the file
> "/etc/apt/sources.list" . Two different extensions for a list of grub
> stanza's and a list of software sources ;)

The boot grub problem was when I was working with a live CD.  It too was a new 
experience.  Since I do not even know what boot or grub do, other than it is 
required to make the computer work, finding sources.list missing makes sense to 
me now.  While it was happening, it felt like computer demons.  Everyone 
agreed what did not work for me.  I feel a little stupid now, but it won't 
happen again, so it was a good mistake as far as I am concerned.
>
>     -Frans

That is true, but I may have it now.  It is just an area I had no experience 
with, at least with any understanding.  I learned a bunch, and should not 
return with the same problem, hopefully.

I am very grateful for the last two helps; both were very fruitful.  Many 
times I have had to live with a solution and no understanding.  That is not 
the case here.  Both gave me permanent instruction.  Thanks!!

Steven