| Summary: | ld -lF bug | ||
|---|---|---|---|
| Product: | Base System | Reporter: | alex <alex> |
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 5.0-CURRENT | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
alex
2000-04-11 12:10:02 UTC
Thus spake Anatoly Vorobey (mellon@pobox.com): > > ls -lF adds two slashes at the end of a directory: > I don't know that this is a bug. '/' is the name of the "file", > and the other '/' is the mode char. To "fix" this, one would have > to special-case the root directory. No. It's not a special case. it's a bug: alex:~ $ ls -ldF Mail drwx------ 8 alex alex 512 11 Apr 12:32 Mail/ alex:~ $ ls -ldF Mail/ drwx------ 8 alex alex 512 11 Apr 12:32 Mail// Alex -- I need a new ~/.sig. State Changed From-To: open->closed I can't find another UNIX flavour that _doesn't_ show the root directory (/) as "//" when asked to list it with a type indicator (also /). This isn't a bug at all. Have a look at the manual page for ls(1), particularly its description of the -F flag. |