I''ve had minor luck with the fonts. Gaim fonts are ok now, but Mozilla fonts are, well, screwed up. All the text looks like DOS text. I did an "export GDK_USE_XFT=0" and that did it.

I guess I may just give up and use AA fonts like i did in Mandrake, but I don''t like them. I like clear, sharp, although sometimes blocky unAA fonts.

Uh oh, I think I broke something. Now whenever I try to apt-get anything it says this:

E: Dynamic MMap ran out of room
E: Error occured while processing libeel2-2 (NewFileVer1)
E: Problem with MergeList /var/lib/dpkg/status
E: The package lists or status file could not me parsed or opened

What have I done?

The last things I did with apt-get were this and then I added the non-free thingy to my list file.

Wait, I just removed the non-free thingy from the sources list and now it's working! Is there a limit to the number of sources you can have or something?

How does Debian Unstable work? Do packages get put into it when it's the final release version? Like Mandrake and others tend to get prerelease versions of stuff and stick them in their distro as the final version. Does Debian do that, or do they wait until, for instance, Mozilla 1.3 Final comes out before they .deb it all up and stick it in their archives?

[edited by - BradDaBug on June 28, 2003 11:50:16 AM]

Adjust your APT::Cache-Limit in apt.conf.

man apt.conf
man apt-cache

.zfod

[edited by - zfod on June 28, 2003 1:11:43 PM]

I can''t seem to get the nvidia drivers to work. modprobe nvidia says nothing, but when I first did it it gave the usual not GPL warning and stuff. The X server appears to be crashing during startup. The log file just stops, no warning or error or anything but the console where you run it says it crashed.

And I''m not sure, but I think I screwed up LILO. It freezes. It looks something like this:

Booting from CDROM...
LI

btw, it always says "booting from CDROM." i guess it should read "checking for bootable CDrom", but that''s just the way my bios is.

The LI thing is what I got on my old 486 whenever I did something to update the kernel. Run lilo again (use a rescue floppy/cd, chroot into your normal system, make sure you''re root, and type "/sbin/lilo".)

If lilo objects, you might have to modify lilo.conf so that it points to a valid kernel (probably won''t have to do this).

See the other thread up right now about booting for a more detailed explanation of why this happens.