Re: [opensuse-factory] About ext3 as default and periodic fs checks
On Mon, 2006-10-30 at 16:53 +0100, Rasmus Plewe wrote:
On Mon, Oct 30, 2006 at 05:41:29PM +0200, Silviu Marin-Caea wrote:
The periodic ext3 fs checks at boot are driving me nuts. I know they can be disabled.
Couldn't they be performed at shutdown instead of boot? [...] These would be the steps, from boot:
0. boot 1. is fs dirty? then fsck and prompt user how to fix errors [...] This way, the user would never have to wait at boot, and the filesystem would still be checked periodically.
No.
What do you think?
I would prefer the following: If a fsck at boot time occurs - kill the splash screen (usually the computer boots in 3 minutes, now it's still unchanged after 10 minutes. Something must be broken. Poweroff/on. Does still not boot. Damn Linux, doesn't work. Changing OS because Linux doesn't work for me). - present an option "you can interrupt the current fsck by pressing ESC. This means the fsck is repeated upon next boot." - As user, I know what will happen next time I boot and prepare for it.
If you trust hardware and file systems, you might want to present an easy option to the user to disable those checks alltogether. I wouldn't recommend that.
That's why trying to ape Windoze is often not such a good idea, yes the
splash screens are pretty but when fsck kicks in the scenario becomes
different, even Windoze says that there was a problem and shows it's
checking system in all it's character glory. I found someone locked in
the "nothing happening/power switch" circle. He'd installed the system
with a multisync screen and now the lower quality screen that was
connected was turning itself off because it couldn't handle the
resolution.
--
Dave Cotton
On Mon, 2006-10-30 at 17:08 +0100, Dave Cotton wrote:
On Mon, 2006-10-30 at 16:53 +0100, Rasmus Plewe wrote:
On Mon, Oct 30, 2006 at 05:41:29PM +0200, Silviu Marin-Caea wrote:
The periodic ext3 fs checks at boot are driving me nuts. I know they can be disabled.
Couldn't they be performed at shutdown instead of boot? [...] These would be the steps, from boot:
0. boot 1. is fs dirty? then fsck and prompt user how to fix errors [...] This way, the user would never have to wait at boot, and the filesystem would still be checked periodically.
No.
What do you think?
I would prefer the following: If a fsck at boot time occurs - kill the splash screen (usually the computer boots in 3 minutes, now it's still unchanged after 10 minutes. Something must be broken. Poweroff/on. Does still not boot. Damn Linux, doesn't work. Changing OS because Linux doesn't work for me). - present an option "you can interrupt the current fsck by pressing ESC. This means the fsck is repeated upon next boot." - As user, I know what will happen next time I boot and prepare for it.
If you trust hardware and file systems, you might want to present an easy option to the user to disable those checks alltogether. I wouldn't recommend that.
That's why trying to ape Windoze is often not such a good idea, yes the splash screens are pretty but when fsck kicks in the scenario becomes different, even Windoze says that there was a problem and shows it's checking system in all it's character glory. I found someone locked in the "nothing happening/power switch" circle. He'd installed the system with a multisync screen and now the lower quality screen that was connected was turning itself off because it couldn't handle the resolution.
As the splash screen says, press ESC for more info. When an fsck is happening during a boot, doing this tells what is going on. Of course, it is in geekese. But it does also say that it is checking the file system, and there is a progress bar and a spinning doodad. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Mon, 2006-10-30 at 18:53 +0100, Roger Oberholtzer wrote:
As the splash screen says, press ESC for more info. When an fsck is happening during a boot, doing this tells what is going on. Of course, it is in geekese. But it does also say that it is checking the file system, and there is a progress bar and a spinning doodad.
You missed the point completely.
Windoze does this itself, the average Fred then knows something is
actually happening, even if they have no idea what it means. The machine
does not appear to be locked up.
--
Dave Cotton
On Mon, 2006-10-30 at 22:07 +0100, Dave Cotton wrote:
On Mon, 2006-10-30 at 18:53 +0100, Roger Oberholtzer wrote:
As the splash screen says, press ESC for more info. When an fsck is happening during a boot, doing this tells what is going on. Of course, it is in geekese. But it does also say that it is checking the file system, and there is a progress bar and a spinning doodad.
You missed the point completely.
Windoze does this itself, the average Fred then knows something is actually happening, even if they have no idea what it means. The machine does not appear to be locked up.
I'm not sure I did miss the point. I would rather say that when windows (or any OS for that matter) boots, many things happen that can fail. Some are fatal errors, some are warnings. In Windows (95/98/XP) all I get to see are the ones someone decided should be called to my attention. It lacks the esc of the SUSE boot theme to let me see more. I see the lack to be on the part of the windows boot. If a computer seems to be stuck, and the screen says to press esc for more info, what is the problem? It is the only text on the screen. No clutter or menu to navigate. I guess you could disable the boot theme to be text, so the fsck is shown without expecting the user to bother reading and pressing a key when the boot is not done fast enough. I'm not looking for an argument. But I do not think the SUSE boot theme is so user unfriendly. -- Roger Oberholtzer
On Mon, 2006-10-30 at 22:07 +0100, Dave Cotton wrote:
On Mon, 2006-10-30 at 18:53 +0100, Roger Oberholtzer wrote:
As the splash screen says, press ESC for more info. When an fsck is happening during a boot, doing this tells what is going on. Of course, it is in geekese. But it does also say that it is checking the file system, and there is a progress bar and a spinning doodad.
You missed the point completely.
Windoze does this itself, the average Fred then knows something is actually happening, even if they have no idea what it means. The machine does not appear to be locked up.
I'm not sure I did miss the point. I would rather say that when windows (or any OS for that matter) boots, many things happen that can fail. Some are fatal errors, some are warnings. In Windows (95/98/XP) all I get to see are the ones someone decided should be called to my attention. It lacks the esc of the SUSE boot theme to let me see more. I see the lack to be on the part of the windows boot. If a computer seems to be stuck, and the screen says to press esc for more info, what is the problem? It is the only text on the screen. No clutter or menu to navigate. I guess you could disable the boot theme to be text, so the fsck is shown without expecting the user to bother reading and pressing a key when the boot is not done fast enough. I'm not looking for an argument. But I do not think the SUSE boot theme is so user unfriendly. -- Roger Oberholtzer
participants (2)
-
Dave Cotton -
Roger Oberholtzer