unable to boot system! Why?

[igueths at attbi.com]

Hi Kenny. What I meant is that the base system tarball should contain the 
directory structure necessary 
i.e., /usr/bin/progname, /usr/local/bin/progname, /lib/libfile.so, etc etc. So 
what I meant was let's say I cd'ed to / within my chroot shell and typed tar 
zxvf basefile.tgz. It should theoretically extract to all appropriate 
directories including /lib and /usr? And if base-files isn't all includd in the 
tarball, do you know what other packages comprise it? Because what I figured I 
would do is extract the tarball to / and it should extract to all its 
directories contained in the structure. So my restore process would go 
something like this. 1. boot the rescue/root potato disks (this is all I have 
for the moment). 2. mount /dev/hda2 /target. 3. mount /dev/hda3 /target/usr. 4. 
chroot /target. 5. cd. 6. su -. 7. examine /etc/lilo.conf and make sure things 
are set up properly. 8. cd /. 9. tar zxvf basefile.tgz. 10. /sbin/lilo. 11. 
exit su and exit chroot shell. 12. umount /target/usr. 13. umount /target. 14. 
reboot with ctrl+alt+del. One more thing. I don't have access to another cdrw 
drive in order to transfer the base system to my Linux system. Does anyone know 
of a good file splitter for tat other os that will allow me to split a given 
file into 1.44 mb chunks? Bc I have about 50-100 or so floppies here so I can 
do that. And then I will just cat all the split files together once they are 
all coppied. The only reason I ask is because I know there are numerous file 
splitters out there, I just figured I would ask for recommendations. So does 
the above procedure work for restoring my system? Thanks all again for all the 
help! 
> 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 at 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
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup