Opened 18 years ago
Closed 18 years ago
#1649 closed defect (wontfix)
Document steps needed to resume process after rebooting
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Book | Version: | SVN |
| Severity: | minor | Keywords: | |
| Cc: |
Description
On IRC, many newcomers interrupt the build and then try to resume it. They don't re-mount filesystems and don't re-populate /dev until someone tells them to do so. Steps needed in order to resume the build after the reboot must be documented in the book (separately for Chapters 5 and 6).
BTW the current /dev population steps are too complex. I propose to drop mounting tmpfs on /dev from Section "6.8. Populating /dev" and instead to create all devices, directories and symlinks listed there in the real /dev, as static nodes. Then, when making the system bootable (Section 8.4), run the udev initscript. This change will minimize the time when tmpfs is mounted on /dev, and decrease the number of steps needed to resume the build.
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
I think those people should seriously reconsider their current abilities before attempting LFS. We specify exactly how to setup the environment. If someone cannot go back and re-read that section, then I would consider that a problem for the reader, not the book. Also, adding static device nodes would only add to the confusion of the /dev tree, IMO. Marking this bug as WONTFIX. If this issue needs more discussion, please use lfs-dev so more people see it.
Please ignore this bug for the purpose of releasing LFS-6.1.1