Opened 18 years ago
Closed 18 years ago
#2176 closed defect (fixed)
xfs uuid link
| Reported by: | Eric Hobbs | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.2.0 |
| Component: | BOOK | Version: | SVN |
| Severity: | normal | Keywords: | xfs uuid |
| Cc: | patrakov@… |
Description
The link for uuid on the xfs page links to a php extension which requres that libuuid be installed.
Change History (4)
comment:1 by , 18 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:2 by , 18 years ago
No, I didn't issue the warning about libuuid. I came up with a different warning for LFS: "install e2fsprogs even if you don't use ext2/ext3 filesystems, because of the generic fsck program that is called by the boot scripts".
comment:3 by , 18 years ago
It was a while ago now, but I must have misinterpreted you at the time. I don't really know if we need that warning in the book. E2fsprogs is a more specific package than most of the other LFS packages, but the bottom line is that we expect that people have followed LFS. We don't say "If you installed Readline,..." or anything else.
The old bug is #1777.
I'm about to just remove the note because I can't even find an alternative UUID. Please comment if you don't agree.
comment:4 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
No comments = everyone agrees or no one cares. The note is gone. If you don't have e2fsprogs, you didn't follow LFS. Removed in r6344.
Thanks, EricTHobbs.
Sorry about that broken link. It seemed right at the time, but I never really investigated.
Looking around now, it seems that the only libuuid I can find comes from e2fsprogs. Even on Solaris and *BSD. I think the whole note should be removed. Thoughts? Alexander, I think you came up with this warning some time ago.