#506 closed defect (invalid)
Consider using 'rootfs' in fstab rather than current / and specifying filesystem explicitly
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Book | Version: | CVS |
| Severity: | normal | Keywords: | |
| Cc: |
Description
By James Iwanek:
i mentioned a while back that you could put:
rootfs / rootfs defaults 1 1
Change History (4)
comment:1 by , 22 years ago
| Summary: | use 'rootfs' in fstab rather than current / and specifying filesystem explicitly → Consider using 'rootfs' in fstab rather than current / and specifying filesystem explicitly |
|---|
comment:2 by , 22 years ago
comment:3 by , 22 years ago
| Priority: | high → low |
|---|
comment:4 by , 21 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
While I don't doubt that one can put "rootfs" into fstab and have it work, there is no real advantage to doing so.
Research indicates this is an internal kernel thing. It is not documented any where. The mount soures contain 1 reference. The kernel sources have a few more. Closing.
Note:
See TracTickets
for help on using tickets.
after over 6 months of testing this ive noticed in my logs that the filesystem has never been checked - im looking for ways to make fsck actually check the filesystem, on a side note ext3 journal recovery does work though. im still certain that rootfs is the way forward ;-)