[Linux-disciples] apt-get problems

Nirmal Trivedi ntrivedi at bostoncoop.net
Sun Apr 18 14:43:56 EDT 2004


Yes, thanks again Dylan for your help. I ran debsums which didn't
produce any further errors, so I'm hoping I'm okay for now. Should I be
using other utilities periodically?

I suspect my disk corruption occurs because of some manual (hard)
shutdowns I had to do with my Omnibook. Whenever I put the computer back
on the base, I have trouble booting up. This usually results in several
attempts at shutting down and restarting, which I'm sure is not good for
the computer. Maybe I should abandon the base altogether since I have an
external DVD drive now. 

On Sat, 2004-04-17 at 00:11, Adam Kessel wrote:
> Ditto everything Dylan said--
> 
> and after *that* you should probably do some checking to see if your hard
> drive is failing.  After what we went through with bostoncoop.net the
> last few days, you should catch hardware failure in the nub.
> 
> There are various utilities that can test your disk, and also you should
> keep an eye on /var/log/syslog--try grepping through the past few weeks
> of syslog files for your hard drive (presumably hda)--and see if there is
> some failure happening...
> 
> This could also be due to suspend/resume, if you're doing that.
> 
> On Fri, Apr 16, 2004 at 07:25:56PM -0400, Dylan Thurston wrote:
> > On Fri, Apr 16, 2004 at 06:11:40PM -0400, Stephen R Laniel wrote:
> > > On Fri, Apr 16, 2004 at 06:01:37PM -0400, Nirmal Trivedi wrote:
> > > > I ran fsck which did fix all kinds of broken inodes (?), but it looks
> > > > like that process also removed /usr/sbin/install-info. The file no
> > > > longer exists, which also means I cannot run dpkg or apt-get install.
> > > 
> > > That sucks. Does anyone know of a way to bootstrap onesself
> > > into dpkg, short of just sending along a tarball of all the
> > > dpkg files with all the metadata inside?
> > 
> > A .deb is an ar file which in turn contains some .tar.gz files.  To open
> > it up:
> > 
> > -------
> > dpt at lotus:/tmp/dpkg$ ar xvf /var/cache/apt/archives/dpkg_1.10.20_i386.deb 
> > x - debian-binary
> > x - control.tar.gz
> > x - data.tar.gz
> > dpt at lotus:/tmp/dpkg$ tar xvfz data.tar.gz 
> > ./
> > ./usr/
> > ./usr/share/
> > ./usr/share/doc/
> > ./usr/share/doc/dpkg/
> > ./usr/share/doc/dpkg/THANKS.gz
> > ./usr/share/doc/dpkg/TODO.gz
> > ./usr/share/doc/dpkg/changelog.gz
> > ./usr/share/doc/dpkg/dpkg.cfg
> > ......
> > ------
> > 
> > So you should grab a copy of your version of dpkg (say, from
> > packages.debian.org), open it up, grab /usr/sbin/install-info, and then
> > reinstall dpkg the proper way (dpkg -i <dpkg deb>).
> > 
> > You might also want to install debsums to check if you had any other
> > disk corruption.
> > 
> > Peace,
> > 	Dylan
> 
> 
> 
> > _______________________________________________
> > Linux-disciples mailing list
> > Linux-disciples at lists.bostoncoop.net
> > http://lists.bostoncoop.net/mailman/listinfo/linux-disciples
> 


More information about the Linux-disciples mailing list