From: Kenny Hitt <kennyhitt@knology.net>
To: speakup@braille.uwo.ca
Subject: Re: unable to boot system! Why?
Date: Mon, 7 Apr 2003 07:46:51 -0500 [thread overview]
Message-ID: <20030407124651.GA1521@potpal> (raw)
In-Reply-To: <E192VXx-0005HE-00@speech.braille.uwo.ca>
Hi. No, base-files is a package. Try downloading the base system and
untaring it into an empty directory. I'm not sure if base-files is all
that's included in the base system tar ball. If the-files package is
all that's in a base system tar ball, you can try installing it with
dpkg -i base-files*.deb
This command assumes you are in the same directory as the base-files
package.
Kenny
n Mon, Apr 07, 2003 at 12:15:50PM +0000, igueths@attbi.com wrote:
> Hi Kenny. Assuming the libs won't work even after I chroot, can I just download
> the base system from the latest stable version onto a Cd, and then untar it
> from the chroot shell? As in chroot /target cd tar zxvf basefile.tgz?
> > Hi. Not sure what caused your problem, but I'm almost certain that when
> > you copied the potato boot disk's /lib to /target/lib you made things
> > worse.
> > The libraries on the install disk are stripped down versions. The files
> > you see in /lib after an install were unpacked from the base system.
> > Also, the files in /lib have likely been updated since you first
> > installed the system. If you've dist-upgraded to Woody since the
> > install most of /lib was replaced with newer versions.
> >
> > The way to run the lilo on your installed system if you have booted from
> > a rescue disk is to chroot into /target first. That way, the system
> > should use the corect lilo and shared libs. Since you have already done
> > the cp command, it might be to late.
> >
> > If I'm wrong then hopefully someone will corect me.
> > Kenny
> >
> > On Sun, Apr 06, 2003 at 08:32:17PM -0700, Igor Gueths wrote:
> > > Hi Greg. Well, I can access all the data on the drive just fine. However, I
> > > can't boot from the hard disk. Lilo just does what I described earlier in
> > > the previous post. I also can't do anything to the already installed lilo
> > > from the rescue floppies, because I get that error while loading shared
> > > libraries. I do not have another Linux box to aid in this restoration
> > > process. And restoring the libs from the rescue disk to the target /lib
> > > didn't do anything. The files got coppied, but I got the same error. Does
> > > loading shared libraries. ./Lilo: Symbol __cxa_atexit, version glibc_1.2.3,
> > > not defined in file libc.so.6 with link time reference. I tried copying the
> > > /lib directory from the rescue flopppy (root floppy) to /target/lib, and no
> > > effect. I still got the same error. And this box still will not reboot. And
> > > I do not want to install my entire system over again. Is there any way I can
> > > restore Lilo/all the libs without having to re-install everything? Has
> > > anyone encountered this error before and if so how did you fix it? Thanks!
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
igueths
` Kenny Hitt [this message]
-- strict thread matches above, loose matches on Subject: below --
igueths
igueths
Igor Gueths
` Gregory Nowak
` Igor Gueths
` Adam Myrow
` Kenny Hitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030407124651.GA1521@potpal \
--to=kennyhitt@knology.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).