Jaunty reloaded and working
Karl F. Larsen
klarsen1 at gmail.com
Sat Jun 13 11:56:20 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
> Karl F. Larsen wrote:
>> H.S. wrote:
>>> Karl F. Larsen wrote:
>>>> H.S. wrote:
>>>>> Karl Larsen wrote:
>>>>>> It was easy as always to completely remove my broken Jaunty and load a
>>>>>> new one and update it from Beta with 450 upgrades! I now have
>>>>> What do you mean by "update it from Beta"?
>>>> Exactly what it says. I have a CD-Rom LiveCD of Jaunty version Beta.
>>>> This is where I started.
>>> Why would you update form beta and not from the release? Betas are
>>> exactly what they say, betas. And are not as stable as the releases. You
>>> are inviting unnecessary trouble by installing and updating a beta version.
>>> Now, if you wrote beta but are actually following the release, then it
>>> is different than what you wrote.
>>> The usual method is to start with the release. This way you would have
>>> fewer updates to do. Not to mention the fact that the release is
>>> considered more stable than beta, hence saving you from potential problems.
>> You are just not smart enough to understand how things work. So let me
> No need to be caustic. It won't give you anything in the long term here.
> However, you still haven't been able to explain how you screwed up your
> own /etc/hosts.
That is easy. I had named my Jaunty "mycrap" when I loaded it the first
time. I wanted to change this to Jaunty. I tried several times with the
Terminal writing $sudo hostname jaunty and it would change for the time
it was up but then revert to mycrap on the next re-boot.
So I found /etc/hostname and I changed it there. That was fine but
should also have changed it in /etc/hosts.
Is that clear?
At present, it is clear you have no clue what happened
> with your system that you are administering. Given these factors, I
> suggested you start with the most reliable method of installation at
> your disposal. But hey, whatever rocks your boat.
Well you said that using the Beta version would not work. This is not
true, it works fine.
>> spell it out for you:
>> Step 1: Put the LiveCD CD-Rom into the reader. It is a Jaunty-Beta cd I
>> d/l from the Ubuntu web page.
>> Step 2: Fix the /boot/grub/menu.lst so it boots like I like it!
>> Step 3: See the Update Manager say you have 450 upgrades to add to your
>> system. Ask it to start and go to your meetings.
> What happens to the prompts aptitude may throw at you?
> There is a better and more cautious and robust method to this though. I
> am sure you already know that.
>> Step 4: Reboot and now you have what someone with the other LiveCD and
>> 200 upgrades. EXACTLY THE SAME THING!!!
> Yet your system is behaving all weird. Did you not follow this exact
> same path last time as well? I don't know, that is why I am asking.
This version I did yesterday has no problems I have found. It has
Breserio to make CD-Roms and also the Gnome system which I like. I found
the PGP numbers from my old setup at /home/karl/.gnupg/ and got it
working again better than it was.
I did follow the exact same path last time. But last time I got very
mad at Totem and I deleted Totem. That is an error since Bresario uses
some of Totems libs.
This time I played Moviemaker's game and got the drivers it needed to
play .wmv and .avi files just like VLC does right out of the bag. Then I
got the codex needed to play movies on VLC and by golly Moviemaker
actually can display a movie too.
Karl F. Larsen, AKA K5DI
Key ID = 3951B48D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the ubuntu-users