Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 127146 - "chroot" can not work. :(
"chroot" can not work. :(
Status: CLOSED DUPLICATE of bug 121351
Product: Fedora
Classification: Fedora
Component: coreutils (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2004-07-02 13:09 EDT by Lee Shih-Yuan
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:04:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lee Shih-Yuan 2004-07-02 13:09:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; zh-TW; rv:1.6) Gecko/20040122

Description of problem:
Fedora Core 2
# chroot /mnt/hda7 /bin/bash
Inconsistency detected by ld.so: rtld.c: 1192: dl_main: Assertion
`(void *) ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
# rpm -qf /usr/sbin/chroot
# uname -a
Linux localhost.localdomain 2.6.6-1.435 #1 Mon Jun 14 09:09:07 EDT
2004 i686 i686 i386 GNU/Linux

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.mount /dev/hda7 /mnt/hda7
2.chroot /mnt/hda7 /bin/bash
3.then fails. :(

Additional info:
Comment 1 Tim Waugh 2004-07-02 16:42:54 EDT
You need to boot with vdso=0 to work around this glibc bug.

*** This bug has been marked as a duplicate of 121351 ***
Comment 2 Lee Shih-Yuan 2004-07-03 04:41:56 EDT
I add vdso=0 to boot fedora core 2 ...

This time it appears "Segmentation fault". XD
Comment 3 Tim Waugh 2004-07-03 05:39:15 EDT
This is not a coreutils problem, but an already-reported glibc bug.

*** This bug has been marked as a duplicate of 121351 ***
Comment 4 Red Hat Bugzilla 2006-02-21 14:04:19 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.