base-files 3.0.13 introduced the /media directory (new installs only), and 3.0.15 stopped creating the /cdrom and /floppy directories for new installes. The installer still sets up a fstab with /cdrom and /floppy, and creates those directories. Wanting to follow base-file's lead, I looked at converting the installer to use /media, but it seems difficult. /cdrom is hardcoded all over, in d-i, in base-config, in apt-cdrom, probably in a number of things such as desktop environments, and in many documents. This doesn't feel like an item for sarge, but it will be sorta strange if sarge has both /cdrom and /media/cdrom and entries in fstab for both that use the same device. Would it be sane to have /cdrom and /floppy be symlinks into /media in sarge? Mount will follow a symlink, so I think that programs like apt-cdrom, that may try to mount /cdrom, will continue to work. There's also the question of how we can possibly safely change programs like apt-cdrom to use /media/cdrom by default. Since upgraded systems are not getting a /media created at all, and will have fstab entries for /cdrom, any behavior change in apt-cdrom would break it on those systems. Will we leave this up to the admins to sort out, will we fix up their fstab and create the mount points on upgrade, or should programs that once mounted /cdrom be changed to try both mount points? -- see shy jo
Attachment:
signature.asc
Description: Digital signature