topic title: FamErrlist
Posts: 2
cliffgecko
Joined: 29 Apr 2009
#1
I tried antiX-M8 in VertualBox, setting Ram at 64 mb. (I intend to put it in old laptop.) The installation halted. The last line is

/usr/sbin/lighttpd: Symbol 'FamErrlist' has different size in shared object, consider re-linking

I'm completely newbie. Please help me what to do. Thanks

Cliff
Posts: 21
ZenMystic
Joined: 22 Apr 2009
#2
I'm not in a position to help with that error, but I think you need more memory to install. Don't forget about the swap partition
Posts: 316
DJiNN
Joined: 26 Oct 2007
#3
cliffgecko wrote:I tried antiX-M8 in VertualBox, setting Ram at 64 mb. (I intend to put it in old laptop.) The installation halted. The last line is

/usr/sbin/lighttpd: Symbol 'FamErrlist' has different size in shared object, consider re-linking
I'm completely newbie. Please help me what to do. Thanks
Cliff
I've also had the same errors here using antiX 8 in VirtualBox (With a RAM setting of 256mb) so i don't think it's anything to do with the RAM setting (although that's just a guess). I did get antiX to run, even after that error. Try is with 128mb ram and see if there's any difference?

Does antiX actually run in VB after the install has finished? 64mb is very low, but i'm not sure what the minimum requirements are for antiX 8.

DJiNN
Posts: 2
cliffgecko
Joined: 29 Apr 2009
#4
Thank ZenMystic and DJiNN. The minimum RAM requirement is 64 mb. That is why I need antiX -- I've got only 64mb in the old laptop. The system halted at the error always, but there are two times that it got through and struck at somewhere else. I'll create a swap partition with debian cd and give it another try.
Posts: 21
ZenMystic
Joined: 22 Apr 2009
#5
Hi cliff
just another couple of thoughts: if you're installing from a physical cdr, you could try using the .iso image. Did you check the md5sum to verify the download? Did you verify the burn and use a speed less than maximum?
Posts: 516
oldhoghead
Site Admin
Joined: 01 Oct 2007
#6
That error message can be ignored, have you tried any of the cheat codes to get it to boot? when you boot the livecd, scroll to the antiX Extra Options and try the available options there.

cheers,
olhoghead
Posts: 1,520
eriefisher
Joined: 07 Oct 2007
#7
The error message should have nothing to do with the boot failure. It's more likely that it's a bad burn or down load. I would reburn at the slowest speed possible or if using VB just boot directly from the iso as mentioned earlier.

Lighttpd is a light weight web server. I thought anti had removed it from the iso. It's actually a very good app.
Posts: 1,228
secipolla
Joined: 15 Jun 2008
#8
Antix will have much more trouble in VirtualBox than in real hardware. Specially because it's installation process is not that light (although after installed it'll run with few resources).
My Antix-8 system runs with 55-60 MB RAM idle (forget using Iceweasel then). I'm not a geek, so I use its default configuration.
SliTaz runs with 45-50 MB idle and is a 'snap' to install (the ISO is just 30 MB), just in case you have trouble with Antix. It loads the whole system to RAM in live-cd mode, though, so maybe you should boot with some code for it to run from the cd-rom.
Puppy Linux has a so called 'derivative' (Turbopup - alpha3a) that runs with 20/43 MB RAM idle/Seamonkey (this is lightweight!).
Antix base.iso (deep purple!) runs with 25/50 MB idle/Iceweasel in a VirtualBox machine here.

All of them are, in a certain sense, complete operating systems.
Posts: 1,228
secipolla
Joined: 15 Jun 2008
#9
cliffgecko wrote:I tried antiX-M8 in VertualBox, setting Ram at 64 mb. (I intend to put it in old laptop.) The installation halted. The last line is

/usr/sbin/lighttpd: Symbol 'FamErrlist' has different size in shared object, consider re-linking

I'm completely newbie. Please help me what to do. Thanks

Cliff
This line appears normally at boot time, only it boots very much slower in VirtualBox (so one would have to wait). And 64 MB is a struggle for it to install.

Besides that, while installing, if you let it go, after a while it returns to the host system and the screen looks like it's frozen. Just click at it to update.

I've installed the base.iso (with 256 MB) and I found that it's somewhat sluggish even using so few RAM. It may have something to do with VirtualBox 2.1.4 somewhat poor support for it (I used 'Linux 2.6' option - don't know if choosing 'Debian' would change anything). It seems the new VB 2.2 has better video support for Linux, but I haven't tried it.