From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 Description of problem: If the user chooses "linux reiserfs" as their arguments for starting the installation, selinux should default to 0 (as if they had typed "linux reiserfs selinux=0"). If you don't, they'll get through the installation thinking everything was okay, and then get struck by the fact that one of the most important packages - initscripts - failed to install (along with slocate) because the pre scriptlets failed. Other less critical errors will occur in installation of other packages. Reiserfs and selinux, until these bugs are fixed, should be viewed as incompatible. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Startup with "linux reiserfs" 2. Choose the defaults when asked about selinux (i.e., leave it on) 3. Try to boot Additional info:
reiserfs is completely unsupported.
Understood. However, it *is* an option, and it would seem that it would take just as much effort to remove it as an option (which you might as well if it doesn't work from a normal install) as it would to pass selinux=0 when reiserfs is chosen. Knowingly leaving broken options without even a notice is just bad form.
It's documented in fsset.py: # this is totally, 100% unsupported. Boot with "linux reiserfs" # at the boot: prompt will let you make new reiserfs filesystems # in the installer. Bugs filed when you use this will be closed # WONTFIX. However if you have time to make a patch that's more likely to be looked at.
Sure - here's my patch: change those lines in fsset.py to read: # this is totally, 100% unsupported. Boot with "linux reiserfs selinux=0" # at the boot: prompt will let you make a new reiserfs filesystem # in the installer. Bugs filed when you use this will be closed # WONTFIX Then it's documented.