#183 closed defect (fixed)
/etc/mtab a symlink to /proc/mounts?
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | highest | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | normal | Keywords: | |
Cc: |
Description
perhaps make that link, it would make sense, and helps for good working of mounting and unmounting if / is read-only
Change History (12)
comment:1 by , 23 years ago
dependson: | → 184 |
---|
comment:2 by , 23 years ago
Resolution: | → later |
---|---|
Status: | new → closed |
comment:3 by , 23 years ago
Resolution: | later |
---|---|
Status: | closed → reopened |
comment:4 by , 23 years ago
comment:5 by , 23 years ago
Priority: | normal → highest |
---|
comment:6 by , 23 years ago
The /dev/root loss of information disappears with devfs, since /dev/root is made a symlink to your current root partition. I'd like to suggest to leave the mtab like it is now (although I've been using it myself for ages now). I don't know about the loopback devices, but we could deal with that later.
comment:7 by , 23 years ago
Shall we take this to lfs-dev for a discussion? If so, I'll post all the comments from here.
comment:8 by , 23 years ago
- Check if proc file system is enabled by default in the kernel
- Add a note to book if user doesn't want to use proc file system, don't use the
symlink
comment:9 by , 23 years ago
ok, I've checked. 2.4.16 definately has proc support enabled by default so we should be ok on that one. (I *think* it's been enabled by default for quite a while now)
comment:10 by , 23 years ago
Owner: | changed from | to
---|---|
Status: | reopened → assigned |
I've been doing this for ages and in general it works well.
I did see a report on LKML today however that when you do this, you lose some information; for example you see /dev/root in your mount output as opposed to (e.g.) /dev/hda1 for the / partition. You also lose some information when using loop devices. Do the advantages outweigh the disadvantages is the question..