Andrew Sackville-West wrote:
On Wed, Feb 07, 2007 at 11:17:50PM -0800, Freddy Freeloader wrote:
Freddy Freeloader wrote:
Kevin Ross wrote:
Errors were encountered while processing:
libc6
libc6-amd64
libc6-dev
I'm running Sid with the 2.6.18-4-486 kernel.
Is it even possible to run 64-bit apps with a 486 kernel?
This is something that I have wondered about too. I've been curious
as to why it was installed. It definitely isn't something that I
intentionally installed. It had to have been installed either with
the system originally, or as a dependency requirement for another
package.
Well, this is solved, at least it's working anyway. What I found was
that /etc/init.d/glibc.sh had been renamed. Once I renamed it libc6,
libc6-amd64, and libc6-dev all installed normally. How the glibc.sh
script came to be renamed I haven't a clue.
This is the the 5th or 6th strange thing that has happened since I
rebuilt my laptop. The others have all been related to
/etc/apt/sources.list. The first time I booted into the machine and
went to install software I found all lines in sources.list had been
commented out. This has been happening on a daily basis since then.
All entries in the file were commented out again. It seems to have
happened during the failed update that included the libc6 packages.
ongoing problem? the lines in sources.list keep getting commented out?
that ain't right. I've never seen *anything* touch sources.list except
apt-spy and I think it warns you.
A
Yeah. It's pretty strange. I've run both chkrootkit and rkhunter, as
this made me very suspicious, but they find nothing amiss.
As for apt-spy, it is a handy little tool, but it seems to me that I
read in DWN that it was orphaned not too long ago.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
