#380 closed defect (wontfix)
bug in the install instructions of ch6-glibc
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | highest | Milestone: | |
| Component: | Book | Version: | 2.4.4 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
glibc-2.2.5 finds pwd in /static/bin - we shouldnt delete /bin/pwd after installing the kernel headers i dont know if the current behaviour will cause a problem but its trivail to fix this one ;-)
Change History (3)
comment:1 by , 22 years ago
comment:2 by , 22 years ago
| Priority: | normal → highest |
|---|
from what i read and heard after last comment it doesn't seem to be an issue other than maybe cosmetic. Let's have a close look at it, but I doubt this is going to be an issue. Expect this bug to be WONTFIX'ed soon.
comment:3 by , 22 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Closing this bug. The use of /static/bin/pwd over /bin/pwd does not harm Glibc installation.
Note:
See TracTickets
for help on using tickets.
Is it a problem that it finds /static/pwd and uses it during the installation? I guess the question is: will c library files ever use the program /static/pwd directly? I'd say the c library would just call a C routine to figure out the current working directly, much like pwd would do it.