GUIs for system preservation

Registered by John Bradley Bulsterbaum on 2007-12-01

Okay,

So the average user might get quickly fed-up with the forced filesystem check at boot-up because of (maybe) a few darn erros in a partition that Linux isn't even allowed to use. When I first ventured into Ubuntu my hacker/programmer buddy had to tell me that I needed to optimize start-up in config files for faster boot-times...because start-up took forever doing what seemed like EVERYTHING.

However if someone is told to go into config files to do these kinds of things...odds aren't bad they're going to break something even if the "help" is followed all the way through: the "help" may be a knowledgeable linux user, but they're probably not the ones who know this system through-and-through (the programmers themselves).

ANYTHING that needs editing to a config file needs a gui: starting with high-frequency use and then considering essentials that people will quickly notice (like start-up). In Windows when one uses a gui, odds are we won't be able to break anything (the exception is the display, but this has a keep/return-to-last dialogue just as Ubuntu does). Start-up optimization is a perfect example, and such dialogues could give recommendations. For instance, "fschk every 3 or 4 boots", "fschk [option] after crashes"; include options like "DON'T synchronize the [@#$] clock before log-in", "DON'T start firestarte UNTIL LOG-IN" (because of the number of permissions problems). (Heck, why is the system allowed to connect to the internet without some kind of logging-in anyways?)

Newbs and windows-users should be polled, NOT terminal-users for what they want and then go from there, (since terminal-junkies don't care about GUIs presence and just use the terminal anyways).

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.