amd64/122624: unusable mininal installation of FreeBSD-7.0

[Fernan Aguero]

The following reply was made to PR amd64/122624; it has been noted by GNATS.

From: Fernan Aguero <fernan at iib.unsam.edu.ar>
To: John Baldwin <jhb at freebsd.org>
Cc: freebsd-amd64 at freebsd.org, freebsd-gnats-submit at freebsd.org
Subject: Re: amd64/122624: unusable mininal installation of FreeBSD-7.0
Date: Fri, 18 Apr 2008 11:53:08 -0300

 > On Thursday 10 April 2008 02:44:11 pm Fernan Aguero wrote:
 > > > ld-elf.so.1 doesn't use anything from /usr/src.  The specific assert that 
 > is 
 > > > failing is this:
 > > > 
 > > >         assert(ELF_R_TYPE(rela->r_info) == R_X86_64_JMP_SLOT);
 > > > 
 > > > in reloc_plt() in src/libexec/rtld-elf/amd64/reloc.c.  
 > > 
 > > I wrote down that error on paper and typed it in the email
 > > ... but I'm sure it said /usr/src ... that's why I decided
 > > to set my /etc/fstab to mount freebsd-7.0 sources from another FreeBSD
 > > box and symlink /usr/src.
 > 
 > That's because the assert() macro puts the full filename of the current file 
 > into the binary when it is compiled for the error message.  The binary is not 
 > trying to read anything from /usr/src itse.f
 > 
 > > > I wonder if you somehow have 32-bit binaries instead of 64-bit?
 > > > 
 > > > -- 
 > > > John Baldwin
 > > 
 > > I wonder the same thing because after doing that, even
 > > though make was now OK (I was able to cd
 > > /usr/ports/sysutils/screen && make install), other commands
 > > failed (vi, Exec format error. Binary file not executable).
 > 
 > It certainly sounds like you have mixed and matched some things.  Maybe just 
 > do a minimal install but include the 'lib32' dist for 32-bit binary compat?  
 > minimal probably doesn't include it (but vi also should be a 64-bit binary, 
 > try using 'file' rather than brandelf to see what file thinks vi is).
 
 Sorry for the delay in replying,
 
 I have just did a new install (completely erasing and
 reformatting the disk) and this time I did a standard
 install, choosing developer + lib32. Now the box
 stops in the boot process attempting to mount root:
 
 [...]
 ad4: 152587 <WDC WD1600JS-75NCB3 10.02E04> at ata2-master UDMA33
 SMP: AP CPU #1 Launched!
 SMP: AP CPU #2 Launched!
 SMP: AP CPU #3 Launched!
 Trying to mount root from ufs:/dev/ad4s1a
 /libexec/ld-elf.so.1: /lib/libncurses.so.7: Shared object
 has no run-time symbol table
 Enter fill pathname of shell or RETURN for /bin/sh:
 
 I cannot even type RETURN and enter a shell, because the
 same message about libncurses.so.7 appears!
 
 Disk slicing/partitioning is as follows:
 1) ad4s1 (using whole disk), set bootable
 2) Install Boot Manager
 3) ad4s1b, 32G, swap
    ad4s1a, 1G, /
    ad4s1d, 1G, /tmp
    ad4s1e, 5G, /usr
    ad4s1f, 10G, /var
    ad4s1g, rest of disk, /home
 
 BTW, I don't understand what you mean by "It certainly
 sounds like you have mixed and matched some things" ... this
 is a new box, fresh, and I'm using the 7.0 ISO that I just
 downloaded from freebsd.org (cheksums are OK), and following
 a straightforward installation procedure.  I'm not trying to
 select any other package apart from those that are selected
 by choosing the options put forward by the installer
 (remember I started with a minimal install!). So in any
 case, if there's any 'mix and match' issue, it's an issue
 of mixed and matched packages included in the ISO image or a
 wrong combination of selections made by the installer ...
 
 BTW, I have just succesfully installed both
 ubuntu-7.10-amd64 (server edition) and FreeBSD-6.1-RELEASE
 (amd64) without any issues on the same box. In both cases, I
 was able to SSH in from another box and install third party
 packages (postgresql, screen, vim).
 
 To me this sounds like a problem with the 7.0-RELEASE CD
 and/or installer.
 
 Fernan