Prev: HELP no more Xwindows! libtermcap.so.2 cannot open shared object
Next: cdrecord versus mkisofs ?
From: Bill Marcum on 3 Jan 2010 21:02
On 2010-01-04, Ohmster <root(a)dev.nul.invalid> wrote:
>
> /bin/sh: error while loading shared libraries: libtermcap.so.2 cannot open
> shared object file: No such file or directory
>
> Oh Christ, what did I do and more important, how can I get my Xwindows back
> with beryl and all that cool stuff, all gone! Please help.
>
Maybe it's time to install a more recent distro.
From: J.O. Aho on 4 Jan 2010 00:44
Ohmster wrote:
> I was trying to update firefox and ran into some fc6 rpms installed on my
> fc9 platform so I could not update firefox. As it turns out, firefox itself
> was an fc6 rpm!
>
> So this time I updated the fc6 file that was causing the problem, as well
> as the yelp fc6 file that was stopping me from doing that, in est, this is
> what I did:
>
> sudo yum update gnome-doc-utils yelp firefox
>
> Now this actually worked with what appeard to be some minor errors at the
> end, like this:
>
> /bin/sh: error while loading shared libraries: libtermcap.so.2: cannot open
> shared object file: No such file or directory
> error: %postun(nspr-4.6.7-0.6.1.fc6.i386) scriptlet failed, exit status 127
> error: %preun(yelp-2.16.0-13.fc6.i386) scriptlet failed, exit status 127
>
> This did not seem too bad but now I have no Xwindows at all! Now when I try
> startx, I get this error and no more windows:
>
> /bin/sh: error while loading shared libraries: libtermcap.so.2 cannot open
> shared object file: No such file or directory
>
> Oh Christ, what did I do and more important, how can I get my Xwindows back
> with beryl and all that cool stuff, all gone! Please help.

yum update termcap

You will most likely have something else broken, all those fc6 things really
has caused you these problems and you need to replace those with the correct
packages.


--

//Aho
From: David W. Hodgins on 4 Jan 2010 10:50
On Mon, 04 Jan 2010 10:30:59 -0500, Ohmster <root(a)dev.nul.invalid> wrote:

> and files from. My original disk is VolGroup00 as an lvm disk and Fedora

man vgrename. May need to edit /etc/fstab before rebooting, if
it's still using /dev/mapper/??? entries, instead of labels or
uuids.

> will install to the new disk as VolGroup00 thus making it impossible for me

I haven't used the fedora installer. I expect a little digging
would show that you can override the volume group name.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
From: Dan C on 5 Jan 2010 09:00
On Mon, 04 Jan 2010 19:38:35 -0600, Ohmster wrote:

> Nico Kadel-Garcia <nkadel(a)gmail.com> wrote in news:bfa3981f-5d53-47e8-
> 8bb8-45fbc8e58d73(a)e27g2000yqd.googlegroups.com:
>
>> Oh, dear gods. That explains it. I wish you'd mentioned using oddball
>> repositories earlier.
>>
>> Cleaning up that kind of mess would take me a day, with good bandwidth,
>> and I'd bill you for it if you needed it that badly. But you should be
>> able to add the new disk, set it up with a live CD, set up LVM on the
>> new disk with a different Volume and Group name, or use Fedora disks to
>> *manually* configure disks and set them up appropriately.
>
> Nico,
>
> Hah! I did not see your offer in the begriming of this paragraph. Thank
> you for the offer, that would be pretty neat, you clean it up remotely
> with my cable connection and I pay for the service, but, to me, Linux is
> about the learning. l love it because I learn new things. I just copied
> the lvm man page to a text file so that I can read it more easily with a
> list of all of the major lvm tools that I will be able to use. I also
> found the FAQ at TLDP, LVM HOWTO, and found some good reasons to use lvm
> in Chapter 2. What is Logical Volume Management?, Section 2.2. Benefits
> of Logical Volume Management on a Small System actually makes good sense
> and I will use this as a tool for my next install so that I know what
> the heck I am doing this time and can name and create the volumes as
> necessary, label them appropriately, and size them accordingly. I
> especially like that you can move the space around if you need to or
> even add another disk to the file system and it just blends right into
> the file system as a whole and can then be doled out where it is needed
> most, in more than one area if need be. This sure beats the old method
> of splicing in a new drive under "\home" like I used to do.
>
> Maybe lvm is not so bad, once you get to understand it and use it
> properly. Oh and thanks for the cleanup offer. That was very generous as
> a task like that might tale forever, even though you do know what you
> are doing.

What exactly is it that you do, that requires management of huge disk
space? Why would you need LVM, or to "splice in a new drive" on a normal
home system?

Seriously, what are you saving? How much volume are you doing, anyway?


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he wiped the vomit from his chin.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
From: Dan C on 5 Jan 2010 09:01
On Mon, 04 Jan 2010 13:41:28 -0600, Ohmster wrote:

> Bill Marcum <marcumbill(a)bellsouth.net> wrote in
> news:nqu717-0rv.ln1(a)marcumbill.bellsouth.net:
>
>>> Oh Christ, what did I do and more important, how can I get my Xwindows
>>> back with beryl and all that cool stuff, all gone! Please help.
>>>
>> Maybe it's time to install a more recent distro.
>>
>>
> It definitely is Bill. Just trying to cobble together what I have now
> but for sure, it's time.

Then quit cobbling, and friggin install something from this century.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he wiped the vomit from his chin.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
 |  Next  |  Last
Pages: 1 2
Prev: HELP no more Xwindows! libtermcap.so.2 cannot open shared object
Next: cdrecord versus mkisofs ?