#4211 closed bug (invalid)
"Disable user add-ons" doesn't disable UserBootscript
| Reported by: | humdinger | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/Boot Loader | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This is hrev32189.
When checking "Disable user add-ons" from the safe mode options of the boot screen, the ~/config/UserBootscript will still be started.
Change History (3)
comment:1 by , 15 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 15 years ago
Are you sure BeOS behaved the same way?
I think it's useful to be able to disable any user specific changes of the system in case Mr. User messed things up accidentally. Be it by installing a misbehaving add-on or by modifying the UserBootscript in a way that prevents normal bootup. (Annecdote: I recently very smartly put a "shutdown -r" in there to have the system continually restart for a while for testing. That's how I found out that "Disable user add-ons" doesn't do what I assumed... :).
Using Safe Mode to boot into a full screen bash is not a nice solution for a lost user.
comment:3 by , 15 years ago
The current Safe Mode will go away. I think that should be done even before releasing the alpha, actually.
Because that option isn't supposed to affect UserBootscript. All it does (and is intended to do) is disable loading anything in ~/config/add-ons. If you want UserBootscript to be ignored, then you should be picking safe mode.