Message ID | 20221118154234.26067-1-robin.roevens@disroot.org |
---|---|
State | Accepted |
Commit | afd2a2a7b143ecf69bc7cda9b54199caadc4f7d4 |
Headers |
Return-Path: <development-bounces@lists.ipfire.org> Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4NDLf86PDnz3wgd for <patchwork@web04.haj.ipfire.org>; Fri, 18 Nov 2022 15:43:12 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4NDLf66rpLzyZ; Fri, 18 Nov 2022 15:43:10 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4NDLf65hdqz2xlg; Fri, 18 Nov 2022 15:43:10 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4NDLf56Fvcz2xKv for <development@lists.ipfire.org>; Fri, 18 Nov 2022 15:43:09 +0000 (UTC) Received: from knopi.disroot.org (knopi.disroot.org [178.21.23.139]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (Client did not present a certificate) by mail01.ipfire.org (Postfix) with ESMTPS id 4NDLf44nTszdn for <development@lists.ipfire.org>; Fri, 18 Nov 2022 15:43:08 +0000 (UTC) Authentication-Results: mail01.ipfire.org; dkim=pass header.d=disroot.org header.s=mail header.b=FonmizLG; dmarc=pass (policy=reject) header.from=disroot.org; spf=pass (mail01.ipfire.org: domain of robin.roevens@disroot.org designates 178.21.23.139 as permitted sender) smtp.mailfrom=robin.roevens@disroot.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=lists.ipfire.org; s=202003rsa; t=1668786188; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=lqh0XRgRQJbIFK8V+P+fVOTm9gaD4EZXaSBAj11nH4M=; b=MX6UnxCYr9ywlxu6hHs1jW/UlhpdyKlaVYckHPcYPzShNmpX+sCRgVolRmOWTRUNd/PKl5 5h2XTNYRhsI+Ho/Y7T6sbixJoKONJlAvI/C6/Vr/t6AWrodcgqH0rWrZ1oT8mcYmZZdp2z NuTDugn8q/kVhYQT5jtdnlbYYuuGYjBqFzCnCKKXj5K21PFWOJKdsiP0J8N0fZ98vINiD0 zXELMOWU3fYx46D0HJ3gQXOpUc2NvzJpGkk7g3VzDu78hNJP3S82hJC/UMMwosxuQT1WPl 5eMY720D96BZ02F8gqg1zgjFjf8Wpis6enPEZyp7OXhxvaBDTgZ3rP5gp1PH6w== ARC-Authentication-Results: i=1; mail01.ipfire.org; dkim=pass header.d=disroot.org header.s=mail header.b=FonmizLG; dmarc=pass (policy=reject) header.from=disroot.org; spf=pass (mail01.ipfire.org: domain of robin.roevens@disroot.org designates 178.21.23.139 as permitted sender) smtp.mailfrom=robin.roevens@disroot.org ARC-Seal: i=1; s=202003rsa; d=lists.ipfire.org; t=1668786188; a=rsa-sha256; cv=none; b=eRFYuibNrPNK63X3EMCVFWoKu1S/Bb3+Nb7IeKV70BbrNRGd6hrzLlW8V216q6R/aXUM7l scUz6dQsRLg3A+Od8b1j4D359xRXCyXWBzMKs1Ecb7lMygrSMY/AFZjrYtv+WsaQMhMuJA eS2hgD92l4HdgPAc6zK/dWH6ZSohv+5smsY0NYpk7jtUVZxDO2H5ietcUn8gzc6a0zH1gV d5i5tuqjl+PfirBcg0sQyNKZOVUD5wYTmjDd8VlnvUSg/L8nDAT2MKWeeDc3oFaWgRM7G4 PK+b+Cu4hE0oEe53TILNaMpCszsqgCNQxrfPj4w9j9f0tiJUQb0Vcsh2L+XPTg== Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 8F885410B0 for <development@lists.ipfire.org>; Fri, 18 Nov 2022 16:43:07 +0100 (CET) X-Virus-Scanned: SPAM Filter at disroot.org Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fkd-_VfFqWLw for <development@lists.ipfire.org>; Fri, 18 Nov 2022 16:43:06 +0100 (CET) Received: from chojin.sicho.home (amaterasu.sicho.home [192.168.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (no client certificate requested) (Authenticated sender) by hachiman (MailScanner Milter) with SMTP id C90CE84679; Fri, 18 Nov 2022 16:42:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1668786186; bh=ckxXQ8hfVXs7srPdhFwMI/uv9izkjLokdNT09e2e+s4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=FonmizLG/vvaIec3nUUq3+XCKFWUmcC8X4cuwZnIn1nZLq7QEKDxsHsKZ4hUxIua9 b0xjszKl3URFFTivYy/vJousdrL2aWhCJs/XmLxxoZHyGmSQFQoJ+sCVqkD+etGdbd w/sO05ebHpPjLpDSwXafhTEqospOzTEdfHmA6oxFK6DyPD5EHa+1pC4iPp5mxnbL7r czwmNKlJba2D/lcsEOTGriEZid7SUM4++CL1xg2mybA6iqsZR83N7dy5Ty+SY2k8Jk WVuUuIuXqO3SSjVua9hullfm9PPThnII7dVSweG1PRA5Ric9A3vupirze//jx2wahQ e7GSDl4wUFIjA== From: Robin Roevens <robin.roevens@disroot.org> To: development@lists.ipfire.org Subject: [PATCH] Rename misleading "check filesystem" reboot option NL translation Date: Fri, 18 Nov 2022 16:42:34 +0100 Message-Id: <20221118154234.26067-1-robin.roevens@disroot.org> In-Reply-To: <20221118104915.1320-1-hofmann@leo-andres.de> References: <20221118104915.1320-1-hofmann@leo-andres.de> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-sicho-MailScanner-ID: C90CE84679.A8A80 X-sicho-MailScanner: Found to be clean X-sicho-MailScanner-From: robin.roevens@disroot.org X-sicho-MailScanner-Watermark: 1669390981.56116@3omNtHbakxWPCs6kWDYBmg X-Spamd-Result: default: False [-5.67 / 11.00]; BAYES_HAM(-3.00)[99.99%]; R_DKIM_ALLOW(-1.42)[disroot.org:s=mail]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM(-1.00)[-0.999]; IP_REPUTATION_HAM(-1.00)[asn: 50673(-0.28), country: NL(-0.01), ip: 178.21.23.139(-0.71)]; SPF_REPUTATION_SPAM(0.76)[0.2543000359645]; DKIM_REPUTATION(-0.71)[-0.70754746212917]; R_MISSING_CHARSET(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[disroot.org,reject]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; MX_GOOD(-0.01)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:50673, ipnet:178.21.23.0/24, country:NL]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[disroot.org:+]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; PREVIOUSLY_DELIVERED(0.00)[development@lists.ipfire.org]; RCVD_COUNT_THREE(0.00)[4]; ARC_SIGNED(0.00)[lists.ipfire.org:s=202003rsa:i=1]; ARC_NA(0.00)[] X-Rspamd-Server: mail01.haj.ipfire.org X-Rspamd-Queue-Id: 4NDLf44nTszdn X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk <development.lists.ipfire.org> List-Unsubscribe: <https://lists.ipfire.org/mailman/options/development>, <mailto:development-request@lists.ipfire.org?subject=unsubscribe> List-Archive: <http://lists.ipfire.org/pipermail/development/> List-Post: <mailto:development@lists.ipfire.org> List-Help: <mailto:development-request@lists.ipfire.org?subject=help> List-Subscribe: <https://lists.ipfire.org/mailman/listinfo/development>, <mailto:development-request@lists.ipfire.org?subject=subscribe> Errors-To: development-bounces@lists.ipfire.org Sender: "Development" <development-bounces@lists.ipfire.org> |
Series |
Rename misleading "check filesystem" reboot option NL translation
|
|
Commit Message
Robin Roevens
Nov. 18, 2022, 3:42 p.m. UTC
Some users assume that "check filesystem" does more than just
trigger a simple "fsck" run. This patch changes the button label to avoid
confusion. - NL translation
Signed-off-by: Robin Roevens <robin.roevens@disroot.org>
---
langs/nl/cgi-bin/nl.pl | 1 +
1 file changed, 1 insertion(+)
Comments
I'm still confused by what a user might expect, OTHER than a fsck check? On 11/18/2022 10:42 AM, Robin Roevens wrote: > Some users assume that "check filesystem" does more than just > trigger a simple "fsck" run. This patch changes the button label to avoid > confusion. - NL translation > > Signed-off-by: Robin Roevens <robin.roevens@disroot.org> > --- > langs/nl/cgi-bin/nl.pl | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi-bin/nl.pl > index 4fd6955cc..ebac2754a 100644 > --- a/langs/nl/cgi-bin/nl.pl > +++ b/langs/nl/cgi-bin/nl.pl > @@ -1804,6 +1804,7 @@ > 'read list' => 'lijst met readonly hosts', > 'real address' => 'Echte adressen', > 'reboot' => 'Herstarten', > +'reboot fsck' => 'Herstart & start ‘fsck’', > 'reboot ask' => 'Herstarten?', > 'reboot question' => 'Extra vraag voor herstart en afsluiten', > 'reboot schedule' => 'Inplannen IPFire herstarts',
I can second this. Why is fsck more obvious then “file system check”? It is a more technical term which does not provide any more detail in my opinion. -Michael > On 18 Nov 2022, at 18:02, Tom Rymes <tom@rymes.net> wrote: > > I'm still confused by what a user might expect, OTHER than a fsck check? > > On 11/18/2022 10:42 AM, Robin Roevens wrote: >> Some users assume that "check filesystem" does more than just >> trigger a simple "fsck" run. This patch changes the button label to avoid >> confusion. - NL translation >> Signed-off-by: Robin Roevens <robin.roevens@disroot.org> >> --- >> langs/nl/cgi-bin/nl.pl | 1 + >> 1 file changed, 1 insertion(+) >> diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi-bin/nl.pl >> index 4fd6955cc..ebac2754a 100644 >> --- a/langs/nl/cgi-bin/nl.pl >> +++ b/langs/nl/cgi-bin/nl.pl >> @@ -1804,6 +1804,7 @@ >> 'read list' => 'lijst met readonly hosts', >> 'real address' => 'Echte adressen', >> 'reboot' => 'Herstarten', >> +'reboot fsck' => 'Herstart & start ‘fsck’', >> 'reboot ask' => 'Herstarten?', >> 'reboot question' => 'Extra vraag voor herstart en afsluiten', >> 'reboot schedule' => 'Inplannen IPFire herstarts',
Ok, this was probably a bad idea. So please ignore/remove this patch. Sorry for the noise. Am 19.11.2022 um 12:53 schrieb Michael Tremer: > I can second this. > > Why is fsck more obvious then “file system check”? > > It is a more technical term which does not provide any more detail in my opinion. > > -Michael > >> On 18 Nov 2022, at 18:02, Tom Rymes <tom@rymes.net> wrote: >> >> I'm still confused by what a user might expect, OTHER than a fsck check? >> >> On 11/18/2022 10:42 AM, Robin Roevens wrote: >>> Some users assume that "check filesystem" does more than just >>> trigger a simple "fsck" run. This patch changes the button label to avoid >>> confusion. - NL translation >>> Signed-off-by: Robin Roevens <robin.roevens@disroot.org> >>> --- >>> langs/nl/cgi-bin/nl.pl | 1 + >>> 1 file changed, 1 insertion(+) >>> diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi-bin/nl.pl >>> index 4fd6955cc..ebac2754a 100644 >>> --- a/langs/nl/cgi-bin/nl.pl >>> +++ b/langs/nl/cgi-bin/nl.pl >>> @@ -1804,6 +1804,7 @@ >>> 'read list' => 'lijst met readonly hosts', >>> 'real address' => 'Echte adressen', >>> 'reboot' => 'Herstarten', >>> +'reboot fsck' => 'Herstart & start ‘fsck’', >>> 'reboot ask' => 'Herstarten?', >>> 'reboot question' => 'Extra vraag voor herstart en afsluiten', >>> 'reboot schedule' => 'Inplannen IPFire herstarts',
This does raise the question of how a user would repair filesystem errors if this option only checks for errors and does not present the option to repair any issues found. Should the be an option to do that? Tom > On Nov 19, 2022, at 7:47 AM, Leo-Andres Hofmann <hofmann@leo-andres.de> wrote: > > Ok, this was probably a bad idea. So please ignore/remove this patch. Sorry for the noise. > >> Am 19.11.2022 um 12:53 schrieb Michael Tremer: >> I can second this. >> >> Why is fsck more obvious then “file system check”? >> >> It is a more technical term which does not provide any more detail in my opinion. >> >> -Michael >> >>>> On 18 Nov 2022, at 18:02, Tom Rymes <tom@rymes.net> wrote: >>> >>> I'm still confused by what a user might expect, OTHER than a fsck check? >>> >>> On 11/18/2022 10:42 AM, Robin Roevens wrote: >>>> Some users assume that "check filesystem" does more than just >>>> trigger a simple "fsck" run. This patch changes the button label to avoid >>>> confusion. - NL translation >>>> Signed-off-by: Robin Roevens <robin.roevens@disroot.org> >>>> --- >>>> langs/nl/cgi-bin/nl.pl | 1 + >>>> 1 file changed, 1 insertion(+) >>>> diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi-bin/nl.pl >>>> index 4fd6955cc..ebac2754a 100644 >>>> --- a/langs/nl/cgi-bin/nl.pl >>>> +++ b/langs/nl/cgi-bin/nl.pl >>>> @@ -1804,6 +1804,7 @@ >>>> 'read list' => 'lijst met readonly hosts', >>>> 'real address' => 'Echte adressen', >>>> 'reboot' => 'Herstarten', >>>> +'reboot fsck' => 'Herstart & start ‘fsck’', >>>> 'reboot ask' => 'Herstarten?', >>>> 'reboot question' => 'Extra vraag voor herstart en afsluiten', >>>> 'reboot schedule' => 'Inplannen IPFire herstarts',
On 19/11/2022 16:20, Tom Rymes wrote: > This does raise the question of how a user would repair filesystem errors if this option only checks for errors and does not present the option to repair any issues found. > > Should the be an option to do that? My view on that is that there should not be the option to repair. Repair of a filesystem in some automated fashion without looking at the specific errors involved and deciding the best way to fix them is more likely to result in worse damage than to make things better. If the filesystem involved is a journaling one and that doesn't fix things on a reboot then I believe some pretty severe corruption is likely to have occurred and the best thing is to re-install IPFire and do a restore and/or look at the smart data to see if the hard disk is on the way out rather than trying to fix the corrupted parts of the filesystem. It might be a good idea to put the above info into the wiki page so that people have some guidance on the recommended approach if they end up with errors from the fsck. Regards, Adolf. > Tom > >> On Nov 19, 2022, at 7:47 AM, Leo-Andres Hofmann <hofmann@leo-andres.de> wrote: >> >> Ok, this was probably a bad idea. So please ignore/remove this patch. Sorry for the noise. >> >>> Am 19.11.2022 um 12:53 schrieb Michael Tremer: >>> I can second this. >>> >>> Why is fsck more obvious then “file system check”? >>> >>> It is a more technical term which does not provide any more detail in my opinion. >>> >>> -Michael >>> >>>>> On 18 Nov 2022, at 18:02, Tom Rymes <tom@rymes.net> wrote: >>>> I'm still confused by what a user might expect, OTHER than a fsck check? >>>> >>>> On 11/18/2022 10:42 AM, Robin Roevens wrote: >>>>> Some users assume that "check filesystem" does more than just >>>>> trigger a simple "fsck" run. This patch changes the button label to avoid >>>>> confusion. - NL translation >>>>> Signed-off-by: Robin Roevens <robin.roevens@disroot.org> >>>>> --- >>>>> langs/nl/cgi-bin/nl.pl | 1 + >>>>> 1 file changed, 1 insertion(+) >>>>> diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi-bin/nl.pl >>>>> index 4fd6955cc..ebac2754a 100644 >>>>> --- a/langs/nl/cgi-bin/nl.pl >>>>> +++ b/langs/nl/cgi-bin/nl.pl >>>>> @@ -1804,6 +1804,7 @@ >>>>> 'read list' => 'lijst met readonly hosts', >>>>> 'real address' => 'Echte adressen', >>>>> 'reboot' => 'Herstarten', >>>>> +'reboot fsck' => 'Herstart & start ‘fsck’', >>>>> 'reboot ask' => 'Herstarten?', >>>>> 'reboot question' => 'Extra vraag voor herstart en afsluiten', >>>>> 'reboot schedule' => 'Inplannen IPFire herstarts',
Oh, I overlooked this email. It sums up very well how I see this :) Great write. -Michael > On 19 Nov 2022, at 16:59, Adolf Belka <adolf.belka@ipfire.org> wrote: > > > > On 19/11/2022 16:20, Tom Rymes wrote: >> This does raise the question of how a user would repair filesystem errors if this option only checks for errors and does not present the option to repair any issues found. >> >> Should the be an option to do that? > My view on that is that there should not be the option to repair. > > Repair of a filesystem in some automated fashion without looking at the specific errors involved and deciding the best way to fix them is more likely to result in worse damage than to make things better. > > If the filesystem involved is a journaling one and that doesn't fix things on a reboot then I believe some pretty severe corruption is likely to have occurred and the best thing is to re-install IPFire and do a restore and/or look at the smart data to see if the hard disk is on the way out rather than trying to fix the corrupted parts of the filesystem. > > It might be a good idea to put the above info into the wiki page so that people have some guidance on the recommended approach if they end up with errors from the fsck. > > Regards, > > Adolf. >> Tom >> >>> On Nov 19, 2022, at 7:47 AM, Leo-Andres Hofmann <hofmann@leo-andres.de> wrote: >>> >>> Ok, this was probably a bad idea. So please ignore/remove this patch. Sorry for the noise. >>> >>>> Am 19.11.2022 um 12:53 schrieb Michael Tremer: >>>> I can second this. >>>> >>>> Why is fsck more obvious then “file system check”? >>>> >>>> It is a more technical term which does not provide any more detail in my opinion. >>>> >>>> -Michael >>>> >>>>>> On 18 Nov 2022, at 18:02, Tom Rymes <tom@rymes.net> wrote: >>>>> I'm still confused by what a user might expect, OTHER than a fsck check? >>>>> >>>>> On 11/18/2022 10:42 AM, Robin Roevens wrote: >>>>>> Some users assume that "check filesystem" does more than just >>>>>> trigger a simple "fsck" run. This patch changes the button label to avoid >>>>>> confusion. - NL translation >>>>>> Signed-off-by: Robin Roevens <robin.roevens@disroot.org> >>>>>> --- >>>>>> langs/nl/cgi-bin/nl.pl | 1 + >>>>>> 1 file changed, 1 insertion(+) >>>>>> diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi-bin/nl.pl >>>>>> index 4fd6955cc..ebac2754a 100644 >>>>>> --- a/langs/nl/cgi-bin/nl.pl >>>>>> +++ b/langs/nl/cgi-bin/nl.pl >>>>>> @@ -1804,6 +1804,7 @@ >>>>>> 'read list' => 'lijst met readonly hosts', >>>>>> 'real address' => 'Echte adressen', >>>>>> 'reboot' => 'Herstarten', >>>>>> +'reboot fsck' => 'Herstart & start ‘fsck’', >>>>>> 'reboot ask' => 'Herstarten?', >>>>>> 'reboot question' => 'Extra vraag voor herstart en afsluiten', >>>>>> 'reboot schedule' => 'Inplannen IPFire herstarts', > > -- > Sent from my laptop
I'm not sure.. since I have not yet had any ipfire fs inconsistencies. But if a user presses that button, on a headless system (like an ipfire appliance). How will he know if there where errors on the filesystem ?(except when the errors are so severe that the system won't boot any further) I assume it will be in the system logfiles.. But then currently we are (trying to) accommodate users that don't seem to understand "Reboot & check filesystem" as "run fsck during startup". Hence, if they press that button, they will probably assume to get some filesystem check report after it is done ? Or at least some alert somewhere if there where errors detected ? Considering this, I'm leaning towards the idea to just remove that button :-).. Or maybe the fsck result could be emailed to the user, or trigger a visible alert on de webui.. ? Robin Michael Tremer schreef op ma 21-11-2022 om 11:29 [+0000]: > Oh, I overlooked this email. > > It sums up very well how I see this :) Great write. > > -Michael > > > On 19 Nov 2022, at 16:59, Adolf Belka <adolf.belka@ipfire.org> > > wrote: > > > > > > > > On 19/11/2022 16:20, Tom Rymes wrote: > > > This does raise the question of how a user would repair > > > filesystem errors if this option only checks for errors and does > > > not present the option to repair any issues found. > > > > > > Should the be an option to do that? > > My view on that is that there should not be the option to repair. > > > > Repair of a filesystem in some automated fashion without looking at > > the specific errors involved and deciding the best way to fix them > > is more likely to result in worse damage than to make things > > better. > > > > If the filesystem involved is a journaling one and that doesn't fix > > things on a reboot then I believe some pretty severe corruption is > > likely to have occurred and the best thing is to re-install IPFire > > and do a restore and/or look at the smart data to see if the hard > > disk is on the way out rather than trying to fix the corrupted > > parts of the filesystem. > > > > It might be a good idea to put the above info into the wiki page so > > that people have some guidance on the recommended approach if they > > end up with errors from the fsck. > > > > Regards, > > > > Adolf. > > > Tom > > > > > > > On Nov 19, 2022, at 7:47 AM, Leo-Andres Hofmann > > > > <hofmann@leo-andres.de> wrote: > > > > > > > > Ok, this was probably a bad idea. So please ignore/remove this > > > > patch. Sorry for the noise. > > > > > > > > > Am 19.11.2022 um 12:53 schrieb Michael Tremer: > > > > > I can second this. > > > > > > > > > > Why is fsck more obvious then “file system check”? > > > > > > > > > > It is a more technical term which does not provide any more > > > > > detail in my opinion. > > > > > > > > > > -Michael > > > > > > > > > > > > On 18 Nov 2022, at 18:02, Tom Rymes <tom@rymes.net> > > > > > > > wrote: > > > > > > I'm still confused by what a user might expect, OTHER than > > > > > > a fsck check? > > > > > > > > > > > > On 11/18/2022 10:42 AM, Robin Roevens wrote: > > > > > > > Some users assume that "check filesystem" does more than > > > > > > > just > > > > > > > trigger a simple "fsck" run. This patch changes the > > > > > > > button label to avoid > > > > > > > confusion. - NL translation > > > > > > > Signed-off-by: Robin Roevens <robin.roevens@disroot.org> > > > > > > > --- > > > > > > > langs/nl/cgi-bin/nl.pl | 1 + > > > > > > > 1 file changed, 1 insertion(+) > > > > > > > diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi- > > > > > > > bin/nl.pl > > > > > > > index 4fd6955cc..ebac2754a 100644 > > > > > > > --- a/langs/nl/cgi-bin/nl.pl > > > > > > > +++ b/langs/nl/cgi-bin/nl.pl > > > > > > > @@ -1804,6 +1804,7 @@ > > > > > > > 'read list' => 'lijst met readonly hosts', > > > > > > > 'real address' => 'Echte adressen', > > > > > > > 'reboot' => 'Herstarten', > > > > > > > +'reboot fsck' => 'Herstart & start ‘fsck’', > > > > > > > 'reboot ask' => 'Herstarten?', > > > > > > > 'reboot question' => 'Extra vraag voor herstart en > > > > > > > afsluiten', > > > > > > > 'reboot schedule' => 'Inplannen IPFire herstarts', > > > > -- > > Sent from my laptop > > >
diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi-bin/nl.pl index 4fd6955cc..ebac2754a 100644 --- a/langs/nl/cgi-bin/nl.pl +++ b/langs/nl/cgi-bin/nl.pl @@ -1804,6 +1804,7 @@ 'read list' => 'lijst met readonly hosts', 'real address' => 'Echte adressen', 'reboot' => 'Herstarten', +'reboot fsck' => 'Herstart & start ‘fsck’', 'reboot ask' => 'Herstarten?', 'reboot question' => 'Extra vraag voor herstart en afsluiten', 'reboot schedule' => 'Inplannen IPFire herstarts',