Bug 63471 - Please add a "quit" command to the e2fsck interactive mode
Summary: Please add a "quit" command to the e2fsck interactive mode
Status: CLOSED MOVED
Alias: None
Product: File System
Classification: Unclassified
Component: ext4 (show other bugs)
Hardware: All Linux
: P1 enhancement
Assignee: fs_ext4@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-22 07:16 UTC by unforgettableid
Modified: 2021-02-09 20:56 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.11.6
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description unforgettableid 2013-10-22 07:16:05 UTC 
Some users don't know whether or not it is safe to exit e2fsck using Ctrl+C.

It would be great if you could please add a "quit" command to the e2fsck interactive mode. The "quit" command should quit e2fsck, leaving users confident that they didn't cause any extra damage to the filesystem by quitting early.
Comment 1 unforgettableid 2013-10-23 02:07:23 UTC 
Actually, please call the command "Quit Safely".
Comment 2 unforgettableid 2013-10-31 01:11:42 UTC 
"Quit Safely" would be helpful for e2fsck newbies who want to halt the machine, go to bed, and hire an expert the next day.

"Quit Safely" would also be helpful to e2fsck newbies who want to use a console-mode Web browser or IRC client to get help.

"Quit Safely" would also be helpful to e2fsck newbies who:
* accidentally started the tool in fully-interactive mode
* but realize they should have used -y ("Yes to All") mode.
Those users could simply choose "Quit Safely" then rerun e2fsck with the -y option.
Comment 3 Alan 2013-11-13 12:08:03 UTC 
e2fsck is userspace not kernel.
Comment 4 unforgettableid 2021-02-09 20:56:12 UTC 
My mistake.  Resubmitted at:  https://github.com/tytso/e2fsprogs/issues/59

I appreciate your comment.  Also, I thank you for all your kernel-related work!
Note You need to log in before you can comment on or make changes to this bug.